May 2020 - openstack-discuss - lists.openstack.org

[Neutron] How to change the MAC address of Gateway interface of the router
by Rahul Sharma 20 May '20

20 May '20

Hi, I have setup a multi-host openstack cloud on AWS consisting of 3 servers i.e. Controller, Compute & Network Everything is working as expected. My requirement is that the compute instances should be able to communicate with the internet and vice-versa. However, AWS due to its security policies will drop all traffic that is sourced from the VMs because the VM traffic will have the MAC address of the gateway interface of the router when it hits the AWS switch. This MAC address is not know to AWS hence it drops this traffic. AWS will allow only that traffic that contains the registered MAC address as its source address So I need to change the MAC address of the gateway interface of the L3 router on the network node. I tried googling but could not find any solution. Is there any solution/command to do this ? Thanks, Kaushik

2 2

[largescale-sig] Next meeting: May 20, 8utc
by Thierry Carrez 20 May '20

20 May '20

Hi everyone, The Large Scale SIG will have a meeting this week on Wednesday, May 20 at 8 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200520T08 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - amorin to propose patch against Nova doc - ttx to create an empty oslo-metric repository - masahito to finalize oslo.metric POC code release Talk to you all on Wednesday, -- Thierry Carrez

1 1

[operators] multi release upgrades?
by Fabian Zimmermann 20 May '20

20 May '20

Hi, Does anybody did already some multi release upgrades f.e. queens->train and is able to share his knowhow? Thanks, Fabian

3 2

Re: [Cyborg][PTG]Virtual PTG Planning
by yumeng bao 19 May '20

19 May '20

Hi team, I have booked the following slots for Cyborg Virtual PTG [1] based on the doodle poll results. * June 2 Tuesday 6:00 UTC - 8:00 UTC, Room Cactus * June 3 Wednesday 6:00 UTC - 8:00 UTC,Room Cactus * June 4 Thursday 6:00 UTC - 8:00 UTC,Room Cactus *June 5 Friday 6:00 UTC - 8:00 UTC,Room Bexar Moreover, I have synced with Slaweq and gibi, and we agreed to have a Nova-Neutron-Cyborg cross project discussion on Friday from 14:00 UTC to 15:00 UTC in Room Juno (Thanks to Nova for sharing this time slot!) There are two weeks to go before the virtual PTG. So I would like to encourage you to LOOK AT the etherpad[2] and ADD YOUR NAME to the Attendance section if you are planning to attend! If you have topics for the PTG, please try to start discussing them now either in the etherpad[2] or in a spec or just on the ML. (Such preparation is especially necessary for those cross project topics to get agreements/directions internally first, we have very limited time to conclude the topics during the PTG.) Let’s continue discussing this at tomorrow’s weekly meeting. [1] https://ethercalc.openstack.org/126u8ek25noy [2] https://etherpad.opendev.org/p/cyborg-victoria-goals Regards， Yumeng

1 0

[tripleo][ci] remove upstream multinode scenario jobs (queens, rocky)
by Wesley Hayutin 19 May '20

19 May '20

Greetings, I'd like to propose that we start removing multinode ( 2 node ) based scenario jobs from the upstream that still exist in queens and rocky. We will continue to support a basic multinode deployment [1 ] across all the branches. From stable/stein on we only maintain one multinode job, and the scenarios have all been migrated to single node deployments. The loss of coverage will be augmented by the RDO promotion pipeline [2] that should be verifying all the upstream check/gate jobs across the branches. Issues will be caught periodically vs. on a per patch basis. Issues will be reported, debugged and sent to the appropriate teams. I am not proposing we do this overnight or in one giant patch, but over time start to remove the upstream coverage. We also need to ensure that the upstream version is properly covered in RDO software factory. WHY??? Two node deployments in upstream infrastructure are very unreliable and often timeout. Generally devolving into noise and wasted resources and time spent by developers trying to land patches [3]. Comments / Questions?? [1] tripleo-ci-centos-[7,8]-containers-multinode [2] https://review.rdoproject.org/zuul/builds?pipeline=openstack-periodic-wedne… [3] https://bugs.launchpad.net/tripleo/+bug/1879565

1 0

Virtual PTG Schedule Live & Registration Reminder
by Kendall Waters 19 May '20

19 May '20

Hey everyone, The June 2020 Project Teams Gathering is right around the corner! The official schedule has now been posted on the PTG website [1], the PTGbot has been updated[2], and we have also attached it to this email. Friendly reminder, if you have not already registered, please do so [3]. It is important that we get everyone to register for the event as this is how we will contact you about tooling information and other event details. Please let us know if you have any questions. Cheers, The Kendalls (diablo_rojo & wendallkaters) [1] www.openstack.org/ptg <http://www.openstack.org/ptg> [2] http://ptg.openstack.org/ptg.html <http://ptg.openstack.org/ptg.html> [3] https://virtualptgjune2020.eventbrite.com <https://virtualptgjune2020.eventbrite.com/>

1 0

[ironic] trusted delgation cores?
by Julia Kreger 19 May '20

19 May '20

Greetings awesome people and AIs! Earlier today, I noticed Iury (iurygregory) only had +1 rights on the ironic-prometheus-exporter. I noted this in IRC and went to go see about adding him to the group, and realized we didn't have a separate group already defined for ironic-prometheus-exporter, which left a question, do we create a new group, or just grant ironic-core membership. And the question of starting to engage in trusted delegation of core rights came up in IRC[0]. I think it makes a lot of sense, but wanted to see what everyone thought? Specifically in Iury's case: I feel he has proven himself, in ironic and non-ironic cases, and I think it makes sense to grant him core rights under the premise that he is unlikely to approve non-trivial changes to merge that he is not confident in. Thoughts, concerns, congratulations? For both questions? -Julia [0]: http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-iro…

6 5

[tripleo][ptg] schedule posted
by Wesley Hayutin 19 May '20

19 May '20

Greetings owls, Victoria Schedule has been posted [1]. There are a lot of great topics so we're going to limit the time slots to 1/2 hour each. Creating a blueprint and spec for your topic prior to the PTG will help you make your point and win the game of influence [2]. Please feel free to self sign up on the schedule, I will cross check any unassigned topics prior to the event and punt them to the last day. For now we're going to close adding new topics to fit the schedule. There is spare time on the calendar for Q&A and random ad hoc topics [3] if needed. To prepare for your presentations please ensure you are comfortable w/ the video conferencing [4] as much as possible. Looking forward to seeing you all Thanks!! [1] https://etherpad.opendev.org/p/tripleo-ptg-victoria [2] https://review.opendev.org/#/q/project:openstack/tripleo-specs+status:open https://blueprints.launchpad.net/tripleo [3] https://ethercalc.openstack.org/126u8ek25noy [4] https://meetpad.opendev.org/

1 0

[keystone] scope enforcement ready for prime time?
by Mark Goddard 19 May '20

19 May '20

Hi, I have a use case which I think could be fulfilled by scoped tokens: Allow an operator to delegate the ability to an actor to create users within a domain, without giving them the keys to the cloud. To do this, I understand I can assign a user the admin role for a domain. It seems that for this to work, I need to set [oslo_policy] enforce_scope = True in keystone.conf. The Train cycle highlights suggest this is now fully implemented in keystone, but other most projects lack support for scopes. Does this mean that in the above case, the user would have full cloud admin privileges in other services that lack support for scopes? i.e. while I expect it's safe to enable scope enforcement in keystone, is it "safe" to use it? Cheers, Mark

3 3

[Watcher]IRC meeting on May 20
by licanwei 19 May '20

19 May '20

Hi, Tomorrow at 08:00 UTC on #openstack-meeting-alt. pls update the meeting agenda if you have something want to be discussed. thanks, | | licanwei_cn | | 邮箱：licanwei_cn(a)163.com | 签名由网易邮箱大师定制

1 0

[neutron] Recent incompatible change in stable/rocky branch
by Neil Jerram 19 May '20

19 May '20

I'm sorry, but this is a moan. This merge - https://opendev.org/openstack/neutron/commit/a6fb2faaa5d46656db9085ad6bcfc6… - to the Neutron stable/rocky branch on April 23rd, has broken my team's Neutron plugin, by requiring 3rd party LinuxInterfaceDriver subclasses to take a new 'link_up' argument in their 'plug_new' method. IMO, it should have been obvious to folk proposing or reviewing this, that it would cause breakage. Does Neutron have a different understanding of "stable" than I do? Or do plugins other than OVN not matter anymore?

2 5

[neutron] WSREP: referenced FK check fail: Lock wait index
by Fabian Zimmermann 18 May '20

18 May '20

Hi, im just upgrading my galera nodes from 5.6 to 5.7 and pike -> queens. Now im seeing this lines hitting my mysql.log: -- 2020-05-19T05:41:39.516879Z 11861 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` -- Is this a known issue? Anything I may/should do? Thank a lot, Fabian

1 1

[ironic] III SPUC - The Sanity Preservation Un-Conference
by Iury Gregory 18 May '20

18 May '20

Hello everyone \o/ It's time for the third edition of SPUC! It will happen this Friday (May 22) at 5pm UTC! For those who doesn't know what is SPUC check [0]. We will be using Julia's bluejeans: https://bluejeans.com/u/jkreger Etherpad for <crazy> ideas: https://etherpad.opendev.org/p/IIISanityPreservationUnConference [0] http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013521.ht… -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 1

[all] Virtual Ussuri Celebration
by Kendall Nelson 18 May '20

18 May '20

Hello Everyone! I wanted to invite you all to a virtual celebration of the release! Next Friday, May 15th at 20:00 UTC, I invite you to join me in celebrating :) The purpose of this meeting will be two fold: 1. To celebrate all that our community has accomplished over the last release since we can't get together in person in June. I was thinking with trivia and a baking contest (I was going to attempt a cake in the shape of the OpenStack logo or maybe the actual Ussuri logo) :) There was also a request for piano karaoke which is also still on the table.. 2. To test out the OpenDev team's meetpad instance and work out kinks so that it can be vetted for PTG use. Here is the room we will be testing: https://meetpad.opendev.org/virtual-ussuri-celebration Worst case scenario, I'll share my zoom. Can't wait to see you all there (and what you've baked)! -Kendall (diablo_rojo) <https://meetpad.opendev.org/virtual-ussuri-celebration>

3 4

[tc][tricircle] Retiring the Tricircle project
by Ghanshyam Mann 18 May '20

18 May '20

Hello Everyone, As you know, Tricirlce is a leaderless project for the Victoria cycle means there is no PTL candidate for Victoria cycle. 'No PTL' is one of the criteria which triggers TC to start checking the health, maintainers of the project for dropping project from OpenStack Governance[1]. TC discussed the Tricircle project in today's meeting[2] and checked if the project has maintainers but no PTL or it is missing the maintainer completely. By looking at the Ussuri cycle development work, it seems no activity related to Tricircle except few gate fixes or community goal commits[2]. Based on all these checks, we are going to start the process of removing Tricircle from governance in the Victoria cycle as specified in the Mandatory Repository Retirement resolution [4] and detailed in the infra manual [5]. NOTE: release team is trying to do Ussuri release for Tricircle's deliverables if we can get this reno fix merge - https://review.opendev.org/#/c/721697/ >From the Victoria cycle, Tricircle will move out of OpenStack governance by keeping their repo under OpenStack namespace with an empty master branch with 'Not Maintained' message in README. If someone from old or new maintainers shows interest to continue its development then it can be re-added to OpenStack governance. With that thanks to all Tricircle contributors and PTLs for maintaining this project. [1] https://governance.openstack.org/tc/reference/dropping-projects.html [2] http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-04-21-15.01.log.html [3] https://www.stackalytics.com/?metric=commits&release=ussuri&module=tricircl… [4] https://governance.openstack.org/tc/resolutions/20190711-mandatory-reposito… [5] https://docs.opendev.org/opendev/infra-manual/latest/drivers.html#retiring-… -gmann

1 1

[nova][ptg] Ussuri Retrospective
by Balázs Gibizer 18 May '20

18 May '20

Hi, There is a common but seemingly not that popular topic on each nova PTG, the retrospective. I added the retrospective to the PTG etherpad [0]. Please collect retrospective topics there or tell me privately if you have a sensitive topic you want me to bring up. If there won't be any topic collected until the PTG then we will simply skip the retrospective. Cheers, gibi [0] https://etherpad.opendev.org/p/nova-victoria-ptg

1 0

[blazar] IRC meeting cancelled on May 19
by Pierre Riteau 18 May '20

18 May '20

Hello, Due to a scheduling conflict, I will not be able to chair the Blazar IRC meeting on Tuesday May 19. I propose to cancel and meet as usual on May 26, when we will finalise the agenda for the PTG meeting. Best wishes, Pierre Riteau (priteau)

1 0

[neutron] bug deputy report for week of 2020-05-11
by Bence Romsics 18 May '20

18 May '20

Hi Neutrinos, Here's the deputy report for last week: High: * https://bugs.launchpad.net/neutron/+bug/1878042 SRIOV agent does not parse correctly "ip link show <dev>" fix proposed: https://review.opendev.org/726918 * https://bugs.launchpad.net/neutron/+bug/1878160 [OVN] Functional tests environment is using old OVN fix proposed (wip): https://review.opendev.org/727193 Medium: * https://bugs.launchpad.net/neutron/+bug/1877977 [DVR] Recovery from openvswitch restart fails when veth are used for bridges interconnection unassigned * https://bugs.launchpad.net/neutron/+bug/1875981 Admin deleting servers or ports leaves orphaned DNS records fix proposed (wip): https://review.opendev.org/728385 related test: https://review.opendev.org/728409 * https://bugs.launchpad.net/neutron/+bug/1878299 [floatingip port_forwarding] changing external port to used value hangs with retriable exception unassigned * https://bugs.launchpad.net/neutron/+bug/1878358 OVN migration doesn't clean up the existing ml2-ovs agents fix proposed: https://review.opendev.org/727648 * https://bugs.launchpad.net/neutron/+bug/1878632 Race condition in subnet and segment delete: The segment is still bound with port(s) assigned, no fix proposed yet test reproducing the bug: https://review.opendev.org/728904 * https://bugs.launchpad.net/neutron/+bug/1878916 When deleting a network, delete the segment RP only when the segment is deleted fix proposed: https://review.opendev.org/728507 Incomplete: * https://bugs.launchpad.net/neutron/+bug/1877978 SNAT Problem Floating IP * https://bugs.launchpad.net/neutron/+bug/1878719 DHCP Agent's iptables CHECKSUM rule causes skb_warn_bad_offload kernel * https://bugs.launchpad.net/neutron/+bug/1879009 attaching extra port to server raise duplicate dns-name error See you on the meeting, Bence

1 0

[nova][gate] openstack-tox-pep8 job failing
by melanie witt 18 May '20

18 May '20

Hey all, The openstack-tox-pep8 job is now failing too since hacking 3.1.0 was released [1], which brings in a newer flake8 version, which adds new checks to the code and we have a few failures. We have a change that would pin hacking >= 3.0.1 and < 3.1.0 [2] to prevent new checks from rolling in automatically, but it is stuck behind the failing openstack-tox-docs job [3]. This is unfortunately a chicken and egg situation. The proposed nova patch for the docs job, as mentioned from my other ML post: https://review.opendev.org/727898 fails the pep8 job and the proposed nova patch for the pep8 job [2] fails the docs job. I'm not sure how people will want to proceed here because a nova-side-only gate fix would involve squashing ^ and [2]. If we can get another fix or revert to openstackdocstheme to take care of the docs job, we'd then only need [2] on the nova side to unblock the nova gate. Cheers, -melanie [1] https://review.opendev.org/728016 [2] https://review.opendev.org/727347 [3] http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014876.html

3 5

[gate] parallel releasenotes job builds
by melanie witt 18 May '20

18 May '20

Hi all, We recently merged a change [1] that will run the build-openstack-releasenotes job with 'sphinx-build -j auto' to allow the build to run on multiple CPUs. With the recent releases of reno 3.1.0 and openstackdocstheme 2.1.2, both libraries advertise that they are parallel_read_safe and thus can support the '-j' option. This effort was inspired by the nova build-openstack-releasenotes job which typically takes 52m to > 1h to run. The job timeout is 1h, so we were occasionally seeing TIMED_OUT job failures. With parallel sphinx-build, the nova job run time is reduced down to about 15m (awesome!). I wanted to say thanks to smcginnis, dhellmann, clarkb, and AJaeger for helping this newbie to reno and docs builds. If anyone encounters any issues around the parallel reno builds in their projects, please let us know. Cheers, -melanie [1] https://review.opendev.org/727473

3 2

[kolla] Ceph transition plan
by Eric K. Miller 18 May '20

18 May '20

Hi, I noticed that in Kolla's master branch that Ceph has been removed, as expected for a deprecated component (I'm sad, though, since it works so well!). In the release notes, it is noted that "Prior to this we will ensure a migration path to another tool such as Ceph Ansible is available." Is this migration path documented since it appears that the latest release will not have the Kolla Ceph container available? Thanks! Eric

2 1

[ops] ops meetups team meeting 2020-5-5
by Chris Morgan 15 May '20

15 May '20

Hey all, The openstack ops meetups team has been fairly dormant recently for obvious reasons. However with the realisation that in-person meetups, conferences, summits etc are simply not coming back any time soon, we've started to regroup to discuss next steps. We are also seeing some requests for virtual meetups from some operators via the OpsMeetup twitter account. Thus we had a quick IRC meeting today, and also a trial run at an open source based video conference meeting using jitsi via an instance running on infra provided by Erik McCormick. This seems to be promising. We'll look into trialling some ops related events leveraging this. We also agreed to try and have an operators session during the upcoming virtual PTG (replacing the Vancouver event now cancelled). More info will be shared as and when we can. I hope you're all doing as well as can be expected. Chris - on behalf of the ops meetups team Meeting minutes: Minutes: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2020/ops_meetup_tea… 12:01 PM Minutes (text): http://eavesdrop.openstack.org/meetings/ops_meetup_team/2020/ops_meetup_tea… 12:01 PM Log: http://eavesdrop.openstack.org/meetings/ops_meetup_team/2020/ops_meetup_tea… -- Chris Morgan <mihalis68(a)gmail.com>

5 9

[barbican] Nominating Moisés Guimarães for barbican-core
by Douglas Mendizabal 15 May '20

15 May '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I would like to nominate Moisés Guimarães to be added to the barbican-core team. Moisés has been very helpful in helping us review barbican patches, and has done an excellent job of helping maintain the castellan library. If there are no objections, we will officially add Moisés to the team next week. Thanks, Douglas Mendizábal Barbican PTL -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEwcapj5oGTj2zd3XogB6WFOq/OrcFAl6+9XMACgkQgB6WFOq/ OrdzzxAAgxxymvuA+yGDuitEcjqwlggPJBYGb5PlHqqTkXcrS6IEcneG1eEJ/Rp2 JovTMN5sv3PwhtSMxjEmyrBVR9g6MKbQoQvDk1p77fFIL9ofIFV3xKOpZutnb3ig Y2/gSMWNDfuz7DPpNofUsyzvK5eBNWC8aBbpSeN0R4qLAlyOPFe6ftOAI1RvIX4W s6CwOiMQGGGNUK8TZgvG9BOOJorgMZ+maq4tFRN8P6bLA6q7kcsUob/LBIwCpoEF xdl9EO/IaRM4kMP8y/quIzDnBJV9Im4t8WrJ5sYNPnpfS+0yXseuCACAMYWSNp63 Zf9oRyIuv3Z/+z6qjcpkct/xhijdtB+Sc0MpmGv43RSoEHkYAGU6ue2nlZkVIow9 GO5Itq38WbORBIFwlGK+J+u40ikY+EjldzIwsxoBZDvuNMsGltpVclAkyW2VUwL3 HOyKPCm0dLiVz3qYo2dTH2eC2cdSbGxF91gckke1m5o69RDK9vYi6YQxtO0ms7Em yZoVQ6OnA4KCZUEd4sby7jWm/1ueXZq05BQgnB1tXbdMa6hDp6CwVKSAfH0fHS6D 5dCuo1EoDWxCTsh3lH0wogeODcCBReNTNCWEy/ia19aOO4cXrlpLznP6GONENwEo zbaPfwnmdw5Q1ARmLcEpgsbVF+mIymVkqGpNZ8DFA/wR+mQ/fkU= =Syoj -----END PGP SIGNATURE-----

2 1

[all][InteropWG] Request to PTLs for highligting Core Feature add-remove
by prakash RAMCHANDRAN 15 May '20

15 May '20

Hi all, Interop WG needs patches to complete the 2020.06 Ussuri guidelines. PTL or team members of CoreNovaNeutronCinderKeystoneGlanceSwiftadd-onHeat -OrchedtrationDesignate - DNS potential for Victoria add-onsIronicZunSenlinKolla & KuryrPlease suggest others Open Infra (Potential Bare Metal & Container APIs)StarlingXAirshipKata We are reviewing your release notes, but if you can advice us on non-amin APIs for Objects that you can qualify as core for current or future release please send Advisory with your module name. eg.Nova: Advisory - Cell API is potential candidate for core. etc. Alternate visit the TODO plan as on etherpad for interop next week callhttps://etherpad.opendev.org/p/interop Validate your APIs in community sitehttps://refstack.openstack.org/#/community_results Add your items for next week Fri 10 AM PDT call for Fri May 22nd. Plus if you want to attend and Present in PTG interopWG please add your topics and +1 those you like to see on June 1st 6-8 AM PDThttps://etherpad.opendev.org/p/interop_virtual_ptg_planning_june_2020 Thankson behalf ofChair - InteropWG PrakashVice Chair - Mark T Voelker Sent from Yahoo Mail on Android

1 0

[neutron] 15-05-2020 drivers meeting agenda
by Slawek Kaplonski 15 May '20

15 May '20

Hi, For tomorrow's drivers meeting we have only one RFE to discuss: * https://bugs.launchpad.net/neutron/+bug/1877301 - L3 Router support ndp proxy It was initially triaged by Brian (Thank You) and discussed already on L3 subteam meeting. See You all tomorrow and have a nice day :) -- Slawek Kaplonski Senior software engineer Red Hat

2 1

[swift] Adding disks - one by one or all lightly weighted?
by Mark Kirkwood 14 May '20

14 May '20

Hi, We are wanting to increase the number of disks in each of our storage nodes - from 4 to 12. I'm wondering whether it is better to: 1/ Add 1st new disk (with a reduced weight)...increase the weight until full, then repeat for next disk etc 2/ Add 'em all with a (much i.e 1/8 of that in 1/ ) reduced weight...increase the weights until done Thoughts? regards Mark

2 2

[all] pep8 job failing due to flake8 3.8.0
by Ghanshyam Mann 14 May '20

14 May '20

Hello Everyone. You might have noticed that few or most of the projects pep8 job started failing. That is because flake8 new version 3.8.0 added the new pycodestyle with new rules. Hacking capped it with 4.0.0 version not with the minor version for 3.*. The new hacking version 3.0.1 is released which cap the flake8<3.8.0. Thanks to dtantsur and stephenfin for tacking care of it. To fix your pep8 job you can, - Either fix the pep8 error in code if easy and fast to fix. - Or bump the hacking minimum version to 3.0.1. I have proposed it for a few projects failing pep8. - https://review.opendev.org/#/q/topic:hacking-fix+(status:open+OR+status:mer… If pep8 job is passing then you do not need to do anything. The existing hacking version cap will work fine. -gmann

4 12

OpenStack Ussuri Community Meeting Recordings & Presentation Decks
by Allison Price 14 May '20

14 May '20

Hi everyone, Thanks to all who joined or created content and presented at the community meetings yesterday! There were quite a few project updates presented for the Ussuri release. If you missed the meetings, you can find the recordings in this playlist [1] and links to the presentations are also included in the video abstracts. We have also posted both meeting recordings on Tencent Cloud, so you can watch the first community meeting [2] or the second community meeting [3] there as well. If you have any trouble accessing these resources, please let me know. Cheers, Allison [1] https://www.youtube.com/playlist?list=PLKqaoAnDyfgpYADSiOfIVwgKb5zbL0GJE <https://www.youtube.com/playlist?list=PLKqaoAnDyfgpYADSiOfIVwgKb5zbL0GJE>[2] https://v.qq.com/x/page/q0966o61rz9.html <https://v.qq.com/x/page/q0966o61rz9.html> [3] https://v.qq.com/x/page/d09667otaf1.html <https://v.qq.com/x/page/d09667otaf1.html> Allison Price OpenStack Foundation allison(a)openstack.org

1 0

[nova][gate] openstack-tox-docs job failure
by melanie witt 14 May '20

14 May '20

Howdy all, There's a upper-constraints bump to openstackdocstheme 2.1.0 which has recently merged [1] which is going to break the openstack-tox-docs job for nova. I've proposed a patch to fix it here: https://review.opendev.org/727898 if people could please take a look. Cheers, -melanie [1] https://review.opendev.org/727850

2 2

[neutron] parent ports for trunks being claimed by instances
by Nate Johnston 14 May '20

14 May '20

Neutron developers, I am currently working on an issue with trunk ports that has come up a few times in my direct experience, and I hope that we can create a long term solution. I am hoping that developers with experience in trunk ports can validate my approach here, especially regarding fixing current behavior without introducing an API regression. By way of introduction to the specifics of the issue, let me blockquote from the LP bug I raised for this [1]: ---- When you create a trunk in Neutron you create a parent port for the trunk and attach the trunk to the parent. Then subports can be created on the trunk. When instances are created on the trunk, first a port is created and then an instance is associated with a free port. It looks to me that's this is the oversight in the logic. From the perspective of the code, the parent port looks like any other port attached to the trunk bridge. It doesn't have an instance attached to it so it looks like it's not being used for anything (which is technically correct). So it becomes an eligible port for an instance to bind to. That is all fine and dandy until you go to delete the instance and you get the "Port [port-id] is currently a parent port for trunk [trunk-id]" exception just as happened here. Anecdotally, it's seems rare that an instance will actually bind to it, but that is what happened for the user in this case and I have had several pings over the past year about people in a similar state. I propose that when a port is made parent port for a trunk, that the trunk be established as the owner of the port. That way it will be ineligible for instances seeking to bind to the port. ---- Clearly the above behavior indicates buggy issue that should be rectified in master and stable branches. Nobody wants a VM that can't be fully deleted because the port can't ever be deleted. This is especially egregious when it causes heat stack deletion failures. I am mostly concerned that by adding the trunk as an owner of the parent port, then the trunk will need to be deleted before the parent port can be deleted, otherwise a PortInUse error will occur when the port is deleted (i.e. on tempest test teardown). That to me seems indicative of an inadvertent API change. Do you think it's all right to say that if you delete a port that is a parent port of a trunk, and that trunk has no other subports, that the trunk deletion is implicit? Is that the lowest impact to the API that we can incur to resolve this issue? Your wisdom is appreciated, Nate [1] https://bugs.launchpad.net/neutron/+bug/1878031

5 6

[oslo][nova][vmware] Replacement for suds library
by Stephen Finucane 14 May '20

14 May '20

The suds-jurko library used by oslo.vmware is emitting the following warnings in nova tests. /nova/.tox/py36/lib/python3.6/site-packages/suds/resolver.py:89: DeprecationWarning: invalid escape sequence \% self.splitp = re.compile('({.+})*[^\%s]+' % ps[0]) /nova/.tox/py36/lib/python3.6/site-packages/suds/wsdl.py:619: DeprecationWarning: invalid escape sequence \s body.parts = re.split('[\s,]', parts) These warnings are going to be errors in Python 3.10 [1]. We have over 18 months before we need to worry about this [2], but I'd like to see some movement on this well before then. It seems the suds-jurko fork is dead [3] and movement on yet another fork, suds-community, is slow [4]. How difficult would it be to switch over to something that does seem maintained like zeep [5] and, assuming it's doable, is anyone from VMWare/SAP able to do this work? Stephen [1] https://docs.python.org/3.9/whatsnew/3.9.html#you-should-check-for-deprecat… [2] https://www.python.org/dev/peps/pep-0596/ [3] https://bitbucket.org/jurko/suds/src/default/ [4] https://github.com/suds-community/suds/pull/32 [5] https://python-zeep.readthedocs.io/en/master/

5 6

[ironic] [release] Proposal for a new release model for ironic projects
by Dmitry Tantsur 14 May '20

14 May '20

Hi folks, I would like to formally present this proposal: https://review.opendev.org/#/c/725547/ It is largely driven by a desire to produce frequent supported and tested intermediate releases for standalone consumers, as well as address a few minor issues we've found over time. I would like to try applying it to Victoria already. Please read and comment. Thanks, Dmitry

1 0

[RDO][OpenStack] Removal of Pike and Ocata Trunk repos
by Yatin Karel 13 May '20

13 May '20

Hi, The topic was discussed in yesterday's RDO meeting[1] and to reach a wider audience it's being raised here. Ocata and Pike are in the Extended maintenance phase[2] for more than a year now, The promotion jobs which used to test these repos were dropped long ago[3][4]. Now we are planning to drop these trunk repos[5][6] in the first week of June, 2020. We already stopped building new commits for pike/ocata[7]. So if anyone still using these repos consider moving to upgrade to queens or any later releases. If something is blocking you to stop relying on ocata/pike repos raise your voice here so we can consider it before dropping the repos. [1] https://lists.rdoproject.org/pipermail/dev/2020-May/009379.html [2] https://releases.openstack.org/ [3] https://review.rdoproject.org/r/#/q/topic:remove_pike [4] https://review.rdoproject.org/r/#/c/16485/ [5] http://trunk.rdoproject.org/centos7-ocata/ [6] http://trunk.rdoproject.org/centos7-pike/ [7] https://softwarefactory-project.io/r/#/c/18347/ On Behalf of RDO Team Thanks and Regards Yatin Karel

1 0

[all] OpenStack Ussuri Community Meeting in 30 Minutes
by Allison Price 13 May '20

13 May '20

Hi everyone, I just wanted to remind you that there is a community meeting in 30 minutes to cover OpenStack Ussuri highlights. The meeting will be moderated by Mohammed Naser from the OpenStack Technical Committee and include project updates from: - Slawek Kaplonski, Neutron - Michael Johnson, Octavia - Goutham Pacha Ravi, Manila - Mark Goddard, Kolla - Balazs Gibizer, Nova - Brian Rosmaita, Cinder You can find dial-in information in this etherpad [1]. The recording and slides will be shared on the mailing list after the meeting. There will also be another meeting tomorrow, Thursday May 14 at 0200 UTC, moderated by Rico Lin from the OpenStack TC, and you can see who will be presenting here [1]. [1] https://etherpad.opendev.org/p/CommunityMeeting_Ussuri <https://etherpad.opendev.org/p/CommunityMeeting_Ussuri> Allison Price OpenStack Foundation allison(a)openstack.org

3 2

[all] OpenStack Ussuri Community Meeting Recording and time for Meeting 2
by Allison Price 13 May '20

13 May '20

Thank you to everyone who joined the community meeting earlier today to learn more about OpenStack Ussuri as well as the contributors who presented the release highlights! If you were unable to attend, you can check out the recording [1] which includes a link to the slides or check out the attached deck. There is also going to be another community meeting in 7.5 hours at 0200 UTC on Thursday, May 14. You can find the list of presenters as well as the dial-in information here [2]. [1] https://www.youtube.com/watch?v=T5-Dr1lxPB0&feature=youtu.be <https://www.youtube.com/watch?v=T5-Dr1lxPB0&feature=youtu.be> [2] https://etherpad.opendev.org/p/CommunityMeeting_Ussuri <https://etherpad.opendev.org/p/CommunityMeeting_Ussuri> Thanks! Allison Allison Price OpenStack Foundation allison(a)openstack.org

1 1

OpenStack Ussuri is officially released!
by Sean McGinnis 13 May '20

13 May '20

The official OpenStack Ussuri release announcement has been sent out: http://lists.openstack.org/pipermail/openstack-announce/2020-May/002035.html Thanks to all who were part of making the Train series a success! This marks the official opening of the releases repo for Victoria, and freezes are now lifted. Ussuri is now a full stable branch. Thanks! Sean

5 6

[kolla] Kolla klub meeting 21st May
by Mark Goddard 13 May '20

13 May '20

Hi, In today's Kolla IRC meeting we agreed to host a project onboarding session for the next Kolla Klub meeting on the 21st May. We'll cover a variety of topics on the many different ways you can contribute to the project. Gaël Therond will also fill us in on some of the questions put to him since the last meeting about his case studies. https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… Thanks, Mark

1 0

[TripleO][Rdo][Train] Deploy OpenStack using only provisioning network
by Ruslanas Gžibovskis 13 May '20

13 May '20

Hi all, I am doing some testing and will do some deployment on some remote hosts. Remote hosts will use provider network only specific for each compute. I was thinking, do I really need all the External, InternalAPI, Storage, StorageManagemnt, Tenant networks provided to all of the nodes? Maybe I could use a Provision network for all of that, and make swift/glance copy on all computes to provide local images. I understand, if I do not have tenant network, all VM's in same project but in different sites, will not see each other, but it is ok at the moment. Thank you for your help -- Ruslanas Gžibovskis +370 6030 7030

3 6

[horizon][qa][infra] horizon master gate failure
by Akihiro Motoki 12 May '20

12 May '20

Hi, horizon master branch is now failing due to permission defined during installing tempest-horizon into the tempest venv [1]. It happens since May 9. The source tempest-horizon repo is located in /home/zuul/src/opendev.org/openstack/tempest-horizon/. I digged into the detail for a while but haven't figured out the root cause yet. I have the following questions on this: (1) Did we have any changes on the job configuration recently? stable/ussuri and master branches are similar but it only happens in the master branch. (2) When I changed the location of the tempest-horizon directory specified as tempest-plugins, the failure has gone [2]. Is there any recommendation from the tempest team? Thanks, -amotoki [1] https://zuul.opendev.org/t/openstack/build/9389be57c39d4971867abfa831bd3793 [2] https://review.opendev.org/#/c/726698/1/.zuul.yaml

3 2

Tox basepython and Python3
by Clark Boylan 12 May '20

12 May '20

Hello everyone, This has come up a few times on IRC so we are probably well overdue for a email about it. Long story short, if your tox.ini config sets basepython [0] to `python3` and you also use py35, py36, py37, or py38 test targets there is a good chance you are not testing what you intend to be testing. You also need to set ignore_basepython_conflict to true [1]. The reason for this is basepython acts as an override for the python executable to be used when creating tox virtualenvs. `python3` on most platforms indicates a specific python3 version: Ubuntu Xenial 3.5, Ubuntu Bionic and CentOS 8 3.6, and so on. This means that even though you are asking for python 3.7 via py37 you'll get whatever version `python3` is on the running platform. To address this we can set ignore_basepython_conflict and tox will use the version specified as part of the target and not the basepython override. You might wonder why using basepython is useful at all given this situation. The reason for it is the default python used by tox for virtualenvs is the version of python tox was installed under. This means that if tox is running under python2 it will use python2 for virtualenvs when no other version is set. Since many software projects are now trying to drop python2 support they want to explicitly force python3 in the default case. basepython gets us halfway there, ignore_basepython_conflict the rest of the way. [0] https://tox.readthedocs.io/en/latest/config.html#conf-basepython [1] https://tox.readthedocs.io/en/latest/config.html#conf-ignore_basepython_con… Hopefully this helps explain some of tox's odd behavior in a beneficial way. Now go and check your tox.ini files :) Clark

7 9

[all][PTL] U Community Goal: Project PTL & Contrib Docs Update #9
by Kendall Nelson 12 May '20

12 May '20

Hello Everyone! Even more excellent progress[1] has been made as we are inching closer to completion. Again, thank you for all the hard work! Projects listed below are missing progress/merged status according to the story[4]. If you are on this list, please get started IMMEDIATELY. All told, if you are doing the bare minimum of only filling out the template[2] it shouldn't take more than 5-10 minutes per repo. - Barbican - Cloudkitty - Congress - Cyborg - Ec2-API - Freezer - Heat - Horizon - Karbor - Kuryr - LOCI - Masakari - Mistral - Monasca - Murano - OpenStack Charms - openstack-chef - OpenStackAnsible - OpenStackClient - Packaging-RPM - Placement - Puppet OpenStack - Rally - Release Management - Senlin - Solum - Storlets - Swift - Tacker - Telemetry - Tricircle - TripleO - Zaqar PLEASE add me if you need help with reviews and let me know if there is any other help I can provide; we are nearly out of time and there is a lot of work to be done still. If you have questions about the goal itself, here is the link to that[3]. And as you push patches, please be sure to update the StoryBoard story[4]. Thanks! -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

5 4

[tripleo] triaged bugs older than 365 days
by Wesley Hayutin 11 May '20

11 May '20

Greetings, I have moved any bug older than 365 days that are in Triaged status to "incomplete". If you think it should still be addressed just flip the bug back from incomplete back to triaged and add some updated comments. I'm pretty sure just commenting on the bug will keep it from expiring as well. Email me directly if you have any questions or concerns about a particular bug. We're just cleaning up. Thanks 1811713,Triaged,in-stable-queens in-stable-rocky, https://bugs.launchpad.net/tripleo/+bug/1811713,"'rocky undercloud fails to install'" 1812640,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1812640,"'iptables rules are not host-based when using podman'" 1814250,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1814250,"'races condition at os-net-config in overcloud deploy OVB'" 1814880,Triaged,in-stable-queens in-stable-rocky queens-backport-potential rocky-backport-potential, https://bugs.launchpad.net/tripleo/+bug/1814880,"'Containerized HAProxy cannot log in a dedicated log file'" 1815134,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1815134,"'openstack tripleo deploy stack failures truncate useful error messages'" 1815226,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1815226,"'puppet duplicate declaration error'" 1817356,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1817356,"'tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001 check job in RDO is failing on ovb stack cleanup'" 1817552,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1817552,"'periodic fs021 failing on overcloud deploy'" 1820671,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1820671,"'No matching service: barbican_tempest_plugin.tests.scenario.test_image_signing.ImageSigningTest'" 1821790,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1821790,"'selinux ssh denieals on CentOS/RHEL 8'" 1821854,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1821854,"'mistral leaks ssh processes'" 1822540,Triaged,security-hardening, https://bugs.launchpad.net/tripleo/+bug/1822540,"'By default show_image_direct_url MUST be set to False'" 1822609,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1822609,"'neutron ovs cleanup is docker.service specific'" 1823527,Triaged,dhcp-agent neutron unhealthy, https://bugs.launchpad.net/tripleo/+bug/1823527,"'neutron's dockers are unhealthy'" 1824993,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1824993,"'[network] Ceph monitor doesn't bootstrap in a standalone deployment'" 1825826,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1825826,"'standalone-upgrade failing during deploy steps for CalledProcessError: Command '['systemctl', 'stop', u'tripleo_keystone.service']' returned non-zero exit status'" 1826179,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1826179,"'standalone-upgrade fails during deploy steps (generate config) step1 for 'Evaluation Error:... Could not find class ::tripleo::profile::base::placement::api' '" 1828172,Triaged,zuul-reproducer, https://bugs.launchpad.net/tripleo/+bug/1828172,"'No match for argument: python2-dnf on tripleo reproducer libvirt Fedora 30'" 1828233,Triaged,ci zuul-reproducer, https://bugs.launchpad.net/tripleo/+bug/1828233,"'[reproducer] standalone deploy failed to access mirrors'" 1828276,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1828276,"'reproducer: still getting permission errors on docker commands by user on centos-7'" 1560111,Triaged,python-tripleoclient, https://bugs.launchpad.net/tripleo/+bug/1560111,"'The list of enabled Sahara plugins should be written to the generated deployer-input file'" 1680894,Triaged,containers validations, https://bugs.launchpad.net/tripleo/+bug/1680894,"'RFE: create a validation playbook for a containerized deployment'" 1705994,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1705994,"'openstack overcloud image upload - should support updating specific image '" 1706112,Triaged,composable-roles, https://bugs.launchpad.net/tripleo/+bug/1706112,"'Specifying custom flavor for controllers is inconsistent with other roles'" 1709706,Triaged,tripleoclient, https://bugs.launchpad.net/tripleo/+bug/1709706,"'Need better client-side error reporting'" 1714214,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1714214,"'Lack of documentation about TCP ports used by TripleO Services'" 1714544,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1714544,"'cant delete stuck with network-isolation'" 1716391,Triaged,ux,https://bugs.launchpad.net/tripleo/+bug/1716391,"'Should be possible to aggregate some Neutron configs across templates'" 1722218,Triaged,workflows,https://bugs.launchpad.net/tripleo/+bug/1722218,"'node cleaning to be a part of stack-delete'" 1722558,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1722558,"'Promoter: identify a way to store privately the secrets used by the promotion server, so they can be used in all the promotion-setup runs'" 1722871,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1722871,"'Promoter: add more disk space to promoter server'" 1723229,Triaged,containers validations, https://bugs.launchpad.net/tripleo/+bug/1723229,"'[RFE] Deploy should fail much earlier if the container images aren't found'" 1726593,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1726593,"'Cinder API v2 support needs to be removed in TripleO'" 1729541,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1729541,"' The VIP of OpenDaylight's Neutron Northbound port is configured to listen on Control Plane network'" 1729835,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1729835,"'Message formatting issue when retries all fail (introspection)'" 1734158,Triaged,quickstart ux, https://bugs.launchpad.net/tripleo/+bug/1734158,"'Adapt config downloads in quickstart for deployed servers'" 1734947,Triaged,quickstart tech-debt, https://bugs.launchpad.net/tripleo/+bug/1734947,"'RFE: support role data generation in quickstart'" 1736254,Triaged,pike stable tripleo tripleo-heat-templates, https://bugs.launchpad.net/tripleo/+bug/1736254,"'Using composable network or custom named network for MysqlNetwork results in deployment failure'" 1736272,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1736272,"'integrate elastic recheck into tempest email results'" 1736499,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1736499,"'quickstart fails with http_proxy'" 1737768,Triaged,ci quickstart tech-debt validations, https://bugs.launchpad.net/tripleo/+bug/1737768,"'CI/featureset010: validations aren't fatal'" 1740396,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1740396,"'Validation: missing check for HostnameMap'" 1740940,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1740940,"'Neutron timeout has different settings on ctrl and comp'" 1741288,Triaged,tripleo-common tripleoclient ux workflows, https://bugs.launchpad.net/tripleo/+bug/1741288,"''overcloud node' commands should allow deleting by node name also'" 1741470,Triaged,documentation, https://bugs.launchpad.net/tripleo/+bug/1741470,"'Improve docs for manual install on a virtual env'" 1742237,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1742237,"'Failure when deploying the overcloud on a predeployed server'" 1743239,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1743239,"'deployment failure with external ceph setup'" 1745090,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1745090,"'Heat engine resource check failed when adding a node after undercloud newton->ocata->pike->master upgrade'" 1745223,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1745223,"'default reproduce-script to deploy latest code'" 1745225,Triaged,quickstart ux, https://bugs.launchpad.net/tripleo/+bug/1745225,"'devmode.sh should support a mode to tear down without redeployment'" 1745449,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1745449,"'neutron interface driver names should use shortnames'" 1745500,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1745500,"'pre-provisioned nodes hostnames should not resolve to 127.0.0.1'" 1746285,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1746285,"'RFE: measure undercloud puppet install steps and leave artifact'" 1746291,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1746291,"'RFE: measure the overcloud deployment steps and leave artifact '" 1747606,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1747606,"'undercloud vm - has an unusable dns from the last network, if network > 1'" 1747999,Triaged,containers,https://bugs.launchpad.net/tripleo/+bug/1747999,"'docker-puppet.py config hash update logging is misleading'" 1749435,Triaged,workflows,https://bugs.launchpad.net/tripleo/+bug/1749435,"'Node delete always overwrites *RemovalPolicies'" 1749446,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1749446,"'Novajoin availability should not impeach deploy'" 1749477,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1749477,"'Quickstart installed undercloud async tasks broken'" 1751929,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1751929,"'Quickstart script kills non-root user processes during initial deploy'" 1752132,Triaged,ui,https://bugs.launchpad.net/tripleo/+bug/1752132,"'horizon returns 500 error due to missing heat-dashboard'" 1752427,Triaged,quickstart tech-debt, https://bugs.launchpad.net/tripleo/+bug/1752427,"'containers-check script is installed via pip'" 1752925,Triaged,containers ux, https://bugs.launchpad.net/tripleo/+bug/1752925,"'Deployments with docker containers in unhealthy state should fail deployment'" 1753817,Triaged,ci quickstart tech-debt, https://bugs.launchpad.net/tripleo/+bug/1753817,"'branch jobs on quickstart/extras/tripleo-ci fail if they depend on a master change in a branched repo'" 1755223,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1755223,"'Remove Newton Support from oooq-extras validate-tempest role'" 1756138,Triaged,controller replace, https://bugs.launchpad.net/tripleo/+bug/1756138,"'replace controller fail in build containers in new controller '" 1757211,Triaged,documentation quickstart ux, https://bugs.launchpad.net/tripleo/+bug/1757211,"'[quickstart] overcloud_as_undercloud needs to be clarified and documented'" 1758324,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1758324,"'5 minute delay when provisioning over IPv6'" 1760735,Triaged,ocata-backport-potential pike-backport-potential queens-backport-potential validations, https://bugs.launchpad.net/tripleo/+bug/1760735,"'[rfe] validation to check for overcloud node clock sync relative to Undercloud'" 1761504,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1761504,"'Worflows 'list' and 'list_groups' from tripleo.validations.v1 don't produce any output'" 1761716,Triaged,pike-backport-potential queens-backport-potential, https://bugs.launchpad.net/tripleo/+bug/1761716,"'docker-puppet puppet-generated dirs not cleaned during rsync'" 1763433,Triaged,ux,https://bugs.launchpad.net/tripleo/+bug/1763433,"'Logical puzzles in tripleo CLI'" 1764476,Triaged,upgrade,https://bugs.launchpad.net/tripleo/+bug/1764476,"'poor use of variable names in tripleo_upgrade role re: triple_ci variable'" 1765787,Triaged,low-hanging-fruit, https://bugs.launchpad.net/tripleo/+bug/1765787,"'01-package-installs should fail the whole image build if it python tracebacks'" 1766199,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1766199,"'Link timedatectl to ntp'" 1767125,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1767125,"'Compute specific L3 agent no longer required'" 1767132,Triaged,nova,https://bugs.launchpad.net/tripleo/+bug/1767132,"'InstanceNameTemplate parameter is not applied in compute nodes'" 1768092,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1768092,"'improve promoter script error message by including dlrn hash'" 1820576,Triaged,tech-debt,https://bugs.launchpad.net/tripleo/+bug/1820576,"'master: Standalone002 job fails, keystone container didn't start because could not bind to address 192.168.24.1:35357'" 1821419,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1821419,"'[Docs] Document Rendering NIC Templates for Customization'" 1821600,Triaged,in-stable-queens queens-backport-potential, https://bugs.launchpad.net/tripleo/+bug/1821600,"'iscsid is not stoped after running FFU'" 1823003,Triaged,in-stable-queens queens-backport-potential, https://bugs.launchpad.net/tripleo/+bug/1823003,"'Queens: epmd process is not always started by systemd when initiating undercloud upgrade'" 1823260,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1823260,"'RFE: Provide the ability to retag already existing images in the undercloud registry'" 1823849,Triaged,in-stable-queens in-stable-rocky queens-backport-potential rocky-backport-potential, https://bugs.launchpad.net/tripleo/+bug/1823849,"'trck the enablement of deep_compare with puppet-pacemaker on queens and rocky'" 1824143,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1824143,"'Cleaning ha-env files for ovn'" 1824186,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1824186,"'ansible timeout issue'" 1827724,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1827724,"'Podman service is not used in certain NFV roles'" 1828001,Triaged,documentation, https://bugs.launchpad.net/tripleo/+bug/1828001,"'heat templates now end in j2.yaml on page Configuring Network Isolation in tripleo-docs'" 1686353,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1686353,"'Proxy Options for TripleO QuickStart'" 1708302,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1708302,"'openstack clients which can use ceph, should not need to depend on /etc/ceph'" 1709826,Triaged,ci documentation quickstart, https://bugs.launchpad.net/tripleo/+bug/1709826,"'Having a README file inside the core roles'" 1721841,Triaged,containers,https://bugs.launchpad.net/tripleo/+bug/1721841,"'ceph docker containers do not log to /var/log/containers'" 1723540,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1723540,"'tripleo-quickstart ASCII banner has wrong indentation in logs.o.o'" 1724991,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1724991,"'tracker - tripleo stack create canceled or timeout in stage 3'" 1739620,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1739620,"'quickstart covers up deficiency in swift logging in standard deployment'" 1746505,Triaged,tripleo-heat-templates, https://bugs.launchpad.net/tripleo/+bug/1746505,"'Keystone caching not enabled by default?'" 1746812,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1746812,"'rdo ovb jobs do not test the change submitted'" 1755368,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1755368,"'Missing centos-binary-tacker on hub.docker.com'" 1757271,Triaged,containers low-hanging-fruit, https://bugs.launchpad.net/tripleo/+bug/1757271,"'openstack overcloud container image prepare should handle slashes in namespace entries'" 1761093,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1761093,"'Upgrade 'Pike BM' -> 'Pike Containers': httpd issue'" 1763089,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1763089,"'undercloud vm fails to start properly'" 1769520,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1769520,"'RFE (reproducer): 'ci dev mode' for iterating on reproducer script/roles'" 1769526,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1769526,"'RFE (libvirt-reproducer): add param to take an array of DNS ip's vs. singular param'" 1769527,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1769527,"'RFE (libvirt-reproducer): check for disk space needed as part of initial libvirt-nodepool playbook/role '" 1769529,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1769529,"'RFE (libvirt-reproducer): handle case where 'stack' user already exists on virthost, script fails'" 1769531,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1769531,"'RFE (libvirt-reproducer): Display summary of domains + IP's created by script'" 1771470,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1771470,"'dlrnapi promoter: make output of container existence check more clear'" 1785799,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1785799,"'Multinode jobs in check pipeline in rdo sf are launched in the wrong nodepool provider'" 1789836,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1789836,"'openstack overlay deploy failed with docker error 'not a shared mount''" 1793774,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1793774,"'tripleo-docs out of date around containers'" 1795646,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1795646,"'When using containerized openshift-ansible, we're losing the profile_tasks output callback'" 1801388,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1801388,"'build output is impossible to read due to nested json dumps'" 1801825,Triaged,low-hanging-fruit, https://bugs.launchpad.net/tripleo/+bug/1801825,"'Don't quote {posargs} in tox.ini'" 1805186,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1805186,"'tripleo jobs failing on ImageNotFoundException: Not found image: docker'" 1815208,Triaged,documentation, https://bugs.launchpad.net/tripleo/+bug/1815208,"'Security Hardening in tripleo-docs Incorrect indentation in YAML example'" 1819461,Triaged,containers,https://bugs.launchpad.net/tripleo/+bug/1819461,"''sudo' calls try to connect to host DBus from within a container'" 1828070,Triaged,low-hanging-fruit, https://bugs.launchpad.net/tripleo/+bug/1828070,"'puppet deploy has excessive warnings about unresolved dependencies'" 1397477,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1397477,"'rabbitmq-server configure Memory and Disk limit '" 1594389,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1594389,"'[RFE] Add a squid proxy'" 1604525,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1604525,"'enable selinux enforcing as an option'" 1628518,Triaged,ci,https://bugs.launchpad.net/tripleo/+bug/1628518,"'[RFE] add snapshotting functionality'" 1634646,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1634646,"'memcache for keystone authtoken should be a single server'" 1639172,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1639172,"'Fixed IP assignment to physical node during openstack deployment'" 1641419,Triaged,ui ux,https://bugs.launchpad.net/tripleo/+bug/1641419,"'[RFE]: Better handling of large instackenv.json files'" 1647676,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1647676,"'Make `--teardown none` the default behavior'" 1647761,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1647761,"'No overcloud-public-vip in /etc/hosts on undercloud vm'" 1649813,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1649813,"'Use predictable placement by default'" 1650428,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1650428,"'RFE: support of ScaleIO backend for Cinder'" 1654198,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1654198,"'Multiple backends of the same type can not be used in cinder/manila'" 1659452,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1659452,"'[RFE] split out topology and provisioner details from the general config'" 1663025,Triaged,edge quickstart, https://bugs.launchpad.net/tripleo/+bug/1663025,"'[RFE] Add per-node network-to-NIC mapping'" 1663034,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1663034,"'[RFE] Enable and configure DHCP relay on virt-host'" 1664743,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1664743,"'[RFE] Support Mixed Virt/Bare Metal Environments'" 1666916,Triaged,low-hanging-fruit quickstart, https://bugs.launchpad.net/tripleo/+bug/1666916,"'[quickstart][RFE] Add configuration for multi-nic network isolation'" 1693928,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1693928,"'Support split RPC/notification messaging backends'" 1694773,Triaged,quickstart,https://bugs.launchpad.net/tripleo/+bug/1694773,"'[RFE][Quickstart] Update devmode.sh to display relevant info after deploying to RDO Cloud'" 1698302,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1698302,"'RFE - Use an options file for deployment'" 1729452,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1729452,"'[RFE] TripleO should report IP addresses used on each host post-deployment'" 1731973,Triaged,ui ux,https://bugs.launchpad.net/tripleo/+bug/1731973,"'[RFE] Simplify create/import plan modal'" 1731989,Triaged,ui ux,https://bugs.launchpad.net/tripleo/+bug/1731989,"'[RFE] Automatically introspect and provide nodes to simplify workflow'" 1782139,Triaged,edge upgrade ux, https://bugs.launchpad.net/tripleo/+bug/1782139,"'[RFE] support automatic t-h-t decoupling and versioning for mixed UC/OC cases (git integration for deployment plans and tht)'" 1789197,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1789197,"'Adding THT support for Cinder backup Google cloud driver'" 1812205,Triaged,containers,https://bugs.launchpad.net/tripleo/+bug/1812205,"'ContainerImagePrepare: ability to override specific container images'" 1815918,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1815918,"'[RFE]u00a0DeployedServer - Create neutron ports on ctlplane instead of using a fake port and DeployedServerPortMap'" 1817364,Triaged,,https://bugs.launchpad.net/tripleo/+bug/1817364,"'tripleo-build-containers: use quickstart to collect logs'" 1818503,Triaged,ci quickstart, https://bugs.launchpad.net/tripleo/+bug/1818503,"'[RFE] Make the configuration of quickstart variable-centric'"

1 0

[horizon] [infra] horizon stable gate failure: yarn is required?
by Akihiro Motoki 11 May '20

11 May '20

Hi, nodejs4 jobs in stein and older stable branches in horizon are now failing [1]. The symptom is that "yarn --version" fails during ensure-yarn [2]. It looks like that yarn now requires nodejs 10 or later and does not support nodejs4. The failure happens in the jobs on ubuntu-xenial nodes. When I try nodejs10 in stable/stein, the nodejs4 jobs (lint/run) succeeded [3]. My question is whether we need to install yarn in the pre-run? horizon does not require yarn. All nodejs jobs inherit nodejs-npm job defined in zuul/zuul-jobs and the pre-run playbook [4] installs yarn. I am not sure when we started to require yarn and who requires yarn. Generally speaking, I don't think it is a good idea to switch the nodejs version in these older stable branches. horizon and horizon plugins use nodejs only for testing, so if switching to nodejs10 would solve the failure completely, it might be an option too though. Thought? -amotoki [1] https://review.opendev.org/#/q/topic:health-check+status:open+project:opens… [2] https://zuul.opendev.org/t/openstack/build/72317c21cf7b4a1a885b9a26c5ae4c2d… [3] https://review.opendev.org/#/c/726702/ [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/playbooks/javascript/p…

4 4

[SENLIN] Senlin Installation Help
by Amit Bhardwaj 11 May '20

11 May '20

Hello group! I am stuck at installation and verification of Senlin for Stein release on Ubuntu 18.04.. I had raised a request on ask.openstack.org too. Kindly have a look and suggest further. https://ask.openstack.org/en/question/127499/senlin-installation-problems/ Regards, Amit Bhardwaj

1 0

[requirements][qa] new pip resolver & our constraints needs
by Doug Hellmann 11 May '20

11 May '20

The PyPA team is working on a new resolver for pip. As part of that work, they have had some questions about the way OpenStack uses the constraints feature. They’ve been great about taking input, and prometheanfire has been doing some testing to ensure the new work doesn’t break compatibility [1] (thanks Matthew!). There is a new question from the pip maintainers about whether constraints need to support “nameless” entries (by referring to a URL in a constraints file instead of using package names) [2]. I don’t see anything in the upper-constraints.txt that looks like a URL, but I don’t know how teams might be configuring their lower-constraints.txt or whether we do anything in devstack to munge the constraints list to point to local packages as part of LIBS_FROM_GIT handling. Is anyone aware of any uses of URLs in constraints files anywhere within OpenStack? Doug [1] https://review.opendev.org/#/c/726186/ [2] https://github.com/pypa/pip/issues/8210

4 4

[baremetal-sig][ironic] Baremetal whitepaper round 3: doodle
by Arne Wiebalck 11 May '20

11 May '20

Dear all, The white paper is taking shape ... but still needs a little more work. If you want to help and join the session(s) to discuss the current state and the next steps, please reply to the doodle before the end of this week: https://doodle.com/poll/zcprxptw6nk4diq7 Like last time, I will send out the call details once we have settled on the time slot(s). Thanks! Arne -- Arne Wiebalck CERN IT

1 1

[neutron] Bug deputy report week of May 4 - 10
by Miguel Lavalle 10 May '20

10 May '20

Medium: - https://bugs.launchpad.net/neutron/+bug/1876752 neutron-ovn-db-sync-util fails with KeyError: 'ovn'. Proposed fix https://review.opendev.org/#/c/725309 - https://bugs.launchpad.net/neutron/+bug/1877146 neutron-dynamic-plugin tempest jobs fail on stable/train branch. Proposed fix: https://review.opendev.org/#/c/725920/ - https://bugs.launchpad.net/neutron/+bug/1877296 Tunnel ports are not cleaned up with several ovs agents restart - https://bugs.launchpad.net/neutron/+bug/1877377 [OVN] neutron-ovn-tempest-ovs-master-fedora periodic job is failing - https://bugs.launchpad.net/neutron/+bug/1877404 Add "qos_policy_id" field to "FloatingIP" OVO. Proposed fix: https://review.opendev.org/#/c/726208/ - https://bugs.launchpad.net/neutron/+bug/1877408 Implement FIP QoS in OVN backend - https://bugs.launchpad.net/neutron/+bug/1877447 Add TCP/UDP port forwarding extension to OVN - https://bugs.launchpad.net/neutron/+bug/1877560 Optimize "QosPolicy" OVO bound objects retrieve methods. Proposed fix https://review.opendev.org/#/c/726358/ - https://bugs.launchpad.net/neutron/+bug/1877254 neutron agent. list API lacks sort and page feature Low: - https://bugs.launchpad.net/neutron/+bug/1876898 L3 agent should reports enabled extensions to the server. Proposed fix: https://review.opendev.org/#/c/725532 - https://bugs.launchpad.net/neutron/+bug/1877195 [ovn] neutron devstack needs to support openflow15. Proposed fix: https://review.opendev.org/#/c/726010/ Opinion: - https://bugs.launchpad.net/neutron/+bug/1877248 Rabbitmq cluster split brain causes l2 population related flows to be cleared when ovs-neutron-agent is restarted RFEs: - https://bugs.launchpad.net/neutron/+bug/1877301 [RFE] L3 Router support ndp proxy

1 0

OpenStack Ussuri Community Meetings
by Allison Price 10 May '20

10 May '20

Hi everyone, The OpenStack Ussuri release is only a week and a half away! Members of the TC and project teams are holding two community meetings: one on Wednesday, May 13 and Thursday, May 14. Here, they will share some of the release highlights and project features. Join us: Wednesday, May 13 at 1400 UTC Moderator Mohammed Naser, TC Presenters / Open for Questions Slawek Kaplonski, Neutron Michael Johnson, Octavia Goutham Pacha Ravi, Manila Mark Goddard, Kolla Balazs Gibizer, Nova Brian Rosmaita, Cinder Thursday, May 14 at 0200 UTC Moderator: Rico Lin, TC Presenters / Open for Questions Michael Johnson, Octavia Goutham Pacha Ravi, Manila Rico Lin, Heat Feilong Wang, Magnum Brian Rosmaita, Cinder See you there! Allison Allison Price OpenStack Foundation allison(a)openstack.org

5 8

[release] Release countdown for week R-0, May 11 - 15
by Sean McGinnis 08 May '20

08 May '20

Development Focus ----------------- We will be releasing the coordinated OpenStack Ussuri release next week, on May 13. Thanks to everyone involved in the Ussuri cycle! We are now in pre-release freeze, so no new deliverable will be created until final release, unless a release-critical regression is spotted. Otherwise, teams participating in the virtual PTG June 1-5 should start to plan what they will be discussing there, by creating and filling team etherpads. You can access the list of PTG etherpads at: http://ptg.openstack.org/etherpads.html General Information ------------------- On release day, the release team will produce final versions of deliverables following the cycle-with-rc release model, by re-tagging the commit used for the last RC. A patch doing just that will be proposed. PTLs and release liaisons should watch for that final release patch from the release team. While not required, we would appreciate having an ack from each team before we approve it on the 13th, so that their approval is included in the metadata that goes onto the signed tag. Upcoming Deadlines & Dates -------------------------- Final Ussuri release: May 13 Virtual Victoria PTG: June 1-5

1 0

[RelMgmt] Victoria PTG Schedule
by Sean McGinnis 08 May '20

08 May '20

Hello release team, In our weekly meeting we had discussed a couple of time slots for the virtual PTG that could work for the team. We were waiting on the TC sessions to be set before picking one to avoid conflicts though. Those TC sessions are now set, so it looks like we will need to take the earlier timeslot. I have put us down for the Folsom room for 13UTC-14UTC. I have started an etherpad here: https://etherpad.opendev.org/p/relmgmt-victoria-ptg We can still capture things in our tracking etherpad, but if we end up needing to take any other notes, please add them to the PTG etherpad. Also, feel free to add anything in there ahead of the PTG to make sure we cover anything that we want to discuss. Let me know if there are any questions or concerns. Sean

1 0

[qa][tempest-plugins] Tempest plugins guide for release, stable branch support, testing etc
by Ghanshyam Mann 08 May '20

08 May '20

Hello Everyone, This is one of the pending items, Tempest team wanted to do. Tempest has more than 70 plugins and 57 are active and in running state. Tempest and its plugins have similar use cases for testing upstream CI/CD as well as the production cloud. There are always question on how we can coordinate and make release, stable branches testing more consistent among all the plugins. To do that, I have documented the policy all plugins can follow along with Tempest. - https://docs.openstack.org/tempest/latest/plugins/index.html The above document includes the plugin creation, releases for start the support for new release or end of support for Extended Maintenance branches, testing the supported stable etc. I will be working on a few of those policy implementations on plugins. One thing I already started is to add the supported stable branch job on plugins master gate. Few plugins like neutron, ironic, heat, Octavia already doing this but not all. - https://review.opendev.org/#/q/topic:stable-testing-tempest-plugins+(status… This document will be improved with more items and more best practices we can use for writing tests among all the plugins. One of the pending items I can think is to make the plugins service clients stable interface for other plugins so that integrated testing among plugins can be done in a more consistent and reliable way. All the plugins can register their service clients in Tempest and other plugins can detect them from Tempest itself. Tempest already provide the central framework to do that. -gmann

1 0

[tc] ptg etherpad
by Mohammed Naser 08 May '20

08 May '20

Hi everyone, Please have a look at the following Etherpad and try to fill it out with any suggested topics as well as attendance in order to gauge how much time we will need at the PTG: https://etherpad.opendev.org/p/tc-victoria-ptg Thank you, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 1

[Tempest][Restack]Call for help on 2020:06 Certificaion
by prakash RAMCHANDRAN 08 May '20

08 May '20

Hi all, Appreciate all your inputs in mail and one-on-one conversations I had with few of you. Like to set proper expectations before we deal with extending our goals. First we must deliver on continuity of Refstack, while we evaluate the value it adds to end users through survey. I. Every Release - There is a new criterion for Certification - Do we have one for 2020.06? - Who has volunteered or would like to volunteer for this effort? II. Can we have previous WG Chair or anyone can brief us (by call or by email ) as what the process was and how it was managed. |||. Who were last release OSF Reviewers? Can they volunteer for 2020:06 release definition for Refstack - https://opendev.org/openstack/refstack/ VI. Given the circumstances (CoViD-19) will it be possible to deliver Refstack in June /July 2020? (Need some estimates from TC or others who managed this in past years) V. Is Zun - ?, Magnum -? Are both OCI and/or CNI compliant? - Can they be tested using Tempest and add those two or any other container projects to refstack core? For Survey (suggest any specifics Questions to ask- may be few questions to - Customer / Vendors/ new feedback Q1-Value of Certification , Q2. How Often customers ask for it in RFP or sales cycle?, Q3. What additional Tests, process, frequency etc will add value for them?Q4. Do you think we should continue the efforts of Refstack?) Let me know through email and have added this to TC meeting for Thursday April 2.https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting ThanksPrakash Sent from Yahoo Mail on Android

2 1

[tripleo] TripleO CI Summary: Unified Sprint 26
by Rafael Folco 08 May '20

08 May '20

Greetings, The TripleO CI team has just completed **Unified Sprint 26** (Apr 17 thru May 06). The following is a summary of completed work during this sprint cycle [1]: - Ussuri branching prep work: container/image builds, job definitions and shifted periodic pipelines. - Contributed for TripleO-Operator-Ansible. - Initial design for the internal component pipeline prep work: resolved dependencies and requirements to build the pipeline. Successfully built RHEL8 OSP containers. - Started migrating promoter jobs to CentOS8. Converted molecule delegated jobs to run on tox environment (WIP - code needs a few fixes and consolidation). - Resumed work on an upstream standalone TLS job. - Resumed work to validate ansible 2.9 and the latest ceph-ansible. - Ruck/Rover recorded notes [2]. The planned work for the next sprint [3] extends the work started in the previous sprint and focuses on the following: - Stable branching work (ussuri). - TripleO-Operator-Ansible: contribute w/ code, docs, tests and zuul jobs. - Internal component pipeline: create basic standalone and baremetal jobs. - Continue vexxhost migration and zuul reproducer (on-going) work. - Fix promoter tests on CentOS8 and build an internal promoter server. - TripleO IPA multinode job merge. - Build CentOS8 train full promotion pipeline and a job to upgrade from train to ussuri. The Ruck and Rover for this sprint are Rafael Folco (rfolco) and Bhagyashri Shewale (bhagyashris). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes to be tracked in etherpad [4]. Thanks, rfolco [1] https://tree.taiga.io/project/tripleo-ci-board/taskboard/unified-sprint-26 [2] https://hackmd.io/1pY-KQB_QwOe-a-5oEXTRg [3] https://tree.taiga.io/project/tripleo-ci-board/taskboard/unified-sprint-27 [4] https://hackmd.io/2MdkNAUuT7aBcM0Yck4xnw

1 0

[TripleO][Manila] 'DEFAULT/network_plugin_ipv6_enabled' parameter - why is it not simply enabled by default?
by Harald Jensås 08 May '20

08 May '20

Hi, I'm working on a change to remove some parameters related to IPv6 in TripleO. This is to simplify/automate the process for operators, and reduce failures due to user error. See: https://review.opendev.org/723898 I'm not sure what to do about the 'ManilaIPv6' parameter in TripleO. It control's the *DEFAULT/network_plugin_ipv6_enabled* parameter as well as *${share_backend_name}/network_plugin_ipv6_enabled* for some backends. Dockstrings [2] and [3] in the puppet module for these backends says the same as the Manila doc[1]. A note in Manilla doc[1] reading: """ The ip version of the share network is defined by the flags of network_plugin_ipv4_enabled and network_plugin_ipv6_enabled in the manila.conf configuration since Pike. The network_plugin_ipv4_enabled default value is set to True. The network_plugin_ipv6_enabled default value is set to False. If network_plugin_ipv6_enabled option is True, the value of network_plugin_ipv4_enabled will be ignored, it means to support both IPv4 and IPv6 share network. """ Is there a downside in simply enabling IPv6 by default in Manila? Why is this option present at all? [1] https://docs.openstack.org/manila/latest/admin/shared-file-systems-network-… [2] https://opendev.org/openstack/puppet-manila/src/branch/master/manifests/bac… [3] https://opendev.org/openstack/puppet-manila/src/branch/master/manifests/bac… -- Harald Jensås

2 2

[cinder] RC-3 released
by Brian Rosmaita 08 May '20

08 May '20

Just for awareness: we cut a RC-3 yesterday in order to include a backport of Corey Bryant's eventlet fix [0]. So the official Ussuri release of cinder will be based on RC-3. (I'm only mentioning this because at the weekly meeting, it looked like the release would be based on RC-2.) [0] https://review.opendev.org/#/c/725797/

1 0

[openstack/requirements] Horizon image works abnormal because of the conflict bewteen mysqlclient and Django
by YuChengDe 08 May '20

08 May '20

Hello: I have built a horizon image in ussuri version, but it works abnormal due to package mismatch problem. According to Django===2.2.12 from latest upper-constraint.txt, it is not compatible with mysqlclient. Using old version Django===2.1.5 can fix the problem. Could you help me to check the mismatch problem. Many thanks. -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德产品开发部邮箱(Email): yu.chengde(a)99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net

2 2

rabbitmq api query
by Satish Patel 07 May '20

07 May '20

Folks, I am just playing with API and getting strange result, may be i am doing something wrong please correct me. [root@aio1-rabbit-mq-container-5233d3c3 root]# rabbitmqctl list_vhosts Listing vhosts ... name /neutron /designate /keystone /aodh / /nova /glance /ceilometer and i have configured monitoring user to query data from API Following works and i am getting data #curl -s http://172.29.239.29:15672/api/vhosts --user monitoring:de4a28d10da980077cea | jq now try to query specific vhosts like nova getting error # curl -s http://172.29.239.29:15672/api/vhosts/nova --user monitoring:de4a28d10da980077cea | jq { "error": "not_authorised", "reason": "Not administrator user" } Even i set full permission, getting same error no_authorised, what i am missing? # rabbitmqctl set_permissions monitoring -p /nova "" "" ""

3 6

[keystone] Core group changes
by Colleen Murphy 07 May '20

07 May '20

Hi team, I'm very pleased to say that Vishakha Agarwal has joined the python-keystoneclient core team! Vishakha has gained a lot of knowledge of the clients in the last few months and this change will help empower her to continue to drive our goals of ensuring all of the clients fully support keystone's APIs. Thanks for taking this on, Vishakha! I also must announce that I've removed Dave Chen from the core list. Dave's responsibilities at his company have not been related to keystone for some time, and although we've been very grateful for the occasional review he gives from time to time, he's let me know he believes it's time to be formally removed. As with every core removal, if life brings him back to keystone we'll gladly welcome him back to the core team. Thanks, Dave, for all your hard work on keystone! Colleen

4 3

[OSSA-2020-005] Keystone: OAuth1 request token authorize silently ignores roles parameter (CVE PENDING)
by Gage Hugo 07 May '20

07 May '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================== OSSA-2020-005: OAuth1 request token authorize silently ignores roles parameter ============================================================================== :Date: May 06, 2020 :CVE: Pending Affects ~~~~~~~ - - Keystone: <15.0.1, ==16.0.0 Description ~~~~~~~~~~~ kay reported a vulnerability in Keystone's OAuth1 Token API. The list of roles provided for an OAuth1 access token are ignored, so when an OAuth1 access token is used to request a keystone token, the keystone token will contain every role assignment the creator had for the project instead of the provided subset of roles. This results in the provided keystone token having more role assignments than the creator intended, possibly giving unintended escalated access. Patches ~~~~~~~ - - https://review.opendev.org/725894 (Rocky) - - https://review.opendev.org/725892 (Stein) - - https://review.opendev.org/725890 (Train) - - https://review.opendev.org/725887 (Ussuri) - - https://review.opendev.org/725885 (Victoria) Credits ~~~~~~~ - - kay (CVE Pending) References ~~~~~~~~~~ - - https://launchpad.net/bugs/1873290 - - http://cve.mitre.org/cgi-bin/cvename.cgi?name=Pending Notes ~~~~~ - - The stable/rocky branch is under extended maintenance and will receive no new point releases, but a patch for it is provided as a courtesy. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEWa125cLHIuv6ekof56j9K3b+vREFAl6zFWsACgkQ56j9K3b+ vRFDnhAArgXdQUnCyckPQciBvxMxQvqhCEhzGH0aQNAmMLaImYUwFhFVVO0DlcNb kt/ynLQLdyi3YnCz1x4VhUXaCh4Rhi9pYkU4LKa/tvJj6anrCSLHmuDD52idkZeB sFslgkh/BGfdM4HcuPLhs4SSaZpI53ASitiOhyjBIN/DmpLUbZgmJ1iz3FfQ3cTB wtjYI4jGCCMq+4POSozWMzeYdL3JzR264jBCRrCw1ErIPjpF4KSOFaH5vqakBnzw Ot7KR7s7FmIwU7LhCuvjgLW3rxwE1g5bz+Qd/97rC1bTx/iPHklQjMP5SoGwmjta Kx1prUaQqFys5Bw93e0cj1Fwn0zNHUjqLs4LZscNbyGRyAZCPREeg2quwBxVUNk9 D6jxW3J2LYIu+ictVV5fnBQd4/+NtxM8ofLDM03QZouUpkNfCHAmW81BYqd2+Pii VbJi5Litz+DHLrAyh0O4zD/PBc5+5zxB2EXEDVEJitqaxQWfogJwJzGe89ULom0I VXMuYOvqaLV9f2JIG6SEBiKrfaUhSgoHTrmznt82KOlsOBMamQUaj5iTqDoDzPD2 LVB2WLABj1cFZsnTFAec1qKwEPXuT0p3Dsb7eyvwsq5aJYS5I2bjK6Q1WcCcqzJF 1b+v0iqW0Qu+Hk4fwvcrqqQMDZ7Q982tT+B7sU8xV4jYBtFLseQ= =iEFE -----END PGP SIGNATURE-----

1 1

[OSSA-2020-004] Keystone: Keystone credential endpoints allow owner modification and are not protected from a scoped context (CVE PENDING)
by Gage Hugo 07 May '20

07 May '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ================================================================================================================= OSSA-2020-004: Keystone credential endpoints allow owner modification and are not protected from a scoped context ================================================================================================================= :Date: May 06, 2020 :CVE: Pending Affects ~~~~~~~ - - Keystone: <15.0.1, ==16.0.0 Description ~~~~~~~~~~~ kay reported two vulnerabilities in keystone's EC2 credentials API. Any authenticated user could create an EC2 credential for themselves for a project that they have a specified role on, then perform an update to the credential user and project, allowing them to masquerade as another user. (CVE #1 PENDING) Any authenticated user within a limited scope (trust/oauth/application credential) can create an EC2 credential with an escalated permission, such as obtaining admin while the user is on a limited viewer role. (CVE #2 PENDING) Both of these vulnerabilities potentially allow a malicious user to act as admin on a project that another user has the admin role on, which can effectively grant the malicious user global admin privileges. Patches ~~~~~~~ - - https://review.opendev.org/725895 (Rocky) - - https://review.opendev.org/725893 (Stein) - - https://review.opendev.org/725891 (Train) - - https://review.opendev.org/725888 (Ussuri) - - https://review.opendev.org/725886 (Victoria) Credits ~~~~~~~ - - kay (CVE Pending) References ~~~~~~~~~~ - - https://launchpad.net/bugs/1872733 - - https://launchpad.net/bugs/1872735 - - http://cve.mitre.org/cgi-bin/cvename.cgi?name=Pending Notes ~~~~~ - - The stable/rocky branch is under extended maintenance and will receive no new point releases, but a patch for it is provided as a courtesy. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEWa125cLHIuv6ekof56j9K3b+vREFAl6zE70ACgkQ56j9K3b+ vREQsBAAnHZLyrbjSwu7/CEdDVfb0sQZfDvyuXMttzouXQ6ZwEgLFKzc/aFWMjru loyst9jAx2pJzvxDfMYO11oU0M5tYFCFxhKsVvu+3ggbcNHeov1s25bPkxE7A2j7 IYJj9b+bbieYVj1ru3FJjDl3iTae4K73DeHNBCdxTSeahJZdya7hiboA1VJFt4p7 fNqU3+szsYt/vwspPBi7x+xnZszIMaUw8tVgxzB4KVD6YXbDR9Mp7itH77kGdn8l e3OpnURvfaIkPbK6fqE6jjwjQEL/6+Ahffaf4KqvsdjbAcdQRpK0UQrBX+n6DIWd TRwV/W7bEy64HrC16W78fcBlegRmEUUM4xNmdll3lwUS5KqfEeM3vXU4Ksfe9tQ2 8fDU1hDALcC55+2CMMrdFfmX/MBSTz0HVmP4snaGuoXBL/iQz22OmekFKC1tmXxb +vAtOUBsdzphRZn9KWvPIHOFGeuepWb9W0eN594JT2pdHfniLj6EaPrBaN63l7M/ pu0DTPygN5IdUXv6v/vquQZp50CaN59okmXDNiFkBeHsfaAqhdyjJjRaYvyU62OA apjVam8/f2HM0RC0vvpIqv0z0kU55NPCo61dlMZPg6U9JiQd2PzBqvEtDF1lyByF vz5e+r9fmtRcgCJIYr0Z7VlOlSMONpITN03oICaexieDTEXDXHc= =lSDG -----END PGP SIGNATURE-----

1 1

[OSSA-2020-003] Keystone: Keystone does not check signature TTL of the EC2 credential auth method (CVE PENDING)
by Gage Hugo 07 May '20

07 May '20

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ====================================================================================== OSSA-2020-003: Keystone does not check signature TTL of the EC2 credential auth method ====================================================================================== :Date: May 06, 2020 :CVE: Pending Affects ~~~~~~~ - - Keystone: <15.0.1, ==16.0.0 Description ~~~~~~~~~~~ kay reported a vulnerability with keystone's EC2 API. Keystone doesn't have a signature TTL check for AWS signature V4 and an attacker can sniff the auth header, then use it to reissue an openstack token an unlimited number of times. Patches ~~~~~~~ - - https://review.opendev.org/725385 (Rocky) - - https://review.opendev.org/725069 (Stein) - - https://review.opendev.org/724954 (Train) - - https://review.opendev.org/724746 (Ussuri) - - https://review.opendev.org/724124 (Victoria) Credits ~~~~~~~ - - kay (CVE Pending) References ~~~~~~~~~~ - - https://launchpad.net/bugs/1872737 - - http://cve.mitre.org/cgi-bin/cvename.cgi?name=Pending Notes ~~~~~ - - The stable/rocky branch is under extended maintenance and will receive no new point releases, but a patch for it is provided as a courtesy. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEWa125cLHIuv6ekof56j9K3b+vREFAl6zEjwACgkQ56j9K3b+ vRFejhAAvzq3MBwKGXIKsJxQmwVS0RxVFifTAfnKIjBGskG3knWkQHopY0IcmwoZ 3Kv2AnRgFVBuQpZ0t9Y3S3U7KRI63FT+kzA3gy9sB+h7rdqzquxejXvljRMGJlex WRCOQwRP4prFpzpUqzBg9/bIAyWpkrjJIvz7iJ9U3z6MbrZIjV+YEZ3JIRQTdMUj MajgwJ4EDynkh8trm63n7Gyuvq8ukj1FCrG1APWJi96HhwNz6XwiqXIWci4CTaEW sY9v8luETMCyv+nY2pt9IF8wXOaJKJXPTilf6sisjN2zDq+UWgsxEC0sp3h09tnZ m6cy3OvUQeDmdJVQ/VNsfUTeRYRvYri2u44FaOUBjsNxeZca1U4MCVkAiN9BBzkg k1Xb8zgGoXaytT/lzzyr67h6ZghKm6cnSUktWnX56847byOMPi/g9q1cu0edUwwC 7SDaQ08JbsEstiXtPVBhatTLxbjlNy5eql6NaZmFQatYJAQKZsasvwV4YBv290mu OsVHUEqjmYk4b4CZNPQC2681CDtAQpiLuasYiLnxC6I+zBTwfP+6tzP0xVHW4woi 4Jhl/watZMudrtMS3YoOmwZ4iFNJRzQcDWmiAr0CZiC0NGamLjvHWHRslnvmhy92 kSGWLilaMD5vBODXVY82lQHrbl96dPRbpe8/z29sALsEs6aNFYk= =qyBV -----END PGP SIGNATURE-----

1 1

[Syntribos] Does anyone still use this?
by Gage Hugo 07 May '20

07 May '20

The Security SIG has recently been looking into updating several sites/documentation and one part we discussed the last couple meetings was the security tools listings[0]. One of the projects listed there, Syntribos, doesn't appear to have much activity[1] outside of zuul/python/docs maintenance and the idea of retiring the project was mentioned. However, there does seem to be an occasional bug-fix submitted, so we are sending this email out to see if anyone is still utilizing Syntribos. If so, please either respond here, reach out to us in the #openstack-security irc channel, or fill out the section in the Security SIG Agenda etherpad[2]. Thanks! [0] https://security.openstack.org/#security-tool-development [1] https://review.opendev.org/#/q/project:openstack/syntribos [2] https://etherpad.openstack.org/p/security-agenda

2 2

[infra][qa][sigs][tc] Forming a Testing and Collaboration Tools (TaCT) SIG
by Jeremy Stanley 07 May '20

07 May '20

The Infrastructure team, and the CI team before it, has traditionally existed to care for the continuous integration and collaboration infrastructure on which the OpenStack community relies. With the rise of the OpenDev Collaboratory as a distinct effort outside of (but still primarily in service of) OpenStack, the majority of the team's former systems administration activities are no longer occurring under the authority of OpenStack. Most of the software and configuration management repositories previously in the care of the Infra team are also no longer official OpenStack deliverables, and have become part of OpenDev as well (and their biggest development effort, Zuul+Nodepool, was already spun out as an independent Open Infrastructure Project last year). With the above responsibilities moved elsewhere, the existence of a formal team is less of a necessity. What remains is a need to support OpenStack's project-specific testing and collaboration tooling and services, primarily job configuration and other things which shouldn't currently be generalized into components of the OpenDev Collaboratory. To this end, I propose the creation of a new Testing and Collaboration Tools (TaCT) SIG which would serve the role currently occupied by the OpenStack Infrastructure team. I'm open to alternative names, but employing the vague term "infrastructure" has perpetually confused newcomers to our community, so this seems like an opportunity for something less overloaded. The TaCT SIG would consist of the usual suspects: people who review OpenStack job configuration changes, people who dig into problems with test frameworks to unblock the integrated gate queue, people who figure out strange Python packaging related issues, people who help work out lapsed control of Launchpad admin groups... also, ideally, the person selected by the TC to serve as OpenStack's representative on the OpenDev Advisory Council would be heavily involved. Many of these activities are closely related to work the Quality Assurance team is doing, so hopefully folks who are active in QA will also participate in this SIG. What do you think? Does this satisfactorily capture the infrastructure needs of the OpenStack community, and could it serve as an alternative to the current Infrastructure team? -- Jeremy Stanley

5 7

OpenDev Events Update - we need your feedback!
by Ashlee Ferguson 07 May '20

07 May '20

Hi everyone, Thanks so much for your feedback that’s continually helping us shape these virtual OpenDev events[1]. Keep reading this email for some important updates on all three events! 1. OpenDev: Large-scale Usage of Open Infrastructure Software - June 29 - July 1 (1300 - 1600 UTC each day) - Registration is open[2]! - High-level schedule coming soon; Find a brief topic summary and more information here[1] 2. OpenDev: Hardware Automation - July 20 - 22 - Help us pick a time - visit this etherpad[3] and +1 the times you’re available and the topics you would like to cover - please provide your input by this Thursday, March 7. 3. OpenDev: Containers in Production - August 10 - 12 - Help us pick a time - visit this etherpad[4] and +1 the times you’re available and the topics you would like to cover - please provide your input by this Thursday, March 7. Find more information and updates on all of these events here[1]. [1] https://www.openstack.org/events/opendev-2020 [2] https://opendev_largescale.eventbrite.com [3] https://etherpad.opendev.org/p/OpenDev_HardwareAutomation [4] https://etherpad.opendev.org/p/OpenDev_ContainersInProduction Thanks! Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation

1 2

[ironic] II SPUC - The Sanity Preservation Un-Conference
by Iury Gregory 07 May '20

07 May '20

Hello everyone \o/ We are going for the second edition of SPUC! For those who doesn't know what is SPUC check [0]. There is only 3 things you need to do: 1) Fill out the doodle in [1] *, it has options for the next two weeks since May 1st is a holiday. 2) Brainstorm some ideas of things you might want to talk about/present or LEARN! * 3) Dust off your silly hats! * * From Julia's email =) [0] Thank you! [0] http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013521.ht… [1] https://doodle.com/poll/2q5zmv3g6uy2475e -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

3 3

[neutron] Agenda of the 08.05.2020 Drivers meeting
by Slawek Kaplonski 07 May '20

07 May '20

Hi, For tomorrows drivers meeting we have 2 new RFEs to be discussed: * https://bugs.launchpad.net/neutron/+bug/1875516 - [RFE] Allow sharing security groups as read-only * https://bugs.launchpad.net/neutron/+bug/1873091/ - [RFE] Neutron ports dns_assignment does not match the designate DNS records for Neutron port See You tomorrow on the meeting. -- Slawek Kaplonski Senior software engineer Red Hat

1 0

[all] [qa] [oslo] Usage of testtools?
by Dmitry Tantsur 07 May '20

07 May '20

Hi folks, Most OpenStack projects use testtools/fixtures/unittest2 for unit tests. It was immensely helpful in Python 2 times, but I wonder if we should migrate away now. I've hit at least these three bugs: https://github.com/testing-cabal/testtools/issues/235 https://github.com/testing-cabal/testtools/issues/275 https://github.com/testing-cabal/testtools/issues/144 We can invest time in fixing them, but I wonder if we should just migrate to the standard unittest (and move oslotest to it) now that we require Python >= 3.6. Thoughts? Dmitry

2 2

[kolla] Kolla klub meeting today
by Mark Goddard 07 May '20

07 May '20

Hi, Just a reminder that we have the third Kolla Klub meeting today at 3pm UTC. We have Gaël Therond and Дмитрий Грачев (Dmitry Grachev) giving case studies. Meeting notes, connection info and agenda: https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… Cheers, Mark

1 0

[keystone] How to create a session using trust-scoped token
by Lingxian Kong 06 May '20

06 May '20

Hi keystone team, I met with an issue that can't perform openstack operations using openstack client lib by providing a trust scoped token. However, I can use that token to send HTTP request directly. Here is my code and the error message, http://dpaste.com/1N6AX0R I asked several times in #openstack-keystone IRC channel, but got no response. --- Lingxian Kong Senior Software Engineer Catalyst Cloud www.catalystcloud.nz

2 3

[First Contact] [SIG] [PTG] Discussion Topic Collection
by Kendall Nelson 06 May '20

06 May '20

Hello! I signed us up for some time (just an hour) on Monday and figured I should create an etherpad[1] to collect topics for us to discuss. Feel free to add your ideas! Can't wait to see you all there! -Kendall (diablo_rojo) [1] https://etherpad.opendev.org/p/FC-SIG-V-PTG

1 0

[ptl][release] Ussuri final RC deadline reminder
by Sean McGinnis 06 May '20

06 May '20

Hey everyone, We need several days before the final coordinate release to make sure no major issues are found, downstream packagers have time to get things lined up, and to make sure that things are stable for next week's Ussuri release date. To that end, and as a reminder to everyone, tomorrow is the deadline for any final RC releases before we enter the freeze. This is the last chance to get anything released and included in the initial Ussuri release. Looking through merged commits, there are a few repos that have merged code that the team's may want to consider releasing in a final RC. Things we do NOT need to get released for the final release: - .gitreview updates for the stable/ussuri branch - Upper constraints updates for the stable/ussuri branch - Tox and/or Zuul configuration changes Things you may want to include: - Translations - Bugfixes backported to stable/ussuri Also keep in mind that a stable release can be done quickly after the coordinated release and the freeze is over. So some minor issues are OK if they don't make it in. But if things are ready, it may be worth picking up anything that has merged so it is in those first official versions. See below for a listing of some repos that have things merged in stable/ussuri that look like they may be worth releasing one more final RC. Thanks! Sean [ Unreleased changes in openstack/compute-hyperv (stable/ussuri) ] Changes between 10.0.0.0rc1 and d449954 * d449954 2020-04-24 11:51:50 +0000 Address driver API changes (finish_migration) [ Unreleased changes in openstack/heat (stable/ussuri) ] Changes between 14.0.0.0rc1 and bceca6189 * 5bc6787a8 2020-04-28 07:13:57 +0000 Imported Translations from Zanata [ Unreleased changes in openstack/keystone (stable/ussuri) ] Changes between 17.0.0.0rc1 and 0e463a78d * 8d5becbe4 2020-04-30 20:25:13 +0000 Check timestamp of signed EC2 token request * aef912187 2020-04-26 07:04:33 +0000 Imported Translations from Zanata [ Unreleased changes in openstack/magnum (stable/ussuri) ] Changes between 10.0.0.0rc1 and c6e536ae * c6e536ae 2020-05-04 21:50:23 +0000 [k8s] Fix docker storage of Fedora CoreOS * abafef16 2020-05-01 09:15:52 +0000 Use ensure-* roles | * 45563f37 2020-05-01 18:57:43 +0000 [k8s] Upgrade k8s dashboard version to v2.0.0 |/ * c2f4b9b5 2020-04-27 23:01:40 +0000 [k8s] Fix no IP address in api_address [ Unreleased changes in openstack/manila (stable/ussuri) ] Changes between 10.0.0.0rc1 and 653092e5 * cec83f8c 2020-04-27 20:32:57 +0000 [CI] Fix grenade share networks test | * 3ea582e1 2020-04-28 18:59:44 +0000 Update share-manager behavior for shrink share operation |/ | * 541f9d8d 2020-04-30 05:28:27 +0000 [Unity] Fix unit test issue |/ * bdb955a1 2020-04-26 16:51:40 -0700 [grenade][stable/ussuri only] Switch base version [ Unreleased changes in openstack/monasca-agent (stable/ussuri) ] Changes between 3.0.0.0rc1 and 5eb3b78 * eee191a 2020-04-27 18:54:50 +0000 Do not copy /sbin/ip to /usr/bin/monasa-agent-ip [ Unreleased changes in openstack/networking-hyperv (stable/ussuri) ] Changes between 8.0.0.0rc1 and 6da239c * 6da239c 2020-04-27 06:57:06 +0000 Pick up security group RPC API changes [ Unreleased changes in openstack/neutron-vpnaas (stable/ussuri) ] Changes between 16.0.0.0rc1 and 3bf327fd5 * 4bc39fa53 2020-05-03 22:34:26 +0000 Fix unsubscriptable-object error [ Unreleased changes in openstack/neutron (stable/ussuri) ] Changes between 16.0.0.0rc1 and c06cb95b6f * 1e81440b63 2020-05-05 15:50:41 +0000 Monkey patch original current_thread _active | * 54ffa37538 2020-05-04 15:20:08 +0000 Add Octavia file in devstack/lib |/ * cca0aebb26 2020-05-01 17:23:28 +0200 Add Prelude for Ussuri release notes. * e3e9a90f75 2020-04-26 07:31:19 +0000 Imported Translations from Zanata [ Unreleased changes in openstack/octavia-dashboard (stable/ussuri) ] Changes between 5.0.0.0rc1 and 57e9ea7 * 57e9ea7 2020-05-06 08:27:54 +0000 Imported Translations from Zanata * 97d1c6d 2020-04-28 08:47:09 +0000 Imported Translations from Zanata | * c53fa6a 2020-04-26 07:52:04 +0000 Imported Translations from Zanata [ Unreleased changes in openstack/sahara-dashboard (stable/ussuri) ] Changes between 12.0.0.0rc1 and 0fa9e96 * 0fa9e96 2020-05-06 09:15:35 +0000 Imported Translations from Zanata [ Unreleased changes in openstack/sahara (stable/ussuri) ] Changes between 12.0.0.0rc1 and a6ee5223 * a6ee5223 2020-05-06 13:53:41 +0000 Monkey patch original current_thread _active * 3db9f750 2020-04-26 08:17:19 +0000 Imported Translations from Zanata [ Unreleased changes in openstack/searchlight-ui (stable/ussuri) ] Changes between 8.0.0.0rc1 and 75216df * 75216df 2020-05-06 09:32:28 +0000 Imported Translations from Zanata [ Unreleased changes in openstack/searchlight (stable/ussuri) ] Changes between 8.0.0.0rc1 and 395df50 * 824e749 2020-04-26 08:42:41 +0000 Imported Translations from Zanata [ Unreleased changes in openstack/senlin (stable/ussuri) ] Changes between 9.0.0.0rc1 and dd528700 * f1e20d12 2020-04-26 08:48:31 +0000 Imported Translations from Zanata [ Unreleased changes in openstack/watcher (stable/ussuri) ] Changes between 4.0.0.0rc1 and 870e6d75 * 870e6d75 2020-04-26 09:05:18 +0000 Imported Translations from Zanata

2 1

[tc] proposed time poll
by Mohammed Naser 06 May '20

06 May '20

Hi everyone, I've created the following doodle to help us pick a time for the upcoming PTG: https://doodle.com/poll/3ywuywu825hu7v23 Please post the times that work for you. Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[tripleo] Proposing Sergii Golovatiuk and Jesse Petorius for tripleo-upgrade core
by Jose Luis Franco Arza 06 May '20

06 May '20

Hi, I would like to propose to Sergii Golovatiuk and Jesse Pretorius as core members for the tripleo-upgrade <https://github.com/openstack/tripleo-upgrade>repository. This repository is being used mostly to automate the workflow to upgrade, update and fast-forward TripleO. And it is being used in our CI automation, downstream and upstream. Both, Sergii <https://review.opendev.org/#/q/project:openstack/tripleo-upgrade+owner:%22S…> and Jesse <https://review.opendev.org/#/q/project:openstack/tripleo-upgrade+owner:%22J…>, have been very active in the repository with patches and reviews. And they have a good understanding of the code, as well as its integration with tripleo-quickstart and infrared. Please, feel free to add your votes into the thread. Thanks, José Luis

11 13

On-disk image much bigger than VM shows with df.
by Ken D'Ambrosio 06 May '20

06 May '20

Hey, all. I've got a VM -- this is in Juno -- which du shows as using 152 GB on the compute node's disk. In the VM, itself, it says it's using 39 GB of an 80 GB volume. So, clearly, that sparse file has gotten crazy huge with un-reclaimed stuff. I seem to recall doing snapshots and then defragging them, "back in the day," but I have no idea if there's a way to do that to an instance *without* snapshotting. So: * If I snapshot it, can I then just defrag the snapshot and then make use of it to bring my system back? * Even better: is there a way to defrag the on-disk VM files without snapshotting? Thanks... -Ken

1 0

Feedback on StarlingX pilot project
by Ildiko Vancsa 06 May '20

06 May '20

Hi, I’m reaching out to you about the StarlingX project as they will start their confirmation process with the OSF staff and Board of Directors next week with a few pre-review and early feedback calls to prepare for their confirmation review on the next Board meeting in early June. A draft of the slide deck[1] they plan to present is available for reference. Per the confirmation guidelines[2], the OSF Board of directors will take into account the feedback from representative bodies of existing confirmed Open Infrastructure Projects (Airship, Kata, OpenStack and Zuul) when evaluating StarlingX for confirmation. Particularly worth calling out, guideline #4 "Open collaboration” asserts the following: Project behaves as a good neighbor to other confirmed and pilot projects. If you have any observations/interactions with the StarlingX project which could serve as useful examples for how this project does or does not meet this and other guidelines, please provide them on the etherpad[3]. If possible, include a citation with links to substantiate your feedback. I'll assemble this feedback and send it to the Board (via the public foundation mailing list) for consideration before their review meeting with the BoD. If you could give your feedback till the end of next week that would be highly appreciated. Thanks and Best Regards, Ildikó Váncsa [1] https://drive.google.com/file/d/16FPqzLT_3UH5AbZQJGg5Y9g4CN6AsRmx/view?usp=… [2] https://wiki.openstack.org/wiki/Governance/Foundation/OSFProjectConfirmatio… [3] https://etherpad.opendev.org/p/openstack-feedback-starlingx-confirmation

1 0

[TripleO][train][rdo] installation of undercloud fails during Run container-puppet tasks step1
by Ruslanas Gžibovskis 06 May '20

06 May '20

Hi all, I am running a fresh install of rdo train, on centos7 I almost a week I am facing error at this step: TASK [Run container-puppet tasks (generate config) during step 1] So I have ansible.log attached, I cannot find anything, where it is failing. According to some understanding in ansible, it fails if it finds stderr output. I cannot find error/fail or smth, I see Notices and Warnings, but I believe it is not stderr? I see containers running and removed after some time. (as it should be I think)... Could you help me, where to dig? -- Ruslanas Gžibovskis +370 6030 7030

5 19

[charms][ptg] Victoria Cycle PTG planning
by James Page 06 May '20

06 May '20

Hi Team I've setup an etherpad: https://etherpad.opendev.org/p/charms-ptg-victoria and tentatively proposed slots for us to meet on: Wednesday 3rd June - 1400-1700 UTC Thursday 4th June - 1400-1700 UTC Please add proposed discussion topics and your name to the etherpad. Cheers James

1 0

[largescale-sig] Next meeting: May 6, 8utc
by Thierry Carrez 06 May '20

06 May '20

Hi everyone, The Large Scale SIG will have a meeting this week on Wednesday, May 6 at 8 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200506T08 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - amorin to propose patch against Nova doc - masahito to prepare oslo.metric POC code release - belmoreira to continue working on scaling story on https://etherpad.openstack.org/p/scaling-stories - ttx to talk to oneswig about his bare metal cluster scaling story work item Talk to you all on Wednesday, -- Thierry Carrez

1 1

[Cyborg][PTG]Virtual PTG Planning
by yumeng bao 06 May '20

06 May '20

Hi team, We are now collecting topics for Virtual PTG [1] and we need to choose the slots for it on the official schedule[2]. If you are interested in participating PTG you will need to do two things: 1. Please add your name and topics to the etherpad[3], we are still collecting topics. 2. Please help to choose a time by filling out the doodle poll[4]. We now have 12 topics, so we will need 2 or 3 hours for 3 days (total 6-9 hours) or more if we have more topics. PS: The official deadline for team registration is May 10th, it will be appreciated if you can do this poll ASAP. ^ ^ Regards, Yumeng [1]http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.… [2]https://ethercalc.openstack.org/126u8ek25noy [3]https://etherpad.opendev.org/p/cyborg-victoria-goals [4]https://doodle.com/poll/wdw5cyeucayzhu9k

1 0

[Octavia] Help with bridge interfaces with openstack queens in a existing neutron openvswitch dvr snat environment
by Bujack, Stefan 05 May '20

05 May '20

Hello, I am trying to install octavia in our existing Openstack Queens Cloud and have problems with the lb-mgmt network ports. Is there anybody who could please help me with this issue? Thanks in advance, Greets Stefan Bujack

2 1

[puppet] Configuring Debian's uwsgi for each service
by Thomas Goirand 05 May '20

05 May '20

Hi, In Debian all service APIs are by default using uwsgi. This means that there's no reason to setup Apache for the API, as uwsgi comes by default. However, there are a number of things that operators may want to configure, like for example, the number of workers. This is why I started this PR: https://review.opendev.org/725065 Since Tobias asked for more details about what I was doing, I thought it was a good idea to start a thread in the list, rather than just discussing in the patch review. So, what I did for Neutron is only the beginning. If it works as I expect, I intend to generalize this on all OpenStack services supported by Debian. This means at least: - nova - keystone - glance - cinder - barbican - neutron - aodh - panko - gnocchi - etc. The first step is having this neutron_uwsgi_config provider up and running, then I'll see how to integrate with the rest of puppet-openstack and have things like number of workers integrated with <SERVICE>::api stuff... Your thoughts? Cheers, Thomas Goirand (zigo)

4 6

[openstack-ansible] dropping suse support
by Mohammed Naser 05 May '20

05 May '20

Hi everyone, I've been trying to avoid writing this email for the longest time ever. It's really painful to have to reach this state, but I think we've hit a point where we can no longer maintain support for SUSE within OpenStack Ansible. Unfortunately, with the recent layoffs, the OSA team has taken a huge hit in terms of contributors which means that there is far less contributors within the project. This means that we have less resources to go around and it forces us to focus on a more functional, reliable and well tested set of scenarios. Over the past few cycles, there has been effort to add SUSE support to OpenStack Ansible, during the time that we had maintainers, it was great and SUSE issues were being fixed promptly. In addition, due to the larger team at the time, we found ourselves having some extra time where we can help unbreak other gates. Jesse used to call this a "labour of love", which I admired at the time and hoped we continue to do as much as we can of. However, the lack of a committed maintainer for OpenSUSE has resulted in constantly failing jobs[1][2] (which were moved to non-voting, wasting CI resources as no one fixed them). In addition, it's causing several gate blocks for a few times with no one really finding the time to clean them up. We are resource constrained at this point and we need the resource to go towards making the small subset of supported features functional (i.e. CentOS/Ubuntu). We struggle with that enough, and there seems to be no deployers that are running SUSE in real life at the moment based on bugs submitted. With that, I propose that we drop SUSE support this cycle. If anyone would like to volunteer to maintain it, we can review that option, but that would require a serious commitment as we've had maintainers step off and it hurts the velocity of the project as no one can merge code anymore. ..Really wish I didn't have to write this email Mohammed [1]: http://zuul.opendev.org/t/openstack/builds?job_name=openstack-ansible-funct… [2]: http://zuul.opendev.org/t/openstack/builds?job_name=openstack-ansible-funct…

6 9

[all][qa] grenade zuulv3 native job available now and its migration plan
by Ghanshyam Mann 05 May '20

05 May '20

Hello Everyone, Finally, after so many cycles, grenade base job has been migrated to zuulv3 native[1]. This is merged in the Ussuri branch. Thanks to tosky for keep working on this and finish it!! New jobs 'grenade', 'grenade-multinode', 'grenade-postgresql' and 'grenade-forward' are zuulv3 native now and we kept old job name 'grenade-py3' as an alias to 'grenade' so that it would not break the gate using 'grenade-py3'. * Start using this new base job for your projects specific grenade jobs. * Migration to new job name: The integrated template and projects are using old job name 'grenade-py3' need to move to a new job name. Job is defined in the integrated template and also in the project's zuul.yaml for irrelevant-files. So we need to switch both places at the same time otherwise you will be seeing the two jobs running on your gate (master as well as on Ussuri). Integrated service specific template has switched to new job[2] which means you might see two jobs running 'grenade' & 'grenade-py3' running on your gate until you change .zuul.yaml. Example: Nova did for master as well as Ussuri gate - https://review.opendev.org/#/q/I212692905a1d645cd911c2a161c13c794c0e0f4d It needs to be done in Ussuri also as Tempest where integrated templates are present is branchless and apply the change for Ussuri job also. [1] https://review.opendev.org/#/c/548936/ [2] https://review.opendev.org/#/c/722551/ -gmann

7 14

[tripleo] Container image tooling roadmap
by Kevin Carter 05 May '20

05 May '20

Hello Stackers, As you may have seen, the TripleO project has been testing the idea of building container images using a simplified toolchain [0]. The idea is to build smaller, more easily maintained images to simplify the lives of TripleO consumers. Since TripleO's move to containers, the project has been leveraging Kolla to provide Dockerfiles, and while this has worked, TripleO has created considerable tooling to bend Kolla images to its needs. Sadly this has resulted in an image size explosion and the proliferation of difficult to maintain tools, with low bus factors, which are essential to the success of the project. To address the risk centered around the TripleO containerization story, we've drafted a spec [0], which we believe outlines a more sustainable future. In this specification, we've designed a new, much more straightforward, approach to building container images for the TripleO project. The "simple container generation," specification does not intend to be a general-purpose tool used to create images for the greater OpenStack community, both Loci and Kolla do that already. This effort is to build containers only for TripleO using distro provided repositories, with distro maintained tooling. By focusing only on what we need, we're able to remove all general-purpose assumptions and create a vertically integrated stack resulting in a much smaller surface area. To highlight how all this works, we've put together several POC changes: * Role and playbook to implement the Containerfile specification [1]. * Tripleoclient review to interface with the new role and playbook [2]. * Directory structure for variable file layout [3]. * To see how this works using the POC code, building images we've tested in real deployments, please watch the ASCII-cast [4]. * Example configuration file examples are here [5][6][7]. A few examples of size comparisons between our proposed tooling versus current Kolla based images [8]: - base: + Kolla: 588 MB - new: 211 MB # based on ubi8, smaller than centos8 - nova-base: + Kolla: 1.09 GB - new: 720 MB - nova-libvirt: + Kolla: 2.14 GB - new: 1.9 GB - keystone: + Kolla: 973 MB - new: 532 MB - memcached: + Kolla: 633 MB - new: 379 MB While the links shown are many, the actual volume of the proposed change is small, although the impact is massive: * With more straightforward to understand tools, we'll be able to get broader participation from the TripleO community to maintain our containerization efforts and extend our service capabilities. * With smaller images, the TripleO community will serve OpenStack deployers and operators better; less bandwidth consumption and faster install times. We're looking to chart a more reliable path forward, and making the TripleO user experience a great one. While the POC changes are feature-complete and functional, more work is needed to create the required variable files; however, should the proposed specification be ratified, we expect to make quick work of what's left. As such, if you would like to be involved or have any feedback on anything presented here, please don't hesitate to reach out. We aim to provide regular updates regarding our progress on the "Simple container generation" initiative, so stay tuned. Thanks, Kevin and Emilien [0] https://review.opendev.org/#/c/723665/ [1] https://review.opendev.org/#/c/722557/ [2] https://review.opendev.org/#/c/724147/ [3] https://review.opendev.org/#/c/722486/ [4] https://files.macchi.pro:8443/demo-container-images/ [5] http://paste.openstack.org/show/792995/ [6] http://paste.openstack.org/show/792994/ [7] http://paste.openstack.org/show/792993/ [8] https://4ce3fa2efa42bb6b3a69-771991cd07d409aaec3e4ca5eafdd7e0.ssl.cf2.rackc… Kevin Carter IRC: kecarter

11 27

[blazar] Updating blazar-core and blazar-release groups
by Pierre Riteau 05 May '20

05 May '20

Hello, I noticed in a recent blazar-specs patch [1] that lots of historical contributors were requested as reviewers. I assume this is because the blazar-core group was used (this is not a feature that I've used before on Gerrit). To avoid spamming people who haven't worked on Blazar for years, I propose to remove the following members of the blazar-core group: Dina Belova Hiroaki Kobayashi Nikolay Starodubtsev Pablo Andres Fuente Ryota MIBU Swann Croiset Sylvain Bauza I would also remove Hiroaki Kobayashi from the blazar-release group. Please let me know if you have any objections. [1] https://review.opendev.org/#/c/723115/

2 2

[neutron] bug deputy report (4/27-5/3)
by Akihiro Motoki 05 May '20

05 May '20

Hi, I was a bug deputy last week. The last week was relatively a quiet week. Higher priority bugs have assignees. They are not release blockers, while it is nice to have them backported. A bug on DVR with flat network needs to be covered by L3 team. ## Untriaged * https://bugs.launchpad.net/neutron/+bug/1876092 DVR with Flat network result in ICMP reply DUP New, Undecided It needs to be checked by DVR folks. I am not sure DVR with flat network is not supported by design or it is just a bug. * https://bugs.launchpad.net/neutron/+bug/1876021 create multiple reserved_dhcp_port doesn't work as expected I will try to reproduce it after the holiday week in my side is over. ## Assigned * https://bugs.launchpad.net/neutron/+bug/1875849 not ensure default security group exists when filter by project_id Medium, In Progress, the reporter is working on the fix ## In Progress * https://bugs.launchpad.net/nova/+bug/1863021 eventlet monkey patch results in assert `len(_active) == 1` AssertionError High, In Progress, a fixed is in the gate * https://bugs.launchpad.net/neutron/+bug/1876148 OVNL3RouterPlugin should add_router_interface as in RouterPluginBase Medium, In Progress * https://bugs.launchpad.net/neutron/+bug/1876094 Dnsmasq 2.81 broke neutron's DHCP service High, In Progress ## New RFEs * https://bugs.launchpad.net/neutron/+bug/1875516 [RFE] Allow sharing security groups as read-only will be discussed in coming drivers meetings * https://bugs.launchpad.net/neutron/+bug/1875852 [RFE] [OVN] SRIOV routing on VLAN Tenant networks ## Fix Released * https://bugs.launchpad.net/neutron/+bug/1875865 SRIOV OVN metadata namespaces not cleaned up after ports are unbounded * https://bugs.launchpad.net/bugs/1875344 Cleanup in neutron_tempest_plugin.api.admin.test_external_network_extension.ExternalNetworksRBACTestJSON may fail in dvr deployments

1 0

[all][docs] docs.openstack.org: Check Ussuri Index pages
by Andreas Jaeger 05 May '20

05 May '20

The Ussuri index pages [1] are now published, the default on docs.o.o to Ussuri will change with release. The index pages only list entries that existed yesterday, so if a project was branched but did not merge any change, then no Ussuri content might exist and thus the project is not listed in the index pages. In such a case: Merge the usual bot updates, wait for the content to be published, and then propose a change to [3]. For details see [2]. Andreas [1] https://docs.openstack.org/ussuri/ [2] https://docs.openstack.org/doc-contrib-guide/doc-index.html [3] https://opendev.org/openstack/openstack-manuals/src/branch/master/www/proje… -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB

1 0

[Watcher] No IRC meeting tomorrow
by licanwei 05 May '20

05 May '20

1 0

[ironic][ptg] Virtual PTG - Victoria
by Iury Gregory 05 May '20

05 May '20

Hello Ironicers! We need to choose the slots for the Virtual PTG[1] on the official schedule [2]. So, if you are interested in participating you need to do two things: 1- Add your name and topics to the etherpad [3]. 2- Fill out the doodle in [4]. Thank you! [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.ht… [2] https://ethercalc.openstack.org/126u8ek25noy [3] https://etherpad.opendev.org/p/Ironic-VictoriaPTG-Planning [4] https://doodle.com/poll/mbpr2x7z3t5hqec6 -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 2

[neutron][QoS] IRC meeting cancelled on May 5
by Rodolfo Alonso 05 May '20

05 May '20

Hello: Due to the lack of agenda, I'm going to cancel the Neutron QoS meeting today. Regards. Rodolfo Alonso (ralonsoh)

1 0

[all][PTL][TC] PTG Signup Last Call
by Kendall Nelson 04 May '20

04 May '20

Hello! In an effort to get a schedule set and posted on the website and so that you can all block your calendars for the event, we ask that *teams finish signing up for time by Sunday, May 10th at 7:00 UTC*. We have done some consolidation to save room resources (as we will have to set up/pay for rooms ahead of time) so if you are in the list below, please note that your room may have changed, but the timing should be the same. Also note, some teams may be set to switch rooms throughout the week. Currently Signed Up Teams: Airship Automation SIG Cinder Edge Computing Group First Contact SIG Interop WG Ironic Glance Heat Horizon Kata Containers Kolla Manila Monasca Multi-Arch SIG Neutron Nova Octavia OpenDev OpenStackAnsible OpenStackAnsibleModules OpenStack-Helm Oslo QA Scientific SIG Security SIG Tacker TripleO Thanks! -The Kendalls(diablo_rojo & wendallkaters)

1 0

[all] Virtual PTG Registration Live
by Kendall Waters 04 May '20

04 May '20

Hey everyone, Registration for the June 2020 Virtual PTG is now live! It is free but its still extremely important that you register as this is primarily so we have a way to contact attendees with information about the event as we figure the rest of the details out. So please take a minute to register: https://virtualptgjune2020.eventbrite.com <https://virtualptgjune2020.eventbrite.com/> Let us know if you have any questions! -the Kendalls (diablo_rojo & wendallkaters)

1 0

cross distro Virtual PTG planning
by Thomas Goirand 04 May '20

04 May '20

Dear package maintainers, We used to have a cross-distro discussion during each PTG (well, summits, since I didn't attend any PTG since the split). I was wondering if people from other distros would be interested in having such a session again. Please tell if you hare as a follow-up here, then maybe we can add ourselves in the ethercalc. I used to know everyone, like Haikel, people from SuSE, etc. Nowadays, I only know people from Canonical. I'd love to meet the new guys around. Cheers, Thomas Goirand (zigo)

3 2

[cinder] critical bugs/patches for RC-2
by Brian Rosmaita 03 May '20

03 May '20

The proposed list is here: https://etherpad.opendev.org/p/cinder-ussuri-rc-backport-potential Please prioritize your reviewing accordingly. There are several proposed but not approved bugs on the list; I could use some feedback on whether they are release-critical or not. Please reply on the etherpad. thanks, brian

1 2

[blazar] IRC meeting cancelled on May 5
by Pierre Riteau 03 May '20

03 May '20

Hello, Due to a scheduling conflict, I will not be able to chair the Blazar IRC meeting on Tuesday May 5. I propose to cancel and meet as usual on May 12. Best wishes, Pierre Riteau (priteau)

1 0

[InteropWG] Draft Guidelines for 2020.06 Ussuri core and addons for orchestration and dns
by prakash RAMCHANDRAN 02 May '20

02 May '20

Hi all, We have been trying to draft Ussuri guidelines API for Market logo mark as part of InteropWGIn case anyone is interested in reviewing the draft patch please feel free to comment with +1 only.The +2's are reserved for Mark-Voelker & Egle.sigler c Vice Chair and past Vice-Chairs for Interop WGCall for Review: https://review.opendev.org/722137 We are investing add-ons for OpenStack Edge , Containers and Swift backends.If you have any suggestions please pitch in. Please add your ideas to PTG etherpad link in the follwoing (Jine 1st - 1st 2 hour slot)https://etherpad.opendev.org/p/interop ThnaksPrakash https://etherpad.opendev.org/p/ecg_virtual_ptg_planning_june_2020

2 1

[goals][Drop Python 2.7 Support] Status Report: COMPLETED \o/
by Ghanshyam Mann 02 May '20

02 May '20

Hello Everyone, Please find the final status for the py2.7 drop goal. Finally, it is COMPLETED!! With this (after three continuous cycles), I am taking a break from community goals (at least for V cycle :))!!. Wiki page is updated: https://wiki.openstack.org/wiki/Python3 I have added the 'Python3 Only' column here https://wiki.openstack.org/wiki/Python3#Python_3_Status_of_OpenStack_projec… Completion Report: =============== * Swift & Storlets are the two projects keeping py2.7 support. * All projects have completed the goal and now are python3-only. * It has been another roller coaster :) and I appreciate everyone helped in this work and all the projects reviewing the patches on time with few exceptions :). * A Lot of gate issues occurred and fixed during this transition especially making branchless tooling testing the mixed python version ( stable branch on py2 and other on py3). * I finished the audit for all the projects. requirement repo will be cleaning up the py2 caps in Victoria cycle[1]. Some ongoing work on deployement projects repo or unmaintained repo: ------------------------------------------------------------------------------------------- These are dpendendant on other work for testing framework etc. This can be continued and need not to be tracked under this goal. * python-barbicanclient: https://review.opendev.org/#/c/699096/ ** This repo seems unmaintained for last 6 months and the gate is already broken. * Openstack Charms - Most of them merged, few are waiting for the team to migrate to Python3 Zaza functional test framework. * Openstackansible - This will finish once centos jobs will be migrated to Centos8. * Openstack-Helm - No conclusion yet from help team on what else to do for py2 drop. -gmann

6 6

[all][qa] Gate Status: week 20-18
by Ghanshyam Mann 01 May '20

01 May '20

Hello Everyone, I am highlighting the few of the gate issues we fixed or in-progress recently. 1. Ubuntu xenial node jobs on stable stein onwards gate or 3rd party CI. Tempest 23.0.0 is the last version supported for py2.7 or py3.5. And we used the that version to tests stable/rocky jobs(py3.5 env) gate and any py2.7 job on stein or train gate. It was fixed on many projects when gate started failing with master Tempest. Last week when Tempest new version 24.0.0 is released and the same is updated in master upper-constraint, we found xenial node job running on stein gate (for Octavia and Ironic at least). Fixing those is not easy which needs overriding the constraint for that particular job. Octavia and Ironic removed the xenial job which is the right step. But few 3rd party CI not migrated to Bionic stein onwards will stop working now. One workaround can be to override the constraint to stable/rocky via env var UPPER_CONSTRAINTS_FILE but I have not tried if that works or not. If not, moving your CI to Bionic is the way forward. I am trying a new approach to cap the constraint in tox.ini itself whenever a new Tempest version is released. That can avoid hacking the same via UPPER_CONSTRAINTS_FILE. For example, Tempest 24.0.0 tag's tox.ini use stable/ussuri constraint. 2. Bug#1876330. devstack-plugin-ceph-tempest-py3 failing for rescue BFV instance test New tests added for rescue BFV instance feature on Nova failed on ceph job. lyarwood is working on the bug but for now, we have taken the step forward to skip the tests for ceph. Any new tests which do not work on ceph, we need to add the tests in ceph blacklist file until the bug is fixed. Job is green now. if it was failing on your gate where it is running as voting, please recheck. - https://review.opendev.org/#/c/724866/ I have also proposed to make ceph job as voting on the Tempest side (it was n-v till now) so that we can take these steps well before merging the new tests on the Tempest gate. - https://review.opendev.org/#/c/724948/1 -gmann

1 0

[all] A call for consolidation and simplification
by Thierry Carrez 01 May '20

01 May '20

Hi all, I'd like to issue a call for consolidation and simplification for OpenStack development. In the early years of the project, we faced a lot of challenges. We had to spread the development load across manageable-size groups, so we encouraged the creation of a lot of project teams. We wanted to capture all the energy that was sent towards the project, so we passed project structure reforms (like the big tent) that would aggressively include new community groups in the "official" OpenStack community. We needed to remove bottlenecks, so we encouraged decentralized decision making. And we had to answer unique challenges, so we created software to match them (Zuul). In summary, we had a lot of people, and not enough systems to organize them, so we created those. Fast-forward to 2020, and our challenges are different. The many systems that we created in the early days have created silos, with very small groups of people working in isolation, making cross-project work more difficult than it should be. The many systems that we created generate a lot of fragmentation. Like we have too many meetings (76, in case you were wondering), too much energy spent running them, too much frustration when nobody joins. Finally, the many systems that we created represent a lot of complexity for newcomers to handle. We have 180 IRC channels, most of them ghost towns where by the time someone answers, the person asking the question is long gone. So I think it's time to generally think about simplifying and consolidating things. It's not as easy as it sounds. Our successful decentralization efforts make it difficult to make the centralized decision to regroup. It's hard to justify time and energy spent to /remove/ things, especially those that we spent time creating in the first place. But we now have too many systems and not enough people, so we need to consolidate and simplify. Back around Havana, when we had around the same number of active contributors as today, we used to have 36 meetings and 20 teams. Do we really need 180 IRC channels, 76 meetings, 63 project teams (not even counting SIGs)? Yes, we all specialized over time, so it's hard to merge for example Oslo + Requirements, or QA + Infrastructure, or Stable + Release Management, or Monasca + Telemetry. We are all overextended so it's hard to learn new tricks or codebases. And yet, while I'm not really sure what the best approach is, I think it's necessary. Comments, thoughts? -- Thierry Carrez (ttx)

9 16