x/apmec
Code Issues Proposed changes
Edge orchestration service
7 Commits 1 Branch 0 Tags 1.2 MiB
Python 91.2%
Gettext Catalog 4.5%
Shell 3.6%
reStructuredText 0.6%
Mako 0.1%
3360c1b1fa
Go to file
Zuul 3360c1b1fa Merge "Replace port 35357 with 5000 for "auth_url""
2018-06-07 19:35:21 +00:00
apmec Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
devstack Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
doc Replace port 35357 with 5000 for "auth_url" 2018-06-07 23:07:04 +08:00
etc Update APMEC code 2018-05-07 13:25:56 +02:00
samples Update APMEC code 2018-05-07 13:25:56 +02: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
babel.cfg Update APMEC code 2018-05-07 13:25:56 +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 Update taxonomy 2018-06-07 11:39:44 -07:00
README.rst Update APMEC code 2018-05-07 13:25:56 +02:00
requirements.txt Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
setup.cfg Update APMEC code 2018-05-07 13:25:56 +02:00
setup.py Update APMEC code 2018-05-07 13:25:56 +02:00
test-requirements.txt Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00
TESTING.rst Update APMEC code 2018-05-07 13:25:56 +02:00
tox.ini Add .gitreview file, zuul jobs, and refactoring code 2018-05-30 14:16:53 -07:00

README.md

apmec

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

The objective of APMEC is to:

  • manage the lifecycle of MEC applications including "create/update/delete"

  • monitor MEC application

  • 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)

Taxonomy:

MEP: MEC Platform

MEM: MEC Manager

MEO: MEC Orchestrator

MEA: MEC Application

MEAD: MEA Descriptor

Authors:

Deutsche Telekom Chair of Communication Networks,

Technical University of Dresden, Germany.