|
3 years ago | |
---|---|---|
apmec | 4 years ago | |
devstack | 3 years ago | |
doc | 3 years ago | |
etc | 4 years ago | |
samples | 4 years ago | |
tools | 4 years ago | |
.coveragerc | 4 years ago | |
.gitignore | 4 years ago | |
.gitreview | 3 years ago | |
.testr.conf | 4 years ago | |
.zuul.yaml | 4 years ago | |
CONTRIBUTING.rst | 4 years ago | |
HACKING.rst | 4 years ago | |
LICENSE | 4 years ago | |
README.md | 4 years ago | |
README.rst | 4 years ago | |
TESTING.rst | 4 years ago | |
babel.cfg | 4 years ago | |
lower-constraints.txt | 4 years ago | |
requirements.txt | 4 years ago | |
setup.cfg | 3 years ago | |
setup.py | 4 years ago | |
test-requirements.txt | 4 years ago | |
tox.ini | 4 years ago |
README.md
apmec
This project aims at building an automated provisioning framework for Multi-access Edge Computing (MEC) based on OpenStack platform.
Current features of APMEC are to:
-
orchestrate the MEC services
-
leverage MANO's API to allow the reuse of NF network services (currently use OpenStack Tacker - NFV Orchestration service) for MEC services
-
support multi-MANO features that offer the scalability and improve resource utilization of MEC services.
-
manage the life-cycle of MEC applications (creation, update, deletion)
-
monitor MEC applications
-
scale in/out MEC applications
On-going features:
-
fast live migration in order to support mobility in MEC
-
state management for the stateful MEC applications
-
acceleration technologies like DPDK, VPP, FPGA,...
-
container technologies like Docker/Kubernetes
Acronym:
MEP: MEC Platform
MESO: MEC Service Orchestrator
MES: MEC service
MEO: MEC Orchestrator
MEM: MEC Manager
MEA: MEC Application
MEAD: MEA Descriptor
Authors:
Deutsche Telekom Chair of Communication Networks,
Technical University of Dresden, Germany.