Edge orchestration service
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
OpenDev Sysadmins c876490db4 OpenDev Migration Patch 3 years ago
apmec Refactor MEO's db 4 years ago
devstack Replace openstack.org git:// URLs with https:// 3 years ago
doc Replace openstack.org git:// URLs with https:// 3 years ago
etc Add MESO component that allows: 4 years ago
samples Refector samples 4 years ago
tools Add .gitreview file, zuul jobs, and refactoring code 4 years ago
.coveragerc Add .gitreview file, zuul jobs, and refactoring code 4 years ago
.gitignore Add .gitreview file, zuul jobs, and refactoring code 4 years ago
.gitreview OpenDev Migration Patch 3 years ago
.testr.conf Add .gitreview file, zuul jobs, and refactoring code 4 years ago
.zuul.yaml Remove publish-openstack-sphinx-docs 4 years ago
CONTRIBUTING.rst Update APMEC code 4 years ago
HACKING.rst Update APMEC code 4 years ago
LICENSE Update APMEC code 4 years ago
README.md Add photo for APMEC framework 4 years ago
README.rst Update APMEC code 4 years ago
TESTING.rst Update APMEC code 4 years ago
babel.cfg Update APMEC code 4 years ago
lower-constraints.txt Merge "Add tosca-paser packge and heat-translator to support MEC" 4 years ago
requirements.txt Add tosca-paser packge and heat-translator to support MEC 4 years ago
setup.cfg Change openstack-dev to openstack-discuss in setup.cfg 3 years ago
setup.py Update APMEC code 4 years ago
test-requirements.txt Add python-apmmecclient package 4 years ago
tox.ini Update min tox version to 2.0 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.

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.