- Edge-computing - lists.opendev.org

APAC slot weekly call reminder
by Ildiko Vancsa 06 Mar '19

06 Mar '19

Hi, It is a friendly reminder that we have the next APAC time slot weekly call tomorrow at 8am CET / 0700 UTC. You can find the dial-in details and agenda on the wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings Thanks and Best Regards, Ildikó

1 0

Hacking days
by Ildiko Vancsa 06 Mar '19

06 Mar '19

Hi, I’m reaching out to you with an idea that we were discussing with Gergely. As many of us would be interested in make our hands dirty but can’t dedicate a lot of time to it steadily we were thinking about doing ‘hacking days’. Our goal is to identify smaller tasks such as the items on the Keystone x509 bug list and work on them as a group on a dedicated day. The idea is to get together virtually, like opening a Google Hangouts call and learn from each other while solving problems, doing testing, and so forth. We can also look into organizing an in person version at the Summits/PTGs if we have enough interest. Who would be interested in participating? Do you have a topic to work on and/or a preferred time to join? Thanks, Ildikó

4 3

Uses cases weekly call in a half an hour
by Ildiko Vancsa 26 Feb '19

26 Feb '19

Hi, It is a friendly reminder that the next Uses cases sub-group call is at 1pm PT / 2100 UTC. Call details and agenda are here: https://wiki.openstack.org/wiki/Edge_Computing_Group#Use_cases Please let me know if you have any questions. Thanks, Ildikó

1 0

Use cases weekly call in new time slot starts on February 25
by Ildiko Vancsa 20 Feb '19

20 Feb '19

Hi, We are moving the use cases weekly calls back to a more popular slot. The new time is every other Monday at 1pm PT / 2100 UTC: https://www.openstack.org/assets/edge/OSF-Edge-WG-Use-Cases-Weekly-Calls.ics For dial-in info and agenda please see the wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group#Use_cases Please let me know if you have any questions. Thanks and Best Regards, Ildikó

3 3

Open Infrastructure Summit Forum and PTG preparations
by Ildiko Vancsa 20 Feb '19

20 Feb '19

Hi, The Open Infrastructure Summit & PTG in Denver is approaching quickly so it is time to start preparing for the Forum and think of topics for the PTG as well. I created an etherpad to collect Forum session ideas: https://etherpad.openstack.org/p/edge-wg-forum-preparation-denver-2019 The Forum session proposal period opens on February 22 and closes on March 8. For the detailed process and deadlines please see the following wiki: https://wiki.openstack.org/wiki/Forum Please add you ideas to the etherpad above and add +1’s for other ones you like and -1’s that you don’t think being a good fit for the Forum. We can revisit and finalize planning next week and the session moderators can go ahead and submit the sessions through the CFP tool. We’ve decided to request for a half day slot at the PTG for Edge WG specific topics and in the remaining time sit with project teams for discussing relevant items. To make sure we spend the time available to discuss important topics I created another etherpad to collect ideas and start planning: https://etherpad.openstack.org/p/edge-wg-ptg-preparation-denver-2019 Please check the etherpads and add your ideas and comments there. Let me know if you have any questions. Thanks and Best Regards, Ildikó

1 0

LF Edge Glossary PR-s
by Csatari, Gergely (Nokia - HU/Budapest) 19 Feb '19

19 Feb '19

Hi, Here are the pr-s what I'm proposing to the edge glossary: https://github.com/lf-edge/glossary/pull/50 https://github.com/lf-edge/glossary/pull/49 https://github.com/lf-edge/glossary/pull/48 https://github.com/lf-edge/glossary/pull/47 https://github.com/lf-edge/glossary/pull/46 [https://avatars3.githubusercontent.com/u/11458775?s=400&v=4]<https://github.com/lf-edge/glossary/pull/46> Adding a remark about cloud hw to Central Office by CsatariGergely · Pull Request #46 · lf-edge/glossary<https://github.com/lf-edge/glossary/pull/46> New, cloud optimized hardware designs do not suffer from the constraints of a CEntral Office. It is important to add this to the Central Office section as this hardware design makes possible to reu... github.com Please check and comment them. Br, Gerg0 [https://avatars3.githubusercontent.com/u/11458775?s=400&v=4]<https://github.com/lf-edge/glossary/pull/47> Correction to Cloud Computing by CsatariGergely · Pull Request #47 · lf-edge/glossary<https://github.com/lf-edge/glossary/pull/47> The definition of Cloud Computing missed the networking resources and had network servers instead. Signed-off-by: Gergely Csatari gergely.csatari(a)nokia.com github.com [https://avatars3.githubusercontent.com/u/11458775?s=400&v=4]<https://github.com/lf-edge/glossary/pull/48> Cloud ran by CsatariGergely · Pull Request #48 · lf-edge/glossary<https://github.com/lf-edge/glossary/pull/48> Adding a references to DAS hub. github.com [https://avatars3.githubusercontent.com/u/11458775?s=400&v=4]<https://github.com/lf-edge/glossary/pull/49> CPE definition clarifcation by CsatariGergely · Pull Request #49 · lf-edge/glossary<https://github.com/lf-edge/glossary/pull/49> The CPE definition did not specify in which direction it is one hop away from cloud infra. Signed-off-by: Gergely Csatari gergely.csatari(a)nokia.com github.com

1 0

MEC presentation slides and recording
by Ildiko Vancsa 14 Feb '19

14 Feb '19

Hi, Attached please find the ETSI MEC slides from this week’s weekly call. You can check out the recording from the meeting here: https://zoom.us/recording/share/dnRWoPhLvMJz1QUvsjMV7COhydppAwtc3J8w2q08Vqm… The recording starts at 00:16. I also added a section to the wiki on ETSI MEC with a few pointers: https://wiki.openstack.org/wiki/Edge_Computing_Group#ETSI_MEC Thanks, Ildikó

1 0

Edge Node locator
by bharath thiruveedula 14 Feb '19

14 Feb '19

Hi , Disclaimer: I am not sure the question following is in the scope of this forum. I am trying to understand the Edge Architecture from UE point of view. How an app in UE can detect what the nearest edge it has to contact and how does it know whether the app is provisioned in that edge or not? Can you please share some pointers from this perspective? Best Regards Bharath T

5 12

Re: [Edge-computing] Edge Node locator
by Christopher Price 14 Feb '19

14 Feb '19

Bharath, A left field thought which I find quite interesting is to run your application on a CDN overlay. This can be constrained to the application layer and run over IP which reduces the need to try and weld this type of function to the infrastructure layer or expose too much service awareness through an extended mesh. (security security) Moves the problem to a defined space and keeps your infrastructure and app workloads simple and focused on what they should be doing. Millions of ways to skin that poor little cat though, imagination Vs cost… / Chris From: bharath thiruveedula <bharath_ves(a)hotmail.com> Date: Tuesday, 12 February 2019 at 18:53 To: "edge-computing(a)lists.openstack.org" <edge-computing(a)lists.openstack.org> Subject: [Edge-computing] Edge Node locator Hi , Disclaimer: I am not sure the question following is in the scope of this forum. I am trying to understand the Edge Architecture from UE point of view. How an app in UE can detect what the nearest edge it has to contact and how does it know whether the app is provisioned in that edge or not? Can you please share some pointers from this perspective? Best Regards Bharath T

3 4

[keystone] x509 authentication
by Lance Bragstad 13 Feb '19

13 Feb '19

Hi all, We've been going over keystone gaps that need to be addressed for edge use cases every Tuesday. Since Berlin, Oath has open-sourced some of their custom authentication plugins for keystone that help them address these gaps. The basic idea is that users authenticate to some external identity provider (Athenz in Oath's case), and then present an Athenz token to keystone. The custom plugins decode the token from Athenz to determine the user, project, roles assignments, and other useful bits of information. After that, it creates any resources that don't exist in keystone already. Ultimately, a user can authenticate against a keystone node and have specific resources provisioned automatically. In Berlin, engineers from Oath were saying they'd like to move away from Athenz tokens altogether and use x509 certificates issued by Athenz instead. The auto-provisioning approach is very similar to a feature we have in keystone already. In Berlin, and shortly after, there was general agreement that if we could support x509 authentication with auto-provisioning via keystone federation, that would pretty much solve Oath's use case without having to maintain custom keystone plugins. Last week, Colleen started digging into keystone's existing x509 authentication support. I'll start with the good news, which is x509 authentication works, for the most part. It's been a feature in keystone for a long time, and it landed after we implemented federation support around the Kilo release. Chances are there won't be a need for a keystone specification like we were initially thinking in the edge meetings. Unfortunately, the implementation for x509 authentication has outdated documentation, is extremely fragile, hard to set up, and hasn't been updated with improvements we've made to the federation API since the original implementation (like shadow users or auto-provisioning, which work with other federated protocols like OpenID Connect and SAML). We've started tracking the gaps with bugs [0] so that we have things written down. I think the good thing is that once we get this cleaned up, we'll be able to re-use some of the newer federation features with x509 authentication/federation. These updates would make x509 a first-class federated protocol. The approach, pending the bug fixes, would remove the need for Oath's custom authentication plugins. It could be useful for edge deployments, or even deployments with many regions, by allowing users to be auto-provisioned in each region. Although, it doesn't necessarily solve the network partition issue. Now that we have an idea of where to start and some bug reports [0], I'm wondering if anyone is interested in helping with the update or refactor. Because this won't require a specification, we can get started on it sooner, instead of having to wait for Train development and a new specification. I'm also curious if anyone has comments or questions about the approach. Thanks, Lance [0] https://bugs.launchpad.net/keystone/+bugs?field.tag=x509

4 6