Monat: Januar 2020

A year in review: How OpenStack continues to be one of the top three most active open source projects

A total of 1,518 unique change authors approved more than 47,500 changes and published two major releases, code named Stein and Train (due to our undying love of Trains). We started to work on Ussuri, our next release, to be delivered in 2020. In 2018, we introduced the “Extended Maintenance” concept, a period on which bugfixes can be accepted for projects following it (but these won’t produce further releases). As of today, Ocata, Pike, and Queens are in extended maintenance.

Like in 2018, the component project teams completed work on stability, performance, and operational/usability improvements. They also worked on themes related to integrating with other OpenStack components, other OpenStack Foundation Open Infrastructure Projects, and projects from adjacent communities, for example Kubernetes or Ansible. We have introduced a deployment tools capabilities map, to make it even easier for new users to select their deployment tool of choice.

In addition to component-specific work, we continued to improve our OpenStack-wide processes by adding pop up teams next to goals, in order to have more flexibility on achieving large scale changes. During 2019, we have added two pop up teams “Image Encryption” (implementing encryption and decryption of images and the handling of those images in OpenStack) and the “Secure Default Policies” (consistent policies across OpenStack). This is in addition to our OpenStack wide goals: we made sure all the projects can render their documentation into PDFs, ensured that OpenStack works and is tested in IPv6 only environments (not only dual stacks!). We are also making sure the community is moving up in the python versions with an ultimate removal of python2 of our development pipelines in 2020.

The Technical Committee (TC) itself has evolved in 2019. We plan to reduce our members to 9 in 2020. Over the whole year, Chris Dent, Davanum Srinivas, Sean McGinnis, Doug Hellmann, Jeremy Stanley, Lance Bragstad, and Julia Kreger left the TC, to make way for first-time members Alexandra Settle, Jim Rollenhagen, Rico Lin, Kendall Nelson, Kevin Carter, Nate Johnston, and Jay Bryant.

2019 saw the beginnings of a transition from OpenStack project infrastructure hosting into OpenDev project hosting. This process will eventually separate our project hosting tools from OpenStack itself so that they may be more clearly reused by other projects. We expect to make significant progress on this transition in 2020.

With the input from the OpenStack Foundation board, the OpenStack TC updated its “help wanted list” to actively track where business and leadership opportunities can be for companies willing to invest in OpenStack.

During 2019, the OpenStack project infrastructure was renamed opendev.org, to make it clearer it can be used beyond OpenStack. Using Opendev namespaces, we now have a clear separation between official OpenStack projects and non-OpenStack open source projects developed under the same development tooling. In terms of project teams, the most visible change in 2019 was the extraction of Placement from the Nova team. Regarding SIGs, we are launching a “Multi-architecture” SIG (including the orginal work from the PowerVM project team which became the PowerVM SIG…), Ansible SIG, Containers SIG, Auto-scaling SIG (which is planned to merge with the existing self-healing SIG to form a new Automation SIG in the near future), Large Scale SIG, Technical Writing SIG, Public Cloud SIG (migrated from Public Cloud WG), Bare Metal SIG, and Edge Computing SIG (renamed from FEMDC SIG). This year, we closed down the Upgrade SIG, as we consider their work achieved and completed. This year, a lot of work was done to help creating and maintaining new SIGs (thanks to the “Meta SIG” team). This includes more guidelines and reference documents. As usual, the TC members will continue their work to expose SIGs broadly, to ensure all the different profiles and interests in OpenStack are efficiently represented, working, and collaborating together.

In 2019, the OpenStack User Committee (UC) brought onboard several new members including John Studarus (February electee), Belmiro Moreira (February electee), Mohamed Elsakhawy (August electee), and Jaesuk Ahn (September electee). Amy Marrich was re-elected to continue their service on the UC.

In this year we worked closely with the OpenStack Foundation staff to adopt new policies to better support the user groups. The migration of the user groups onto Meetup.com has allowed us to better support groups through local leadership transitions and reduce technical headaches. We also smoothed the process for new user groups to come online and be supported by the Foundation increasing the reach in these new and emerging regions of the world.

We continue to identify ways in which the new technologies developed can be promoted and evangelized. We believe the current Ambassador program, which is currently focused on supporting the user groups, can either be modified, or a new program created to help support those individuals actively promoting and evangelize our open source offerings.

The UC took an active role in updating the SIG and Working Group records to better reflect the leadership, goals, and status of these entities. We feel that having accurate records allows those looking to get involved to readily find the active communities.

The UC has been investigating reducing its membership from five (5) to three (3) members with plans to have the membership rules modified in time for the February 2020 election. We believe having fewer UC members will make it easier to keep the UC fully elected.
Quelle: openstack.org