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

[tc][election] Simple question for the TC candidates
by Jean-Philippe Evrard 09 Apr '20

09 Apr '20

Hello, I read your nominations, and as usual I will ask what do you _technically_ will do during your mandate, what do you _actively_ want to change in OpenStack? This can be a change in governance, in the projects, in the current structure... it can be really anything. I am just hoping to see practical OpenStack-wide changes here. It doesn't need to be a fully refined idea, but something that can be worked upon. Thanks for your time. Regards, Jean-Philippe Evrard

12 26

[manila][release] Ussuri release preparation
by Goutham Pacha Ravi 09 Apr '20

09 Apr '20

Hi Stackers, (Following gibi's lead here on relaying release status to the ML) We're at feature freeze, and I'm providing the current state of Ussuri release deliverables from the manila team: openstack/python-manilaclient is waiting on a couple of changes: - Release patch: https://review.opendev.org/#/c/718254/ - Pending changes: bp/create-share-from-snapshot-in-another-pool-or-backend: - https://review.opendev.org/#/c/712543/ bp/graduate-share-groups-feature - https://review.opendev.org/#/c/708282/ openstack/manila-ui has a few open bug-fixes, we'll target a release in the next week or so: - https://review.opendev.org/#/q/topic:bug/1823078 openstack/manila has the following pending changes concerning Feature Freeze - bp/create-share-from-snapshot-in-another-pool-or-backend: - https://review.opendev.org/#/c/709697/ (Manila server side changes) - https://review.opendev.org/#/c/711611/ (ZFSOnLinux implementation) - https://review.opendev.org/#/c/712642/ (NetApp driver implementation) - bp/graduate-share-groups-feature - https://review.opendev.org/#/c/706959/ Ussuri Release goals status: - Drop Python 2.7 Support - Complete - Project Specific PTL and Contributor Documentation - In-Progress Thanks, Goutham

1 0

[StoryBoard][Security] The process to report a security bug
by Lingxian Kong 09 Apr '20

09 Apr '20

As most of the projects have migrated to storyboard for bug tracking, after reading https://security.openstack.org/vmt-process.html, I have two questions: 1. I didn't find openstack/ossa or ossa project exists in storyboard. 2. I didn't find a place in storyboard to attach a patch. Am I missing something? - Best regards, Lingxian Kong Catalyst Cloud

2 3

[all] Please remove all external resources from docs
by Thomas Goirand 09 Apr '20

09 Apr '20

Hi, I've wrote about this earlier I guess, but I believe I need to do it once more. Often I see in the docs things like this: .. image:: https://governance.openstack.org/tc/badges/<FOO>.svg :target: https://governance.openstack.org/tc/reference/tags/index.html [note: this is only one simple example, there's many of other types linking to external images, I've even seen stuff linking to CDNs...] I'd like to see these go away. Indeed, distributions like mine (ie: Debian) are packaging the doc. And it's *very* annoying when one browses the doc to have such an external link, and the browser going on the internet to fetch an external resource. So, in Debian, I'm patching these away. Often, the most ugly way where I don't care about the resulting document (as long as the doc is there). This is both annoying, and a loss of my time. The solution is simple: have the resource being *LOCAL* (ie: stored in the project's doc), not stored on an external site. Thanks to anyone who will follow this advice. Cheers, Thomas Goirand (zigo)

7 9

[nova] Ussuri release preparation
by Balázs Gibizer 09 Apr '20

09 Apr '20

Hi, Today is Feature Freeze for Ussuri and the final release of novaclient for Ussuri. Release TODOs are tracked in [1]. Any feature code in nova that is approved before end of today is OK to be rechecked or rebased if needed after the freeze. Features that are close to land but haven't approved until the freeze, needs a Feature Freeze Exception on the ML or they will be postponed to the Victoria cycle. When you request such FFE please try to find cores who support your request. Bug fixes, test coverage and documentation enhancements are still OK to be proposed after the freeze. However please be careful approving risky patches. Any release blocker issue should have a bug tagged with ussuri-rc-potential in launchpad. Please also add them the the etherpad [1] Cheers, gibi [1] https://etherpad.openstack.org/p/nova-ussuri-rc-potential

1 0

Re: [Release-job-failures] release-post job for openstack/releases for ref refs/heads/master failed
by Sean McGinnis 08 Apr '20

08 Apr '20

On 4/8/20 4:53 PM, zuul(a)openstack.org wrote: > Build failed. > > - tag-releases https://zuul.opendev.org/t/openstack/build/28b78b5235894878b4cb92822b95bbff : FAILURE in 5m 53s > - publish-tox-docs-releases https://zuul.opendev.org/t/openstack/build/None : SKIPPED This failure was due to a new operation we added to the branching process. Once working, the new code will propose patches to branched repos to update them to use the job template defined for the next release cycle, similar to how the patches are proposed to update reno. I think this was due to an error in a sed command that is used to perform that update, and will hopefully be fixed after https://review.opendev.org/718564 merges. No further action is needed here. The only thing missed was the publishing of the releases docs, but that will be corrected with the next release patch that goes through. Sean

1 0

[all][PTL][release] Call for Ussuri Cycle Highlights
by Kendall Nelson 08 Apr '20

08 Apr '20

Hello Everyone! Its time to start thinking about calling out 'cycle-highlights' in your deliverables! As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from the last few releases: Rocky[1], Stein[2], Train[3]. We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. Looking through your release notes might be a good place to start. *The deadline for cycle highlights is the end of the R-5 week [4] on April 10th.* How To Reminder: ------------------------- Simply add them to the deliverables/train/$PROJECT.yaml in the openstack/releases repo like this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin. The formatting options for this tag are the same as what you are probably used to with Reno release notes. Also, you can check on the formatting of the output by either running locally: tox -e docs And then checking the resulting doc/build/html/train/highlights.html file or the output of the build-openstack-sphinx-docs job under html/train/ highlights.html. Can't wait to see you all have accomplished this release! Thanks :) -Kendall Nelson (diablo_rojo) [1] https://releases.openstack.org/rocky/highlights.html [2] https://releases.openstack.org/stein/highlights.html [3] https://releases.openstack.org/train/highlights.html [4] htt <https://releases.openstack.org/train/schedule.html#t-cycle-highlights> https://releases.openstack.org/ussuri/schedule.html

2 5

No UC meeting this week
by Mohamed Elsakhawy 08 Apr '20

08 Apr '20

Hi All, There will be no UC meeting tomorrow. Our next meeting is on Thursday April 16th in our regular time. Thanks Mohamed

1 0

[all] Gate status: tempest-full broken on stein
by Ghanshyam Mann 08 Apr '20

08 Apr '20

Hello Everyone, tempest-full (py2 job) started failing on stable/stein gate because devstack try to install master Tempest on system-wide and fail for min require py version by Tempest. We did not set the INSTALL_TEMPEST flag to false for stable branches since stable/pike. I am going to add this as one of thing to do while cutting devstack stable branch. More details on Bug: https://bugs.launchpad.net/tempest/+bug/1871327 Here are the fixes, I am backporting from stable/train: Please hold the recheck until they are merged. https://review.opendev.org/#/q/I60949fb735c82959fb2cfcb6aeef9e33fb0445b6 -gmann

1 2

[tc][oslo] Looking for a Victoria Oslo PTL volunteer
by Thierry Carrez 08 Apr '20

08 Apr '20

Hello everyone, Nobody stepped up yet to continue the great work of Ben Nemec as PTL of the Oslo project team. Oslo handles common code between our various projects, and is key to reduce duplication of code and waste of effort. Oslo is very critical for OpenStack, as all other projects depend on its libraries, but can be relatively low-maintenance as most libraries are feature-complete. Being the Oslo PTL gives you a great horizontal perspective on OpenStack, so they are a great opportunity for smaller organizations that depend on OpenStack to keep track of what's happening and contribute back, without having to specialize in one of the larger projects. I suspect Ben can help answer any question on the workload it represents to be the Oslo PTL. Getting a new volunteer for Oslo PTL is our preferred solution. In case the PTL position is just too intimidating and nobody volunteers, the TC is considering experimenting with a PTL-less form of governance that would involve only designating two liaisons (a release liaison(s) and a security liaison(s)). That is the minimal accountability that we require of an openstack project team (someone(s) signing off releases, and someone(s) to contact in case of embargoed vulnerabilities). I say "someone(s)" as ideally multiple people sign up to be a liaison. In that form of governance, if there is any conflict in the team, the TC can ultimately arbitrate the conflict, instead of the PTL. That would be our plan B. So please let us know if you'd be interested in the Oslo PTL position, or if you'd be OK just for filling the duties of a specific liaison. Thanks for considering it! -- Thierry Carrez (ttx)

3 3