Welcome new members to the OpenStack Technical Committee

Please join the community in congratulating the five newly elected members of the OpenStack Technical Committee (TC). Graham Hayes (mugsie) Kristi Nikolla (knikolla) Mohammed Naser (mnaser) Belmiro Moreira (belmoreira) Rico Lin (ricolin) These members join: Kendall Nelson (diablo_rojo) Jay Bryant (jungleboyj) Jean-Phillippe Evrard (evrardjp) Nate Johnston (njohnston) Ghanshyam Mann (gmann) Kevin Carter (cloudnull) For more… Read more »
Quelle: openstack.org

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

Developer Mailing List Digest February 17-23rd

Helpful PTG links

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

Main welcome email http://lists.openstack.org/pipermail/openstack-dev/2018-February/127611.html
Quick links: http://ptg.openstack.org/
PDF schedule: http://lists.openstack.org/pipermail/openstack-dev/attachments/20180221/5c279bb3/attachment-0002.pdf
PDf map for PTG venue: http://lists.openstack.org/pipermail/openstack-dev/attachments/20180221/5c279bb3/attachment-0003.pdf

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

[0] – https://www.openstack.org/community

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]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127584.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127651.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127465.html

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] – https://openstackfoundation.formstack.com/forms/cca_nominations_vancouver

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127634.html

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] – https://wiki.openstack.org/wiki/Release_Naming/S_Proposals
[1] – https://governance.openstack.org/tc/reference/release-naming.html

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127592.html

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: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127540.html

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] – https://review.openstack.org/#/c/522290/
[1] – http://codesearch.openstack.org/?q=oslo_db.tests&i=nope&files=&repos=

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2018-February/thread.html#127531

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] – https://docs.openstack.org/infra/zuul/user/config.html#attr-job.post-timeout
[1] – https://docs.openstack.org/infra/zuul/user/config.html#attr-job.host-vars

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127591.html
Quelle: openstack.org

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

More: https://wiki.openstack.org/wiki/Successes

[0] – https://www.translate.openstack.org

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

More: https://wiki.openstack.org/wiki/Thanks

[0] – https://storyboard.openstack.org/#!/project/923

Community Summaries

Release countdown [0]

TC report [1]

Technical Committee status update [2]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128036.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127991.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128098.html

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] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127936.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127937.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127968.html
[3] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127988.html
[4] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127994.html
[5] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128002.html
[6] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128005.html
[7] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128041.html
[8] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128044.html
[9] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128055.html
[10] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128085.html
[11] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128094.html

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] – https://releases.openstack.org/queens/
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127813.html

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127812.html

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] – https://etherpad.openstack.org/p/release-cycles-ptg-rocky
[1] – https://review.openstack.org/#/c/548916/

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128005.html

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] – http://superuser.openstack.org/articles/community-participation-remote/

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2018-March/thread.html#128043
Quelle: openstack.org

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:

 
Quelle: openstack.org

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:

Quelle: openstack.org

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
Quelle: openstack.org

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

More: https://wiki.openstack.org/wiki/Successes

[0] – https://www.translate.openstack.org

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

More: https://wiki.openstack.org/wiki/Thanks

[0] – https://storyboard.openstack.org/#!/project/923

Community Summaries

Release countdown [0]

TC report [1]

Technical Committee status update [2]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128036.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127991.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128098.html

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] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127936.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127937.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127968.html
[3] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127988.html
[4] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/127994.html
[5] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128002.html
[6] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128005.html
[7] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128041.html
[8] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128044.html
[9] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128055.html
[10] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128085.html
[11] – http://lists.openstack.org/pipermail/openstack-dev/2018-March/128094.html

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] – https://releases.openstack.org/queens/
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127813.html

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127812.html

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] – https://etherpad.openstack.org/p/release-cycles-ptg-rocky
[1] – https://review.openstack.org/#/c/548916/

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-March/128005.html

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] – http://superuser.openstack.org/articles/community-participation-remote/

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2018-March/thread.html#128043
Quelle: openstack.org

Developer Mailing List Digest February 17-23rd

Helpful PTG links

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

Main welcome email http://lists.openstack.org/pipermail/openstack-dev/2018-February/127611.html
Quick links: http://ptg.openstack.org/
PDF schedule: http://lists.openstack.org/pipermail/openstack-dev/attachments/20180221/5c279bb3/attachment-0002.pdf
PDf map for PTG venue: http://lists.openstack.org/pipermail/openstack-dev/attachments/20180221/5c279bb3/attachment-0003.pdf

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

[0] – https://www.openstack.org/community

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]

[0] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127584.html
[1] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127651.html
[2] – http://lists.openstack.org/pipermail/openstack-dev/2018-February/127465.html

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] – https://openstackfoundation.formstack.com/forms/cca_nominations_vancouver

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127634.html

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] – https://wiki.openstack.org/wiki/Release_Naming/S_Proposals
[1] – https://governance.openstack.org/tc/reference/release-naming.html

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127592.html

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: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127540.html

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] – https://review.openstack.org/#/c/522290/
[1] – http://codesearch.openstack.org/?q=oslo_db.tests&i=nope&files=&repos=

Full thread: http://lists.openstack.org/pipermail/openstack-dev/2018-February/thread.html#127531

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] – https://docs.openstack.org/infra/zuul/user/config.html#attr-job.post-timeout
[1] – https://docs.openstack.org/infra/zuul/user/config.html#attr-job.host-vars

Full message: http://lists.openstack.org/pipermail/openstack-dev/2018-February/127591.html
Quelle: openstack.org