<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yui_3_16_0_ym19_1_1473827401643_41401" dir="ltr">Hi all ? <br id="yui_3_16_0_ym19_1_1473827401643_41372"><br id="yui_3_16_0_ym19_1_1473827401643_41373">lets meet 7-8am PDT (Wed 14:00-15:00 UTC)irc Channel?: <br id="yui_3_16_0_ym19_1_1473827401643_41374">#openstack-meghdwar<br id="yui_3_16_0_ym19_1_1473827401643_41375"><br id="yui_3_16_0_ym19_1_1473827401643_41376">You can edit the etherpad if you want to update agenda...or reply be email on item1-5 below.<br id="yui_3_16_0_ym19_1_1473827401643_41377">https://etherpad.openstack.org/p/meghdwar<br id="yui_3_16_0_ym19_1_1473827401643_41378"><br id="yui_3_16_0_ym19_1_1473827401643_41379">1.a.Megdwar Gateway API discussions?<br id="yui_3_16_0_ym19_1_1473827401643_41380">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. refer latest Blueprint <br id="yui_3_16_0_ym19_1_1473827401643_41381">https://blueprints.launchpad.net/meghdwar/+spec/edge-cloud-gateway-api<br id="yui_3_16_0_ym19_1_1473827401643_41382"><br id="yui_3_16_0_ym19_1_1473827401643_41383">1.b.Would like to discuss Joes idea about (use pull not push)<br id="yui_3_16_0_ym19_1_1473827401643_41384">joehuang: 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.<br id="yui_3_16_0_ym19_1_1473827401643_41385"><br id="yui_3_16_0_ym19_1_1473827401643_41386">1.c Proposed by Narinder based on LXD live migration <br id="yui_3_16_0_ym19_1_1473827401643_41387">APIs - requires Meghdwar service process will have configuration file for each cloudlet at the Edge gateway.<br id="yui_3_16_0_ym19_1_1473827401643_41388">Dump (take Snapshot), Create , Read, List, Write, Start, Stop - Cloudlets<br id="yui_3_16_0_ym19_1_1473827401643_41389">Refer live migration using LXD<br id="yui_3_16_0_ym19_1_1473827401643_41390">https://www.stgraber.org/2016/04/25/lxd-2-0-live-migration-912/<br id="yui_3_16_0_ym19_1_1473827401643_41391"><br id="yui_3_16_0_ym19_1_1473827401643_41392">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. Reviewed other Catalog modules (application-catalog-ui, murano, murano-agent to be tested) on Rackspace<br id="yui_3_16_0_ym19_1_1473827401643_41393"><br id="yui_3_16_0_ym19_1_1473827401643_41394">To discuss Binder option for two cloudlets. as one app in 1(a,b,c) <br></div><div id="yui_3_16_0_ym19_1_1473827401643_43562" dir="ltr">Cloudlet Gateway Management (Gateway Service Management) <br id="yui_3_16_0_ym19_1_1473827401643_41395"> d. python Cloudlet / MEC Gateway Management ?<br id="yui_3_16_0_ym19_1_1473827401643_41396"><br id="yui_3_16_0_ym19_1_1473827401643_41397">4. How do we go about priority?<br id="yui_3_16_0_ym19_1_1473827401643_41398">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 in 1.c<br id="yui_3_16_0_ym19_1_1473827401643_41399"><br id="yui_3_16_0_ym19_1_1473827401643_41400">Thanks</div><div id="yui_3_16_0_ym19_1_1473827401643_43631" dir="ltr">Prakash<br></div></div></body></html>