[Starlingx-discuss] Propose OpenStack/Apmec to StarlingX like an upstream component

Tung Doan doantungbk.203 at gmail.com
Mon Nov 5 20:21:06 UTC 2018

Hi Dean,

Thank you for your attention to this integration. I just gave you the
feedbacks. Please see inline.

Vào Th 5, 1 thg 11, 2018 vào lúc 18:16 Dean Troyer <dtroyer at gmail.com> đã

> On Thu, Nov 1, 2018 at 7:44 AM Tung Doan <doantungbk.203 at gmail.com> wrote:
> > I am Tung Doan - An OpenStack contributor and the PTL of OpenStack/Apmec
> project. Since we acknowledged the potential integration between Apmec and
> StarlingX, I am writing this email to propose adding OpenStack/Apmec to
> StarlingX like an upstream project.
> >
> > Project description: OpenStack Apmec [1] stands for the Automated
> Provisioning Framework for Multi-access Edge Computing which is the first
> orchestration and management framework dedicated to the MEC services in
> OpenStack. Below are some of the outstanding features of Apmec project:
> I believe Apmec is not an official OpenStack project (as listed in
> [0]), do you have plans to apply to become an official OpenStack
> project under TC governance?  (Until then you do need to be careful
> about referring to Apmec as 'an OpenStack project', it is hosted by
> OpenStack, but is not (yet?) an OpenStack project.)

Apmec is not official OpenStack but we planned to aplly to make it become
the official project as stated in [1].

> - no need to take care of the NFV functionalities. Since existing NFV
> MANO frameworks (Tacker, ONAP, OSM, OpenBaton,...) are diverse, integrating
> them can make StarlingX complicated. Apmec was designed to take over
> responsibility for integrating them since the delivery of MEC services is
> our critical mission.
> Is this replacing existing StarlingX functionality?

Our desire is to make Apmec become a "bridge" that helps StarlingX to
cooperate with different NFV MANO frameworks. Instead of managing various
APIs from the diffirent NFV MANO frameworks, StarlingX can offload them to

> >  - no need to take care of the life-cycle management of the MEC
> applications. Apmec offers API to help StarlingX perform this function.  As
> mentioned earlier, Apmec is OpenStack project, therefore, to provide
> low-latency for MEC applications,  Apmec is also planned to support
> acceleration technologies (e.g, integrated with OpenStack Cyborg) such as
> DPDK and FPGA.
> Can you get more specific about what the integration with StarlingX looks
> like?

Since Apmec is OpenStack repo, it has good chances to leverage different
OpenStack projects. When integrated with Starling, Apmec provides APIs that
help Starling manage the MEC applications which could be supported many
acceleration technologies. StarlingX does not need to take care of
low-layer design for such features. StarlingX only needs to describe the
requirements for the applications (Apmec provides tool to describe them
[2]), the rest will be taken care by Apmec.

> dt
> [0] https://governance.openstack.org/tc/reference/projects/index.html
> --
> Dean Troyer
> dtroyer at gmail.com

[1] https://review.openstack.org/#/c/612962/
[2] https://review.openstack.org/#/c/570797/

Name: Doan Van Tung
Email: van_tung.doan at mailbox.tu-dresden.de
A member of 5G Lab Germany
*Deutsche Telekom Chair of Communication Networks (ComNets)*

*Würzburger Str. 35, 01187 Dresden*

*TU Dresden, Germany*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181105/d1f0f69e/attachment-0001.html>

More information about the Starlingx-discuss mailing list