September 2019 - Airship-discuss - lists.airshipit.org

Canceled: [sig][airship-yaml] Meetings
by PACHECO, RODOLFO J 23 Sep '19

23 Sep '19

Folks, Sorry for the late notice. Need to cancel this meeting today. Will work on getting the Repo for the crd’s created this week. IF you have any pressing topic for the sig please add it to the Etherpad. https://etherpad.openstack.org/p/Airship_UI

1 0

IPAM for Airship
by Dmitry Ukov 20 Sep '19

20 Sep '19

Hello, I'm working on cloud-init generator as a part of airshipctl bootstrap isogen command. This cloud init will be used to deploy K8s on ephemeral node. Following information is needed to set up ephemeral node: - IP address - Net mask - Default Gateway - DNS server address There is no CRD/CR that actually has this information. For example BareMetalHost resource has IP and Netmask as a part of Status field (and determined dynamically by beremetal operator) and there is no info about Default GW and DNS. This actually leads us to the situation where we need to have IPAM (ip address management) operator and appropriate CRs/CRDs. Unfortunately there is not much IPAM services that can act as K8s operator (I've found only one actually https://github.com/inwinstack/ipam and it has limitations I guess). As an alternative we have to implement IPAM as a part of Airship 2.0. What do you think? -- Kind regards Dmitry Ukov Principal Deployment Engineer Mirantis, Inc.

3 10

Updated invitation: Airship TC meetings @ Monthly from 9am to 10am on the second Thursday (CDT) (airship-discuss@lists.airshipit.org)
by claire＠openstack.org 17 Sep '19

17 Sep '19

This event has been changed. Title: Airship TC meetings Agendas: https://wiki.openstack.org/wiki/Airship/Airship-TC Join Zoom Meeting https://zoom.us/j/384128660 One tap mobile +16699006833,,384128660# US (San Jose) +16468769923,,384128660# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 384 128 660 Find your local number: https://zoom.us/u/adA54OXFxP (changed) When: Monthly from 9am to 10am on the second Thursday Central Time - Chicago Where: https://zoom.us/j/384128660 Calendar: airship-discuss(a)lists.airshipit.org Who: * claire(a)openstack.org - organizer * airship-discuss(a)lists.airshipit.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzZjbzMwYzFoOGQwajJiY… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss(a)lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Invitation: Airship WC bi-weekly mtg @ Every 2 weeks from 2pm to 3pm on Monday (CDT) (airship-discuss@lists.airshipit.org)
by claire＠openstack.org 17 Sep '19

17 Sep '19

You have been invited to the following event. Title: Airship WC bi-weekly mtg Agendas: https://wiki.openstack.org/wiki/Airship/Airship-WC Join Zoom Meeting https://zoom.us/j/384128660 One tap mobile +16699006833,,384128660# US (San Jose) +16468769923,,384128660# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 384 128 660 Find your local number: https://zoom.us/u/adA54OXFxP When: Every 2 weeks from 2pm to 3pm on Monday Central Time - Chicago Where: https://zoom.us/j/384128660 Calendar: airship-discuss(a)lists.airshipit.org Who: * claire(a)openstack.org - organizer * airship-discuss(a)lists.airshipit.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzY5MGowZGE1Nm9xM2NiO… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss(a)lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Open Infrastructure Summit Shanghai: Forum Submissions Open
by Jimmy McArthur 16 Sep '19

16 Sep '19

Hello Everyone! We are now accepting Forum [1] submissions for the 2019 Open Infrastructure Summit in Shanghai [2]. Please submit your ideas through the Summit CFP tool [3] through September20th. Don't forget to put your brainstorming etherpad up on the Shanghai Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. Keep in mind, Forum submissions are for discussions, not presentations. The timeline for submissions is as follows: Sep 4th | Formal topic submission tool opens: https://cfp.openstack.org. Sep 20th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. Sep 30th | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. Oct 7th | Scheduling committee final meeting Oct 14th | Forum schedule final Nov 4-6| Forum Time! If you have questions or concerns, please reach out to speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>. Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/shanghai-2019/ [3] https://cfp.openstack.org [4] https://wiki.openstack.org/wiki/Forum/Shanghai2019

1 1

Re: [Airship-discuss] Redfish Golibrary Findings
by Prakash.Ramchandran＠Dell.com 13 Sep '19

13 Sep '19

Kanwal, Glad to see you active on this Redfish issue. In have been following Jira ticket and did comment that we plan to use http for remote direct based on my previous and your follow up analysis. Good to see you code and will review this and absorb it into what our team was working to update by Monday. ( Note It's MIT license and will need exception from OSF) https://github.com/nordix-airship/go-redfish I had browse through oneAPI and that's why I was asking why not swagger and you answer was it's based on Swagger and we discussed that on Thursday. Dell team started with Redfish Virtual Machine Emulation (AIR-81) - Based on Redfish v1 and python sushy-client & sushy-tools This tested as a Fedora VM by JT William and for using vBMC we were tying to locate a base directory as atishipctl/tools However it was debated that we don't need VM but only should use a Docker container as in isoboot so this we deferred and will try find a location for that in validates next week. Dell team had submitted earlier for testing based on https://airship.atlassian.net/browse/AIR-88 https://review.opendev.org/#/c/681327/ At that time the specs drawn by me were as follows for hierarchy of plugins and we were still trying to work out on go language library for Redfish, which we still will stick it to gofish once things steeled on it's shortcomings ans License issues. airshipctl remoteboot -none/interface [pxe/ipxe/virtualmedia] -proto [http/tftp/file] deploy - interafce (Redfish/IPMI/iDRAC) action (register,getContext,bootorder,restart, gracefull-stop, force-stop) source -none/image [endpoint:port] target bmhost -oob/ib [endpoint/MachineSpecs/node-nnnnnn/ip-addr] This was just initial thoughts and we were still trying to merge these ideas with community airshipctl cli and looking at google docs as where to place them. We were debating the way to organize the code and our thinking was we need fake unit testing included as part of action to ensure we can complete development unit by unit before taking on vBMC or real BMC. Hope this helps and we can sort this out through email or call next week, meanwhile I review the go-redfish you have posted. Thanks Prakash Message: 1 Date: Tue, 10 Sep 2019 12:31:29 +0300 From: Kanwar Saad <kanwar.sbl(a)gmail.com<mailto:kanwar.sbl@gmail.com>> To: airship-discuss(a)lists.airshipit.org<mailto:airship-discuss@lists.airshipit.org> Subject: Re: [Airship-discuss] Redfish Golibrary Findings Message-ID: <CAFiv+i14VJL0K1xtx8u2gyz_Umh+XB0qjn_Z5ZCFsXOfdq5ULw(a)mail.gmail.com<mailto:CAFiv+i14VJL0K1xtx8u2gyz_Umh+XB0qjn_Z5ZCFsXOfdq5ULw@mail.gmail.com>> Content-Type: text/plain; charset="utf-8" Hi all, No one replied on this thread. So before the next meeting, I took the liberty of creating my own go client library for redfish. I have implemented, all the basic functions which sushy-emulator supports. Rest of the operations can be added on a need basis. I guess this can serve our purpose for now. I have to add authentication support and then I will add helper utility to do common operations easily using current primitive functions. Please try it out and give feedback. https://github.com/nordix-airship/go-redfish Br, Kanwar Saad Ericsson On Thu, Sep 5, 2019 at 3:33 PM Kanwar Saad <kanwar.sbl(a)gmail.com<mailto:kanwar.sbl@gmail.com>> wrote: > Hi, > > I spent some time on generating go client code for redfish spec using > openapi generator. But it is failing to generate code for that. I guess > code generator do not cover all scenarios of openapi. The redfish openapi > specification is huge(around 1200 documents) and it is failing for few > hundred. I dont want to spend time investigating that because that is > another rabbit hole. In that case we are left with these options. > > *Gofish:* > - only contains functions for getting redfish resources but not setting. > - The resources we want like virtualmedia is not even supported for > reading. > - It is not very well maintained. > - Extending It is not feasible since they create all datastructures by > hand and then we have to create Marshall/Unmarshall functions for each > datastructure. > > *GoRackHD:* > - It is made to work with Dell's RackHD. > - Last commit was done in 2016. > - They have used a similar approach which I was trying. They created their > own subset of swagger specification and generate client code using that > swagger spec. The spec is old and do not support virtualmedia actions which > we want. > - Extending this is complicated since we dont know whether that will be > compatible with RackHD(or we need to make a fork continue ourself). > Secondly, it uses old swagger spec than openapi and conversion to openapi > is not straightforward. > > *Use Containerized Tool:* > > One option is to use a well tested, well maintained redfish client in any > language in a container just like isogen. this option also requires writing > wrappers around that library inside contianer. > > *Create our own redfish go client :* > > 1. We can use a similar approach as of goRackHD. We can create our own > openapi spec for redfish only for the resources which we need in the start > and extend later. And generate client code using that. This might also > require maintaining the openapi spec parallel to the redfish standard spec > but since the redfish spec is not changing too fast so we can live with it. > > 2. Second option is to create a really lightweight utility functions which > will just perform the operations which we want using standard http library. > Since we might not need too much redfish functions so it could be a viable > option. If we want to rely heavily on redfish for validations(i have not > seen what kind of validations you want so its vague for me), then this > option might not work very well. > > > Br, > Kanwar Saad > Ericsson >

1 0

New Meeting Proposal - "Airship Flight Plan"
by PACHECO, RODOLFO J 13 Sep '19

13 Sep '19

We have been discussing a New Weekly Meeting “Airship Flight Plan” Purpose of this meeting would be to : • Perform JIRA Management o Make sure JIRA Tasks identified in community meetings are getting created. o Manage priority . • Identify issues that need to be reprioritized, o Manage association/Milestones/Themed Sprints o Open Questions on Milestones/Tasks/Issues Priorities • Patchsets Management o Open Discussion about Comments or Patchsets o Help push Patchsets to the Finish Line • Any other Roadmap type Q/A and Mgmt. Activities The doodle below is for proposed Meeting Times : https://doodle.com/poll/avr3zhbpqf4tnprm Regards Rodolfo Pacheco

1 0

Clusterctl is replaced with clusteradm
by Kanwar Saad 11 Sep '19

11 Sep '19

Hi, FYI, As discussed in last design call, clusterctl is now deprecated and it will be replaced by new tool clusteradm. (https://github.com/timothysc/clusteradm) The initial design doc is here ( https://docs.google.com/document/d/1ox_2dVzxJtWy_zv1SID0bGIes-hQyOVlAIC5ARc…) There is not much activity going on for this since the start of August because this tool is expected in the next releases. Whether it will be included in the v1alpha3 release, that will be discussed in the next cluster-api face-to-face grooming/design meeting on 17th September in San Francisco. This meeting's agenda also includes other important requirements in which we are also interested like cluster upgrades etc. Full agenda can be seen here ( https://docs.google.com/document/d/1GWMXvNIUJQW9RkTiWMXrQ1p5Rjg-9AplEMnSaS6… ). Br, Kanwar Saad Ericsson

1 0

[TC Meeting Moved]
by VAN WYK, RYAN L 10 Sep '19

10 Sep '19

All, the TC meeting this week has been rescheduled to Friday @ 10:30am CST. The meeting logistics are on the TC wiki. Thanks, Ryan van Wyk Assistant Vice President (AVP) – Network Cloud Engineering C: 312-860-0966<tel:312-860-0966> rv6848(a)att.com<mailto:rv6848@att.com> Assistant: Lisa Selsor | 314.450.2687<tel:314.450.2687> | ls2276(a)att.com<mailto:ls2276@att.com>

1 0

Redfish Golibrary Findings
by Kanwar Saad 10 Sep '19

10 Sep '19

Hi, I spent some time on generating go client code for redfish spec using openapi generator. But it is failing to generate code for that. I guess code generator do not cover all scenarios of openapi. The redfish openapi specification is huge(around 1200 documents) and it is failing for few hundred. I dont want to spend time investigating that because that is another rabbit hole. In that case we are left with these options. *Gofish:* - only contains functions for getting redfish resources but not setting. - The resources we want like virtualmedia is not even supported for reading. - It is not very well maintained. - Extending It is not feasible since they create all datastructures by hand and then we have to create Marshall/Unmarshall functions for each datastructure. *GoRackHD:* - It is made to work with Dell's RackHD. - Last commit was done in 2016. - They have used a similar approach which I was trying. They created their own subset of swagger specification and generate client code using that swagger spec. The spec is old and do not support virtualmedia actions which we want. - Extending this is complicated since we dont know whether that will be compatible with RackHD(or we need to make a fork continue ourself). Secondly, it uses old swagger spec than openapi and conversion to openapi is not straightforward. *Use Containerized Tool:* One option is to use a well tested, well maintained redfish client in any language in a container just like isogen. this option also requires writing wrappers around that library inside contianer. *Create our own redfish go client :* 1. We can use a similar approach as of goRackHD. We can create our own openapi spec for redfish only for the resources which we need in the start and extend later. And generate client code using that. This might also require maintaining the openapi spec parallel to the redfish standard spec but since the redfish spec is not changing too fast so we can live with it. 2. Second option is to create a really lightweight utility functions which will just perform the operations which we want using standard http library. Since we might not need too much redfish functions so it could be a viable option. If we want to rely heavily on redfish for validations(i have not seen what kind of validations you want so its vague for me), then this option might not work very well. Br, Kanwar Saad Ericsson

1 1