May 2019 - Edge-computing - lists.opendev.org

Re: [Edge-computing] Lab requirements collection
by Waines, Greg 17 Sep '19

17 Sep '19

Agreed I did volunteer. I can put something together for next week’s meeting. Greg. From: "ANDREAS.FLORATH(a)TELEKOM.DE" <ANDREAS.FLORATH(a)TELEKOM.DE> Date: Friday, May 31, 2019 at 5:58 AM To: "gergely.csatari(a)nokia.com" <gergely.csatari(a)nokia.com>, "edge-computing(a)lists.openstack.org" <edge-computing(a)lists.openstack.org> Cc: "matthias.britsch(a)telekom.de" <matthias.britsch(a)telekom.de> Subject: Re: [Edge-computing] Lab requirements collection Hello! We are also waiting that somebody asks for hardware ;-) IMHO Greg volunteered to collect requirements: https://etherpad.openstack.org/p/edge-wg-ptg-preparation-denver-2019 > ACTION(gwaines): Put together requirements and start collecting an inventory of hardware that can be used for a testing lab > Requirements for both distributed and centralized MVPs > Greg Waines, greg.waines(a)windriver.com, GregWaines, in person Kind regards Andre ________________________________ From: Csatari, Gergely (Nokia - HU/Budapest) <gergely.csatari(a)nokia.com> Sent: Tuesday, May 28, 2019 17:05 To: edge-computing(a)lists.openstack.org Subject: [Edge-computing] Lab requirements collection Hi, During the PTG sessions we agreed that we will try to build and verify the minimal reference architectures (formally known as MVP architectures). We also discovered, that we might need to have some hardware for this. Some companies were kind enough to promise some hardware resource for us if we can define the “lab requirements” for these. There was someone in the room who volunteered for this task, but unfortunatelly I forgot the name. Can someone please remind me who was the kind person to volunteer for this task? Thanks, Gerg0

3 5

Re: [Edge-computing] [ironic][ops] Taking ironic nodes out of production
by Bogdan Dobrelya 09 Aug '19

09 Aug '19

[CC'ed edge-computing(a)lists.openstack.org] On 20.05.2019 18:33, Arne Wiebalck wrote: > Dear all, > > One of the discussions at the PTG in Denver raised the need for > a mechanism to take ironic nodes out of production (a task for > which the currently available 'maintenance' flag does not seem > appropriate [1]). > > The use case there is an unhealthy physical node in state 'active', > i.e. associated with an instance. The request is then to enable an > admin to mark such a node as 'faulty' or 'in quarantine' with the > aim of not returning the node to the pool of available nodes once > the hosted instance is deleted. > > A very similar use case which came up independently is node > retirement: it should be possible to mark nodes ('active' or not) > as being 'up for retirement' to prepare the eventual removal from > ironic. As in the example above, ('active') nodes marked this way > should not become eligible for instance scheduling again, but > automatic cleaning, for instance, should still be possible. > > In an effort to cover these use cases by a more general > "quarantine/retirement" feature: > > - are there additional use cases which could profit from such a > "take a node out of service" mechanism? There are security related examples described in the Edge Security Challenges whitepaper [0] drafted by k8s IoT SIG [1], like in the chapter 2 Trusting hardware, whereby "GPS coordinate changes can be used to force a shutdown of an edge node". So a node may be taken out of service as an indicator of a particular condition of edge hardware. [0] https://docs.google.com/document/d/1iSIk8ERcheehk0aRG92dfOvW5NjkdedN8F7mSUT… [1] https://github.com/kubernetes/community/tree/master/wg-iot-edge > > - would these use cases put additional constraints on how the > feature should look like (e.g.: "should not prevent cleaning") > > - are there other characteristics such a feature should have > (e.g.: "finding these nodes should be supported by the cli") > > Let me know if you have any thoughts on this. > > Cheers, > Arne > > > [1] https://etherpad.openstack.org/p/DEN-train-ironic-ptg, l. 360 > -- Best regards, Bogdan Dobrelya, Irc #bogdando

4 6

[ironic][edge]: Recap of PTG discussions
by Csatari, Gergely (Nokia - HU/Budapest) 31 May '19

31 May '19

Hi, There was a one hour discussion with Julia from Ironic with the Edge Computing Group [1]. In this mail I try to conclude what was discussed and ask some clarification questions. Current Ironic uses DHCP for hardware provisioning, therefore it requires DHCP relay enabled on the whole path to the edge cloud instances. There are two alternatives to solve this: 1) Virtual media support [2] where the ip configuration is embedded into a virtual image what is booted via the board management interface 2) Redfish support, however the state and support of redfish for host management is not clear. Is there already a specification has been added for redfish support? Upgrade of edge cloud infrastructures: - Firmware upgrade should be supported by Ironic. Is this something on its way or is this a new need? - Operating system and infra update can be solved using Fenix [3], however handling several edge cloud instances from a central location needs new features. Handling of failed servers: - A monitoring system or the operator should provide the input to mark a server as failed - Ironic can power down the failed servers and have the definition of a maintenance state - Discussed in [4] Additional ideas what we half discussed: - Running Ironic containers in a switch with the images hosted by Swift somewhere else. Are there any concerns about this idea? Any missing features from somewhere? [1]: https://etherpad.openstack.org/p/edge-wg-ptg-preparation-denver-2019 [2]: https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/L3… [3]: https://wiki.openstack.org/wiki/Fenix [4]: http://lists.openstack.org/pipermail/edge-computing/2019-May/000582.html Br, Gerg0

4 4

Lab requirements collection
by Csatari, Gergely (Nokia - HU/Budapest) 31 May '19

31 May '19

Hi, During the PTG sessions we agreed that we will try to build and verify the minimal reference architectures (formally known as MVP architectures). We also discovered, that we might need to have some hardware for this. Some companies were kind enough to promise some hardware resource for us if we can define the "lab requirements" for these. There was someone in the room who volunteered for this task, but unfortunatelly I forgot the name. Can someone please remind me who was the kind person to volunteer for this task? Thanks, Gerg0

2 1

[edge][neutron]: PTG conclusions
by Csatari, Gergely (Nokia - HU/Budapest) 28 May '19

28 May '19

Hi, According to my best memories we agreed on the PTG, that Ian will propose a neutron specification for "Segment ranges in tenant networks configureble by a tenant using an API extension" [1]. Do I remember correctly? [1]: https://photos.app.goo.gl/hGzBA2Nzu2dfG3if8 Thanks, Gerg0

3 2

Minutes of todays meeting
by Csatari, Gergely (Nokia - HU/Budapest) 28 May '19

28 May '19

Are here: http://eavesdrop.openstack.org/meetings/weekly_edge_computing_group_call/20… Br, Gerg0

1 0

Use cases sub-group call
by Ildiko Vancsa 20 May '19

20 May '19

Hi, Friendly reminder that the next Use cases sub-group call is today according to the calendar: https://wiki.openstack.org/wiki/Edge_Computing_Group#Use_cases If you’re interested in joining the call details are up on the above wiki. The latest calendar invite file is available here: https://www.openstack.org/edge-computing/ Thanks, Ildikó

1 0

Project EVE presentation on the Edge Group call tomorrow
by Ildiko Vancsa 14 May '19

14 May '19

Hi, It is a friendly reminder that we are having our next weekly call tomorrow (Tuesday, May 14) at 7am PST / 1400 UTC where we will have Roman Shaposhnik from Zededa to talk about Project EVE. You can find the full meeting agenda and dial-in details on the wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings Thanks and Best Regards, Ildikó

1 1

Edge weekly call is on
by Ildiko Vancsa 07 May '19

07 May '19

Hi, I missed to update the meeting invite, but if any of you is around the edge call is on: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings We will have the Summit and PTG as main topics for this week and next week as well. Thanks, Ildikó

1 0

- Airship 2.0 support for edge
by David.Paterson＠dell.com 05 May '19

05 May '19

I am in the last Airship PTG day and the Edge Working Group came up in the discussion. It would be really good to have someone from Airship attend one of our calls to go over Airship's plan for the edge in their next release. I would suggest sometime this summer would be good. Thanks! dp

2 1