From ildiko at openstack.org Tue Feb 23 08:55:36 2021 From: ildiko at openstack.org (Ildiko Vancsa) Date: Tue, 23 Feb 2021 09:55:36 +0100 Subject: [Edge-computing] OpenStack for the Edge presentation from INRIA on March 1st Message-ID: <2F28DD01-5561-4D1E-A3F2-0387226B33A6@openstack.org> Hi, I would like to draw your attention to the weekly call on March 1st. We will have a presentation from INRIA, delivered by Marie Delavergne, to learn about INRIA’s activities to test and evaluate edge platform options. The abstract of the presentation: Cloud computing applications are often represented as a collection of loosely coupled services encapsulated into sandboxing technologies such as containers. That modularization helps programmers to cope with the complexity of distributed infrastructures. Not only does it make the application easier to understand, but also enable DevOps to build generic features on top of it. The externalization of the application life-cycle management (deployment, monitoring, scaling, etc.) from the business logic is a perfect example. With the arrival of the edge computing paradigm, new challenges arise for applications: How to benefit from geo-distribution? How to deal with inherent constraints such as network latencies and partitioning? The general approach consists in implementing edge-native applications by entangling geo-distribution aspects in the business logic. In addition to complexifying the code, this is in contradiction with the idea of externalizing concerns. We suggest to rely, once again, on modularity of applications to externalize geo-distribution concerns and avoid meddling in the business logic. In this approach, an instance of the application is deployed on each edge location and a generic mechanism enables DevOps to recompose, on demand, the different services of these application instances in order to give the illusion of a single application instance. Our proposal requires some extensions to be complete. However, we present its relevance on a real use-case: OpenStack for the Edge. Thanks to this approach, DevOps can make multiple autonomous instances of OpenStack collaborative to manage a geo-distributed infrastructure. Please join us next week to attend the presentation and participate in the discussion about the topic. 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ó ——— Ildikó Váncsa Ecosystem Technical Lead Open Infrastructure Foundation From ildiko at openstack.org Fri Feb 26 18:02:14 2021 From: ildiko at openstack.org (Ildiko Vancsa) Date: Fri, 26 Feb 2021 19:02:14 +0100 Subject: [Edge-computing] OpenStack for the Edge presentation from INRIA on March 1st In-Reply-To: <2F28DD01-5561-4D1E-A3F2-0387226B33A6@openstack.org> References: <2F28DD01-5561-4D1E-A3F2-0387226B33A6@openstack.org> Message-ID: Hi, It is a friendly reminder to join us at the working group’s weekly call next Monday (March 01) at 1400 UTC for the presentation from INRIA about their evaluation work around OpenStack and containers for edge, followed by a discussion. You can find more information about the meeting here: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Ecosystem Technical Lead Open Infrastructure Foundation > On Feb 23, 2021, at 09:55, Ildiko Vancsa wrote: > > Hi, > > I would like to draw your attention to the weekly call on March 1st. We will have a presentation from INRIA, delivered by Marie Delavergne, to learn about INRIA’s activities to test and evaluate edge platform options. > > The abstract of the presentation: > > Cloud computing applications are often represented as a collection of loosely coupled services encapsulated into sandboxing technologies such as containers. That modularization helps programmers to cope with the complexity of distributed infrastructures. Not only does it make the application easier to understand, but also enable DevOps to build generic features on top of it. The externalization of the application life-cycle management (deployment, monitoring, scaling, etc.) from the business logic is a perfect example. > > With the arrival of the edge computing paradigm, new challenges arise for applications: How to benefit from geo-distribution? How to deal with inherent constraints such as network latencies and partitioning? > > The general approach consists in implementing edge-native applications by entangling geo-distribution aspects in the business logic. In addition to complexifying the code, this is in contradiction with the idea of externalizing concerns. > > We suggest to rely, once again, on modularity of applications to externalize geo-distribution concerns and avoid meddling in the business logic. In this approach, an instance of the application is deployed on each edge location and a generic mechanism enables DevOps to recompose, on demand, the different services of these application instances in order to give the illusion of a single application instance. Our proposal requires some extensions to be complete. However, we present its relevance on a real use-case: OpenStack for the Edge. Thanks to this approach, DevOps can make multiple autonomous instances of OpenStack collaborative to > manage a geo-distributed infrastructure. > > > Please join us next week to attend the presentation and participate in the discussion about the topic. > > 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ó > > ——— > > Ildikó Váncsa > Ecosystem Technical Lead > Open Infrastructure Foundation > > > > > _______________________________________________ > Edge-computing mailing list > Edge-computing at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/edge-computing