From aw442m at att.com Tue Dec 3 17:10:41 2019 From: aw442m at att.com (WALTERS, ANDREW) Date: Tue, 3 Dec 2019 17:10:41 +0000 Subject: [Airship-discuss] Final Airship Working Committee Meeting of 2019 Message-ID: Hey everyone! The Working Committee will hold it's final meeting of 2019 on December 9th at 20:00 UTC (2:00 PM CST). The meeting agenda [1] includes addressing feedback from the Airship project confirmation, establishing "docs.airshipit.org", and migrating from Jira to GitHub issues. Airship Working Committee meetings are open to all, and the last fifteen minutes of every meeting are reserved for open discussion. Past meeting minutes, recordings, and future meeting logistics are advertised on the Airship Working Committee wiki page [2]. [1] https://etherpad.openstack.org/p/airship-wc-meeting-2019-12-09 [2] https://wiki.openstack.org/wiki/Airship/Airship-WC -------------- next part -------------- An HTML attachment was scrubbed... URL: From aw442m at att.com Tue Dec 3 17:33:44 2019 From: aw442m at att.com (WALTERS, ANDREW) Date: Tue, 3 Dec 2019 17:33:44 +0000 Subject: [Airship-discuss] Query related to Airskiff deployment In-Reply-To: <608de1fa-d993-14be-b567-3cf25d31af5f@calsoftinc.com> References: <608de1fa-d993-14be-b567-3cf25d31af5f@calsoftinc.com> Message-ID: Hi! The Airskiff check job is operational again, so all previously-broken script paths in the Airskiff scripts should be repaired. Are you still seeing this issue with the latest version of Treasuremap? Best, Drew Walters From: Garima Misra Sent: Tuesday, October 22, 2019 10:08 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Query related to Airskiff deployment Hello Everyone, I am trying to deploy Airskiff using following URL: https://airship-treasuremap.readthedocs.io/en/latest/airskiff.html And in one of the step (Deploy Kubernetes with Minikube) ta script file "./tools/deployment/common/005-deploy-k8s.sh" is mentioned, which is missing from the github repository. Thus, there is no installation of k8s done in this case. Note: I am using Master branch in this case. Moreover, there is no "/tools/deployment/common" folder in 'treasuremap' directory. Please suggest any resolutions to these. -- Thanks and Regards, Garima Misra -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Tue Dec 3 18:00:29 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 3 Dec 2019 18:00:29 +0000 Subject: [Airship-discuss] [airship-discuss] GitHub Issues for Airship? Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970AA6FD5@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship community, At the KubeCon meetup, the idea was brought up to potentially switch forward-looking scope (and bug) tracking from Jira to GitHub Issues. Specifically, we would use Issues on our projects in the readonly GitHub mirror of OpenDev Gerrit. I've captured additional details, along with pros, cons, and background, in an etherpad: https://etherpad.openstack.org/p/airship-github-issues Please give this some thought, and add additional benefits, concerns, or ideas to the etherpad. In any case, we wouldn't need to rush this switch. I think this would be a great topic to bring up in the weekly Airship Flight Plan meeting as well. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire at openstack.org Tue Dec 3 18:48:20 2019 From: claire at openstack.org (claire at openstack.org) Date: Tue, 03 Dec 2019 18:48:20 +0000 Subject: [Airship-discuss] Updated invitation: Airship WC bi-weekly mtg @ Mon Dec 9, 2019 2pm - 3pm (CST) (airship-discuss@lists.airshipit.org) Message-ID: <000000000000d9410b0598d12315@google.com> This event has been changed. 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: Mon Dec 9, 2019 2pm – 3pm Central Time - Chicago (changed) Where: https://zoom.us/j/384128660 Calendar: airship-discuss at lists.airshipit.org Who: * claire at openstack.org - organizer * Stas Egorov * airship-discuss at lists.airshipit.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzY5MGowZGE1Nm9xM2NiOW04NHNrNGI5azhoMGo2YjlvNmgyNGFiOWk3MG9qOGhoazZzcmowZ3EyODhfMjAxOTEyMDJUMjAwMDAwWiBhaXJzaGlwLWRpc2N1c3NAbGlzdHMuYWlyc2hpcGl0Lm9yZw&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmcwYTY0YjViZDhmM2FkMTQwNmFiNDZhMzI5MjEwMWIzM2IyNGNlZmNj&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2955 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3033 bytes Desc: not available URL: From cboylan at sapwetik.org Tue Dec 3 20:14:46 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 03 Dec 2019 12:14:46 -0800 Subject: [Airship-discuss] Thread on OpenDev Independence and Governance Message-ID: Hello, I wanted everyone to be aware of this thread [0] at openstack-infra at lists.openstack.org that I've started to formalize OpenDev's future independence and governance. Currently the infra team is formally an OpenStack project, but we think that we'll be better able to serve our non OpenStack users if the OpenDev aspects of this team become independent with its own governance. We are more than happy to hear feedback so please read this thread and respond if the topic interests you. Note, I'm using this pointer thread in an effort to avoid cross posting and losing feedback. It would be great if people can respond to the original on openstack-infra at lists. [0] http://lists.openstack.org/pipermail/openstack-infra/2019-December/006537.html Thank you, Clark From MM9745 at att.com Tue Dec 3 21:08:02 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 3 Dec 2019 21:08:02 +0000 Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship team, I'd like to propose the project "airship/go-redfish", which will be a reusable go library for interfacing with the Redfish API. The project would start as a rehoming of Kanwar's great work here, which was done on behalf of airshipctl: https://github.com/Nordix/go-redfish As discussed in today's design call, rehoming this project under the Airship umbrella will help ensure it's ongoing enhancement and maintenance, while making it available to other projects inside and outside of our community. It's important to note that Kanwar & team created this in the first place because of feature gaps in the other Redfish library implementations that are out there - so, this is a valuable thing to share. If you agree (or disagree) with creation this project, please reply +1/-1; or if you'd like to defer discussion to our weekly IRC meeting let me know. Normally that's where I'd bring this up, but I didn't want to wait a full week with the holidays approaching. Once I get some general consensus, I'll move ahead with the project creation. My thanks to Kanwar & the other developers for their work on this, and willingness to move it into Airship. Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Tue Dec 3 21:20:44 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 3 Dec 2019 21:20:44 +0000 Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <99088997CCAD0C4BA20008FD094344963C4A590D@MISOUT7MSGUSRDI.ITServices.sbc.com> +1 ________________________________ From: MCEUEN, MATT Sent: Tuesday, December 03, 2019 4:08 PM To: 'airship-discuss at lists.airshipit.org' Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, I’d like to propose the project “airship/go-redfish”, which will be a reusable go library for interfacing with the Redfish API. The project would start as a rehoming of Kanwar’s great work here, which was done on behalf of airshipctl: https://github.com/Nordix/go-redfish As discussed in today’s design call, rehoming this project under the Airship umbrella will help ensure it’s ongoing enhancement and maintenance, while making it available to other projects inside and outside of our community. It’s important to note that Kanwar & team created this in the first place because of feature gaps in the other Redfish library implementations that are out there – so, this is a valuable thing to share. If you agree (or disagree) with creation this project, please reply +1/-1; or if you’d like to defer discussion to our weekly IRC meeting let me know. Normally that’s where I’d bring this up, but I didn’t want to wait a full week with the holidays approaching. Once I get some general consensus, I’ll move ahead with the project creation. My thanks to Kanwar & the other developers for their work on this, and willingness to move it into Airship. Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From ih616h at att.com Tue Dec 3 22:18:10 2019 From: ih616h at att.com (HOWELL, IAN) Date: Tue, 3 Dec 2019 22:18:10 +0000 Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <2A7C8018C01D6044934139A38A7891EC13D5669F@MOSTLS1MSGUSREH.ITServices.sbc.com> +1 Thanks, Ian From: MCEUEN, MATT Sent: Tuesday, December 3, 2019 3:08 PM To: 'airship-discuss at lists.airshipit.org' Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, I'd like to propose the project "airship/go-redfish", which will be a reusable go library for interfacing with the Redfish API. The project would start as a rehoming of Kanwar's great work here, which was done on behalf of airshipctl: https://github.com/Nordix/go-redfish As discussed in today's design call, rehoming this project under the Airship umbrella will help ensure it's ongoing enhancement and maintenance, while making it available to other projects inside and outside of our community. It's important to note that Kanwar & team created this in the first place because of feature gaps in the other Redfish library implementations that are out there - so, this is a valuable thing to share. If you agree (or disagree) with creation this project, please reply +1/-1; or if you'd like to defer discussion to our weekly IRC meeting let me know. Normally that's where I'd bring this up, but I didn't want to wait a full week with the holidays approaching. Once I get some general consensus, I'll move ahead with the project creation. My thanks to Kanwar & the other developers for their work on this, and willingness to move it into Airship. Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From ji5690 at att.com Tue Dec 3 22:21:39 2019 From: ji5690 at att.com (GU, JAMES) Date: Tue, 3 Dec 2019 22:21:39 +0000 Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish In-Reply-To: <2A7C8018C01D6044934139A38A7891EC13D5669F@MOSTLS1MSGUSREH.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> <2A7C8018C01D6044934139A38A7891EC13D5669F@MOSTLS1MSGUSREH.ITServices.sbc.com> Message-ID: +1. Thanks, James From: HOWELL, IAN Sent: Tuesday, December 3, 2019 2:18 PM To: MCEUEN, MATT; 'airship-discuss at lists.airshipit.org' Subject: Re: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. +1 Thanks, Ian From: MCEUEN, MATT > Sent: Tuesday, December 3, 2019 3:08 PM To: 'airship-discuss at lists.airshipit.org' > Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, I'd like to propose the project "airship/go-redfish", which will be a reusable go library for interfacing with the Redfish API. The project would start as a rehoming of Kanwar's great work here, which was done on behalf of airshipctl: https://github.com/Nordix/go-redfish As discussed in today's design call, rehoming this project under the Airship umbrella will help ensure it's ongoing enhancement and maintenance, while making it available to other projects inside and outside of our community. It's important to note that Kanwar & team created this in the first place because of feature gaps in the other Redfish library implementations that are out there - so, this is a valuable thing to share. If you agree (or disagree) with creation this project, please reply +1/-1; or if you'd like to defer discussion to our weekly IRC meeting let me know. Normally that's where I'd bring this up, but I didn't want to wait a full week with the holidays approaching. Once I get some general consensus, I'll move ahead with the project creation. My thanks to Kanwar & the other developers for their work on this, and willingness to move it into Airship. Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From petebirley at googlemail.com Tue Dec 3 23:46:13 2019 From: petebirley at googlemail.com (Pete Birley) Date: Tue, 3 Dec 2019 17:46:13 -0600 Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: +1 On Tue, Dec 3, 2019, 15:10 MCEUEN, MATT wrote: > Airship team, > > > > I’d like to propose the project “airship/go-redfish”, which will be a > reusable go library for interfacing with the Redfish API. The project > would start as a rehoming of Kanwar’s great work here, which was done on > behalf of airshipctl: https://github.com/Nordix/go-redfish > > > > As discussed in today’s design call, rehoming this project under the > Airship umbrella will help ensure it’s ongoing enhancement and maintenance, > while making it available to other projects inside and outside of our > community. It’s important to note that Kanwar & team created this in the > first place because of feature gaps in the other Redfish library > implementations that are out there – so, this is a valuable thing to share. > > > > If you agree (or disagree) with creation this project, please reply +1/-1; > or if you’d like to defer discussion to our weekly IRC meeting let me > know. Normally that’s where I’d bring this up, but I didn’t want to wait a > full week with the holidays approaching. Once I get some general > consensus, I’ll move ahead with the project creation. > > > > My thanks to Kanwar & the other developers for their work on this, and > willingness to move it into Airship. > > > Matt > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Wed Dec 4 08:40:31 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Wed, 4 Dec 2019 09:40:31 +0100 Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <15A14EA1-23B5-42C6-9A2E-85437519130E@gmail.com> +1 — Roman Gorshunov From dukov at mirantis.com Wed Dec 4 13:23:11 2019 From: dukov at mirantis.com (Dmitry Ukov) Date: Wed, 4 Dec 2019 17:23:11 +0400 Subject: [Airship-discuss] [airship-discuss] Project proposal: airship/go-redfish In-Reply-To: <15A14EA1-23B5-42C6-9A2E-85437519130E@gmail.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970AA719D@MOSTLS1MSGUSRFF.ITServices.sbc.com> <15A14EA1-23B5-42C6-9A2E-85437519130E@gmail.com> Message-ID: +1 On Wed, Dec 4, 2019 at 12:43 PM Roman Gorshunov wrote: > +1 > > — > Roman Gorshunov > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -- Kind regards Dmitry Ukov Principal Deployment Engineer Mirantis, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From roman.gorshunov at att.com Wed Dec 4 14:40:35 2019 From: roman.gorshunov at att.com (Gorshunov, Roman) Date: Wed, 4 Dec 2019 14:40:35 +0000 Subject: [Airship-discuss] [sig][airship-bootstrap] Meeting time announcement - 12/4/2019 meeting is cancelled Message-ID: Cancelling meeting on 12/4/2019, as there is no agenda posted and I'm on vacation. When: Weekly from 2pm UTC to 3pm UTC (10 EST to 11 EST) on Wednesday from Wed Aug 7 to Tue Dec 31 Where: https://attcorp.webex.com/join/rg445d +~+~+~+~+~+~+~+~+~+ This was the time with the most votes on the doodle meeting time poll. First sig-airship-bootstrap meeting will be next week. * Etherpad: https://etherpad.openstack.org/p/Airship_bootstrap Notice that the subject line includes [sig][airship-bootstrap], please make sure you add this to any email to airship-discuss at lists.airshipit.org when the topic relates to the airship-bootstrap discussion. Best regards, -- Roman Gorshunov -- Do not delete or change any of the following text. -- Join meeting in my Webex Personal Room https://attcorp.webex.com/join/rg445d | 731 907 899 Join from a video conferencing system or application Dial rg445d at attcorp.webex.com You can also dial 173.243.2.68 and enter your meeting number. If you are the host, you can also enter your host PIN in your video conferencing system or application to start the meeting. Join by phone Tap to call in from a mobile device (attendees only) 1-618-230-6039 United States Toll 1-844-517-1415 United States Toll Free Access code: 731 907 899 Global call-in numbers | Toll-free calling restrictions Accessibility and Assistive Technologies Select this job aid for tips and guides to make Webex Meetings accessible to persons with disabilities who may rely on assistive technologies. Can't join the meeting? IMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: text/calendar Size: 7110 bytes Desc: invite.ics URL: From rv6848 at att.com Wed Dec 4 21:05:02 2019 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Wed, 4 Dec 2019 21:05:02 +0000 Subject: [Airship-discuss] [TC] Message-ID: <9B4615ED4FEDC74EA1FAF8B11F578BFA55B96943@MOSTLS1MSGUSREG.ITServices.sbc.com> I am sad to say that I need to tender my resignation to the Airship Technical Committee. This is not because I wont continue to support Airship, but with my recent promotion within AT&T, I just won’t have the time needed to perform my TC duties. That said in my new role, I will continue to marshal resources both within AT&T and the larger community to grow Airship support and adoption. Andrew Leasck who has been instrumental in leading the development and Airship and owns Airship internally within AT&T, intends to nominate himself to replace me on the TC. I would encourage the community to elect him to the position. Thanks, Ryan van Wyk VP – Network Cloud m 312.860.0966 | rv6848 at att.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Dec 11 15:58:36 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 11 Dec 2019 15:58:36 +0000 Subject: [Airship-discuss] Canceled: Airship Flight Plan - Meeting Message-ID: <54FBEF42-39F7-48AA-B944-510935CD8D26@att.com> Need to Cancel this meeting, will resume next year. Weekly Meeting Agenda : • 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Wed Dec 11 19:50:28 2019 From: ashlee at openstack.org (Ashlee Ferguson) Date: Wed, 11 Dec 2019 13:50:28 -0600 Subject: [Airship-discuss] Airship Update - November 2019 Message-ID: Hi everyone, The latest Airship blog post is up! Check out the updates from November 2019— https://www.airshipit.org/blog/airship-update-november-2019.html If you’d like to receive this monthly newsletter, you can subscribe here by selecting "Infrastructure lifecycle management (featuring Airship)." Ashlee — Ashlee Ferguson OpenStack Foundation ashlee at openstack.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Dec 11 15:34:28 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 11 Dec 2019 15:34:28 +0000 Subject: [Airship-discuss] Canceled: Airship Flight Plan - Meeting Message-ID: <99088997CCAD0C4BA20008FD094344963C4B468C@MISOUT7MSGUSRDI.ITServices.sbc.com> Need to Cancel this meeting, will resume next year. Weekly Meeting Agenda : • 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3626 bytes Desc: not available URL: From rp2723 at att.com Thu Dec 12 16:55:47 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 12 Dec 2019 16:55:47 +0000 Subject: [Airship-discuss] Airship - Open Design Call - Tuesday Dec 17, 2019 - Canceled Message-ID: <937AE3E6-F18B-42F8-B63A-3902BD51DA4F@att.com> Airship - Open Design Call - Tuesday Dec 17, 2019 – Canceled Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Thu Dec 12 16:56:54 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 12 Dec 2019 16:56:54 +0000 Subject: [Airship-discuss] Airship - Open Design Call - Tuesday Dec 24, 26, 31, 2019 - Canceled Message-ID: Airship - Open Design Call - - Will resume on Jan 2, 2020 after the Dec 19, call next week. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Thu Dec 12 16:56:54 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 12 Dec 2019 16:56:54 +0000 Subject: [Airship-discuss] Airship - Open Design Call - Tuesday Dec 24, 26, 31, 2019 - Canceled Message-ID: Airship - Open Design Call - - Will resume on Jan 2, 2020 after the Dec 19, call next week. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Mon Dec 16 01:42:28 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 16 Dec 2019 01:42:28 +0000 Subject: [Airship-discuss] Canceled: [sig][airship-yaml] Meeting Dec 16, 2019 Message-ID: <1FFEDAE7-9D91-4A26-B2F3-0BA0C9C2BDC7@att.com> All, there is only a single topic in the etherpad for tomorrow I added. I haven’t complete the Kustomize CRD Transformer Plugin yet. I need to cancel the meeting tomorrow. Following 2 weeks are holidays, we will resume the Airship SIG Yaml meetings on Monday January 6, 2020 Happy Holidays to all. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire at openstack.org Mon Dec 16 17:30:11 2019 From: claire at openstack.org (claire at openstack.org) Date: Mon, 16 Dec 2019 17:30:11 +0000 Subject: [Airship-discuss] Updated invitation: Airship WC bi-weekly mtg @ Every 2 weeks from 2pm to 3pm on Monday except Mon Dec 16 2pm (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <0000000000004506420599d59045@google.com> This event has been changed. 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 except Mon Dec 16 2pm Central Time - Chicago (changed) Where: https://zoom.us/j/384128660 Calendar: airship-discuss at lists.airshipit.org Who: * claire at openstack.org - organizer * airship-discuss at lists.airshipit.org * Stas Egorov Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzY5MGowZGE1Nm9xM2NiOW04NHNrNGI5azhoMGo2YjlvNmgyNGFiOWk3MG9qOGhoazZzcmowZ3EyODggYWlyc2hpcC1kaXNjdXNzQGxpc3RzLmFpcnNoaXBpdC5vcmc&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmdjNjczY2Q1YzkxZmVhZjY5ZTBmODI3ODY0MzIwNmM5YmNlYWE4YmQx&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2965 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3044 bytes Desc: not available URL: From claire at openstack.org Mon Dec 16 17:30:17 2019 From: claire at openstack.org (claire at openstack.org) Date: Mon, 16 Dec 2019 17:30:17 +0000 Subject: [Airship-discuss] Updated invitation: Airship WC bi-weekly mtg @ Every 2 weeks from 2pm to 3pm on Monday except Mon Dec 16 2pm or Mon Dec 30 2pm (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <000000000000a085da0599d5901b@google.com> This event has been changed. 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 except Mon Dec 16 2pm or Mon Dec 30 2pm Central Time - Chicago (changed) Where: https://zoom.us/j/384128660 Calendar: airship-discuss at lists.airshipit.org Who: * claire at openstack.org - organizer * airship-discuss at lists.airshipit.org * Stas Egorov Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzY5MGowZGE1Nm9xM2NiOW04NHNrNGI5azhoMGo2YjlvNmgyNGFiOWk3MG9qOGhoazZzcmowZ3EyODggYWlyc2hpcC1kaXNjdXNzQGxpc3RzLmFpcnNoaXBpdC5vcmc&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmdjNjczY2Q1YzkxZmVhZjY5ZTBmODI3ODY0MzIwNmM5YmNlYWE4YmQx&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3009 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 3089 bytes Desc: not available URL: From MM9745 at att.com Mon Dec 16 18:09:36 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 16 Dec 2019 18:09:36 +0000 Subject: [Airship-discuss] WC Meetings cancelled through EOY Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970AAC554@MOSTLS1MSGUSRFF.ITServices.sbc.com> Team, Just a reminder that Airship Working Committee meetings are cancelled through the end of year, and will resume in January. Thanks, and Happy Holidays! Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From ji5690 at att.com Tue Dec 17 00:18:25 2019 From: ji5690 at att.com (GU, JAMES) Date: Tue, 17 Dec 2019 00:18:25 +0000 Subject: [Airship-discuss] Any interest in IPMI+SMASH support in Airship 2.0 Message-ID: Hello All, Airship bootstrap 2.0 leverages Redfish in baremetal provisioning. I had briefly worked on adding the IPMI support for older generation of hardware that does not support Redfish. The work was based on specific requirement from a community member who had pulled out recently from OpenStack. It's still work in progress. I am curious to poll the community 1) if there is continued interest/value for IPMI support in the Airship 2.0; 2) if there is any interest in contributing in this area in any form, development, testing, hardware, docs etc. Thanks, James Gu -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Tue Dec 17 20:34:53 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 17 Dec 2019 20:34:53 +0000 Subject: [Airship-discuss] [WC] Special Election Procedure Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970AACBB7@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship Working Committee, We'd like to formalize our process around special elections when a seat in the TC or WC becomes vacant. Alex Hughes has proposed a governance change to address: https://review.opendev.org/#/c/698809 I've given my +1 and will await more WC votes before giving a +2. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From dukov at mirantis.com Wed Dec 18 08:28:25 2019 From: dukov at mirantis.com (Dmitry Ukov) Date: Wed, 18 Dec 2019 12:28:25 +0400 Subject: [Airship-discuss] Any interest in IPMI+SMASH support in Airship 2.0 In-Reply-To: References: Message-ID: James, I'd vote for IPMI support development since Redfish support is not that common for generic servers On Tue, Dec 17, 2019 at 4:21 AM GU, JAMES wrote: > Hello All, > > > > Airship bootstrap 2.0 leverages Redfish in baremetal provisioning. I had > briefly worked on adding the IPMI support for older generation of hardware > that does not support Redfish. The work was based on specific requirement > from a community member who had pulled out recently from OpenStack. It’s > still work in progress. I am curious to poll the community 1) if there is > continued interest/value for IPMI support in the Airship 2.0; 2) if there > is any interest in contributing in this area in any form, development, > testing, hardware, docs etc. > > > > Thanks, > > > > James Gu > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -- Kind regards Dmitry Ukov Principal Deployment Engineer Mirantis, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Wed Dec 18 09:01:32 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Wed, 18 Dec 2019 10:01:32 +0100 Subject: [Airship-discuss] Any interest in IPMI+SMASH support in Airship 2.0 In-Reply-To: References: Message-ID: <414979D1-FC8F-4EA5-9310-22F6885CB603@gmail.com> Dmitry, Which one’s don’t have RedFish support? I found out that although not advertised widely (SuperMicro), many do support it. All major vendors do support RedFish. Thank you. Best regards, — Roman Gorshunov > On 18 Dec 2019, at 09:29, Dmitry Ukov wrote: >  > James, > I'd vote for IPMI support development since Redfish support is not that common for generic servers > > -- > Kind regards > Dmitry Ukov > Principal Deployment Engineer > Mirantis, Inc. > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From dukov at mirantis.com Thu Dec 19 09:13:00 2019 From: dukov at mirantis.com (Dmitry Ukov) Date: Thu, 19 Dec 2019 13:13:00 +0400 Subject: [Airship-discuss] Any interest in IPMI+SMASH support in Airship 2.0 In-Reply-To: <414979D1-FC8F-4EA5-9310-22F6885CB603@gmail.com> References: <414979D1-FC8F-4EA5-9310-22F6885CB603@gmail.com> Message-ID: Roman, Some legacy HW definitely not. SiperMicro do have Redfish support that being said you have to purchase additional licence for that which may not be possible in some cases (regular IPMI does not require such licence) On Wed, Dec 18, 2019 at 1:03 PM Roman Gorshunov wrote: > Dmitry, > > Which one’s don’t have RedFish support? I found out that although not > advertised widely (SuperMicro), many do support it. All major vendors do > support RedFish. > > Thank you. > > Best regards, > — > Roman Gorshunov > > > On 18 Dec 2019, at 09:29, Dmitry Ukov wrote: > >  > > James, > > I'd vote for IPMI support development since Redfish support is not that > common for generic servers > > > > -- > > Kind regards > > Dmitry Ukov > > Principal Deployment Engineer > > Mirantis, Inc. > > > > _______________________________________________ > > Airship-discuss mailing list > > Airship-discuss at lists.airshipit.org > > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -- Kind regards Dmitry Ukov Principal Deployment Engineer Mirantis, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jezogwza at gmail.com Thu Dec 19 13:13:35 2019 From: jezogwza at gmail.com (Rodolfo Pacheco) Date: Thu, 19 Dec 2019 08:13:35 -0500 Subject: [Airship-discuss] Airship Design Meeting - Dec 17, 2019 - Canceled Message-ID: Canceling today's Design Meeting, there are no Agenda Topics on the Etherpad. We will resume Thursday Jan 2, 2020 Rodolfo -------------- next part -------------- An HTML attachment was scrubbed... URL: From jezogwza at gmail.com Thu Dec 19 13:14:59 2019 From: jezogwza at gmail.com (Rodolfo Pacheco) Date: Thu, 19 Dec 2019 08:14:59 -0500 Subject: [Airship-discuss] Airship Design Meeting - Dec 19, 2019 - Canceled Message-ID: Canceling today's Design Meeting, there are no Agenda Topics on the Etherpad. We will resume Thursday Jan 2, 2020 Rodolfo -------------- next part -------------- An HTML attachment was scrubbed... URL: From kkalynovskyi at mirantis.com Thu Dec 19 15:53:06 2019 From: kkalynovskyi at mirantis.com (Kostiantyn Kalynovskyi) Date: Thu, 19 Dec 2019 09:53:06 -0600 Subject: [Airship-discuss] Any interest in IPMI+SMASH support in Airship 2.0 In-Reply-To: <414979D1-FC8F-4EA5-9310-22F6885CB603@gmail.com> References: <414979D1-FC8F-4EA5-9310-22F6885CB603@gmail.com> Message-ID: I think you have to buy separate licence if you want support for redfish on many vendors? On Wed, Dec 18, 2019, 3:02 AM Roman Gorshunov wrote: > Dmitry, > > Which one’s don’t have RedFish support? I found out that although not > advertised widely (SuperMicro), many do support it. All major vendors do > support RedFish. > > Thank you. > > Best regards, > — > Roman Gorshunov > > > On 18 Dec 2019, at 09:29, Dmitry Ukov wrote: > >  > > James, > > I'd vote for IPMI support development since Redfish support is not that > common for generic servers > > > > -- > > Kind regards > > Dmitry Ukov > > Principal Deployment Engineer > > Mirantis, Inc. > > > > _______________________________________________ > > Airship-discuss mailing list > > Airship-discuss at lists.airshipit.org > > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Fri Dec 20 17:03:03 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 20 Dec 2019 17:03:03 +0000 Subject: [Airship-discuss] Canceled: [sig][airship-ui] Meeting Dec 20, 2019 Message-ID: <05386E43-1873-4DAA-900F-3F414B8BDB6B@att.com> All, there are no topics in the etherpad for today. Canceling Todays call. We will resume our meeting Jan 7, 2020 Happy Holidays to all. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: