April 2019 - Foundation - lists.openinfra.dev

[OpenStack Foundation] Bylaws change proposed at next week's OpenStack board meeting to support Open Infrastructure project confirmation
by Alan Clark 30 Apr '19

30 Apr '19

As the OpenStack Foundation embraces new areas of strategic focus and as the associated Open Infrastructure projects mature, the OpenStack board desires to do its part in helping the projects thrive and grow. A key step in project advancement is the project confirmation by the Board. Confirmation will enable the Foundation to apply additional Foundation resources towards that project. In support of this process, the board at its last meeting, approved the OSF Project Confirmation Guidelines[1]. As the Guidelines point out, many factors go into the board's decisions. To ensure that the board has the mechanisms needed to be as sensitive as possible to the needs and feelings for those invested in the projects, the board will further discuss a motion to amend bylaws section 4.16 as follows: (changed text in italics). 4.16 Open Meetings and Records. Except as necessary to protect attorney-client privilege, sensitive personnel information, discuss the candidacy of potential Gold Member and Platinum Members, and discuss the review and approval of Open Infrastructure Projects, the Board of Directors shall: (i) permit observation of its meetings by Members via remote teleconference or other electronic means, and (ii) publish the Board of Directors minutes and make available to any Member on request other information and records of the Foundation as required by Delaware Corporate Law. If, during confirmation discussions, a project lead or Director feels that there is sensitive information that needs to be protected this amendment provides a mechanism for such discussion. Thanks, Alan Clark [1] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmation Guidelines

10 15

[OpenStack Foundation] Diversity Events
by Amy Marrich 22 Apr '19

22 Apr '19

Summit is a week away and I wanted to point out a few Diversity related sessions and events taking place. Thanks, Amy (spotz) Monday: 12:20-1:40 - Speed Mentoring Lunch sponsored by Intel - RSVP required https://www.openstack.org/summit/denver-2019/summit-schedule/events/23757/r… Tuesday: 12:20-1:40 - Diversity Networking Lunch sponsored by IBM - RSVP required https://www.openstack.org/summit/denver-2019/summit-schedule/events/23756/r… 1:40-2:20 - The Results are in for the D&I Survey. This is a first review of the data collected. https://www.openstack.org/summit/denver-2019/summit-schedule/events/23692/t… Wednesday: 10:50-11:30 - Diversity WG BoF - looking for help with the Mentoring Program https://www.openstack.org/summit/denver-2019/summit-schedule/events/23745/d… 11:40-12:20 - Diversity and Inclusion WG https://www.openstack.org/summit/denver-2019/summit-schedule/events/23746/d…

1 1

[OpenStack Foundation] [Diversity] D&I WG Meeting Reminder - tomorrow
by Amy Marrich 21 Apr '19

21 Apr '19

The Diversity & Inclusion WG will hold it's next meeting this Monday(4/22) at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any other topics you wish to discuss at the meeting. Including the discuss list to invite potential new members! Thanks, Amy (spotz)

1 0

[OpenStack Foundation] April 8, 2019 Board Meeting
by Jonathan Bryce 08 Apr '19

08 Apr '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 two pilot projects: Kata Containers and Zuul. Eric Ernst from the Kata Containers Architecture Committee presented about the project and covered the areas that the Board had approved as guidelines for confirmation[2]. After the presentation[3], the Board had a number of questions for the Kata Containers team. As the questions wrapped up, the Board decided to proceed with a vote on confirmation today and approved it as the first new top-level Open Infrastructure Project in the foundation. Congrats to the Kata Containers team and community! Next, Monty Taylor presented the Zuul project for consideration[4]. Again, the presentation was followed by discussion and a number of questions around the project. In particular the Board spent a lot of time discussing some of the licensing considerations in Zuul as it integrates with other non-Apache licensed projects and code. Several people made proposals about how to handle the approval of the project to take this into account. In the end, everyone agreed to work that out offline and revisit the licensing and confirmation proposals at the next Board meeting. Finally, Alan reviewed the state of updating the provision in the Bylaws around topics that are allowed to be discussed in Executive Session. There’s been a longer thread on the mailing list on this[5], and the Board will continue to review this with a potential vote at an upcoming Board meeting. Thanks to the Kata and Zuul teams for putting together great presentations and taking the time to discuss their progress with the Board! Jonathan 1. https://wiki.openstack.org/wiki/Governance/Foundation/8April2019BoardMeeting 2. https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmatio… 3. https://docs.google.com/presentation/d/1Vil7Px-KyjxrfjO4TT25hKRDb2O02_qmrn4… 4. https://zuul-ci.org/confirmation/ 5. http://lists.openstack.org/pipermail/foundation/2019-April/002740.html

1 0

[OpenStack Foundation] Reminder for the OpenStack board meeting, April 8th 7am pacific
by Alan Clark 06 Apr '19

06 Apr '19

Reminder, The OpenStack board will hold a board meeting on April 8th at 7am pacific. The main topics for the meeting are a 2 project confirmation previews. Meeting date: April 8th Time: 7am pacific to 9am pacific Location: https://zoom.us/j/9574980705 ( <https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F9574980705&sa=D&us t=1551725789504000&usg=AFQjCNFvenAoL6huE4M30sG0kMRtU9aUJw> map) Agenda: https://wiki.openstack.org/wiki/Governance/Foundation/8April2019BoardMeeting Thanks, AlanClark

1 0

[OpenStack Foundation] [Diversity] D&I WG Meeting Reminder
by Amy Marrich 05 Apr '19

05 Apr '19

The Diversity & Inclusion WG will hold it's next meeting Monday(4/8) at 17:00 UTC in the #openstack-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity-wg-agenda. Please feel free to add any other topics you wish to discuss at the meeting. Including the discuss list to invite potential new members! Thanks, Amy (spotz)

1 0

[OpenStack Foundation] OpenStack TC feedback on Kata Containers for OIP Confirmation
by Mohammed Naser 04 Apr '19

04 Apr '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 far that's just OpenStack) when evaluating the Kata Containers pilot project's upcoming application for OIP confirmation. We reached out to the OpenStack community to get an idea of what interactions have been experienced or observed relevant to these guidelines, and compiled them in an Etherpad[1] for ease of collaboration. The feedback is broken down by each of the five major guideline headings along with a catch-all at the end. Here follows an attempt to summarize what we've learned: Kata Containers aids the OSF's strategic focus by bringing value to those working with multi-tenant and similarly sensitive container-oriented technologies. It has brought the OSF community new inroads with Amazon/AWS technologists through its collaboration and integration with their Firecracker project. Involvement with OpenStack projects seems so far to have been limited to Zun[2], though Kata's testing has indirectly helped improve the state of nested virtualization in OpenStack. Opportunities for interaction with Magnum and other related parts of OpenStack remain as of yet untapped, and it was also suggested that use cases for leveraging Kata to further isolate Zuul executor processes and job nodes merit future exploration. Unfortunately, overall lack of OpenStack community familiarity with Kata seems to indicate some failures at outreach, possibly in both directions (including noted absence from PTGs). The governance[3] established for Kata employs a relatively similar model to that of OpenStack at the top level with their AC parallel to the OpenStack TC, and the election process they've followed is similar as well (though tuned for electors contributing through GitHub rather than OpenDev). On recommended technical practices, they use a vulnerability management process[4] inspired by OpenStack's, but maintain their own public CI system[5] to test and report on proposed pull requests for their software along with performing periodic post-merge performance analyses. When it comes to open collaboration, their reliance on proprietary tools like GitHub and Slack was called out as a possible point of contention, however respondents from the OpenStack community remarked that submitting contributions or otherwise interacting with Kata maintainers was a pleasant/positive experience and the community was genuinely helpful. They seem to be actively engaged with potential users and projects they see as relevant to their scope (notably Firecracker), and maintain a visible presence at popular industry events like KubeCon. [0] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmatio… [1] https://etherpad.openstack.org/p/openstack-tc-kata-confirmation-feedback [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004376.ht… [3] https://github.com/kata-containers/community [4] https://github.com/kata-containers/community/blob/master/VMT/VMT.md [5] http://jenkins.katacontainers.io/ -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0

[OpenStack Foundation] OpenStack TC feedback on Zuul for OIP Confirmation
by Mohammed Naser 04 Apr '19

04 Apr '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 far that's just OpenStack) when evaluating the Zuul pilot project's upcoming application for OIP confirmation. We reached out to the OpenStack community to get an idea of what interactions have been experienced or observed relevant to these guidelines, and compiled them in an Etherpad[1] for ease of collaboration. The feedback is broken down by each of the five major guideline headings along with a catch-all at the end. Here follows an attempt to summarize what we've learned: Zuul furthers the strategic focus of the OSF, helping open infrastrucure projects ensure the highest possible levels of code quality by applying the concept of project gating. It is responsible in great part for the success of OpenStack and OpenDev, as well as found useful by other pilot projects like Airship and StarlingX. It's widely seen as a simplifying force for our continuous integration and project infrastructure. Zuul itself makes heavy use of OpenStack-based services and considers those a first-class supported feature. The governance[2] for Zuul is fairly straightforward, perhaps described in OpenStack terms as a team of consensus-seeking core reviewers (the Zuul Maintainers) who elect a PTL (the Zuul Project Lead) from within their ranks rather than relying on anyone who has contributed a patch to do so. It is also somewhat analogous to how the OpenStack TC elects its chair, though the Zuul Maintainers are a self-selected group rather than being elected by other patch submitters. Given that in OpenStack each PTL is basically always already a core reviewer and a consensus choice of their peers (and almost always the only candidate nominated), and that PTLs tend to defer addition and removal of new core reviewers to consensus among the existing cores, this seems like a model based in the reality of team dynamics. The Zuul project has not discarded the recommended practices from its origins as a part of OpenStack, and indeed is itself responsible for instating many of those practices within OpenStack. The OpenStack community is particularly fond of Zuul's extensive, integrated documentation[3] on which it heavily relies. While there are instructions[4] on how to report suspected vulnerabilities and the team is regularly publishing advisories[5][6][7], it was noted that there is not yet a published document describing the vulnerability management process followed so this is a potential area for improvement. Similarly, Zuul's fundamental collaboration model is also inherited from its OpenStack roots (or you could say Zuul was responsible for much of it while still a part of OpenStack). The members of the Zuul community are happy to help users, including other Open Infrastrucure Projects and OSF pilot projects, solve their problems even (or perhaps especially) when it means Zuul itself needs to grow new features to do so. There was one note that it might be nice to get a clearer picture as to how Zuul relates or could relate to the projects in the newly-formed CD Foundation[8]. As to active engagement, Zuul is remarked as having an obvious diversity of developers and production users from many companies with a rapidly growing ecosystem and presence at industry events like AnsibleFest. The Zuul community has also been observed going to great lengths in assisting new deployers of its software, many of whom are notably operators of third-party CI for testing drivers and features of various OpenStack subsystems. Even the software itself is considered to be a tool of outreach, leaving its own inline review comments for syntax errors in proposed configuration changes. [0] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmatio… [1] https://etherpad.openstack.org/p/openstack-tc-zuul-confirmation-feedback [2] https://zuul-ci.org/docs/zuul/governance.html [3] https://zuul-ci.org/docs/ [4] https://zuul-ci.org/docs/zuul/user/vulnerabilities.html [5] http://lists.zuul-ci.org/pipermail/zuul-announce/2018-November/000027.html [6] http://lists.zuul-ci.org/pipermail/zuul-announce/2019-January/000032.html [7] http://lists.zuul-ci.org/pipermail/zuul-announce/2019-March/000035.html [8] https://cd.foundation/ -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0