From ashlee at openstack.org Wed Jul 1 17:26:42 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Wed, 1 Jul 2020 12:26:42 -0500 Subject: [Airship-discuss] CFP Open! - Open Infrastructure Summit 2020 Message-ID: <7B248318-9F0C-4811-A72F-F03CD7271EC6@openstack.org> We’re excited to announce that the Call for Presentations [1] for the 2020 Open Infrastructure Summit is now open until August 4! During the Summit, you’ll be able to join the people building and operating open infrastructure. Submit sessions featuring projects including Airship, Ansible, Ceph, Kata Containers, Kubernetes, ONAP, OpenStack, OPNFV, StarlingX and Zuul! 2020 Tracks • 5G, NFV & Edge • AI, Machine Learning & HPC • CI/CD • Container Infrastructure • Getting Started • Hands-on Workshops • Open Development • Private & Hybrid Cloud • Public Cloud • Security Types of sessions Presentations; demos encouraged Panel Discussions Lightning Talks If your talk is not selected for the official track schedule, we may reach out to have you present it as a Lightning Talk during the Summit in a shorter 10-15 minute format SUBMIT YOUR PRESENTATION [1] - Deadline August 4, 2020 Summit CFP is only for presentation, panel, and workshop submissions. The content submission process for the Forum and Project Teams Gathering (PTG) will be managed separately in the upcoming months. Programming Committee nominations are also now open. The Programming Committee helps select sessions from the CFP for the Summit schedule. Nominate yourself or or someone else for the Programming Committee [2] before July 10, 2020 and help us program the Summit! Registration and sponsorship coming soon! For sponsorship inquiries, please email kendall at openstack.org . Please email speakersupport at openstack.org with any CFP questions or feedback. Thanks, Ashlee [1] cfp.openstack.org [2] https://openstackfoundation.formstack.com/forms/programmingcommitteenom_summit2020 Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Thu Jul 2 16:55:47 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Thu, 2 Jul 2020 11:55:47 -0500 Subject: [Airship-discuss] [2020 Summit] Programming Committee Nominations Open In-Reply-To: <97832365-8405-4277-BFA6-64BB9F9C1F43@openstack.org> References: <97832365-8405-4277-BFA6-64BB9F9C1F43@openstack.org> Message-ID: <576987C3-647F-43C0-AE6E-F4F3C189DCE4@openstack.org> Hi everyone, Just a reminder that Programming Committee nominations for the 2020 Open Infrastructure Summit are open. If you’re an expert in any of the below categories, and would like to help program the Summit content, please fill out this form to nominate yourself or someone else: https://openstackfoundation.formstack.com/forms/programmingcommitteenom_summit2020 Thanks! Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation > On Jun 24, 2020, at 12:06 PM, Ashlee Ferguson wrote: > > Programming Committee nominations for the 2020 Open Infrastructure Summit are open! > > Programming Committees for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: > • Help the Summit team put together the best possible content based on your subject matter expertise > • Promote the individual Tracks within your networks > • Review the submissions and Community voting results in your particular Track > • Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit > • Ensure diversity of speakers and companies represented in your Track > • Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences > > 2020 Summit Tracks: > • 5G, NFV & Edge > • AI, Machine Learning & HPC > • CI/CD > • Container Infrastructure > • Getting Started > • Hands-on Workshops > • Open Development > • Private & Hybrid Cloud > • Public Cloud > • Security > > If you’re interested in nominating yourself or someone else to be a member of the Summit Programming Committee for a specific Track, please fill out the nomination form[1]. Nominations will close on July 10, 2020. > > NOMINATION FORM[1] > > Programming Committee selections will occur before we open the Call for Presentations (CFP) to receive presentations so that the Committees can host office hours to consult on submissions, and help promote the event. > > The CFP will be open July 1 - August 4, 2020. > > Please email speakersupport at openstack.org with any questions or feedback. > > Cheers, > Ashlee > > [1] https://openstackfoundation.formstack.com/forms/programmingcommitteenom_summit2020 > > > Ashlee Ferguson > Community & Events Coordinator > OpenStack Foundation > > > _______________________________________________ > 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 amy at demarco.com Thu Jul 2 21:22:57 2020 From: amy at demarco.com (Amy Marrich) Date: Thu, 2 Jul 2020 16:22:57 -0500 Subject: [Airship-discuss] [Diversity] Diversity & Inclusion WG Meeting 7/6 Message-ID: The Diversity & Inclusion WG invites members of all OSF projects to our next meeting Monday, July 6th, at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. We will be discussing changing our Wiki page to reflect the broader OSF projects and communities so that the page reflects our mission. Please feel free to add any other topics you wish to discuss at the meeting. Thanks, Amy (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Mon Jul 6 14:04:00 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 6 Jul 2020 14:04:00 +0000 Subject: [Airship-discuss] [sig][yaml] Canceling Monday July 6. Meeting Message-ID: All, SIG YAML Etherpad is empty and although there are a few topics we can continue discussing, some key people are out. Will continue our discussion next week. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Tue Jul 7 14:24:11 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 7 Jul 2020 14:24:11 +0000 Subject: [Airship-discuss] CFP Open! - Open Infrastructure Summit 2020 In-Reply-To: <7B248318-9F0C-4811-A72F-F03CD7271EC6@openstack.org> References: <7B248318-9F0C-4811-A72F-F03CD7271EC6@openstack.org> Message-ID: I wanted to bump this to make sure folks saw it, following the US holiday. CFP is open (till Aug 5) for the Fall Open Infra Summit – see below for details! From: Ashlee Ferguson Sent: Wednesday, July 1, 2020 12:27 PM To: foundation at lists.openstack.org; community at lists.openstack.org; marketing at lists.openstack.org; airship-discuss at lists.airshipit.org; openinfralabs at lists.opendev.org Subject: [Airship-discuss] CFP Open! - Open Infrastructure Summit 2020 We’re excited to announce that the Call for Presentations [1] for the 2020 Open Infrastructure Summit is now open until August 4! During the Summit, you’ll be able to join the people building and operating open infrastructure. Submit sessions featuring projects including Airship, Ansible, Ceph, Kata Containers, Kubernetes, ONAP, OpenStack, OPNFV, StarlingX and Zuul! 2020 Tracks • 5G, NFV & Edge • AI, Machine Learning & HPC • CI/CD • Container Infrastructure • Getting Started • Hands-on Workshops • Open Development • Private & Hybrid Cloud • Public Cloud • Security Types of sessions * Presentations; demos encouraged * Panel Discussions * Lightning Talks * If your talk is not selected for the official track schedule, we may reach out to have you present it as a Lightning Talk during the Summit in a shorter 10-15 minute format SUBMIT YOUR PRESENTATION [1] - Deadline August 4, 2020 Summit CFP is only for presentation, panel, and workshop submissions. The content submission process for the Forum and Project Teams Gathering (PTG) will be managed separately in the upcoming months. Programming Committee nominations are also now open. The Programming Committee helps select sessions from the CFP for the Summit schedule. Nominate yourself or or someone else for the Programming Committee [2] before July 10, 2020 and help us program the Summit! Registration and sponsorship coming soon! For sponsorship inquiries, please email kendall at openstack.org. Please email speakersupport at openstack.org with any CFP questions or feedback. Thanks, Ashlee [1] cfp.openstack.org [2] https://openstackfoundation.formstack.com/forms/programmingcommitteenom_summit2020 Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Tue Jul 7 14:27:07 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 7 Jul 2020 14:27:07 +0000 Subject: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team In-Reply-To: References: Message-ID: <68b538e014924bb48da42f995e6da5ba@att.com> Bumping Nishant's request for feedback, since some folks were out on vacation last week. The WC would like to implement the Airship 1 core team plan below on July 15th, if the broader community is in favor of it. Thanks, Matt From: KUMAR, NISHANT Sent: Monday, June 29, 2020 4:28 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello Airship Community, The Working Committee has been looking for a way to address core reviewer team challenges for the Airship 1 projects. Previously, the Airship 1 projects were split out into multiple core teams due to the large amount of active development and subject matter expertise in each of them. At this point, Airship 1 development is much lighter and a smaller group of developers are owning the responsibility end to end. The Working Committee proposes: o Creating a new "Airship 1" core reviewer team o Membership in the new team would be composed of core reviewers from the current Airship 1 core teams, who have done Airship 1 code reviews in the last 12 months o Following that, the new core team would be able to nominate/vote in additional members as appropriate per usual process. The WC is seeking feedback from the community. If this plan is supported by the community, the WC plans to put it into effect on July 15th. Regards, Nishant -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.w.hughes at accenture.com Tue Jul 7 14:28:55 2020 From: alexander.w.hughes at accenture.com (Hughes, Alexander W.) Date: Tue, 7 Jul 2020 14:28:55 +0000 Subject: [Airship-discuss] [External] Re: Proposal of creating "Airship 1" core reviewer team In-Reply-To: <68b538e014924bb48da42f995e6da5ba@att.com> References: <68b538e014924bb48da42f995e6da5ba@att.com> Message-ID: +1 to the proposal Regards, Alexander Hughes From: MCEUEN, MATT Sent: Tuesday, July 7, 2020 10:27 AM To: KUMAR, NISHANT ; airship-discuss at lists.airshipit.org Subject: [External] Re: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments. ________________________________ Bumping Nishant's request for feedback, since some folks were out on vacation last week. The WC would like to implement the Airship 1 core team plan below on July 15th, if the broader community is in favor of it. Thanks, Matt From: KUMAR, NISHANT > Sent: Monday, June 29, 2020 4:28 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello Airship Community, The Working Committee has been looking for a way to address core reviewer team challenges for the Airship 1 projects. Previously, the Airship 1 projects were split out into multiple core teams due to the large amount of active development and subject matter expertise in each of them. At this point, Airship 1 development is much lighter and a smaller group of developers are owning the responsibility end to end. The Working Committee proposes: o Creating a new "Airship 1" core reviewer team o Membership in the new team would be composed of core reviewers from the current Airship 1 core teams, who have done Airship 1 code reviews in the last 12 months o Following that, the new core team would be able to nominate/vote in additional members as appropriate per usual process. The WC is seeking feedback from the community. If this plan is supported by the community, the WC plans to put it into effect on July 15th. Regards, Nishant ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Thu Jul 9 15:21:46 2020 From: paye600 at gmail.com (Roman Gorshunov) Date: Thu, 9 Jul 2020 17:21:46 +0200 Subject: [Airship-discuss] CI: airshipctl jobs, important information for developers and cores Message-ID: <803A4616-FB8F-46DE-9D00-3B70F4D6D9D7@gmail.com> Dear airshipctl developers, Dear airshipctl cores (in Bcc), As of now we have limited compute capacity available for us trough OpenDev infra to run `airship-airshipctl-gate-script-runner-test` end-to-end CI job. Roughly only 20-30% of test instance launch attempts succeed, other attempts fail. This job is now set to be non-voting to allow you to continue development and merge code to the master. The cloud provider (essentially physical person, not a business) which was generously donating us resources has HVAC failure and would be out of service for quite a while with no estimates to recovery yet. Please, try to decrease workload imposed onto CI and do as much testing as possible locally, and only then pushing changes to Gerrit. Please, rebase on latest master all your work-in-progress patches. Latest master has a decreased number of jobs IMPORTANT INFORMATION Cores, Before mergeing code to master, make sure that there is at least once succesfull run of `airship-airshipctl-gate-script-runner-test` job (green SUCCESS). We are working to get more compute resources into Zuul nodepool to let us run our CI workloads with voting. Thank you. Best regards, Roman Gorshunov From ashlee at openstack.org Fri Jul 10 15:48:21 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Fri, 10 Jul 2020 10:48:21 -0500 Subject: [Airship-discuss] OpenDev: Hardware Automation Message-ID: <0AEC274E-0B26-42A6-A0AC-1DBD6AB6932B@openstack.org> Hi everyone, If you haven’t head yet, we’re doing a virtual event called OpenDev, July 20 - 22 (13:00 - 16:00 UTC/ 8:00 - 11:00am CDT each day), focused around Hardware Automation. This is a discussion-based event centered around end-to-end hardware provisioning lifecycle for baremetal / cradle to grave for hypervisors, consuming baremetal infrastructure to provision cloud based workloads, and networking. These topics are obviously relevant to this community, so I wanted to make sure you all had it on your calendar! It’d be great to have perspectives from the Airship team in the discussions. Feel free to pass this along to your teams as well. Here is more information about the event as well as the schedule . You can register here . Let me know if you have any questions. Thanks! Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Fri Jul 10 17:55:42 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 10 Jul 2020 17:55:42 +0000 Subject: [Airship-discuss] [sig][ui]Meeting Dates change Message-ID: <3E6CAD6D-978C-498D-A832-F7E067998B68@att.com> As discussed in the UI meeting today. We will move to a bi-weekly meeting. Every other Fri 12:00 CDT / 17:00 UTC At https://attcorp.webex.com/attcorp/j.php?MTID=mc721b28407bf8e8d1043fb6c6f7e70b2 Notes & Agenda at: https://etherpad.openstack.org/p/Airship_UI Next meeting will be July 24, 2020 Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dt241s at att.com Fri Jul 10 19:13:17 2020 From: dt241s at att.com (THYAGARAJ, DIWAKAR CHITOOR) Date: Fri, 10 Jul 2020 19:13:17 +0000 Subject: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. Message-ID: <71e5a6f09f094336a60f2933e488aa11@att.com> Hi Airship Team, I nominate Jagan Kavva for core reviewer for Airship-Porthole project. He has been instrumental in growing porthole toward maturity and stability, and have assisted with driving code changes and performing code review across various Airship projects. As Airship keeps growing, so too does its project makeup and codebase. It's my belief that the addition of these individuals to the Airship-Porthole core team will help to foster a stronger community around each of those projects. Thanks, Diwakar Thyagaraj -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Fri Jul 10 19:44:00 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Fri, 10 Jul 2020 19:44:00 +0000 Subject: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. In-Reply-To: <71e5a6f09f094336a60f2933e488aa11@att.com> References: <71e5a6f09f094336a60f2933e488aa11@att.com> Message-ID: +1! Thanks, Matt From: THYAGARAJ, DIWAKAR CHITOOR Sent: Friday, July 10, 2020 2:13 PM To: airship-discuss at lists.airshipit.org Cc: SCARBROUGH, BRIAN P ; KAVVA, JAGAN MOHAN REDDY Subject: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hi Airship Team, I nominate Jagan Kavva for core reviewer for Airship-Porthole project. He has been instrumental in growing porthole toward maturity and stability, and have assisted with driving code changes and performing code review across various Airship projects. As Airship keeps growing, so too does its project makeup and codebase. It's my belief that the addition of these individuals to the Airship-Porthole core team will help to foster a stronger community around each of those projects. Thanks, Diwakar Thyagaraj -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sreejith.Punnapuzha at outlook.com Fri Jul 10 19:46:33 2020 From: Sreejith.Punnapuzha at outlook.com (Sreejith Punnapuzha) Date: Fri, 10 Jul 2020 19:46:33 +0000 Subject: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. In-Reply-To: References: <71e5a6f09f094336a60f2933e488aa11@att.com> Message-ID: <00684F22-56D4-45D8-8424-7E413ADA73A7@outlook.com> +1 Thanks and Regards, Sreejith P From: "MCEUEN, MATT" Date: Friday, July 10, 2020 at 2:44 PM To: "THYAGARAJ, DIWAKAR CHITOOR" , "airship-discuss at lists.airshipit.org" Cc: "SCARBROUGH, BRIAN P" , "KAVVA, JAGAN MOHAN REDDY" Subject: Re: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. +1! Thanks, Matt From: THYAGARAJ, DIWAKAR CHITOOR Sent: Friday, July 10, 2020 2:13 PM To: airship-discuss at lists.airshipit.org Cc: SCARBROUGH, BRIAN P ; KAVVA, JAGAN MOHAN REDDY Subject: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hi Airship Team, I nominate Jagan Kavva for core reviewer for Airship-Porthole project. He has been instrumental in growing porthole toward maturity and stability, and have assisted with driving code changes and performing code review across various Airship projects. As Airship keeps growing, so too does its project makeup and codebase. It’s my belief that the addition of these individuals to the Airship-Porthole core team will help to foster a stronger community around each of those projects. Thanks, Diwakar Thyagaraj -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.w.hughes at accenture.com Mon Jul 13 12:33:33 2020 From: alexander.w.hughes at accenture.com (Hughes, Alexander W.) Date: Mon, 13 Jul 2020 12:33:33 +0000 Subject: [Airship-discuss] WC election process kicks off next week Message-ID: Airship community, It's hard to believe it's that time again already. The Technical Committee is preparing to run the election for the 2020-2021 Working Committee (WC) term. All five seats of the WC are up for re-election, and incumbent members may re-nominate. The schedule will be: * July 20-26: Nominations (open to any Airship code contributor who has had changes merged in the last 12 months) * July 27-August 02: Voting (open to Airship project core reviewers) We'll send out an email with more detailed instructions when each of those phases begins. Note that unlike last year, we are running a two-week cycle, rather than three. The WC plays a crucial role in leading the Airship community toward forward-looking use cases and opportunities, in being ambassadors for Airship, and ensuring the project's health and direction are strong. We encourage anyone with interest in these responsibilities to nominate. Regards, The Airship Technical Committee ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sb0601 at att.com Mon Jul 13 13:54:48 2020 From: sb0601 at att.com (BATRA, SUDEEP) Date: Mon, 13 Jul 2020 13:54:48 +0000 Subject: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. Message-ID: <9304104d9c824e93a235031a7375a598@att.com> +1 ---------------------------------------------------------------------- Message: 1 Date: Fri, 10 Jul 2020 19:46:33 +0000 From: Sreejith Punnapuzha To: "MCEUEN, MATT" , "THYAGARAJ, DIWAKAR CHITOOR" , "airship-discuss at lists.airshipit.org" Cc: "SCARBROUGH, BRIAN P" , "KAVVA, JAGAN MOHAN REDDY" Subject: Re: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. Message-ID: <00684F22-56D4-45D8-8424-7E413ADA73A7 at outlook.com> Content-Type: text/plain; charset="utf-8" +1 Thanks and Regards, Sreejith P From: "MCEUEN, MATT" Date: Friday, July 10, 2020 at 2:44 PM To: "THYAGARAJ, DIWAKAR CHITOOR" , "airship-discuss at lists.airshipit.org" Cc: "SCARBROUGH, BRIAN P" , "KAVVA, JAGAN MOHAN REDDY" Subject: Re: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. +1! Thanks, Matt From: THYAGARAJ, DIWAKAR CHITOOR Sent: Friday, July 10, 2020 2:13 PM To: airship-discuss at lists.airshipit.org Cc: SCARBROUGH, BRIAN P ; KAVVA, JAGAN MOHAN REDDY Subject: [Airship-discuss] Nominate Jagan Mohan Reddy Kavva for Airship-porthole Core. ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hi Airship Team, I nominate Jagan Kavva for core reviewer for Airship-Porthole project. He has been instrumental in growing porthole toward maturity and stability, and have assisted with driving code changes and performing code review across various Airship projects. As Airship keeps growing, so too does its project makeup and codebase. It’s my belief that the addition of these individuals to the Airship-Porthole core team will help to foster a stronger community around each of those projects. Thanks, Diwakar Thyagaraj -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=rzf9M1wTOD1HwHGpyYsQuWbIQUvkmvC45JFH3AlgFEY&m=XiznfXxzzLlmcwVTNZKULPv8DNvySCIlnF9JVIazm-k&s=V7qB4jM7IAIZ0pe--f9RRu6L_vvIYHArQtAcILtQEts&e= ------------------------------ End of Airship-discuss Digest, Vol 26, Issue 8 ********************************************** From Alexander.Hughes at pm.me Mon Jul 13 15:30:12 2020 From: Alexander.Hughes at pm.me (Alexander Hughes) Date: Mon, 13 Jul 2020 15:30:12 +0000 Subject: [Airship-discuss] WC election process kicks off next week Message-ID: Airship community, It's hard to believe it's that time again already. The Technical Committee is preparing to run the election for the 2020-2021 Working Committee (WC) term. All five seats of the WC are up for re-election, and incumbent members may re-nominate. The schedule will be: * July 20-26: Nominations (open to any Airship code contributor who has had changes merged in the last 12 months) * July 27-August 02: Voting (open to Airship project core reviewers) We'll send out an email with more detailed instructions when each of those phases begins. Note that unlike last year, we are running a two-week cycle, rather than three. The WC plays a crucial role in leading the Airship community toward forward-looking use cases and opportunities, in being ambassadors for Airship, and ensuring the project's health and direction are strong. We encourage anyone with interest in these responsibilities to nominate. Regards, The Airship Technical Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Mon Jul 13 20:07:51 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 13 Jul 2020 20:07:51 +0000 Subject: [Airship-discuss] Airship Design Call - Tuesday July 14th - CANCELING Message-ID: There is no topics in the etherpad. Canceling the meeting tomorrow. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Thu Jul 16 13:05:20 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 16 Jul 2020 13:05:20 +0000 Subject: [Airship-discuss] Airship Design Call - Thursday July 16 - Cancelled Message-ID: <293D29BD-60B9-4F90-AA7B-DDB486D08685@att.com> There are no topics on the Etherpad for Today. Will cancel the call. On Tuesday, let’s do a retrospective. Gain a clear understanding of where we are . Will add the details for the discussion I expect on the Etherpad. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Thu Jul 16 21:38:14 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 16 Jul 2020 21:38:14 +0000 Subject: [Airship-discuss] [External] Re: Proposal of creating "Airship 1" core reviewer team In-Reply-To: References: <68b538e014924bb48da42f995e6da5ba@att.com> Message-ID: <0bc18e8d9aa84ea49bb11989b36910cc@att.com> Thanks everyone, this has been completed. The combined Airship 1 core team was implemented using the existing "airship-core" group, to avoid any review interruption. The change affects the following Airship 1 projects: * Armada * Deckhand * Divingbell * Drydock * MaaS * Pegleg * Promenade * Shipyard All pre-existing Airship 1 core team members have been added to the consolidated group, since all have been active reviewers to A1 projects in the last 12 months (thanks, folks!). The exception is Matt Carter, who appears to no longer be in the backing database, and so couldn't be added to airship-core. Please let the Working Committee know if you have any questions. Thanks! Matt From: Hughes, Alexander W. Sent: Tuesday, July 7, 2020 9:29 AM To: MCEUEN, MATT ; KUMAR, NISHANT ; airship-discuss at lists.airshipit.org Subject: RE: [External] Re: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team +1 to the proposal Regards, Alexander Hughes From: MCEUEN, MATT > Sent: Tuesday, July 7, 2020 10:27 AM To: KUMAR, NISHANT >; airship-discuss at lists.airshipit.org Subject: [External] Re: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments. ________________________________ Bumping Nishant's request for feedback, since some folks were out on vacation last week. The WC would like to implement the Airship 1 core team plan below on July 15th, if the broader community is in favor of it. Thanks, Matt From: KUMAR, NISHANT > Sent: Monday, June 29, 2020 4:28 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Proposal of creating "Airship 1" core reviewer team ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello Airship Community, The Working Committee has been looking for a way to address core reviewer team challenges for the Airship 1 projects. Previously, the Airship 1 projects were split out into multiple core teams due to the large amount of active development and subject matter expertise in each of them. At this point, Airship 1 development is much lighter and a smaller group of developers are owning the responsibility end to end. The Working Committee proposes: o Creating a new "Airship 1" core reviewer team o Membership in the new team would be composed of core reviewers from the current Airship 1 core teams, who have done Airship 1 code reviews in the last 12 months o Following that, the new core team would be able to nominate/vote in additional members as appropriate per usual process. The WC is seeking feedback from the community. If this plan is supported by the community, the WC plans to put it into effect on July 15th. Regards, Nishant ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.w.hughes at accenture.com Tue Jul 21 12:37:04 2020 From: alexander.w.hughes at accenture.com (Hughes, Alexander W.) Date: Tue, 21 Jul 2020 12:37:04 +0000 Subject: [Airship-discuss] Airship Working Committee Nominations Message-ID: Hello Airship Community, Nominations for the Airship Working Committee are now open and will remain open until EOD July 26th. All nominations must be submitted as a text file to the airship/election repository, as explained in [1]. Please make sure to follow the candidacy file naming convention: candidates/2020/WC/. All active code contributors to the Airship project (who have had changes merged in the last 12 months) are eligible to run for the Working Committee. Additional information about the nomination process can be found here [1]. Shortly after election officials approve candidates, they will be listed here [2]. Voting will occur via ballots emailed to the electorate (current Airship project core reviewers) on July 27th. The Technical Committee requests the balloter to confirm their email addresses in gerrit before July 26th, so ballots are emailed to the correct email addresses. Regards, Airship Technical Committee [1]: https://docs.airshipit.org/election/procedures.html [2]: https://docs.airshipit.org/election/results/2020/wc.html ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Alexander.Hughes at pm.me Tue Jul 21 13:39:22 2020 From: Alexander.Hughes at pm.me (Alexander Hughes) Date: Tue, 21 Jul 2020 13:39:22 +0000 Subject: [Airship-discuss] 2020-2021 Working Committee Nominations Message-ID: <4bSv0jjWDhQtJT-eRXtbm9iq73rpr7izdRD1PGnJaNT66T5p5YOVQBmSllrXL_v4ZxDHoLsUfvj-bSffxodTZnU2-qveapOrnDg1iDV65aU=@pm.me> Hello Airship Community, Nominations for the Airship Working Committee are now open and will remain open until EOD July 26th. All nominations must be submitted as a text file to the airship/election repository, as explained in [1]. Please make sure to follow the candidacy file naming convention: candidates/2020/WC/. All active code contributors to the Airship project (who have had changes merged in the last 12 months) are eligible to run for the Working Committee. Additional information about the nomination process can be found here [1]. Shortly after election officials approve candidates, they will be listed here [2]. Voting will occur via ballots emailed to the electorate (current Airship project core reviewers) on July 27th. The Technical Committee requests the balloter to confirm their email addresses in gerrit before July 26th, so ballots are emailed to the correct email addresses. Regards, Airship Technical Committee [1]: https://docs.airshipit.org/election/procedures.html [2]: https://docs.airshipit.org/election/results/2020/wc.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Tue Jul 21 21:47:54 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 21 Jul 2020 21:47:54 +0000 Subject: [Airship-discuss] Matt McEuen nominating for the 2020 WC Message-ID: <1b30e049069b4e09982780fe8f8aea23@att.com> Airship community, I'd like to announce my nomination for the 2020 Airship Working Committee election. In the past year on the Working Committee, I have worked to establish the Committee as a source of progress within the Airship community, to listen to feedback from the community, and to make life for our developers as painless as possible. I have overseen Airship's graduation to a full OpenStack Foundation project, and have played a key role in planning an organizing Airship events big and small. I'm nominating for the upcoming term to continue this work and to ensure that we achieve our Airship 2.0 goals. I have been working in the Airship community since its inception, in a variety of different formal and informal roles. I have contributed to the development and design of the Airship projects, promoted and communicated the project to potential contributors and operators, and have worked closely with the OpenStack Foundation to ensure Airship is on the right path to become a full OSF project. Prior to this, I also served as an engineer and PTL of the OpenStack-Helm project. If elected, my goal for 2020-2021 will be to make it easier to get started with Airship, both as a developer and as an operator. This will require a focus on consumability and ease of use of the product and its manifests, as well as on documentation and clarity of work definition. I believe that both of these factors will be key to Airship's success, and has the potential to increase Airship's user base and use cases in very interesting ways. Thank you for your consideration! Matt McEuen -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Wed Jul 22 16:25:35 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 22 Jul 2020 16:25:35 +0000 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn Message-ID: BLUF: current Treasuremap core team members, please respond with +1/-1 by 7/29. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! I would like to propose Kostiantyn Kalynovskyi for the Treasuremap core reviewer team. He has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Kostiantyn will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. Thanks! Matt From Alexander.Hughes at pm.me Wed Jul 22 16:27:20 2020 From: Alexander.Hughes at pm.me (Alexander Hughes) Date: Wed, 22 Jul 2020 16:27:20 +0000 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn In-Reply-To: References: Message-ID: +1 Regards, Alexander Hughes On Wed, Jul 22, 2020 at 12:25, MCEUEN, MATT wrote: > BLUF: current Treasuremap core team members, please respond with +1/-1 by 7/29. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! > > I would like to propose Kostiantyn Kalynovskyi for the Treasuremap core reviewer team. He has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Kostiantyn will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. > > Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. > > Thanks! > 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 nk613n at att.com Wed Jul 22 16:44:13 2020 From: nk613n at att.com (KUMAR, NISHANT) Date: Wed, 22 Jul 2020 16:44:13 +0000 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn In-Reply-To: References: Message-ID: <8145c9020dd94d2893db1d4b52d7e783@att.com> +1 -----Original Message----- From: MCEUEN, MATT Sent: Wednesday, July 22, 2020 11:26 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. BLUF: current Treasuremap core team members, please respond with +1/-1 by 7/29. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! I would like to propose Kostiantyn Kalynovskyi for the Treasuremap core reviewer team. He has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Kostiantyn will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=1lYApeS3F4_-BtMIxOEuvA&m=9IkzVOu7lJ24f9HYDiWu767Y-55l4lptQmWZehMhEEo&s=JMRUU0BU57XtGdSgaTydXc1tEfRSP4ynvrM70_Wpbpo&e= From paye600 at gmail.com Wed Jul 22 16:44:56 2020 From: paye600 at gmail.com (Roman Gorshunov) Date: Wed, 22 Jul 2020 18:44:56 +0200 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn In-Reply-To: References: Message-ID: <39045309-6F91-49B8-83DF-B1057D8AB53D@gmail.com> +1 > On 22 Jul 2020, at 18:26, MCEUEN, MATT wrote: > > BLUF: current Treasuremap core team members, please respond with +1/-1 by 7/29. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! > > I would like to propose Kostiantyn Kalynovskyi for the Treasuremap core reviewer team. He has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Kostiantyn will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. > > Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. > > Thanks! > Matt > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From ca846m at att.com Wed Jul 22 16:45:14 2020 From: ca846m at att.com (ANDERSON, CRAIG) Date: Wed, 22 Jul 2020 16:45:14 +0000 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn In-Reply-To: References: Message-ID: <3fc35a8f9d7743d2a711d20420c8e844@att.com> +1 -----Original Message----- From: MCEUEN, MATT Sent: Wednesday, July 22, 2020 9:26 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. BLUF: current Treasuremap core team members, please respond with +1/-1 by 7/29. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! I would like to propose Kostiantyn Kalynovskyi for the Treasuremap core reviewer team. He has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Kostiantyn will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=aimn2OylFgog_5_aS85wtQ&m=2WGrTee312sgXeQZSDBhslas77eHDuULpGDAykIZbgM&s=ZM2eOP4ZZ6ErlOyMP-BL7ekNSZ20xajhlLM_rjF4fqw&e= From petebirley at googlemail.com Wed Jul 22 16:51:55 2020 From: petebirley at googlemail.com (Pete Birley) Date: Wed, 22 Jul 2020 11:51:55 -0500 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn In-Reply-To: References: Message-ID: +1 On Wed, 22 Jul 2020 at 11:27, MCEUEN, MATT wrote: > BLUF: current Treasuremap core team members, please respond with +1/-1 by > 7/29. Note: currently the Treasuremap core team consists of the > airship-core (aka Airship 1) team, so if you're in that group, this is for > you! > > I would like to propose Kostiantyn Kalynovskyi for the Treasuremap core > reviewer team. He has been very active on airshipctl yaml management > functionality, and the manifests themselves, from code review and > development perspective. As Airship 2 manifests will increasingly be > authored in the Treasuremap repo (starting in the v2 branch), Kostiantyn > will be well positioned to guide manifest authoring in the right direction, > and to help integrate airshipctl appropriately into the larger Airship > ecosystem. > > Per our core nomination/approval conventions, I request that current > Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a > majority vote prior to 7/29 we can call it then. > > Thanks! > 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 aw442m at att.com Wed Jul 22 17:01:57 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Wed, 22 Jul 2020 17:01:57 +0000 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn In-Reply-To: References: Message-ID: <8aca45f3b2c64303b94e5b0660be80ff@att.com> +1 -----Original Message----- From: MCEUEN, MATT Sent: Wednesday, July 22, 2020 11:26 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. BLUF: current Treasuremap core team members, please respond with +1/-1 by 7/29. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! I would like to propose Kostiantyn Kalynovskyi for the Treasuremap core reviewer team. He has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Kostiantyn will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=PhoDOFNqeAuEA29HCtwzVcTGnrbIvubFG152cw193QA&m=YIYXhOYK4w038be0qv0Hb8z_z90jiFRaQ52EQOC2Fko&s=QvPf_TNxWmcWbUXpXdig2ai3-QHsnFF1V3VPf9pB1-g&e= From MM9745 at att.com Wed Jul 22 19:40:24 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 22 Jul 2020 19:40:24 +0000 Subject: [Airship-discuss] Airshipctl Core Reviewer nomination: Stas Message-ID: BLUF: current airshipctl core team members, please respond with +1/-1 by 7/29. I would like to propose Stas Egorov for the airshipctl core reviewer team. Stas has been an active member of the Airship community for around a year and a half, and in 2020 has maintained a strong focus on airshipctl from a quality code review perspective, and a feature development perspective. Stas has demonstrated an ability to guide development in the right direction, and clearly cares about Airship being a high-quality project. I believe Stas would add a lot of value to the team as a core reviewer, and help us to get patches ship-shape and merged in a timely fashion. Per our core nomination/approval conventions, I request that current airshipctl core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. Thanks! Matt From aw442m at att.com Wed Jul 22 19:55:58 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Wed, 22 Jul 2020 19:55:58 +0000 Subject: [Airship-discuss] Airshipctl Core Reviewer nomination: Stas In-Reply-To: References: Message-ID: +1 -----Original Message----- From: MCEUEN, MATT Sent: Wednesday, July 22, 2020 2:40 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airshipctl Core Reviewer nomination: Stas *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. BLUF: current airshipctl core team members, please respond with +1/-1 by 7/29. I would like to propose Stas Egorov for the airshipctl core reviewer team. Stas has been an active member of the Airship community for around a year and a half, and in 2020 has maintained a strong focus on airshipctl from a quality code review perspective, and a feature development perspective. Stas has demonstrated an ability to guide development in the right direction, and clearly cares about Airship being a high-quality project. I believe Stas would add a lot of value to the team as a core reviewer, and help us to get patches ship-shape and merged in a timely fashion. Per our core nomination/approval conventions, I request that current airshipctl core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=PhoDOFNqeAuEA29HCtwzVcTGnrbIvubFG152cw193QA&m=QbCMTp2lTmkKIecuCrcPDGHWGxMQ1mFMgDZTgGK_Cj0&s=ULKwYTk47Tpxy2rE8jIyYOJuIKlKZEcf5nb1efCSBew&e= From aw442m at att.com Wed Jul 22 21:12:52 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Wed, 22 Jul 2020 21:12:52 +0000 Subject: [Airship-discuss] Announcing My Nomination for the 2020 Airship Working Committee Message-ID: <8990a7b106bc413b95cd33d19f0348f8@att.com> Greetings Airship community! My name is Drew Walters, and I am excited to announce my self-nomination for re-election to the Airship Working Committee. It has been my pleasure to serve the community as a member of the Airship Working Committee this past year. During the last year, I have had the privilege of working with the rest of the committee, as well as the Technical Committee, to: - Establish the Airship Vulnerability Management Process [0] - Improve the developer workflow by configuring GitHub issues - Improve the visibility and accessibility of our documentation by migrating it from ReadtheDocs to docs.airshipit.org [1] - Reduce the Airship 1 review time by reuniting the Airship 1 core teams - Host our weekly IRC meetings - Ensure that Airship continues to mature and remain accessible to interested parties - Serve as an ambassador to the OpenStack Foundation While we have seen many improvements over the last year, I identify several new challenges ahead of us. 1. As Airship 2 matures from beta to full release, the Working Committee needs to identify places where Airship is not approachable by surveying new adopters. 2. GitHub issue controls (e.g. closing, labeling, and assigning issues) need to be accessible to Airship developers. 3. The Working Committee needs to assist the community in finding additional ways to improve the reliability of our continuous-integration systems. 4. The Working Committee must continue to survey developers, operators, and core reviewers to identify areas where we can simplify our obligations. Core reviewers, I am asking you for the opportunity to address these challenges and to ensure the continued smooth operation of the Airship project over the next year. Thank you for your consideration this election! Drew Walters [0] https://docs.airshipit.org/learn/vulnerabilities.html [1] https://docs.airshipit.org/index.html From am495p at att.com Wed Jul 22 21:44:24 2020 From: am495p at att.com (MAHMOUDI, AHMAD) Date: Wed, 22 Jul 2020 21:44:24 +0000 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn In-Reply-To: References: Message-ID: +1 -----Original Message----- From: MCEUEN, MATT Sent: Wednesday, July 22, 2020 11:26 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Kostiantyn *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. BLUF: current Treasuremap core team members, please respond with +1/-1 by 7/29. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! I would like to propose Kostiantyn Kalynovskyi for the Treasuremap core reviewer team. He has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Kostiantyn will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=by72G3s3S_fwTMMBYueNpg&m=wvSdBACNVOhp_vRW_ybXeIXD8LtQBrnQmrUeTEgSbeo&s=uNZlj8fR5N5lrYLUV3RBxzQjwKsONipAKk_y5CCjMLs&e= From paye600 at gmail.com Thu Jul 23 06:13:32 2020 From: paye600 at gmail.com (Roman Gorshunov) Date: Thu, 23 Jul 2020 08:13:32 +0200 Subject: [Airship-discuss] Airshipctl Core Reviewer nomination: Stas In-Reply-To: References: Message-ID: <391BCBE3-0CFA-4353-B600-87E00870A7A8@gmail.com> +1 > On 22 Jul 2020, at 21:56, WALTERS, ANDREW wrote: > > +1 > > -----Original Message----- > From: MCEUEN, MATT > Sent: Wednesday, July 22, 2020 2:40 PM > To: airship-discuss at lists.airshipit.org > Subject: [Airship-discuss] Airshipctl Core Reviewer nomination: Stas > > *** Security Advisory: This Message Originated Outside of AT&T ***. > Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. > > BLUF: current airshipctl core team members, please respond with +1/-1 by 7/29. > > I would like to propose Stas Egorov for the airshipctl core reviewer team. Stas has been an active member of the Airship community for around a year and a half, and in 2020 has maintained a strong focus on airshipctl from a quality code review perspective, and a feature development perspective. Stas has demonstrated an ability to guide development in the right direction, and clearly cares about Airship being a high-quality project. I believe Stas would add a lot of value to the team as a core reviewer, and help us to get patches ship-shape and merged in a timely fashion. > > Per our core nomination/approval conventions, I request that current airshipctl core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. > > Thanks! > Matt > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=PhoDOFNqeAuEA29HCtwzVcTGnrbIvubFG152cw193QA&m=QbCMTp2lTmkKIecuCrcPDGHWGxMQ1mFMgDZTgGK_Cj0&s=ULKwYTk47Tpxy2rE8jIyYOJuIKlKZEcf5nb1efCSBew&e= > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From as3525 at att.com Thu Jul 23 13:27:55 2020 From: as3525 at att.com (SCHIEFELBEIN, ANDREW) Date: Thu, 23 Jul 2020 13:27:55 +0000 Subject: [Airship-discuss] Announcing My Nomination for the 2020 Airship Working Committee In-Reply-To: <8990a7b106bc413b95cd33d19f0348f8@att.com> References: <8990a7b106bc413b95cd33d19f0348f8@att.com> Message-ID: <7326a5a776de489fb99aec53610949ac@att.com> +1 -----Original Message----- From: WALTERS, ANDREW Sent: Wednesday, July 22, 2020 4:13 PM To: airship-discuss at lists.airshipit.org Cc: BAILEY, ALEXANDER ; jtwill98 at yahoo.com; Alexey Odinokov ; alexander.hughes at pm.me; kire at kth.se Subject: [Airship-discuss] Announcing My Nomination for the 2020 Airship Working Committee *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Greetings Airship community! My name is Drew Walters, and I am excited to announce my self-nomination for re-election to the Airship Working Committee. It has been my pleasure to serve the community as a member of the Airship Working Committee this past year. During the last year, I have had the privilege of working with the rest of the committee, as well as the Technical Committee, to: - Establish the Airship Vulnerability Management Process [0] - Improve the developer workflow by configuring GitHub issues - Improve the visibility and accessibility of our documentation by migrating it from ReadtheDocs to docs.airshipit.org [1] - Reduce the Airship 1 review time by reuniting the Airship 1 core teams - Host our weekly IRC meetings - Ensure that Airship continues to mature and remain accessible to interested parties - Serve as an ambassador to the OpenStack Foundation While we have seen many improvements over the last year, I identify several new challenges ahead of us. 1. As Airship 2 matures from beta to full release, the Working Committee needs to identify places where Airship is not approachable by surveying new adopters. 2. GitHub issue controls (e.g. closing, labeling, and assigning issues) need to be accessible to Airship developers. 3. The Working Committee needs to assist the community in finding additional ways to improve the reliability of our continuous-integration systems. 4. The Working Committee must continue to survey developers, operators, and core reviewers to identify areas where we can simplify our obligations. Core reviewers, I am asking you for the opportunity to address these challenges and to ensure the continued smooth operation of the Airship project over the next year. Thank you for your consideration this election! Drew Walters [0] https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.airshipit.org_learn_vulnerabilities.html&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=CSkIkQ3UMXw1iEknExFU-w&m=-wOm12bSyvJwiYZQIwRKdgmxzNTgzjHk38ZvFYPZ3d8&s=oY7Iu1vT7PLEJjo49u975m1UKtt0S6_MEBJllP7smDA&e= [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.airshipit.org_index.html&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=CSkIkQ3UMXw1iEknExFU-w&m=-wOm12bSyvJwiYZQIwRKdgmxzNTgzjHk38ZvFYPZ3d8&s=txLPLny6py409PD0ZbszVJkiLhubduCnhSd2MykKGww&e= _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=CSkIkQ3UMXw1iEknExFU-w&m=-wOm12bSyvJwiYZQIwRKdgmxzNTgzjHk38ZvFYPZ3d8&s=Lq9U0moRGuZ7QyWzcQQ4uo0ELXmB7j8ml81QQb1nL_Q&e= From dt241s at att.com Thu Jul 23 13:34:36 2020 From: dt241s at att.com (THYAGARAJ, DIWAKAR CHITOOR) Date: Thu, 23 Jul 2020 13:34:36 +0000 Subject: [Airship-discuss] Airshipctl Core Reviewer nomination: Stas In-Reply-To: References: Message-ID: <964d7a544f394f1b8e28f6caa9e7c52d@att.com> +1 Thanks, Diwakar Thyagaraj -----Original Message----- From: MCEUEN, MATT Sent: Wednesday, July 22, 2020 2:40 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airshipctl Core Reviewer nomination: Stas *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. BLUF: current airshipctl core team members, please respond with +1/-1 by 7/29. I would like to propose Stas Egorov for the airshipctl core reviewer team. Stas has been an active member of the Airship community for around a year and a half, and in 2020 has maintained a strong focus on airshipctl from a quality code review perspective, and a feature development perspective. Stas has demonstrated an ability to guide development in the right direction, and clearly cares about Airship being a high-quality project. I believe Stas would add a lot of value to the team as a core reviewer, and help us to get patches ship-shape and merged in a timely fashion. Per our core nomination/approval conventions, I request that current airshipctl core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 7/29 we can call it then. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=wkPPOhqD46u8zLuDs0Fr7Q&m=_Evy_DS6TGonpFNduOqAU6pzJBriD0N9gvDC-KPt5zA&s=lynr7NI0rJhcss-qLvD_Dh7OyVHTzEnX6MLuRxxASM0&e= From dt241s at att.com Thu Jul 23 13:35:11 2020 From: dt241s at att.com (THYAGARAJ, DIWAKAR CHITOOR) Date: Thu, 23 Jul 2020 13:35:11 +0000 Subject: [Airship-discuss] Announcing My Nomination for the 2020 Airship Working Committee In-Reply-To: <8990a7b106bc413b95cd33d19f0348f8@att.com> References: <8990a7b106bc413b95cd33d19f0348f8@att.com> Message-ID: <43dee4eb444145cb9515e8c64b381220@att.com> +1 Thanks, Diwakar Thyagaraj -----Original Message----- From: WALTERS, ANDREW Sent: Wednesday, July 22, 2020 4:13 PM To: airship-discuss at lists.airshipit.org Cc: BAILEY, ALEXANDER ; jtwill98 at yahoo.com; Alexey Odinokov ; alexander.hughes at pm.me; kire at kth.se Subject: [Airship-discuss] Announcing My Nomination for the 2020 Airship Working Committee *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Greetings Airship community! My name is Drew Walters, and I am excited to announce my self-nomination for re-election to the Airship Working Committee. It has been my pleasure to serve the community as a member of the Airship Working Committee this past year. During the last year, I have had the privilege of working with the rest of the committee, as well as the Technical Committee, to: - Establish the Airship Vulnerability Management Process [0] - Improve the developer workflow by configuring GitHub issues - Improve the visibility and accessibility of our documentation by migrating it from ReadtheDocs to docs.airshipit.org [1] - Reduce the Airship 1 review time by reuniting the Airship 1 core teams - Host our weekly IRC meetings - Ensure that Airship continues to mature and remain accessible to interested parties - Serve as an ambassador to the OpenStack Foundation While we have seen many improvements over the last year, I identify several new challenges ahead of us. 1. As Airship 2 matures from beta to full release, the Working Committee needs to identify places where Airship is not approachable by surveying new adopters. 2. GitHub issue controls (e.g. closing, labeling, and assigning issues) need to be accessible to Airship developers. 3. The Working Committee needs to assist the community in finding additional ways to improve the reliability of our continuous-integration systems. 4. The Working Committee must continue to survey developers, operators, and core reviewers to identify areas where we can simplify our obligations. Core reviewers, I am asking you for the opportunity to address these challenges and to ensure the continued smooth operation of the Airship project over the next year. Thank you for your consideration this election! Drew Walters [0] https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.airshipit.org_learn_vulnerabilities.html&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=wkPPOhqD46u8zLuDs0Fr7Q&m=ugK6gcvuXxFAeNr-L9LIiEltRuPmUN7-td_x0yPY9DE&s=gRgl0ASGo2DNYPSF0nnXyI_TFWSwjJCUmxmURlF0zss&e= [1] https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.airshipit.org_index.html&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=wkPPOhqD46u8zLuDs0Fr7Q&m=ugK6gcvuXxFAeNr-L9LIiEltRuPmUN7-td_x0yPY9DE&s=h0qF8zGK59ph61cWNiF3btmIulY8UdNpHg4cyRkutGk&e= _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=wkPPOhqD46u8zLuDs0Fr7Q&m=ugK6gcvuXxFAeNr-L9LIiEltRuPmUN7-td_x0yPY9DE&s=vCHoKU9ko2PlOpithbdM8lragopKoqaS9j7bnJhqwxs&e= From ashlee at openstack.org Thu Jul 23 15:06:24 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Thu, 23 Jul 2020 10:06:24 -0500 Subject: [Airship-discuss] The Open Infrastructure Summit is Going Virtual! Message-ID: <1EC74071-C04F-4F89-A762-A87BBA8B4F9E@openstack.org> Hi everyone, The Open Infrastructure Summit will officially be held virtually, the week of October 19. I know the community has been planning to announce the 2.0 release at the Summit, and we still can! The OSF Marketing team will be reaching out in the upcoming weeks to discuss what that will look like and how we can create visibility for the new features delivered by the community. Emails about project onboarding / updates, PTG, and the Forum will be coming later, but below are ways you can currently get prepared: Register for free and make sure to mark your calendars for October 19 - 23. Get your Summit submission together now! The CFP deadline is August 4 at 11:59pm PT, so start drafting your presentations and panels around Open Infrastructure use cases like AI/Machine Learning, CI/CD, Container Infrastructure, 5G, Edge Computing and of course, Public, Private and Hybrid Clouds. Get your organization some visibility - check out the prospectus and sign up to sponsor the virtual Summit! Executable Sponsorship Contract will be available starting at 10:30am CT on Tuesday, July 28. If you have any questions, please reach out to summit at openstack.org . “See you” in October! Cheers, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From ji5690 at att.com Fri Jul 24 06:21:26 2020 From: ji5690 at att.com (GU, JAMES) Date: Fri, 24 Jul 2020 06:21:26 +0000 Subject: [Airship-discuss] Self Nomination for the 2020 Airship Working Committee Candidacy Message-ID: <2bef2d9f43c646f3a45630ccc8e9da6a@att.com> Hello Airship community, My name is James Gu and I'd like to announce my candidacy for election to the Airship Working Committee. My journey with Airship started in late 2018 when working for SUSE as a product owner/technical lead. I led a team effort of enabling multi Linux distro's in Airship, with the goal to expand Airship's user base. Collaborating with the OpenStack community, the effort had spanned many Airship projects (Treasuremap, Armada, Shipyard, Deckhand, etc.) as well as OpenStack Helm project. Prior to that, I had worked many years in technical leadership role in the private cloud space, including workflow and orchestration, monitoring and metering, HA and disaster recovery. Some work were directly contributed to OpenStack, and other to proprietary technology. At the end of 2019, I became involved in OPNFV Airship project and was elected the PTL in Spring 2020. I work with both the CNTT (Cloud iNfrastructure Telco Taskforce) and OPNFV community to develop Airship Installer as a Reference Implementation of cloud and NFVi, and support the CNTT Reference Conformance Testing and Certification. Some example work includes Treasuremap 1.8 integration in the CNTT OpenStack Reference implementation and investigate the Airship 2.0 POC for CNTT Cloud Native Reference Architecture. I am also involved in Airship 2.0 development when time allows. If I am elected, I would like to act as the bridge between the CNTT, OPNFV and Airship community. CNTT represents the collective voice of the telco operators and vendors. I want to help to feed their requirements and use cases into the Airship community timely and regularly, and influence the Airship 2 to better aligned with the CNTT direction. Some examples include K8s conformance certification and gating, bring your own baremetal/k8s use cases. On the other hand, Airship is AFAIK the only cloud technology designed for telco, supporting both cloud native and OpenStack, and managing from baremetal and up. I want to continue to be an adamant advocate of Airship in the OPNFV and CNTT community, hoping that Airship will have a positive impact on the CNTT's technology direction. I would also want to ensure Airship 2.0 conform to the CNTT Cloud Native reference architecture and implementation specs, and contribute to the CNTT conformance certification and testing. Thank you in advance for your consideration. James Gu From mf4716 at att.com Fri Jul 24 13:29:07 2020 From: mf4716 at att.com (FIX, MICHAEL A) Date: Fri, 24 Jul 2020 13:29:07 +0000 Subject: [Airship-discuss] Self Nomination for the 2020 Airship Working Committee Candidacy In-Reply-To: <2bef2d9f43c646f3a45630ccc8e9da6a@att.com> References: <2bef2d9f43c646f3a45630ccc8e9da6a@att.com> Message-ID: <860c5d625d1f47aca339b5b547ab6ffa@att.com> +1 Having worked alongside James in CNTT, I can vouch for his technical aptitude, attention to detail, and leadership qualities to lead a project/team through discussions and resolution of complex issues. I may not be a voting member, but wanted to express my sincere commendation for James' candidacy. Best, Mike -----Original Message----- From: GU, JAMES Sent: Friday, July 24, 2020 1:21 AM To: airship-discuss at lists.airshipit.org Cc: BAILEY, ALEXANDER ; jtwill98 at yahoo.com; Alexey Odinokov ; alexander.hughes at pm.me; kire at kth.se Subject: [Airship-discuss] Self Nomination for the 2020 Airship Working Committee Candidacy *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello Airship community, My name is James Gu and I'd like to announce my candidacy for election to the Airship Working Committee. My journey with Airship started in late 2018 when working for SUSE as a product owner/technical lead. I led a team effort of enabling multi Linux distro's in Airship, with the goal to expand Airship's user base. Collaborating with the OpenStack community, the effort had spanned many Airship projects (Treasuremap, Armada, Shipyard, Deckhand, etc.) as well as OpenStack Helm project. Prior to that, I had worked many years in technical leadership role in the private cloud space, including workflow and orchestration, monitoring and metering, HA and disaster recovery. Some work were directly contributed to OpenStack, and other to proprietary technology. At the end of 2019, I became involved in OPNFV Airship project and was elected the PTL in Spring 2020. I work with both the CNTT (Cloud iNfrastructure Telco Taskforce) and OPNFV community to develop Airship Installer as a Reference Implementation of cloud and NFVi, and support the CNTT Reference Conformance Testing and Certification. Some example work includes Treasuremap 1.8 integration in the CNTT OpenStack Reference implementation and investigate the Airship 2.0 POC for CNTT Cloud Native Reference Architecture. I am also involved in Airship 2.0 development when time allows. If I am elected, I would like to act as the bridge between the CNTT, OPNFV and Airship community. CNTT represents the collective voice of the telco operators and vendors. I want to help to feed their requirements and use cases into the Airship community timely and regularly, and influence the Airship 2 to better aligned with the CNTT direction. Some examples include K8s conformance certification and gating, bring your own baremetal/k8s use cases. On the other hand, Airship is AFAIK the only cloud technology designed for telco, supporting both cloud native and OpenStack, and managing from baremetal and up. I want to continue to be an adamant advocate of Airship in the OPNFV and CNTT community, hoping that Airship will have a positive impact on the CNTT's technology direction. I would also want to ensure Airship 2.0 conform to the CNTT Cloud Native reference architecture and implementation specs, and contribute to the CNTT conformance certification and testing. Thank you in advance for your consideration. James Gu _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=gFQQXTRy6CRFDx0lDCOVse8y1YkDDhNJl6yBw13GiP0&m=92b2nQDcPiYQgSs-I5t16GZbysPksfvIl35zCsdPD-E&s=Rv3QoaXYY6N-DktOi3dUM7ojfD5qbhjtCCwg2KJqbAw&e= From as3525 at att.com Fri Jul 24 13:33:14 2020 From: as3525 at att.com (SCHIEFELBEIN, ANDREW) Date: Fri, 24 Jul 2020 13:33:14 +0000 Subject: [Airship-discuss] Self Nomination for the 2020 Airship Working Committee Candidacy In-Reply-To: <2bef2d9f43c646f3a45630ccc8e9da6a@att.com> References: <2bef2d9f43c646f3a45630ccc8e9da6a@att.com> Message-ID: +1 -----Original Message----- From: GU, JAMES Sent: Friday, July 24, 2020 1:21 AM To: airship-discuss at lists.airshipit.org Cc: BAILEY, ALEXANDER ; jtwill98 at yahoo.com; Alexey Odinokov ; alexander.hughes at pm.me; kire at kth.se Subject: [Airship-discuss] Self Nomination for the 2020 Airship Working Committee Candidacy *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello Airship community, My name is James Gu and I'd like to announce my candidacy for election to the Airship Working Committee. My journey with Airship started in late 2018 when working for SUSE as a product owner/technical lead. I led a team effort of enabling multi Linux distro's in Airship, with the goal to expand Airship's user base. Collaborating with the OpenStack community, the effort had spanned many Airship projects (Treasuremap, Armada, Shipyard, Deckhand, etc.) as well as OpenStack Helm project. Prior to that, I had worked many years in technical leadership role in the private cloud space, including workflow and orchestration, monitoring and metering, HA and disaster recovery. Some work were directly contributed to OpenStack, and other to proprietary technology. At the end of 2019, I became involved in OPNFV Airship project and was elected the PTL in Spring 2020. I work with both the CNTT (Cloud iNfrastructure Telco Taskforce) and OPNFV community to develop Airship Installer as a Reference Implementation of cloud and NFVi, and support the CNTT Reference Conformance Testing and Certification. Some example work includes Treasuremap 1.8 integration in the CNTT OpenStack Reference implementation and investigate the Airship 2.0 POC for CNTT Cloud Native Reference Architecture. I am also involved in Airship 2.0 development when time allows. If I am elected, I would like to act as the bridge between the CNTT, OPNFV and Airship community. CNTT represents the collective voice of the telco operators and vendors. I want to help to feed their requirements and use cases into the Airship community timely and regularly, and influence the Airship 2 to better aligned with the CNTT direction. Some examples include K8s conformance certification and gating, bring your own baremetal/k8s use cases. On the other hand, Airship is AFAIK the only cloud technology designed for telco, supporting both cloud native and OpenStack, and managing from baremetal and up. I want to continue to be an adamant advocate of Airship in the OPNFV and CNTT community, hoping that Airship will have a positive impact on the CNTT's technology direction. I would also want to ensure Airship 2.0 conform to the CNTT Cloud Native reference architecture and implementation specs, and contribute to the CNTT conformance certification and testing. Thank you in advance for your consideration. James Gu _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=CSkIkQ3UMXw1iEknExFU-w&m=IKxBsyBxZGr97GfdEBLZxK5hJM1bx_-JfaZOajhjFIQ&s=eFoBKddqceNX_v51FkuE2bMByd1qkFdugDIGTH6-4AA&e= From dev.faz at gmail.com Sat Jul 25 07:38:45 2020 From: dev.faz at gmail.com (Fabian Zimmermann) Date: Sat, 25 Jul 2020 09:38:45 +0200 Subject: [Airship-discuss] Any documentation about how to use Airship2? Message-ID: Hi, i would like to evaluate/test airship2, but it seems there is no documentation on how to use airship2, isnt it? Does someone create some notes / docs about how to start? Thanks, Fabian From dukov at mirantis.com Mon Jul 27 06:12:16 2020 From: dukov at mirantis.com (Dmitry Ukov) Date: Mon, 27 Jul 2020 10:12:16 +0400 Subject: [Airship-discuss] Airshipctl Core Reviewer nomination: Stas In-Reply-To: <964d7a544f394f1b8e28f6caa9e7c52d@att.com> References: <964d7a544f394f1b8e28f6caa9e7c52d@att.com> Message-ID: +1 On Thu, Jul 23, 2020 at 5:35 PM THYAGARAJ, DIWAKAR CHITOOR wrote: > +1 > > Thanks, > Diwakar Thyagaraj > > -----Original Message----- > From: MCEUEN, MATT > Sent: Wednesday, July 22, 2020 2:40 PM > To: airship-discuss at lists.airshipit.org > Subject: [Airship-discuss] Airshipctl Core Reviewer nomination: Stas > > *** Security Advisory: This Message Originated Outside of AT&T ***. > Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. > > BLUF: current airshipctl core team members, please respond with +1/-1 by > 7/29. > > I would like to propose Stas Egorov for the airshipctl core reviewer > team. Stas has been an active member of the Airship community for around a > year and a half, and in 2020 has maintained a strong focus on airshipctl > from a quality code review perspective, and a feature development > perspective. Stas has demonstrated an ability to guide development in the > right direction, and clearly cares about Airship being a high-quality > project. I believe Stas would add a lot of value to the team as a core > reviewer, and help us to get patches ship-shape and merged in a timely > fashion. > > Per our core nomination/approval conventions, I request that current > airshipctl core team members reply with a +1 or -1 by 7/29. If we get a > majority vote prior to 7/29 we can call it then. > > Thanks! > Matt > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=wkPPOhqD46u8zLuDs0Fr7Q&m=_Evy_DS6TGonpFNduOqAU6pzJBriD0N9gvDC-KPt5zA&s=lynr7NI0rJhcss-qLvD_Dh7OyVHTzEnX6MLuRxxASM0&e= > _______________________________________________ > 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 MM9745 at att.com Mon Jul 27 14:59:27 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 27 Jul 2020 14:59:27 +0000 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Dmitry Message-ID: <4bd5bef0bbf8435c81fd9a45d0a2c75d@att.com> BLUF: current Treasuremap core team members, please respond with +1/-1 by 8/3. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! I would like to propose Dmitry Ukov for the Treasuremap core reviewer team, for the same reasons I proposed Kostiantyn last week. Dmitry has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Dmitry will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 8/3 we can call it then. Thanks! Matt From kendall at openstack.org Mon Jul 27 15:02:10 2020 From: kendall at openstack.org (Kendall Waters) Date: Mon, 27 Jul 2020 10:02:10 -0500 Subject: [Airship-discuss] October/November PTG Date Selection Message-ID: Hello Everyone! We wanted to get your input on the best dates for holding the PTG now that its been annouced that the Summit itself will be virtual[1]. Please fill out the CIVS poll by August 3 at 15:00 UTC. We really appreicate your feedback! Poll: https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_a69944444a9b7c93&akey=3eccaa5b4fa5cfe6 There are obviously many pros and cons to each option, below are the conflicts/reasons why we might not want to select that option. Option 0 - Two weeks before Summit (October 5-9) Conflicts with RC work External Event Conflicts: None? Option 1 - One week after Summit (October 26-30) Halloween on Oct 31 Perfect for release timing but event fatigue is a real concern External Event Conflicts: Open Source Summit EU, ODSC Open Data Science Conference East Cloud Foundry Summit EU, KVM Forum Option 2 - Two weeks after the Summit (November 2-6) USA Election day on Nov 3; could be a distraction, contributors needing to go vote (whatever that looks like with the virus), news, etc. Event Conflicts: None? Option 3 - Three weeks after the Summit (November 9-13) Pushes far into the cycle (4 weeks after previous release, a bit late, Veterns day/holiday - may affect France and Germany and US) External Events Conflicts: VMWorld EU -The Kendalls (diablo_rojo & wendallkaters) [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016068.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From aw442m at att.com Mon Jul 27 15:04:56 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Mon, 27 Jul 2020 15:04:56 +0000 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Dmitry In-Reply-To: <4bd5bef0bbf8435c81fd9a45d0a2c75d@att.com> References: <4bd5bef0bbf8435c81fd9a45d0a2c75d@att.com> Message-ID: <2c5fca1b2efa4edb910e13f717c42188@att.com> +1 -----Original Message----- From: MCEUEN, MATT Sent: Monday, July 27, 2020 9:59 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Dmitry *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. BLUF: current Treasuremap core team members, please respond with +1/-1 by 8/3. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! I would like to propose Dmitry Ukov for the Treasuremap core reviewer team, for the same reasons I proposed Kostiantyn last week. Dmitry has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Dmitry will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 8/3 we can call it then. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=PhoDOFNqeAuEA29HCtwzVcTGnrbIvubFG152cw193QA&m=qP38qthzyGOUjERk-onPgaSWJPGFIvRgX9DtDz6KGD4&s=u3uQHhw4vZAL1LhzzUVGjtfW1C2zREM7KKCo3fp_0wk&e= From paye600 at gmail.com Mon Jul 27 15:21:32 2020 From: paye600 at gmail.com (Roman Gorshunov) Date: Mon, 27 Jul 2020 17:21:32 +0200 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Dmitry In-Reply-To: <4bd5bef0bbf8435c81fd9a45d0a2c75d@att.com> References: <4bd5bef0bbf8435c81fd9a45d0a2c75d@att.com> Message-ID: +1 > On 27 Jul 2020, at 16:59, MCEUEN, MATT wrote: > > BLUF: current Treasuremap core team members, please respond with +1/-1 by 8/3. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! > > I would like to propose Dmitry Ukov for the Treasuremap core reviewer team, for the same reasons I proposed Kostiantyn last week. Dmitry has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Dmitry will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. > > Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 8/3 we can call it then. > > Thanks! > Matt > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From ca846m at att.com Mon Jul 27 15:40:01 2020 From: ca846m at att.com (ANDERSON, CRAIG) Date: Mon, 27 Jul 2020 15:40:01 +0000 Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Dmitry In-Reply-To: <2c5fca1b2efa4edb910e13f717c42188@att.com> References: <4bd5bef0bbf8435c81fd9a45d0a2c75d@att.com> <2c5fca1b2efa4edb910e13f717c42188@att.com> Message-ID: <80d77c2fcf64434480a7a7174151f721@att.com> +1 -----Original Message----- From: WALTERS, ANDREW Sent: Monday, July 27, 2020 8:05 AM To: MCEUEN, MATT ; airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Treasuremap Core Reviewer nomination: Dmitry *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. +1 -----Original Message----- From: MCEUEN, MATT Sent: Monday, July 27, 2020 9:59 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Treasuremap Core Reviewer nomination: Dmitry *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. BLUF: current Treasuremap core team members, please respond with +1/-1 by 8/3. Note: currently the Treasuremap core team consists of the airship-core (aka Airship 1) team, so if you're in that group, this is for you! I would like to propose Dmitry Ukov for the Treasuremap core reviewer team, for the same reasons I proposed Kostiantyn last week. Dmitry has been very active on airshipctl yaml management functionality, and the manifests themselves, from code review and development perspective. As Airship 2 manifests will increasingly be authored in the Treasuremap repo (starting in the v2 branch), Dmitry will be well positioned to guide manifest authoring in the right direction, and to help integrate airshipctl appropriately into the larger Airship ecosystem. Per our core nomination/approval conventions, I request that current Treasuremap core team members reply with a +1 or -1 by 7/29. If we get a majority vote prior to 8/3 we can call it then. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=PhoDOFNqeAuEA29HCtwzVcTGnrbIvubFG152cw193QA&m=qP38qthzyGOUjERk-onPgaSWJPGFIvRgX9DtDz6KGD4&s=u3uQHhw4vZAL1LhzzUVGjtfW1C2zREM7KKCo3fp_0wk&e= _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=aimn2OylFgog_5_aS85wtQ&m=9GP7LK4-yn1Qg53sTAzn8v8OFIgvL1kyneo-Ls98690&s=lsFuATZmJBp09RBxaVizucWkLqKD5UYvSer4TAYCQQo&e= From Alexander.Hughes at pm.me Mon Jul 27 18:53:39 2020 From: Alexander.Hughes at pm.me (ProtonMail) Date: Mon, 27 Jul 2020 18:53:39 +0000 Subject: [Airship-discuss] 2020 Working Committee Nominations Extended Message-ID: Hello Airship Community, The initially planned deadline for nominations to the 2020-2021 Working Committee term has passed with four nominees, leaving one vacant seat. To ensure the Working Committee can run at full capacity, we have extended nominations by one week. The new Working Committee election cycle is now a total of three weeks: Nominations: July 20th-August 2nd Voting: August 3rd-August 9th Additional information about the nomination process can be found here [1]. Shortly after election officials approve candidates, they will be listed here [2]. Voting will occur via ballots emailed to the electorate (current Airship project core reviewers) on August 10th. The Technical Committee requests the balloter to confirm their email addresses in gerrit before August 9th, so ballots are emailed to the correct email addresses. [1]: https://docs.airshipit.org/election/procedures.html [2]: https://docs.airshipit.org/election/results/2020/wc.html Regards, Airship Technical Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Thu Jul 30 17:32:45 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 30 Jul 2020 17:32:45 +0000 Subject: [Airship-discuss] Stas & Kostyantyn core reviewer roles Message-ID: <7b5842ee85ff48bf86867f16ab98006d@att.com> Welcome, Kostyantyn & Stas, to (respectively) the Treasuremap and Airshipctl core reviewer teams! I look forward to continue to collaborate with you both in these roles. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: