October 2019 - Foundation - lists.openinfra.dev

[OpenStack Foundation] October 22, 2019 Board Meeting
by Jonathan Bryce 22 Oct '19

22 Oct '19

Hi everyone, The OSF Board of Directors met today. The agenda was posted online[1]. The primary purpose of today’s meeting was confirmation review of the Airship project, although I opened the meeting by giving a review of some community and market stats as well as information about the recently completed Train development cycle for OpenStack. Four members of the Airship community, Matt McEuen, Alex Hughes, Kaspars Skels and Jaesuk Ahn, gave a detailed presentation[2] on the project, its progress during the pilot phase and how it meets the confirmation guidelines the Board has adopted. The Board raised several questions with the Airship team, reviewed feedback from the OpenStack TC and discussed the project in general. One question that created quite a bit of discussion dealt with licensing of golang libraries that may be pulled in as dependencies for certain Airship components. The Board felt that this was something that could be reviewed and dealt with by the project and OSF resources to make sure any dependencies comply with our overall license policies. With this agreed on, the Board voted unanimously to confirm Airship as a new top-level Open Infrastructure Project in the Foundation and the meeting concluded. Congrats to the Airship team and community! Jonathan 1. https://wiki.openstack.org/wiki/Governance/Foundation/22October2019BoardMee… 2. https://www.airshipit.org/images/airship-confirmation-review-for-the-osf-bo…

1 0

[OpenStack Foundation] OpenStack TC feedback on Airship for OIP Confirmation
by Rico Lin 22 Oct '19

22 Oct '19

The OSF Board of directors is soliciting feedback from representatives of existing confirmed Open Infrastructure Projects (Zuul, OpenStack, and Kata) to evaluate the Airship pilot project's upcoming application for OIP confirmation. This is as per the OSF Project Confirmation Guidelines[0]. As part of this process, we reached out to OpenStack TC members and the OpenStack community [2] to gather feedback on interactions observed or experienced (relevant to the guidelines) and requested a compilation of these events in an Etherpad[1]. We have gathered as much feedback as we can due to the unusually short notice this round. The following is a summary of what was provided: *1. Strategic focus* Alignment with the strategic focus areas of the OSF looks strong. Airship makes use of OpenStack components where appropriate. Integration with Ironic for bare metal provisioning is still underway, but has been included in the Airship 2.0 roadmap (through usage of the metal3.io project, which provides Kubernetes-native baremetal management using standalone Ironic). *2. Governance* Open governance for the project has been defined, and is fully respecting the "open community" tenet. Airship chose to define two governance bodies (TC and WC) and it could be clearer which body has oversight on the other on what matter. The governance documentation at https://opendev.org/airship/governancecould be expanded: for example it should probably publish or link to the current TC/WC member lists, as the wiki pages can be a bit hard to find. *3. Technical best practices* Airship has adopted many technical best practices pioneered in the OpenStack community and is in pretty good shape. One point raised is that it's still unclear how devs/users to can report bugs/tasks, and how that's been linked to JIRA. Adding Gerrit support to automatically create hyperlinks to JIRA issues would also help integrating the two tools better. *4. Open collaboration* Airship has been started from day 0 with the "4 opens" philosophy in mind. Despite having strong single-vendor origin, it seems to operate now as a level playing field for everyone to collaborate on an equal footing. Some issues still seem to be assigned on a company basis rather than a per developer basis, but that is rare. We generally prefer to use free and open source software tools to build our software. Airship has adopted most of the Opendev tooling (including Gerrit andZuul), with the exception of JIRA (which is free to access and allows self signup). Airship has been a good neighbor for the OpenStack project. Airship contributors are willing to answer Airship-related questions raised on the openstack-discuss ML, thanks to the significant overlap between Airship and OpenStack-Helm leadership and contributors. Airship code is licensed under an OSI-approved open source license. While documentation is also released under an appropriate license, some raised concerns at the prominent mention of "AT&T Intellectual Property" copyright in the footer of all online documentation, which gives readers the wrong impression. *5. Active engagement* Airship has drastically improved its organizational diversity over the past year. Roughly two-thirds of commits and reviews are coming from AT&T over the past 6 months, compared to 90% a year ago, so this seems to be on a good trend. On the user side, evidence of usage at scale outside of AT&T is still scarce. We hope that the board presentation will shine some light on other key users. On the ecosystem side, adoption by other integrators shows that the technology can fit a variety of use cases. [0] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmatio… [1] https://etherpad.openstack.org/p/openstack-tc-airship-confirmation-feedback [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010164.…

2 1

[OpenStack Foundation] Zuul community feedback on Airship for OIP Confirmation
by Jeremy Stanley 21 Oct '19

21 Oct '19

Per the OSF Project Confirmation Guidelines[0], the OSF Board of directors is soliciting feedback from representatives of existing confirmed Open Infrastructure Projects (so Zuul, OpenStack, and Kata) when evaluating the Airship pilot project's upcoming application for OIP confirmation. I reached out to the Zuul community at large to get an idea of what interactions have been experienced or observed relevant to these guidelines, requesting compilation in an Etherpad[1] for ease of collaboration. The window of opportunity for feedback was, unfortunately, shorter than previous confirmations have afforded; this likely resulted in less feedback overall. On the whole, however, there is a limited and indirect relationship between the projects: Airship is hosted in OpenDev, which integrates Zuul and Gerrit for a unified code-review-driven development experience, so they get Zuul project gating by defining jobs within their Git repositories. They moved their repositories to OpenDev shortly after the Zuul v3 migration there, and have eagerly embraced its use in their workflow since. While Airship contributors interface with the OpenDev sysadmins on a somewhat regular basis, their interaction with the Zuul community has been limited so far. In the future it would be exciting to see them get involved in parts of Zuul relevant to their expertise, such as Nodepool's Kubernetes provider driver or Kubernetes/Helm-related roles in Zuul's standard library of reusable job components. [0] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmatio… [1] https://etherpad.openstack.org/p/zuul-community-airship-confirmation-feedba… -- Jeremy Stanley

1 0

[OpenStack Foundation] OpenStack Board Meeting October 22, 2019 7am pacific
by Alan Clark 16 Oct '19

16 Oct '19

Foundation members, The OpenStack Board will meet on October 22nd for a quick call. The board has one topic that they would like to discuss prior to the Shanghai Summit and November board meeting. The topic is a presentation for confirmation of the Airship project. Please join an OpenStack board meeting on October 22nd. Agenda: https://wiki.openstack.org/wiki/Governance/Foundation/22October2019BoardMeet ing Date: October 22nd Time: 7:00 - 9:00am pacific Information is located on the wiki on how to join and listen to the meeting. Thanks, AlanClark

1 0

[OpenStack Foundation] [Diversity] November Meeting Moved
by Amy Marrich 07 Oct '19

07 Oct '19

As the first Monday of November will be during the Summit. I just wanted to send out an early notice that we decided in today's meeting to move to our optional 3rd week slot. I will send out a reminder before the 3rd Monday as a reminder.:) Thanks, Amy (spotz)

1 0