From ildiko at openstack.org Wed Jul 7 22:27:47 2021 From: ildiko at openstack.org (Ildiko Vancsa) Date: Wed, 7 Jul 2021 15:27:47 -0700 Subject: [Edge-computing] Tangled up in Edge blog post is live! Message-ID: <457E93CF-4845-42C2-BE4A-4B3B958BD669@openstack.org> 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-openinfra-edge-computing-group/ 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 From ildiko at openstack.org Mon Jul 12 22:24:51 2021 From: ildiko at openstack.org (Ildiko Vancsa) Date: Mon, 12 Jul 2021 15:24:51 -0700 Subject: [Edge-computing] Sign up to the upcoming PTG in October Message-ID: <0E8D4C74-CD02-4454-B756-BAA8BD8C1C2B@openstack.org> 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 From ildiko at openstack.org Mon Jul 26 15:17:30 2021 From: ildiko at openstack.org (Ildiko Vancsa) Date: Mon, 26 Jul 2021 08:17:30 -0700 Subject: [Edge-computing] Distributed systems first blog post Message-ID: <49BEA363-0113-4DC2-8B0E-62D9514D69AC@openstack.org> 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 From lebre.adrien at free.fr Wed Jul 28 14:53:23 2021 From: lebre.adrien at free.fr (lebre.adrien at free.fr) Date: Wed, 28 Jul 2021 16:53:23 +0200 (CEST) Subject: [Edge-computing] Distributed systems first blog post In-Reply-To: <49BEA363-0113-4DC2-8B0E-62D9514D69AC@openstack.org> Message-ID: <281742892.213920672.1627484003638.JavaMail.root@zimbra29-e5.priv.proxad.net> 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.)? @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. . Hope this helps move forward the discussion ;-) Thanks Adrien ----- Mail original ----- > De: "Ildiko Vancsa" > À: "edge-computing" > Envoyé: Lundi 26 Juillet 2021 17:17:30 > Objet: [Edge-computing] Distributed systems first blog post > > 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 > > > > > > _______________________________________________ > Edge-computing mailing list > Edge-computing at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing > From bdobreli at redhat.com Thu Jul 29 11:56:58 2021 From: bdobreli at redhat.com (Bogdan Dobrelya) Date: Thu, 29 Jul 2021 13:56:58 +0200 Subject: [Edge-computing] Distributed systems first blog post Message-ID: > 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