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>”


[0] –

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>”


[0] –!/project/923

Community Summaries

Release countdown [0]

TC report [1]

Technical Committee status update [2]

[0] –
[1] –
[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]

[0] –
[1] –
[2] –
[3] –
[4] –
[5] –
[6] –
[7] –
[8] –
[9] –
[10] –
[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!

[0] –
[1] –

Full message:

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

[0] –
[1] –

Full message:

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.

[0] –

Full thread:

Developer Mailing List Digest February 17-23rd

Helpful PTG links

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

Main welcome email
Quick links:
PDF schedule:
PDf map for PTG venue:

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>”

[0] –

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>”

Community Summaries

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

[0] –
[1] –
[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.

[0] –

Full message:

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].

[0] –
[1] –

Full message:

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.

Full message:

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.

[0] –
[1] –

Full thread:

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.

[0] –
[1] –

Full message:

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:


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. 


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 FODSEM 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]: 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/

zaneb [4]: 14% reduction in Heat memory use in the TripleO gate from fixing

Tell us yours in OpenStack IRC channels using the command “#success <comment>”


[0] –
[1] –
[2] –
[3] –
[4] –

Community Summaries

Technical Committee Status update [0]

POST /api-sig/news [1]

Release countdown [2]

Nova placement resource provider update [3]

Keystone team update [4]

Nova Notification Update [5]

TC report [6]

[0] –
[1] –
[2] –
[3] –
[4] –
[5] –
[6] –

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.

[0] –

Full thread:

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.

[0] –

Full thread:

Developer Mailing List Digest November 11-17


POST /api-sig/news [0]
Release countdown for week R-14, November 18-24 [1]

[0] –
[1] –
Upstream Long Term Support Releases
The Sydney Summit had a very well attended and productive session [0] about to go about keeping a selection of past releases available and maintained for long term support (LTS).
In the past the community has asked for people who are interested in old branches being maintained for a long time to join the Stable Maintenance team with the premise that if the stable team grew, it could support more branches for longer periods. This has been repeated for about years and is not working.
This discussion is about allowing collaboration on patches beyond end of life (EOL) and enable whoever steps up to maintain longer lived branches to come up with a set of tests that actually match their needs with tests that would be less likely to bitrot due to changing OS/PYPI substrate. We need to lower expectations of what we’re likely to produce will get more brittle the older the branch gets. Any burden created by taking on more work is absorbed by people doing the work, as does not unduly impact the folks not interested in doing the work.
The idea is to continue the current stable policy more or less as it is. Development teams take responsibility of a couple of stable branches. At some point what we now call an EOL branch, instead of deleting it we would leave it open and establish a new team of people who want to continue to main that branch. It’s anticipated the members of those new teams are coming mostly from users and distributors. Not all branches are going to attract teams to maintain them, and that’s OK.
We will stop tagging these branches so the level of support they provide are understood. Backports and other fixes can be shared, but to consume them, a user will have to build their own packages.
Test jobs will run as they are, and the team that maintain the branch could decide how to deal with them. Fixing the jobs upstream where possible is preferred, but depending on who is maintaining the branch, the level of support they are actually providing and the nature of the breakage, removing individual tests or whole jobs is another option. Using third-party testing came up but is not required.
Policies for the new team being formed to maintain these older branches is being discussed in an etherpad [2].
Some feedback in the room expressed they to start one release a year who’s branch isn’t deleted after a year. Do one release a year and still keep N-2 stable releases around. We still do backports to all open stable branches. Basically do what we’re doing now, but once a year.
Discussion on this suggestion extended to the OpenStack SIG mailing list [1] suggesting that skip-release upgrades are a much better way to deal with upgrade pain than extending cycles. Releasing every year instead of a 6 months means our releases will contain more changes, and the upgrade could become more painful. We should be release often as we can and makes the upgrades less painful so versions can be skipped.
We have so far been able to find people to maintain stable branches for 12-18 months. Keep N-2 branches for annual releases open would mean extending that support period to 2+ years. If we’re going to do that, we need to address how we are going to retain contributors.
When you don’t release often enough, the pressure to get a patch “in” increases. Missing the boat and waiting for another year is not bearable.
[0] –
[1] –
[2] –

Developer Mailing List Digest November 18-27

Community Summaries

Glance priorities [0]
Nova placement resource provider update [1]
Keystone Upcoming Deadlines [2]
Ironic priorities and subteam reports [3]
Keystone office hours [4]
Nova notification update [5]
Release countdown [6]
Technical committee status update [7]

[0] –
[1] –
[2] –
[3] –
[4] –
[5] –
[6] –
[7] –

Self-healing SIG created

Adam Spiers announced the formation of a SIG around self-healing. Its scope is to coordinate the use and development of several OpenStack projects which can be combined in various ways to manage OpenStack infrastructure in a policy-driven fashion, reacting to failures and other events by automatically healing and optimising services.

Full thread:

Proposal for a QA SIG

A proposal to to have a co-existing QA special interest group (SIG) that would be a place for downstream efforts to have a common place in collaborating and sharing tests. Example today the OPNFV performs QA on OpenStack releases today and are actively looking for opportunities to share tools and test cases. While a SIG can exist to do some code, the QA team will remain for now since there are around 15 QA projects existing like Tempest and Grenade.

Full thread:

Improving the Process for Release Marketing

Collecting and summarizing “top features” during release time is difficult for both PTL’s and Foundation marketing. A system is now in place for PTL’s to highlight release notes [0]. Foundation marketing will work with the various teams if needed to understand and make things more press friendly.

Full thread:

[0] –

Developer Mailing List Digest November 25 to December 1st


Project Team Gather (PTG) in Dublin registration is live [0]

[0] –

Community Summaries

TC report by Chris Dent [0]

Release countdown [1]

Technical Committee Status updated [2]

POST /api-sig/news [3]

Nova notification update [4]

Nova placement resource providers update [5]

[0] –
[1] –
[2] –
[3] –
[4] –
[5] –

Dublin PTG Format

We will continue themes as we did in Denver (Monday-Tuesday), but shorter times like half days. Flexibility is added for other groups to book the remaining available rooms in 90-min slots on-demand driven by the PTG Bot (Wednesday-Friday.

Full thread:

First Contact SIG

A wiki has been created for the group [0]. The group is looking for intersted people being points of contact for newcomers and what specified time zones. Resource links like contributor portal, mentoring wiki, Upstream Institute, outreachy are being collected on the wiki page. A representative from the operators side to chair and represent would be good.

[0] –

Policy Goal Queens-2 Update

Queens-2 coming to a close, we recap our community wide goal for policies [0]. If you want your status changed, contact Lance Bragstad. Use the topic policy-and-docs-in-code for tracking related code changes.

Not Started











In Progress






























Full thread:

Tempest Plugin Split Goal

A list of open reviews [0] is available for the Tempest plugin split goal [1].

Not Started


In Progress




[0] –
[1] –