Andreas Jaeger a0855b6801 Remove publish-openstack-sphinx-docs
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
2018-10-24 20:11:17 +02:00
2018-08-31 06:52:53 -07:00
2018-10-17 03:03:00 -07:00
2018-08-31 06:52:53 -07:00
2018-06-08 12:22:10 -07:00
2018-05-07 13:25:56 +02:00
2018-05-07 13:25:56 +02:00
2018-05-07 13:25:56 +02:00
2018-05-07 13:25:56 +02:00
2018-10-23 17:01:12 -07:00
2018-10-17 03:03:00 -07:00
2018-05-07 13:25:56 +02:00
2018-08-31 06:52:53 -07:00
2018-05-07 13:25:56 +02:00
2018-05-07 13:25:56 +02:00
2018-06-10 16:03:14 +00:00

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.

Description
Edge orchestration service
Readme 1.2 MiB
Languages
Python 91.2%
Gettext Catalog 4.5%
Shell 3.6%
reStructuredText 0.6%
Mako 0.1%