Edge orchestration service
bff90fa0b1
- Apmec to collaborate with other orchestration frameworks (e.g, NFV framework) - for oprators to excecute smart placement decisions of MEC applications Change-Id: I28fe23029f11632f1909967238b9fd440aa6f936 |
||
---|---|---|
apmec | ||
devstack | ||
doc | ||
etc | ||
samples | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.md | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
TESTING.rst | ||
tox.ini |
apmec
This project aims at building an automated platform for Multi-access Edge Computing (MEC) based on OpenStack platform
The objective of APMEC is to:
-
manage the lifecycle of MEC applications including "create/update/delete"
-
monitor MEC application
-
scale in/out MEC applications
-
provide advanced features like live migration, state management, and acceleration
-
tightly integrate with OpenStack projects like Tacker (NFV Orchestration service)
Taxonomy:
MEP: MEC Platform
MEM: MEC Manager
MEO: MEC Orchestrator
MEA: MEC Application
MEAD: MEA Descriptor
Authors:
Deutsche Telekom Chair of Communication Networks,
Technical University of Dresden, Germany.