[openstack-dev] [tc] Technical Committee Status update, December 22nd

Thierry Carrez thierry at openstack.org
Fri Dec 22 10:25:25 UTC 2017


Hi!

This is the weekly summary of Technical Committee initiatives. You can
find the full list of all open topics (updated twice a week) at:

https://wiki.openstack.org/wiki/Technical_Committee_Tracker

If you are working on something (or plan to work on something) that is
not on the tracker, feel free to add to it !


== Recently-approved changes ==

* Add assert:supports-accessible-upgrade to designate [1]
* neutron-vpnaas is an official Neutron deliverable again [2]
* Packaging-Deb now officially moved to Debian infra [3]
* Moved repos: tripleo-ci is now a tripleo team repository
* New repos: monasca-tempest-plugin, vitrage-tempest-plugin,
trove-tempest-plugin, ec2api-tempest-plugin, telemetry-tempest-plugin
* Removed repos: puppet-apps_site, and all packaging-deb repos
* Goal updates: watcher, freezer, cinder, manila

[1] https://review.openstack.org/528315
[2] https://review.openstack.org/#/c/527255/
[3] https://review.openstack.org/#/c/524732/

Biggest news in this slow pre-holidays week is that Designate now
supports accessible upgrades (meaning the controlled resources stay
accessible during an upgrade). For more details about this tag
requirements, please see:

https://governance.openstack.org/tc/reference/tags/assert_supports-accessible-upgrade.html

Also worth of note, the removal of the Packaging-Deb project team and
repositories, as that work is now being done directly in the Debian
community and project infrastructure.


== Voting in progress ==

Upgrade assertion tags (like the one Designate just added above) do not
apply to every OpenStack deliverable: they are limited to OpenStack
"services". The tag definition used language around deliverable types
that is no longer current and needs updating. Please see:

https://review.openstack.org/#/c/528745/


== Under discussion ==

The same items as last week carried out.

The discussion started by Graham Hayes to clarify how the testing of
interoperability programs should be organized in the age of add-on
trademark programs is still going on, with most people still trying to
wrap their heads around the various options. We'd welcome more opinions
on that thread, so please chime in on the review:

https://review.openstack.org/521602

Matt Treinish proposed an update to the Python PTI for tests to be
specific and explicit. Wider community input is needed on that topic.
Please review at:

https://review.openstack.org/519751

We still only have one goal proposed for Rocky. We need other proposals
before we can make a call. See the thread:

http://lists.openstack.org/pipermail/openstack-dev/2017-November/124976.html


== TC member actions for the coming week(s) ==

Take some time off, meet with family and friends, celebrate $holiday
and/or new year !


== Office hours ==

To be more inclusive of all timezones and more mindful of people for
which English is not the primary language, the Technical Committee
dropped its dependency on weekly meetings. So that you can still get
hold of TC members on IRC, we instituted a series of office hours on
#openstack-tc:

* 09:00 UTC on Tuesdays
* 01:00 UTC on Wednesdays
* 15:00 UTC on Thursdays

For the coming week, I expect nobody to show up :)


== A final 2017 note ==

I'd like to take this moment to thank everyone in the OpenStack
community. 2017 has been a transitional year for this project, which
triggered a lot of changes and stress. We established a new event, the
PTG, we tackled a series of strategic issues, and we navigated through a
number of shifts in our ecosystem. Looking back, I think we
(collectively) generally handled it well and gracefully. Those efforts
are not finished yet, but as we take some time off for the end-of-year
holidays, let's all relax a bit, take a step back and be proud of what
we achieved.

Our adoption skyrocketed over the last year. More than ever, the world
turns to OpenStack when it needs an open-source,
collaboratively-developed, no lock-in, open infrastructure framework. We
run from public clouds to scientific ships, we power e-commerce, hadron
colliders, trains, mobile phone networks or financial transactions. We
enable everyone else to build great things. That's all thanks to you and
your efforts. Be proud.

Cheers,

-- 
Thierry Carrez (ttx)



More information about the OpenStack-dev mailing list