- Edge-computing - lists.opendev.org

Berlin Summit CFP Closes in a Week
by Ildiko Vancsa 12 Jul '18

12 Jul '18

Hi everyone, The CFP deadline for the OpenStack Summit Berlin is less than one week away, so make sure to submit your talks <https://www.openstack.org/summit/berlin-2018/call-for-presentations/> before July 18th at 6:59am UTC (July 17 at 11:59pm PST). Tracks: • CI/CD • Container Infrastructure • Edge Computing • Hands on Workshops • HPC / GPU / AI • Open Source Community • Private & Hybrid Cloud • Public Cloud • Telecom & NFV SUBMIT HERE <https://www.openstack.org/summit/berlin-2018/call-for-presentations/> Community voting, the first step in building the Summit schedule, will open in mid July. Once community voting concludes, a Programming Committee for each Track will build the schedule. Programming Committees are made up of individuals from many different open source communities working in open infrastructure, in addition to people who have participated in the past. Read the full selection process here <https://www.openstack.org/summit/berlin-2018/call-for-presentations/selecti…>. Register for the Summit <https://www.eventbrite.com/e/openstack-summit-november-2018-berlin-tickets-…> - Early Bird pricing ends August 21 Become a Sponsor <https://www.openstack.org/summit/berlin-2018/sponsors/> Thanks and Best Regards, Ildikó

1 0

Re: [Edge-computing] Invitation: Weekly Edge Computing Group Call (14:00 UTC) @ Weekly from 9am to 10am on Tuesday from Tue Jun 5 to Tue Sep 4 (CDT) (edge-computing@lists.openstack.org)
by Csatari, Gergely (Nokia - HU/Budapest) 10 Jul '18

10 Jul '18

Hi, Notes of the meeting: http://eavesdrop.openstack.org/meetings/weekly_edge_computing_group_call/20… Br, Gerg0 -----Original Appointment----- From: claire(a)openstack.org [mailto:claire@openstack.org] Sent: Tuesday, May 29, 2018 3:30 PM To: claire(a)openstack.org; Ildiko Vancsa; edge-computing(a)lists.openstack.org; Jonathan Bryce Subject: [Edge-computing] Invitation: Weekly Edge Computing Group Call (14:00 UTC) @ Weekly from 9am to 10am on Tuesday from Tue Jun 5 to Tue Sep 4 (CDT) (edge-computing(a)lists.openstack.org) When: kedd 2018. július 10 9:00-10:00 America/Chicago. Where: https://zoom.us/j/777719876 more details »<https://www.google.com/calendar/event?action=VIEW&eid=XzZwMmo4ZGkyNm9zamdiO…> Weekly Edge Computing Group Call (14:00 UTC) When Weekly from 9am to 10am on Tuesday from Tue Jun 5 to Tue Sep 4 Central Time Where https://zoom.us/j/777719876 (map<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F777719876&sa=D&usd…>) Calendar edge-computing(a)lists.openstack.org Who • claire(a)openstack.org - organizer • Ildiko Vancsa • edge-computing(a)lists.openstack.org • Jonathan Bryce Weekly agenda & call notes: https://wiki.openstack.org/wiki/Edge_Computing_Group<https://www.google.com/url?q=https%3A%2F%2Fwiki.openstack.org%2Fwiki%2FEdge…> Going? All events in this series: Yes<https://www.google.com/calendar/event?action=RESPOND&eid=XzZwMmo4ZGkyNm9zam…> - Maybe<https://www.google.com/calendar/event?action=RESPOND&eid=XzZwMmo4ZGkyNm9zam…> - No<https://www.google.com/calendar/event?action=RESPOND&eid=XzZwMmo4ZGkyNm9zam…> more options »<https://www.google.com/calendar/event?action=VIEW&eid=XzZwMmo4ZGkyNm9zamdiO…> Invitation from Google Calendar<https://www.google.com/calendar/> You are receiving this courtesy email at the account edge-computing(a)lists.openstack.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More<https://support.google.com/calendar/answer/37135#forwarding>.

1 0

Use Case Help
by Jess Lampe 10 Jul '18

10 Jul '18

*Are you willing to write up a use case?* In order to complete the use cases by the end of July, we are looking for help drafting several use cases. The template for the use case can be found here: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Use_cases_te… <https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases> The list of unclaimed use cases can be found here: https://wiki.openstack.org/wiki/Edge_Computing_Group/Use_Cases#Additional_U… If you are interested in writing, please copy the use case template under the Use Cases section and add your name after "Author". Thanks!

1 0

Keystone Edge Architectures
by Waines, Greg 10 Jul '18

10 Jul '18

Hey ... just taking a look at the options in https://wiki.openstack.org/wiki/Keystone_edge_architectures . For the first option, i.e. ‘Several keystone instances with federation with API synchronsation’ · I am assuming that the Keystone Instance at each Edge Cloud Instance is communicating with a non-local central Identity Provider · If this is the case, the concern list above related to operability with no connectivity o i.e. “There may be significant times with no connectivity and all functions (e.g. autoscaling) must continue to function” In the ‘Distributed Cloud’ sub-project of the StarlingX project ( i.e. see summit presentation @ https://www.openstack.org/videos/vancouver-2018/edge-computing-operations-d… ) · our initial keystone approach is simply the standard multi-region centralized shared keystone, so no scalability and no autonomy for edge clouds on loss of connectivity, · · BUT we are currently taking more of the ‘second option’ approach (i.e. ‘Keystone database replication’) ... with some additions i.e. o Every Edge Cloud instance runs its own keystone instance, o Keystone resources are replicated from central site to edge clouds using our distribute-cloud-replication-framework, § i.e. projects, users, groups, domains, roles, ... § ( i.e. not a low-level DB synchronization ... more a high-level journaling / synchronization of resources ) o AND o Also supporting Fernet Key synchronization and management across Edge Clouds in order to enable Tokens created at any Edge / Central cloud being able to be used (and authenticated) in any other clouds. § Required for some distributed services scenarios, e.g. glance-api pulling from a remote glance-registry, etc. (likely for future scenarios we don’t currently understand). Comments ? Greg.

3 14

答复: 答复: 答复: Clarification_of_Requirements
by Fu Qiao 10 Jul '18

10 Jul '18

Hi, all. I guess some more explanations for the China Mobile’s network should be added here. The definition for small and medium edge from the whitepaper actually is different from what we say about access/county/city. Our access level CO will include compute nodes of about ten more, with distance from the Base station of 10km, delay about 2ms, and bandwidth about 50GB. Our county level CO includes tens of compute nodes, with distance of 50km, delay about 2.5ms, and bandwidth of about 100GB. City level CO will have hundreds of servers, with distance of more than 100km. I guess the small edge defined in the Whitepaper, with up to 1U, is somehow suitable for edge equipment at the customer site, and this is not actually discussed in my presentation. 发件人: 赵奇慧 [mailto:zhaoqihui@chinamobile.com] 发送时间: 2018年6月20日 10:03 收件人: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari(a)nokia.com>; lebre.adrien <lebre.adrien(a)free.fr> 抄送: edge-computing <edge-computing(a)lists.openstack.org>; paul-andre raymond <paul-andre.raymond(a)b-yond.com> 主题: Re: [Edge-computing] 答复: 答复: Clarification_of_Requirements Hi Gergely, It's great that our data can help. But I think according the the previous definitions of small edge and medium edge, there should be a little modification here. For Small edge, the maximum hardware specs is up to 1 unit, which is similar to our Access-level DC/Edge TIC AP. For Mediun edge, the hardware spec varies from 2RU to 20RU, which is somehow like our County-level DC. So here is my suggestion: --------------------------------------------------------------------------- Small edge: · Number of instances (Edge TIC AP according to <https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#cite_…> [6]): depend on demands · Distance from Base Station (Access-level DC according to <https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#cite_…> [6]): around 10km · E2E delay (from UE to site)(Access according to <https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#cite_…> [6]): 2 ms · Bandwith need (Access according to <https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#cite_…> [6]): 50 GB Medium edge: · Number of instances (Edge TIC County according to <https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#cite_…> [6]): 3000+ · Distance from Base Station (Access-level DC according to <https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#cite_…> [6]): around 50km · E2E delay (from UE to site) (Access according to <https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#cite_…> [6]): less than 2.5 ms · Bandwith need (Access according to <https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#cite_…> [6]): 100GB ---------------------------------------------------------------------------- Best Regards, Qihui Zhao _____ China Mobile Research Institute Department of Network Technology 发件人: Csatari, Gergely (Nokia - HU/Budapest) <mailto:gergely.csatari@nokia.com> 时间: 2018/06/15(星期五)22:14 收件人: lebre.adrien <mailto:lebre.adrien@free.fr> ; 抄送人: paul-andre raymond <mailto:paul-andre.raymond@b-yond.com> ;edge-computing <mailto:edge-computing@lists.openstack.org> ; 主题: Re: [Edge-computing] 答复: 答复: Clarification_of_Requirements Hi, I was thinking about the generic deployment specific requirements, like bandwiths and delays. I've added some of them from the CM presentation to https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Small… and https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG#Mediu… Br, Gerg0 -----Original Message----- From: lebre.adrien(a)free.fr <mailto:lebre.adrien@free.fr> [mailto:lebre.adrien@free.fr] Sent: Thursday, June 14, 2018 11:39 PM To: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari(a)nokia.com <mailto:gergely.csatari@nokia.com> > Cc: Arkady Kanevsky <Arkady.Kanevsky(a)dell.com <mailto:Arkady.Kanevsky@dell.com> >; fuqiao(a)chinamobile.com <mailto:fuqiao@chinamobile.com> ; paul-andre raymond <paul-andre.raymond(a)b-yond.com <mailto:paul-andre.raymond@b-yond.com> >; edge-computing(a)lists.openstack.org <mailto:edge-computing@lists.openstack.org> Subject: Re: [Edge-computing] 答复: 答复: Clarification of Requirements Hi all, Maybe we can try to prioritise the projects we want to investigate and then for each of them identify what are the missing elements/capabilities (one after the others) There are ongoing works on Keystone and Glance. Nova, Neutron could be the next ones because these 4 services would allow to deploy VM at the edge (and so containers inside VMs). Cinder will enable the use of remote attached volumes. Ironic can be useful later. etc.. My two cents, Ad_ri3n_ ----- Mail original ----- > De: "Gergely Csatari (Nokia - HU/Budapest)" > <gergely.csatari(a)nokia.com <mailto:gergely.csatari@nokia.com> > > À: "Arkady Kanevsky" <Arkady.Kanevsky(a)dell.com <mailto:Arkady.Kanevsky@dell.com> >, fuqiao(a)chinamobile.com <mailto:fuqiao@chinamobile.com> , "paul-andre raymond" > <paul-andre.raymond(a)b-yond.com <mailto:paul-andre.raymond@b-yond.com> >, "lebre adrien" > <lebre.adrien(a)free.fr <mailto:lebre.adrien@free.fr> >, edge-computing(a)lists.openstack.org <mailto:edge-computing@lists.openstack.org> > Envoyé: Mercredi 13 Juin 2018 17:38:35 > Objet: RE: [Edge-computing] 答复: 答复: Clarification of Requirements > > Hi, > > Somehow I have a feeling that these latency requirements are related > to all projects, this is why they should be documented in the > Deployment options section. > > Br, > Gerg0 > > -----Original Message----- > From: Arkady.Kanevsky(a)dell.com <mailto:Arkady.Kanevsky@dell.com> [mailto:Arkady.Kanevsky@dell.com] > Sent: Wednesday, June 13, 2018 4:24 PM > To: Csatari, Gergely (Nokia - HU/Budapest) > <gergely.csatari(a)nokia.com <mailto:gergely.csatari@nokia.com> >; fuqiao(a)chinamobile.com <mailto:fuqiao@chinamobile.com> ; > paul-andre.raymond(a)b-yond.com <mailto:paul-andre.raymond@b-yond.com> ; lebre.adrien(a)free.fr <mailto:lebre.adrien@free.fr> ; > edge-computing(a)lists.openstack.org <mailto:edge-computing@lists.openstack.org> > Subject: RE: [Edge-computing] 答复: 答复: Clarification of Requirements > > Gerg0, > I think these 3 projects are implied from the wiki requirements. > But it will be good to state projects that may need work explicitly. > Thanks, > Arkady > > -----Original Message----- > From: Csatari, Gergely (Nokia - HU/Budapest) > [mailto:gergely.csatari@nokia.com] > Sent: Wednesday, June 13, 2018 4:23 AM > To: Kanevsky, Arkady; fuqiao(a)chinamobile.com <mailto:fuqiao@chinamobile.com> ; > paul-andre.raymond(a)b-yond.com <mailto:paul-andre.raymond@b-yond.com> ; lebre.adrien(a)free.fr <mailto:lebre.adrien@free.fr> ; > edge-computing(a)lists.openstack.org <mailto:edge-computing@lists.openstack.org> > Subject: RE: [Edge-computing] 答复: 答复: Clarification of Requirements > > Hi, > > Should we add these to the Deployment Scenarions section of the Dublin > wiki [1]? > > [1]: > https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG# > Deployment_Scenarios > > Br, > Gerg0 > > -----Original Message----- > From: Arkady.Kanevsky(a)dell.com <mailto:Arkady.Kanevsky@dell.com> [mailto:Arkady.Kanevsky@dell.com] > Sent: Wednesday, June 6, 2018 4:49 PM > To: fuqiao(a)chinamobile.com <mailto:fuqiao@chinamobile.com> ; paul-andre.raymond(a)b-yond.com <mailto:paul-andre.raymond@b-yond.com> ; > lebre.adrien(a)free.fr <mailto:lebre.adrien@free.fr> ; edge-computing(a)lists.openstack.org <mailto:edge-computing@lists.openstack.org> > Subject: Re: [Edge-computing] 答复: 答复: Clarification of Requirements > > It is more than just nova to keystone. > We also need to consider at least neutron, glance and cinder also. > > -----Original Message----- > From: Fu Qiao [mailto:fuqiao@chinamobile.com] > Sent: Wednesday, June 6, 2018 8:21 AM > To: 'Paul-Andre Raymond'; lebre.adrien(a)free.fr <mailto:lebre.adrien@free.fr> ; > edge-computing(a)lists.openstack.org <mailto:edge-computing@lists.openstack.org> > Subject: [Edge-computing] 答复: 答复: Clarification of Requirements > > Yes, 5ms is one way. But this is an assumption based on the network > from China Mobile. The latency will be defer if you have different > distance, but the calculation method is the same apparently. > > -----邮件原件----- > 发件人: Paul-Andre Raymond [mailto:paul-andre.raymond@b-yond.com] > 发送时间: 2018年6月6日 21:19 > 收件人: Fu Qiao <fuqiao(a)chinamobile.com <mailto:fuqiao@chinamobile.com> >; lebre.adrien(a)free.fr <mailto:lebre.adrien@free.fr> ; > edge-computing(a)lists.openstack.org <mailto:edge-computing@lists.openstack.org> > 主题: Re: [Edge-computing] 答复: Clarification of Requirements > > Should we separate two kinds of latency requirements: > - Federation Latency: i.e Central Keystone to Local Keystone > - API latency: i.e. Edge Nova to local Keystone > > Should we measure it one way or Round Trip? I assume the 5ms below is > one way. > > > Paul-André > -- > > > On 6/6/18, 5:13 AM, "Fu Qiao" <fuqiao(a)chinamobile.com <mailto:fuqiao@chinamobile.com> > wrote: > > Thank you Adrien. I was just about the reply with more details. > > About latency, this as I understand is actually decided mostly by > the distance of the distributed cloud. So it actually decided by > where exactly the location Keystone would like to deploy, and > what is the distance expectation. Like what I explain in my > presentation, we plan to have keystone sitting in the city level > to control multi cloud in counties, and the latency will be > around 5ms. But again this is a certain situation for China > Mobile. And other operators may make the conlusion on a > different structure. Another thing we can do is work on > simulation and testing and see what kind of latency the current > keystone federation scheme can tolerant. This will help the > operators to work out there structure as well. > > About bandwidth, the impression for me is we could expect more > than 50GB of bandwidth for edge for 5G. And I think that is > enough for most of the app. > > Hope this will help. > > -----邮件原件----- > 发件人: lebre.adrien(a)free.fr <mailto:lebre.adrien@free.fr> [mailto:lebre.adrien@free.fr] > 发送时间: 2018年6月6日 15:25 > 收件人: edge-computing(a)lists.openstack.org <mailto:edge-computing@lists.openstack.org> > 主题: Re: [Edge-computing] Clarification of Requirements > > It is rather difficult to give numbers because there are several > use-cases. > However, a good starting point can be to give a look to the > presentation Qiao Fu gave during the Vancouver summit: > https://www.openstack.org/videos/vancouver-2018/edge-tic-future-edge-cloud-… > There is a lot of numbers regarding the infrastructure China > Mobile is envisioning. > > Hope this helps. > ad_ri3n_ > PS: I cannot attend the meeting yesterday unfortunately but I'm > wondering whether the disconnection aspects have been discussed > (i.e. the fact that one site can be completely isolated for a > certain period of time due to network disconnections). > > ----- Mail original ----- > > De: "Jess Lampe" <jess.lampe(a)gmail.com <mailto:jess.lampe@gmail.com> > > > À: edge-computing(a)lists.openstack.org <mailto:edge-computing@lists.openstack.org> > > Envoyé: Mercredi 6 Juin 2018 07:00:31 > > Objet: [Edge-computing] Clarification of Requirements > > > > > > > > > > During the call today, members of the Glance and Keystone teams > > requested clarity on the following areas: > > > > > > > > * Latency - what are the specific latency requirements that > > need > > to be met? > > * Bandwidth towards the edge - similarly, what are the > > limitations of bandwidth at the edge that we can expect? > > * Security - what are the specific security considerations > > that > > need to be? > > > > > > Please feel free to A.) contribute additional areas that need > > clarifying B.) clarify any of the added. > > > > > > > > > > _______________________________________________ > > Edge-computing mailing list > > Edge-computing(a)lists.openstack.org <mailto:Edge-computing@lists.openstack.org> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing > > > > _______________________________________________ > Edge-computing mailing list > Edge-computing(a)lists.openstack.org <mailto:Edge-computing@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing > > > > > _______________________________________________ > Edge-computing mailing list > Edge-computing(a)lists.openstack.org <mailto:Edge-computing@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing > > > > > > > _______________________________________________ > Edge-computing mailing list > Edge-computing(a)lists.openstack.org <mailto:Edge-computing@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing > _______________________________________________ > Edge-computing mailing list > Edge-computing(a)lists.openstack.org <mailto:Edge-computing@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing > _______________________________________________ Edge-computing mailing list Edge-computing(a)lists.openstack.org <mailto:Edge-computing@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing

7 18

Review of Dublin edge notes
by Csatari, Gergely (Nokia - HU/Budapest) 05 Jul '18

05 Jul '18

Hi, Let's continue the IRC meeting to discuss the comments to the Dublin edge notes from 5.3.2.10 Flavors source side: https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG. Notes of the previous meetings: * http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/ * http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/re… * http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes_ii/2018… * http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes_03/2018… Please note, that the correction of the comments is not finished yet, tracking of comment correction is here: https://etherpad.openstack.org/p/Dublin-edge-notes-wiki Br, Gerg0

1 0

Re: [Edge-computing] Review of Dublin edge notes
by Csatari, Gergely (Nokia - HU/Budapest) 05 Jul '18

05 Jul '18

Hi, Here are the notes from todays meeting: http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/re… As we had lots of freestyle discussions maybe it worth to check also the IRC log: http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/re… Br, Gerg0 -----Original Appointment----- From: Csatari, Gergely (Nokia - HU/Budapest) Sent: Thursday, June 28, 2018 4:40 PM To: Csatari, Gergely (Nokia - HU/Budapest); 'edge-computing'; Srikumar Venugopal; Waines, Greg; beth.cohen(a)verizon.com; Mathieu LAGRANGE; Bernier, Daniel; Martin Bäckström; Randy.Perryman(a)dell.com; Éric Sarault; Francis Dagenais; Arkady.Kanevsky(a)dell.com; Silverman, Ben; D'ANDREA, JOE (JOE); Brendon Mifsud (mifsudb); Shuquan Huang Cc: Beierl, Mark; saiyagar(a)redhat.com; Jan Walzer; jonathan(a)openstack.org; Teresa Peluso; Peter Kapatsos Subject: Review of Dublin edge notes When: csütörtök 2018. július 5 16:00-17:00 (UTC+01:00) Belgrade, Bratislava, Budapest, Ljubljana, Prague. Where: #edge-computing-group on freenode Hi, Let's continue the IRC meeting to discuss the comments to the Dublin edge notes from 5.3.2.8 VM images source side: https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG. Notes of the previous meetings: * http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/ * http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes/2018/re… * http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes_ii/2018… * http://eavesdrop.openstack.org/meetings/review_of_dublin_edge_notes_03/2018… Please note, that the correction of the comments is not finished yet, tracking of comment correction is here: https://etherpad.openstack.org/p/Dublin-edge-notes-wiki Br, Gerg0

1 0

Meeting reminder
by Ildiko Vancsa 05 Jul '18

05 Jul '18

Hi, It is a friendly reminder that we have our next meeting at 0700 UTC tomorrow (July 5). You can find the call details and meeting agenda here: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings See you on the call tomorrow! Thanks and Best Regards, Ildikó (IRC: ildikov)

1 0

Weekly Calls - New Day/Time for First Week of the Month
by Claire Massey 03 Jul '18

03 Jul '18

Hi everyone, Please make note of the update to the Edge Computing Group's weekly call schedule between now and the Berlin Summit in November. The zoom link has also been updated - all of the weekly edge calls will use this link: https://zoom.us/j/879678938 Starting this week on July 5 - on the first week of every month our weekly calls will be held in an APAC friendly time - Thursdays at 0700 UTC (midnight PDT). Throughout the rest of the month the weekly calls will continue as usual on Tuesdays at 1400 UTC (7:00am PDT). The meeting invites and wiki have been updated to reflect the new schedule: https://wiki.openstack.org/wiki/Edge_Computing_Group <https://wiki.openstack.org/wiki/Edge_Computing_Group>. Schedule for reference: THURSDAYS at 0700 UTC (midnight PDT) * July 5 * August 2 * September 6 * October 4 * November 1 TUESDAYS at 1400 UTC (7:00am PDT): * July 10 * July 17 * July 24 * August 7 * August 15 * August 21 * August 28 * September 11 (skip call, instead meet F2F at Denver PTG) * September 18 * September 25 * October 9 * October 16 * October 23 * November 6 * November 13 (skip call, instead meet F2F at Berlin Summit)

1 1

Re: [Edge-computing] [edge][glance][mixmatch]: Wiki of the possible architectures for image synchronisation
by Waines, Greg 03 Jul '18

03 Jul '18

I had some additional questions/comments on the Image Synchronization Options ( https://wiki.openstack.org/wiki/Image_handling_in_edge_environment ): One Glance with multiple backends · In this scenario, are all Edge Clouds simply configured with the one central glance for its GLANCE ENDPOINT ? o i.e. GLANCE is a typical shared service in a multi-region environment ? · If so, how does this OPTION support the requirement for Edge Cloud Operation when disconnected from Central Location ? Several Glances with an independent synchronization service (PUSH) · I refer to this as the PUSH model · I don’t believe you have to ( or necessarily should) rely on the backend to do the synchronization of the images o i.e. the ‘Synch Service’ could do this strictly through Glance REST APIs (making it independent of the particular Glance backend ... and allowing the Glance Backends at Central and Edge sites to actually be different) · I think the ‘Synch Service’ MUST be able to support ‘selective/multicast’ distribution of Images from Central to Edge for Image Synchronization o i.e. you don’t want Central Site pushing ALL images to ALL Edge Sites ... especially for the small Edge Sites · Not sure ... but I didn’t think this was the model being used in mixmatch ... thought mixmatch was more the PULL model (below) One Glance and multiple Glance API Servers (PULL) · I refer to this as the PULL model · This is the current model supported in StarlingX’s Distributed Cloud sub-project o We run glance-api on all Edge Clouds ... that talk to glance-registry on the Central Cloud, and o We have glance-api setup for caching such that only the first access to an particular image incurs the latency of the image transfer from Central to Edge · · this PULL model affectively implements the location aware synchronization you talk about below, (i.e. synchronise images only to those cloud instances where they are needed)? In StarlingX Distributed Cloud, We plan on supporting both the PUSH and PULL model ... suspect there are use cases for both. Greg. From: "Csatari, Gergely (Nokia - HU/Budapest)" <gergely.csatari(a)nokia.com> Date: Thursday, June 7, 2018 at 6:49 AM To: "openstack-dev(a)lists.openstack.org" <openstack-dev(a)lists.openstack.org>, "edge-computing(a)lists.openstack.org" <edge-computing(a)lists.openstack.org> Subject: Re: [Edge-computing] [edge][glance][mixmatch]: Wiki of the possible architectures for image synchronisation Hi, I did some work ont he figures and realised, that I have some questions related to the alternative options: Multiple backends option: - What is the API between Glance and the Glance backends? - How is it possible to implement location aware synchronisation (synchronise images only to those cloud instances where they are needed)? - Is it possible to have different OpenStack versions in the different cloud instances? - Can a cloud instance use the locally synchronised images in case of a network connection break? - Is it possible to implement this without storing database credentials ont he edge cloud instances? Independent synchronisation service: - If I understood [1<https://mixmatch.readthedocs.io/en/latest/>] correctly mixmatch can help Nova to attach a remote volume, but it will not help in synchronizing the images. is this true? As I promised in the Edge Compute Group call I plan to organize an IRC review meeting to check the wiki. Please indicate your availability in [2<https://doodle.com/poll/bddg65vyh4qwxpk5>]. [1]: https://mixmatch.readthedocs.io/en/latest/ [2]: https://doodle.com/poll/bddg65vyh4qwxpk5 Br, Gerg0 From: Csatari, Gergely (Nokia - HU/Budapest) Sent: Wednesday, May 23, 2018 8:59 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev(a)lists.openstack.org>; edge-computing(a)lists.openstack.org Subject: [edge][glance]: Wiki of the possible architectures for image synchronisation Hi, Here I send the wiki page [1<https://wiki.openstack.org/wiki/Image_handling_in_edge_environment>] where I summarize what I understood from the Forum session about image synchronisation in edge environment [2], [3]. Please check and correct/comment. Thanks, Gerg0 [1]: https://wiki.openstack.org/wiki/Image_handling_in_edge_environment [2]: https://etherpad.openstack.org/p/yvr-edge-cloud-images [3]: https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/2176…

2 7