a0855b6801
apmec is not an official repository and thus cannot publish to docs.o.o, see also https://docs.openstack.org/infra/openstack-zuul-jobs/project-templates.html#project_template-publish-openstack-docs-pti Change-Id: Id27dfc6bb5fb22dd6c86cc9ca9fa71f407faabaa |
||
|---|---|---|
| apmec | ||
| devstack | ||
| doc | ||
| etc | ||
| samples | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| .zuul.yaml | ||
| babel.cfg | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| lower-constraints.txt | ||
| 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 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.