April 2020 - openstack-discuss - lists.openstack.org

[octavia] dropping support for stable/queens
by Adam Harwell 10 Apr '20

10 Apr '20

I'm officially proposing dropping support for the queens stable branch of Octavia. Given a quorum of cores, we will move forward with marking it EOL and all that entails. Thanks, --Adam

5 5

[all][PTL][TC] U Community Goal: Project PTL & Contrib Docs Update #6
by Kendall Nelson 10 Apr '20

10 Apr '20

Hello Everyone! While we may be past feature freeze there is still time to complete this goal given that it is documentation focused. I urge those that have not started to do so immediately. If you need help, please let me know ASAP. For those projects that have not started yet, I would start with filling in the template[2] and then go take a look at what the others have done for more inspiration[1]. If you have any questions, please let me know or refer to the goal[3]. Once you get started, please make sure to keep the story up to date[4]. I look forward to reviewing your patches!! If there is anything I can do to help, please let me know. And also, I want to give a HUGE thank you to those that have already started/completed the goal! Nice work :) -Kendall (diablo_rojo) [1] Progress: https://review.opendev.org/#/q/topic:project-ptl-and-contrib-docs+(status:o… [2] Cookiecutter Template: https://opendev.org/openstack/cookiecutter/src/branch/master/%7b%7bcookiecu… [3] Accepted Goal: https://governance.openstack.org/tc/goals/selected/ussuri/project-ptl-and-c… [4] Task Tracking: https://storyboard.openstack.org/#!/story/2007236

1 0

[release] Release countdown for week R-4, April 13 - 17
by Sean McGinnis 10 Apr '20

10 Apr '20

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the ussuri deliverables can be proposed, well ahead of the final ussuri release date. General Information ------------------- We are still finishing up processing a few release requests, but the ussuri release requirements are now frozen. If new library releases are needed to fix release-critical bugs in ussuri, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in ussuri that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By April 23 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/ussuri branches should be created soon for all not-already-branched libraries. You should expect 3-4 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), a tox.ini constraints URL update, and a patch updating any cycle-specific job templates to the victoria version. Please review those in priority so that the branch can be functional ASAP. Note that the victoria job templates may not be quite ready yet, so the patch may initially fail. A simple recheck once they are in place should allow the patch to pass. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for ussuri changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed ussuri cycle-highlights yet, you are already late to the party. Please see http://lists.openstack.org/pipermail/openstack-discuss/2020-April/013823.ht… for details. Upcoming Deadlines & Dates -------------------------- RC1 deadline: April 23 (R-3 week) Final RC deadline: May 7 (R-1 week) Final Ussuri release: May 13

1 0

[release][nova] FFE request for Nova Policy Defaults Refresh BP
by Ghanshyam Mann 10 Apr '20

10 Apr '20

Hello Everyone, I would like to ask the FFE for policy default refresh BP[1]. Most of the work is merged for this[2] but not 100%. Few policies not yet merged (~7) and 3 policies code is not yet up which I am working on. With that, I need more time to finish this work and require the FFE. [1] https://blueprints.launchpad.net/nova/+spec/policy-defaults-refresh [2] https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+(status:ope… -gmann

3 3

[election][tacker][ptl] Announcing my PTL candidacy for Tacker (Hyunsik Yang)
by hyunsikYang 10 Apr '20

10 Apr '20

Hello all Tacker members! I am Hyunsik Yang from the IISTRC(Internet Infra System Technology Research Center), South Korea. I wish to nominate myself for consideration as a Tacker Project PTL for the Victoria Cycle. I've previously contributed code, bug fixes and several reviews for Tacker from the Queens cycle. My goal is to improve the Tacker project by making it more standardized and precise. If you have any questions, please feel free to ask me. Thank you. Best regards, Hyunsik Yang *----------------------------------------------------------------* *Hyunsik Yang (Ph. D candidate)* *DCN laboratory / School of Electronic Engineering* *Soongsil University * *511 Sangdo-dong Dongjak-gu* *Seoul, 156-743 Korea* *TEL : (+82)-2-820-0841 * *M.P: (+82)-10-9005-7439*

2 2

[all][ideas][releases] Introducing Project Stopwatch: Another proposal to change the release cycles
by Jean-Philippe Evrard 09 Apr '20

09 Apr '20

Hello, I would like us to discuss how our release cycles are defined. We've been discussing in the past about longer or shorter cycles. This is only recorded in the mailing lists, which are hard to search. We should try to record conversations in this new "ideas" framework if we can. I think it's time to record something about the release cycles in our ideas. However, before I start the 2020 version of the eternal war "longer cycles" vs "shorter cycles", I would like us to discuss about something a little bit different, that you can find in review [1]: project Stopwatch. I have discussed with a few of you already about Stopwatch and how we could do cycles differently. This is to write the idea down. For me, it's time to change the cycles, by introducing more time to cool down. To make this happen, I need your opinions, as it quite an impactful change for the whole OpenStack. Regards, Jean-Philippe Evrard [1]: https://review.opendev.org/#/c/718929/

1 0

Etherpad and Gerrit maintenance on 2020-04-10
by corvus＠inaugust.com 09 Apr '20

09 Apr '20

Hi, Tomorrow, April 10, 2020, the OpenDev team will be performing minor updates to two services. * Gerrit restart for https://review.opendev.org/ at 16:00 UTC. This should be a momentary outage to restart the service in a container. We will maintain the same version in the same configuration; this is a preparatory step in order to perform future version upgrades more easily. Other than a short outage of about a minute, there should be no service impact or visible changes, but since the environment is changing, we wanted to announce this in case any problems are detected. * Etherpad migration and domain change at 17:00 UTC. We will migrate the data currently hosted on etherpad.openstack.org to a new server, also running in a container, on etherpad.opendev.org. We will set up redirects so that on completion of the migration, all etherpad.openstack.org URLs will redirect to the same pages on etherpad.opendev.org. https://etherpad.opendev.org/ will become the new canonical service URL. This also includes an upgrade to the latest release of Etherpad Lite (1.8.0). This involves a database migration as well. The service will be unavailable for the duration of this migration (expected to be about 30 minutes). Please report any issues in #opendev on Freenode or to the service-discuss(a)lists.opendev.org mailing list. Note that this message is being sent to service-announce and several other lists. Future announcements of this type will only be sent to service-announce, so please sign up[1] for that list if you haven't already. [1] http://lists.opendev.org/cgi-bin/mailman/listinfo/service-announce -Jim

1 0

[release][oslo] FFE request for Oslo Policy
by Ghanshyam Mann 09 Apr '20

09 Apr '20

Hi, This is regarding the FFE request for policy for - https://review.opendev.org/#/c/717879/ This is part of introducing scope_type and new defaults in policies. During Nova implemtnation[1], we came across two things to solve before we release the new policies changes: 1. A lot of warnings as policy default are changing which end up filling the logs (226 MB n-api logs today). 2. Give operators an option to switch to the new system (scope and new defaults) at the same time without overwriting the policy file. We discussed those two things to solve via oslo_policy[2] which need FFE approval. Sorry for being late on this which should be planned early. Please let me know if it is ok to include these changes in the Ussuri release. [1] https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh+(status:ope… [2] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.… -gmann

4 5

[kolla] Kolla Klub first meeting tomorrow
by Mark Goddard 09 Apr '20

09 Apr '20

Hi Kollaborators, Just a reminder that we will meet tomorrow at 15:00 UTC. Join here: https://meet.google.com/hph-pynx-vsy I have created a Google doc for the meeting agenda and notes: https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_…. See you tomorrow, Mark

1 1

[neutron] Drivers meeting - 10.04.2020
by Slawek Kaplonski 09 Apr '20

09 Apr '20

Hi, I will be on PTO on Good Friday so lets cancel our drivers meeting at that day. See You all on drivers meeting next week. And have a great holidays :) — Slawek Kaplonski Senior software engineer Red Hat

1 0