[openstack-dev] [meghdwar] use case for meghdwar API and Wednesday meeting

joehuang joehuang at huawei.com
Wed Sep 7 07:12:13 UTC 2016


For API to move cloudlets, I propose to design API which can talk directly from destination edge gateway to the source gateway, for example,  Pull( srcEdgeGateway, Cloudlet). Using pull will make the destination talk to the source directly, but not to introduce any broker or coordinator for the migration, otherwise all bits will flow to broker or coordinator first then to the destination, this kind of API will introduce latency, overhead, and bottleneck by the broker or coordinator.

Best Regards
Chaoyi Huang(joehuang)
________________________________
From: prakash RAMCHANDRAN [pramchan at yahoo.com]
Sent: 07 September 2016 13:55
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [meghdwar] use case for meghdwar API and Wednesday meeting

Hi all
You can edit the etherpad if you want to update agenda...or reply be email on item1-4 below.
https://etherpad.openstack.org/p/meghdwar

Would like to meet for discussions for BOF and agenda as we can not wait for 2nd Wednesday, so lets meet Wednesday
from 7-8am PDT (Wed 14:00-15:00 UTC) irc Channel : #openstack-meghdwar

Follow up on same points with updates  from last meeting.

1 Megdwar Gateway API discussions based on use case
Focus is what APIs needed for minimum use case of two cloudlets on two edges running 1 app each and how to move one of the apps from source edge gateway to destination edge gateway on compute nodes through those gateways.

APIs - required
Meghdwar service process will have configuration file for each cloudlet at the Edge gateway.
Dump (take Snapshot), Create , Read, List, Write, Start, Stop - Cloudlets

Reviewed other Catalog modules (application-catalog-ui, murano, murano-agent to be tested) on Rackspace
2. What other modules are needed in OpenStack 'meghdwar'
Catalog Refer Murano (May be we use it) - Our Catalog can be for ASP, CSP,NSP and integrated through ESP.



To discuss Binder option for two cloudlets. as for two cloudlets with one app in 1 above.

   c. Cloudlet Gateway Management  (Gateway Service Management)
   d. python  Cloudlet  / MEC Gateway Management

4. How do we go about priority
Consider two cloudlet Binders and see if we can use LXD and LXC ;live migration as 1st API implementation for Meghdwar.
LXD 2.0: Live migration [9/12] | Stéphane Graber's website<https://www.stgraber.org/2016/04/25/lxd-2-0-live-migration-912/>


Thanks
Prakash
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160907/cd2448cc/attachment.html>


More information about the OpenStack-dev mailing list