Correct Readme for APMEC

Change-Id: I5ef0347f1804bc84555e56bb13484ba7734933ad
Signed-off-by: Tung Doan <doantungbk.203@gmail.com>
This commit is contained in:
Tung Doan 2018-10-17 00:28:59 -07:00
parent bff90fa0b1
commit dd8198c905
2 changed files with 29 additions and 8 deletions

View File

@ -1,29 +1,50 @@
# apmec
This project aims at building an automated platform for Multi-access Edge Computing (MEC) based on OpenStack platform
This project aims at building an automated provisioning framework for Multi-access Edge Computing (MEC) based on OpenStack platform
The objective of APMEC is to:
.. figure:: doc/source/_extra/apmec.png
:alt: APMEC framework
- manage the lifecycle of MEC applications including "create/update/delete"
- monitor MEC application
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
- provide advanced features like live migration, state management, and acceleration
- tightly integrate with OpenStack projects like Tacker (NFV Orchestration service)
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
**Taxonomy**:
**Acronym**:
MEP: MEC Platform
MEM: MEC Manager
MESO: MEC Service Orchestrator
MES: MEC service
MEO: MEC Orchestrator
MEM: MEC Manager
MEA: MEC Application
MEAD: MEA Descriptor

BIN
doc/source/_extra/apmec.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 140 KiB