- Edge-computing - lists.opendev.org

Upcoming meeting schedule
by Ildiko Vancsa 31 Aug '21

31 Aug '21

Hi, As we have a couple things coming up for our weekly calls I wanted to give you a quick overview and reminder of our plans for the next few weeks: * August 30 - We’ve been discussing our plans for the upcoming PTG[1] event which we will be finalizing on this call. * September 6 - US Labor Day, the meeting will be cancelled. * September 13 - Chameleon project: edge for education and scientific research presentation and discussion. As a reminder the weekly calls are happening on Mondays at 6am Pacific / 1300 UTC. You can find the meeting details here: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings Please let me know if you have any questions. Thanks, Ildikó [1] https://www.openstack.org/ptg/ ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation

1 1

Updated Edge October 2021 PTG Session writeups
by Cohen, Beth F 26 Aug '21

26 Aug '21

Folks - Please review the session writeups. I have 12 sessions identified from a total of 14. Some of them can be broken into two sessions, so I suspect we do have enough sessions to fill all the slots at this point. https://etherpad.opendev.org/p/ecg-ptg-october-2021 -- -- *Beth Cohen* SDN Network Product Strategy Verizon Business Group M 781.434.8553

4 4

Blog post series and PTG
by Ildiko Vancsa 09 Aug '21

09 Aug '21

Hi, First of all let me announce that our new blog post, 'Is Edge Computing a Distributed System at Scale?’, is now live on Superuser: https://superuser.openstack.org/articles/is-edge-computing-a-distributed-sy… The discussion on distributed systems and/vs edge computing has just started, we have a lot more to untangle there. Hereby I would like to invite everyone who has some follow up thoughts or questions to the above blog to join our calls on Mondays at 6am PDT / 1300 UTC[1]. We have a thread already going about the distributed systems topic. If you’re not on the edge-computing mailing list[2], you can check the archive here: http://lists.openstack.org/pipermail/edge-computing/2021-August/000779.html If you would like to join the discussion please subscribe to the mailing list and reply to the thread. We are also continuously looking for new topics, so if you have an edge conundrum you can bring that to discuss with the group as well! The Edge Computing Group will be participating in the upcoming PTG[3] in October. We have three slots booked for this fully online event for some more deep dive technical discussions about edge infrastructures including challenges and solutions. If you have topics you would like to discuss please add that to our planning etherpad: https://etherpad.opendev.org/p/ecg-ptg-october-2021 Also please add your name to your topic and add your contact info to the etherpad so we can keep you in the loop during the planning phase. Please let me know if you have any questions. Thanks and Best Regards, Ildikó [1] https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings [2] http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing [3] https://www.openstack.org/ptg/ ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation

1 0

Edits to the Blog completed
by Cohen, Beth F 09 Aug '21

09 Aug '21

Ildiko and the rest of the Edge group. I have edited the Blog and hopefully made it a better and more entertaining read. -- -- *Beth Cohen* SDN Network Product Strategy Verizon Business Group M 781.434.8553

4 4

Re: [Edge-computing] Distributed systems first blog post
by lebre.adrien＠free.fr 09 Aug '21

09 Aug '21

> > Hi, > > > > @Ildiko, thanks once again for this draft. > > > > @All, It is still not clear whether the ''centralization'' word is > > clear (in particular in this sentence, "... we will need autonomy > > and centralization..." > > By centralisation here we mean that we would like to be able to > > administrate/use all edge sites (or edge areas) like if it was a > > single DC. However this ''centralisation'' can be implemented in > > different manners. > > Would it be possible to qualify this term or to make it clear that > > it is not a centralized system as such (i.e. a single point of > > failure with all well known limitation such as scalability etc.)? > > How about 'autonomy and hierarchical control loops'? That doesn't > bring the > notion of centralisation but rather subordination. The term ''hierarchical'' looks to me also connoted. I have the feeling that it is the notion of a mechanism capable of giving the illusion that all the edge sites form a single system that is important, isn't it? A kind of single pane of glass that can be used to manage the life cycle of -- both -- the edge sites/areas -- and -- the edge applications. > > > > > @Rob, if you have time, can you please give a look to the questions > > I put in the main etherpad: > > https://etherpad.opendev.org/p/ecg-untangling-the-edge. > > Actually, I'm not sure I'm capturing well t the exact services you > > expect from this ''centralised'' system. If I correctly > > understood, it looks like it is a golden node that is used to > > (re)configure/(re)synchronise the edge sites. If I fully agree > > such services are mandatory to manage/interact with each > > independent control plane (one per edge site/area), this system > > should also provide the right abstractions/mechanisms to manage > > the life cycle of the edge applications (which can be deployed > > across multiple edge sites/areas). In other words, we need > > independent control loops for each edge area and at least one > > control loop to manage applications. > > > > Without discussing now whether such a system could be implemented > > in a (geo-)distributed manner or whether we need one global > > application control loop or one per application, I would > > appreciate if we could highlight the fact that the control loop > > at the higher level (i.e. ''the centralised system you mention in > > your initial text'') is more complex than a golden node that is > > used to keep each edge site synchronised. . > > I would stick to a concept of targeted (or causal) events sourcing. > Like each > edge site has to follow a dedicated sub-flow of events in order to > keep being > synchronised, irrelevant to the state of its neighbours. That is > unlike to the > classic events sourcing, where the golden node tells its replicas to > strictly > apply (or reply) events from a log/journal. Does that makes sense? > The events > source concept is high level enough, it would not bring the blog > readers to the > jungles of technical details. If I'm correctly understanding your point, this might be ok but we need to consider that some events are related to the edge applications you would like to execute across different edge sites (i.e. events are not only related to keeping edge sites synchronised). best regards, Adrien >

1 0

Re: [Edge-computing] Distributed systems first blog post
by Bogdan Dobrelya 02 Aug '21

02 Aug '21

> Hi, > > @Ildiko, thanks once again for this draft. > > @All, It is still not clear whether the ''centralization'' word is clear (in particular in this sentence, "... we will need autonomy and centralization..." > By centralisation here we mean that we would like to be able to administrate/use all edge sites (or edge areas) like if it was a single DC. However this ''centralisation'' can be implemented in different manners. > Would it be possible to qualify this term or to make it clear that it is not a centralized system as such (i.e. a single point of failure with all well known limitation such as scalability etc.)? How about 'autonomy and hierarchical control loops'? That doesn't bring the notion of centralisation but rather subordination. > > @Rob, if you have time, can you please give a look to the questions I put in the main etherpad: https://etherpad.opendev.org/p/ecg-untangling-the-edge. > Actually, I'm not sure I'm capturing well t the exact services you expect from this ''centralised'' system. If I correctly understood, it looks like it is a golden node that is used to (re)configure/(re)synchronise the edge sites. If I fully agree such services are mandatory to manage/interact with each independent control plane (one per edge site/area), this system should also provide the right abstractions/mechanisms to manage the life cycle of the edge applications (which can be deployed across multiple edge sites/areas). In other words, we need independent control loops for each edge area and at least one control loop to manage applications. > > Without discussing now whether such a system could be implemented in a (geo-)distributed manner or whether we need one global application control loop or one per application, I would appreciate if we could highlight the fact that the control loop at the higher level (i.e. ''the centralised system you mention in your initial text'') is more complex than a golden node that is used to keep each edge site synchronised. . I would stick to a concept of targeted (or causal) events sourcing. Like each edge site has to follow a dedicated sub-flow of events in order to keep being synchronised, irrelevant to the state of its neighbours. That is unlike to the classic events sourcing, where the golden node tells its replicas to strictly apply (or reply) events from a log/journal. Does that makes sense? The events source concept is high level enough, it would not bring the blog readers to the jungles of technical details. > > Hope this helps move forward the discussion ;-) > Thanks > Adrien -- Best regards, Bogdan Dobrelya, Irc #bogdando

2 1

Distributed systems first blog post
by Ildiko Vancsa 28 Jul '21

28 Jul '21

Hi, As our discussions have been evolving around distributed systems and edge computing I typed up the first blog entry to kick off the mini series about this topic. I was focusing on questions and highlighting some of our debates as we have a lot of good content on the main etherpad that don’t fit into one blog post neither did we finish discussing some of them. I’m also hoping that we might be able to attract more people to join the conversation. The current version of the blog is here for review before it gets posted on superuser.openstack.org: https://etherpad.opendev.org/p/ecg-distributed-edge-mini-series Please let me know if you have any comments or questions to this piece or the discussion itself. Thanks, Ildikó ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation

2 1

Sign up to the upcoming PTG in October
by Ildiko Vancsa 12 Jul '21

12 Jul '21

Hi, While the next PTG[1] is a little while away on October 18 - 22, we need to decide about time slots for the Edge Computing Group till next Wednesday! The event will be a fully online event. As a reminder, previously we had 2 x 2 hours and 1 x 3 hours to discuss relevant topics as well as to schedule cross-project discussions and sync with adjacent communities. I believe we didn’t always use all the available time, so it might make sense to re-visit. __What is people's preference in terms of the length and number of slots we would like to reserve for edge discussions?__ Please __respond with your preference by the end of this week__ to make sure we have time for debate and to submit our request to the event organizers. If you are planning to attend the event please register[2], the registration is already open. I also created a new etherpad to throw topic ideas in: https://etherpad.opendev.org/p/ecg-ptg-october-2021 Please let me know if you have any questions. Thanks, Ildikó [1] https://www.openstack.org/ptg/ [2] https://openinfra-ptg.eventbrite.com/ ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation

1 0

Tangled up in Edge blog post is live!
by Ildiko Vancsa 07 Jul '21

07 Jul '21

Hi, I wanted to give a heads up and draw your attention to the new blog post from the OpenInfra Edge Computing Group titled ‘Tangled up in Edge’: https://superuser.openstack.org/articles/tangled-up-in-edge-a-blog-by-the-o… It is the first piece of a series, if you are interested in helping to write up the next article join our weekly calls on Mondays! Our next call is on July 12 at 1300 UTC: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings We will keep on talking about the challenges of distributed management for edge infrastructures. You can find the notes from the previous meeting starting from Line 48 on this etherpad: https://etherpad.opendev.org/p/ecg-untangling-the-edge If you cannot join our next meeting just reply to this thread to join the discussion and share your comments or questions. Please let me know if you have any questions. Thanks, Ildikó ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation

1 0

Next meeting on July 5 is cancelled
by Ildiko Vancsa 28 Jun '21

28 Jun '21

Hi, Due to many of the participants will be on holiday next Monday (July 5) we are cancelling the next occasion and will reconvene the week after. The next meeting is on__ Monday, July 12 at 1300 UTC__. For more information about the OpenInfra Edge Computing Group and our meetings please see this wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Senior Manager, Community & Ecosystem Open Infrastructure Foundation

1 0