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.

The OpenStack Foundation (OSF) just published its 2019 annual report. Learn more about other OSF projects and how you can get involved.

OpenStack turns 8: Welcoming new users, more collaboration and new projects

We are celebrating the 8th birthday of OpenStack with the entire OpenStack community during July! OpenStack is an integration engine for diverse technologies, fostering collaboration among emerging communities, and the Foundation facilitates the development of many innovative projects in the open infrastructure space. None of it would be possible without the quickly growing, global community. There are now more than 90,000 community members across 183 countries and more than 670 supporting companies. We think that deserves a worldwide celebration!


We’ve invited all our user groups to celebrate with us. This month, more than 30 OpenStack birthday parties will be thrown all over the world – celebrating the OpenStack community!  We encourage everyone to find a birthday party in your area and join your fellow community members to toast each other on another great year! Don’t forget to post and share your pictures and memories on Flickr.


Find a local celebration in your area:

Paris, France – June 25

Vietnam – July 1

Los Angeles – July 8

Portland, Oregon – July 9

San Francisco, California – July 10

Sweden – July 12

Virginia – July 12

Moscow, Russia – July 13

Rennes, France – July 16

San Diego, California – July 17

Greece – July 18

Tunisia – July 18

Barcelona – July 19

Mexico City – July 19

Nigeria – July 19

Philippines – July 20

Colorado, USA – July 24

Thailand – July 24

Bucharest, Romania – July 25

Ghana – July 25

Brazil – July 27

Korea – July 27

Durban – July 28

Guatemala – July 30

Iran – July 31

Japan – August 2

Seattle, Washington – August 8

Cote d’Ivoire – August 25

OpenStack swag voting: Round 2

Thanks for voting on your favorite OpenStack swag designs yesterday! See the second set of designs below, then head over to Twitter to vote on this round.

Check Twitter on Monday to see the winning designs!


We Are OpenStack:

OpenStack Worldwide:

Stacker Burst:

Fight for the Users:

Vote for your favorite OpenStack swag!

The OSF Swag Store is coming soon, but first, we need your help!

Which of the below designs is your favorite? Tell us know in our Twitter poll and check back tomorrow for another round.

OpenStack Logo:

I <3 OpenStack:

Playing for an Open World:

Free as in Beer, Speech, & Love:



Developer Mailing List Digest March 3-9th

Success Bot Says

  • kong: Qinling now supports Node.js runtime(experimental)
  • AJaeger: Jenkins user and jenkins directory on images are gone. /usr/local/jenkins is only created for legacy jobs
  • eumel8: Zanata 4 is now here [0]
  • smcginnis: Queens has been released!!
  • kong: welcome openstackstatus to #openstack-qinling channel!
  • Tell us yours in OpenStack IRC channels using the command “#success <comment>”

Thanks Bot Says

  • Thanks dhellmann for setting up community wide goals + good use of storyboard [0]
  • Thanks ianw for kind help on upgrading to Zanata 4 which has much better UI and improved APIs!
  • Tell us yours in OpenStack IRC channels using the command “#thanks <comment>”

Community Summaries

  • Release countdown [0]
  • TC report [1]
  • Technical Committee status update [2]

PTG Summaries

Here’s some summaries that people wrote for their project at the PTG:

  • Documentation and i18n [0]
  • First Contact SIG [1]
  • Cinder [2]
  • Mistral [3]
  • Interop [4]
  • QA [5]
  • Release cycle versus downstream consuming models [6]
  • Nova Placements [7]
  • Kolla [8]
  • Oslo [9]
  • Ironic [10]
  • Cyborg [11]

OpenStack Queens is Officially Released!

Congratulations to all the teams who contributed to this release! Release notes of different projects for Queens are available [0] and a list of projects [1] that still need to approve their release note patches!

Release Cycles vs. Downstream consumers PTG Summary

Notes can be found on the original etherpad [0]. A TC resolution is in review [1]
TLDR summary:
  • No consensus on longer / shorter release cycles
  • Focus on FFU to make upgrades less painful
  • Longer stable branch maintenance time (18 months for Ocata)
  • Bootstrap the “extended maintenance” concept with common policy
  • Group most impacted by release cadence are packagers/distros/vendors
  • Need for finer user survey questions on upgrade models
  • Need more data and more discussion, next discussion at Vancouver forum
  • Release Management team tracks it between events

Pros and Cons of face-to-face Meetings

Some contributors might not be able to attend the PTG for various reasons:
  • Health issues
  • Privilege issues (like not getting visa or travel permits)
  • Caretaking responsibilities (children, other family, animals, plants)
  • Environmental concerns
There is a concern if this is preventing us from meeting our four opens [1] if people are not able to attend the events. 
The PTG sessions are not recorded, but there is a super user article on how teams can do this themselves [0]. At the PTG in Denver, the OpenStack Foundation provided bluetooth speakers for teams to help with remote participation.
Consensus is this may not be trivial for everyone and it could still be a challenge for remote participants due to things like audio quality. Some people at the PTG in Dublin due to the weather had to participate remotely from their hotel room and felt it challenging to partipate.

Developer Mailing List Digest February 17-23rd

Helpful PTG links

PTG is around the corner. Here are some helpful links:

Success Bot Says

  • mhayden got centos OSA gate under 2h today
  • thingee: we have an on-boarding page and documentation for new contributors! [0]
  • Tell us yours in OpenStack IRC channels using the command “#success <comment>”
  • More: https://wiki.openstack.org/wiki/Successes

Thanks Bot Says

  • Thanks pkovar for keep the Documentation team going!
  • Thanks pabelanger and infra for getting ubuntu mirrors repaired and backup quickly!
  • Thanks lbragstad for helping troubleshoot an intermittent fernet token validation failure in puppet gates
  • Thanks TheJulia for helping me with a problem last week, it was really a networking problem issue, like you said so 🙂
  • Thanks tosky for backporting devstack ansible changes to pike!
  • Thanks thingee for Thanks Bot
  • Thanks openstackstatus for logging our things
  • Thanks strigazi for the v1.9.3 image
  • Thanks smcginnis for not stopping this.
  • Tell us yours in OpenStack IRC channels using the command “#thanks <comment>”
  • More: https://wiki.openstack.org/wiki/Thanks

Community Summaries

  • TC report [0]
  • POST /api-sig/news [1]
  • Release countdown [2]

Vancouver Community Contributor Awards

The Community contributor awards gives recognition to those that are undervalued, don’t know they’re appreciated, bind the community together, keep things fun, or challenge some norm. There are a lot of people out there that could use a pat on the back and affirmation that they do good work in the community.
Nomination period is open now [0] until May 14th. Winners will be announced in feedback session at Vancouver.

Release Naming For S – time to suggest a name!

It’s time to pick a name for our “S” release! Since the associated Summit will be in Berlin, the Geographic location has been chosen as “Berlin” (state). Nominations are now open [0]. Rules and processes can be seen on the Governance site [1].

Final Queens RC Deadline

Thursday 22nd of April is the deadline for any final Queens release candidates. We’ll enter a quiet period for a week in preparation of tagging the final Queens release during the PTG week. Make sure if  you have patches merged to stable/queens that you propose a new RC before the deadline. PTLs should watch for a patch from the release management team tagging the final release. While not required, an acknowledgement on the patch would be appreciated.

Do Not Import oslo_db.tests.*

Deprecations were made on oslo_db.sqlalchemy.test_base package of DbFixture and DbTestCase. In a patch [0], and assumption was made to that these should be imported from oslo_db.tests.sqlalchemy. Cinder, Ironic and Glance have been found with this issue [1].
Unfortunately these were not prefixed with underscores to comply with naming conventions for people to recognize private code. The tests module was included for consumers to run those tests on their own packages easily.

Some New Zuul Features

Default timeout is 30 minutes for “post-run” phase of the job. A new attribute “timeout” [0] can set this to something else, which could be useful for a job that performs a long artifact upload.
Two new job attributes added “host-vars” and “group-vars” [1] which behave like “vars” but applies to a specific host or group.

Developer Mailing List Digest February 10-16th

Please help shape the future of the Developer Mailing List Digest with this two question survey: https://openstackfoundation.formstack.com/forms/openstack_developer_digest_feedback
Contribute to the Dev Digest by summarizing OpenStack Dev List threads:

Success Bot Says

  • None for this week. Tell us yours in OpenStack IRC channels using the command “#success <comment>”

Thanks Bot Says

  • diablo_rojo on #openstack-101 [0]: spotz for watching the #openstack-101 channel and helping to point newcomers to good resources to get them started 🙂
  • fungi on #openstack-infra [1]: dmsimard and mnaser for getting deep-linking in ara working for firefox
  • fungi on #openstack-infra [2]: to Matt Van Winkle for volunteering to act as internal advocate at Rackspace for our control plane account there!
  • AJaeger on #openstack-doc [3]: corvus for deleting /draft content
  • AJaeger on #openstack-infra [4]: cmurphy for your investigation
  • AJaeger on #openstack-infra [5]: to mordred for laying wonderful groundwork with the tox_siblings work.
  • smcginnis on #openstack-infra [6]: fungi jeblair mordred AJaeger and other infra-team members for clearing up release job issues
  • fungi on #openstack-infra [7]: zuul v3 for having such detailed configuration syntax error reporting.
  • fungi on #openstack-dev [8]: diablo_rojo and persia for smooth but “rocky” ptl elections!
  • Tell us yours in OpenStack IRC channels using the command “#thanks <comment>”

Community Summaries

  • Nova Placement update [0]
  • Release Countdown [1]
  • TC Report [2]
  • Technical Committee Status update [3]

PTG Bot HOWTO for Dublin

The third PTG is an event where topics of discussion are loosely scheduled in tracks to maximize the attendee productivity. To keep track of what’s happening currently we have an event schedule page [0]. Below are some helpful discussions in using PTG bot:

Track Leads

Track leads will be able issue various commands [1] in irc channel #openstack-ptg:
  • #TRACK now <what’s being discussed>
  • example: #swift now brainstorming improvements to the ring.
  • Cross project interactions #TRACK now <what’s being discussed with other #TRACK>:
  • #nova now discussing #cinder interactions
  • What’s next #TRACK next <what will be discussed>:
  • #api-sig next at 2pm we’ll be discussing pagination woes
  • Clear all now and next entries for a track #TRACK clean:
  • #ironic clean

Booking Reservable Rooms

Reservable rooms and what’s being discussed works the same with it showing on the event schedule page [0].
Different set of commands:
  • Get the slot codes with the book command:
  • #TRACK book
  • #TRACK book <slot_code>
  • example: #relmgt book Coiste Bainisti-MonP2
Any track can book additional space. These slots are 1 hour and 45 minutes long. You can ask ttx, diablo_rojo or #openstack-infra to add a track that’s missing. Keep in mind various teams will be soley relying on this for space at the PTG.
Additional commands can be found in the PTG bot README [1].

PTL Election Results and Conclusions

PTL election is over and the results are in [0]! Congrats to returning and new PTLs!
There were three elections that took place:
  • Kolla [1]
  • Mistral [2]
  • Quality Assurance [3]
On the statistics side, we renewed 17 of the 64 PTLs, so around 27%. Our usual renewal rate is more around 35%, but we did renew more at the last elections (40%) so this is likely why we didn’t renew as much as usual this time. Much thanks to our election officials for carrying out this important responsibility in our community!

Election Process Tweaks

Discussions have started with ways to improve our election process. Current scripts in place have become brittle that are needed for governance documentation building that use gerrit lookup functions. Election officials currently have to make changes to an exception file [0] when email address with foundation accounts don’t match gerrit.
Discussed improvements include:
  • Uncouple TC and PTL election processes.
  • Make TC and PTL validation functions separate.
  • Change how-to-submit-candidacy directions to requires candidates email address to match their gerrit and foundation account.
Comments, concerns and better ideas are welcome. The plan is to schedule time at the PTG to start hacking on some of those items so feedback before then would be appreciated by your election officials!

Developer Mailing List Digest February 3-9th

Please help shape the future of the Developer Mailing List Digest with this two question survey: https://openstackfoundation.formstack.com/forms/openstack_developer_digest_feedback

Success Bot Says

  • stephenfin on #openstack-nova [0]: After 3 years and 7 (?) releases, encryption between nova’s consoleproxy service and compute nodes is finally possible ✌️
  • AJaeger on #openstack-infra [1]: zuul and nodepool feature/zuulv3 branches have merged into master
  • ildikov on #openstack-nova [2]: OpenStack now supports to attach a Cinder volume to multiple VM instances managed by Nova.
  • mriedem on #openstack-nova [3]: osc-placement 1.0.0 released; you can now do things with resource providers/classes via OSC CLI now.
  • AJaeger on #openstack-infra [4]: All tox jobs have been converted to Zuul v3 native syntax, run-tox.sh is gone.
  • ttx on #openstack-dev [5]: All teams have at least one candidate for PTL for the Rocky cycle! Might be the first time.
  • Tell us yours in OpenStack IRC channels using the command “#success <comment>”

Community Summaries

  • Release countdown [0]
  • Nova placement resource provider update [1]
  • TC Report [2]
  • POST /api-sig/news [3]
  • Technical Committee Status Update [4]

Dublin PTG Schedule is Up

PTG schedule is available [0]. A lot of rooms are available Monday/Tuesday to discuss additional topics that take half a day and can be requested [1]. For small things (90 min discussions) we can book them dyncamically during the event with the new PTG bot features. Follow the thread for updates to the schedule [2].

Last Chance for PTG Dublin Tickets

PTG tickets for Dublin were sold out this week, and the Foundation received many requests for more tickets. Working with the venue to accommodate the extra capacity, every additional attendee incrementally increases costs to $600. It’s understood the importance of this event and the need to have key team members present, so the OpenStack Foundation has negotiated an additional 100 tickets and will partially subsidize to be at sold at $400 [0].

New Zuul Depends-On Syntax

Recently introduced url-based syntax for Depends-On: footer in your commit message:
Old syntax will continue to work for a while, but please begin using the new syntax. Zuul has grown the ability to talk to multiple backend systems (Gerrit, Git and plain Git so far).
From a change in gerrit you could have:
Or from a Github pull request:
Tips and certain cases contained further in the full message.

Call For Mentors and Funding

The Outreachy program [0] helps people of underrepresented groups get involved in free and open source software by matching interns with established mentors in the upstream community.
OpenStack will be participating in Outreachy May 2018 to August 2018. Application period opens on February 12th.
Interested mentors should publish their project ideas [1]. You can read more information about being a mentor [2].
Interested sponsors [3] can help provide a stipend to interns for a three month program.

Community Goals for Rocky

TC voted by not approved yet:
  • Remove mox [0]
  • Toggle the debug option at runtime [1]
Comment now on the two selected goals, or the TC will approve them and they’ll be discussed at the PTG.

End of PTL Nominations

Official candidate list available [0]. There are 0 projects without candidates, so the TC will not have to appoint an PTL’s.
Three projects will have elections: Kolla, QA and Mistral.

User Group Newsletter – January 2018

Welcome to 2018!


Important Vancouver Summit Updates

The countdown is on until the next Summit in May. Below are some important updates regarding CFP, Travel and Summit Passes

  • CFP is now open!

Call for presentations are now open for the Vancouver Summit. The deadline to submit your proposal is February 8th.

There are some new changes to the structure of the CFP, such as track organisation. Read more here. 

  • Summit Passes and Hotels

These sold quick in 2015 when we last went to Vancouver, don’t miss out and secure yours today. You can do so here

  • Visas

For information regarding Visa applications and invitation letters, read about it here.

As a general planning guideline, if a visa is needed, a foreign traveler should apply for his or her visa as soon as possible, preferably no later than 60 days before the travel date.

  • Travel Support Program

The Travel Support Program (TSP) aims to facilitate participation of key contributors to the OpenStack Summit by covering the costs for their travel and accommodations. The grants will cover a combination of flights, accommodation, and access pass to the Summit. More details here.

All contributors to OpenStack (developers, documentation writers, organizers of user groups around the world, Ask moderators, speakers, translators, etc) are invited to submit a request. You can apply by filling out this form.

  • More Questions?

Got any other questions about the Summit? There is an excellent FAQ here

Ops Meetup Tokyo

The next OpenStack Ops Meetup is happening March 6-7 in Tokyo.

Register here.

Information from Wiki

Project Teams Gathering (PTG)

The Project Teams Gathering (PTG) in Dublin February 26 – March 2. It’s an event for anyone who self-identifies as a member in a specific given project team as well as operators who are specialists on a given project and willing to spend their time giving feedback on their use case and contributing their usage experience to the project team.

Upcoming Industry Events


The Foundation will be present at FOSDEM in Brussels, February 3-4 2018.

OpenStack booth will be in building K, level 1


OpenStack delivers a keynote at Chaosscon

Feb 2, 2018 in Brussels


Upcoming CFP

LF Open Source Leadership

Closing date: January 21, 2018

OSCON 2018

Closing Date: January 30, 2018

LinuxCon ContainerCon | CloudOpen China

Closing Date: March 4, 2018

ONS Europe

Closing Date: June 24, 2018

OpenStack Technical Committee E-office Hours

The TC has e-office hours each week to field any questions you may have.

Find out more details here:

Developer Mailing List Digest January 5-12th

Success Bot Says

  • e0ne on #openstack-horizon [0]: amotoki runs horizon with django 2.0
  • tristianC on #rdo [1]: review.rdoproject.org is now running sf-2.7
  • mriedem on #openstack-nova [2]: nova merged alternate hosts support for server build
  • mriedem on #openstack-nova [3]: After a week of problems, finally got a volume multiattach test run to actually attach a volume to two instances without melting the world. \o/
  • Tell us yours in OpenStack IRC channels using the command “#success <comment>”

Community Goals for Rocky

So far one goal has been proposed by Kendall Nelson for migrating to Storyboard. It was agreed to postpone the goal until the S cycle, as it could take longer than six months to achieve. There is a good backlog of goals [0], just no champions. It’ll be bad for momentum if we have a cycle with no community wide goal.

PTG Post-lunch Presentations

Feedback received from past PTG session(s) was the lack of situational awareness and missed opportunity for “global” communication at the event. In Dublin we’d used the end of the lunch break to for communications that could be interesting to OpenStack upstream developers and project team members. The idea is not to find a presentation for everyday, but if we find content that is generally useful. Interesting topics include general guidance to make the most of the PTG weeks (good Monday content), development tricks, code review etiquette, new library features you should adopt, lightning talks (good Friday content). We’d like to keep the slot under 20 minutes. If you have ideas please fill out this etherpad [0] in a few weeks.