Edge orchestration service
Go to file
Zuul 5ae99cedac Merge "Update min tox version to 2.0" 2018-11-03 13:40:51 +00:00
apmec Refactor MEO's db 2018-10-30 03:59:15 -07:00
devstack Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
doc Refactor MEO's db 2018-10-30 03:59:15 -07:00
etc Add MESO component that allows: 2018-08-31 06:52:53 -07:00
samples Refector samples 2018-06-08 12:22:10 -07:00
tools Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
.coveragerc Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
.gitignore Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
.gitreview Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
.testr.conf Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
.zuul.yaml Remove publish-openstack-sphinx-docs 2018-10-24 20:11:17 +02:00
CONTRIBUTING.rst Update APMEC code 2018-05-07 13:25:56 +02:00
HACKING.rst Update APMEC code 2018-05-07 13:25:56 +02:00
LICENSE Update APMEC code 2018-05-07 13:25:56 +02:00
README.md Add photo for APMEC framework 2018-10-17 03:03:00 -07:00
README.rst Update APMEC code 2018-05-07 13:25:56 +02:00
TESTING.rst Update APMEC code 2018-05-07 13:25:56 +02:00
babel.cfg Update APMEC code 2018-05-07 13:25:56 +02:00
lower-constraints.txt Merge "Add tosca-paser packge and heat-translator to support MEC" 2018-10-26 16:48:19 +00:00
requirements.txt Add tosca-paser packge and heat-translator to support MEC 2018-10-26 05:34:40 -07:00
setup.cfg Add MESO component that allows: 2018-08-31 06:52:53 -07:00
setup.py Update APMEC code 2018-05-07 13:25:56 +02:00
test-requirements.txt Add python-apmmecclient package 2018-10-26 02:39:27 -07:00
tox.ini Update min tox version to 2.0 2018-11-03 07:09:16 +00:00

README.md

apmec

This project aims at building an automated provisioning framework for Multi-access Edge Computing (MEC) based on OpenStack platform.

alt text

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.