March 2022 - openstack-discuss - lists.openstack.org

[puppet] Proposing Alan Bishop (abishop) for puppet-manila core
by Takashi Kajinami 18 Mar '22

18 Mar '22

Hi Team, Alan is currently a partial core reviewer in Puppet OpenStack and covers puppet-cinder and puppet-glance. He has made great reviews in these two modules since he joined the team, but in addition, he has been reviewing patches for puppet-manila and providing good feedback for the past two cycle. https://www.stackalytics.io/?user_id=alan-bishop Based on that fact, I'd like to propose extending his coverage and adding Alan to the puppet-manila core reviewers. If you have any feedback please share it in this thread. I'll add him to the group if we don't hear any objections for 1 week. I'd like to take this moment to thank Alan for his great work and help in this project ! Thank you, Takashi KAJINAMI

3 3

Re: L3 agent issues
by Slawek Kaplonski 18 Mar '22

18 Mar '22

Hi, On piątek, 18 marca 2022 09:22:03 CET Wada Akor wrote: > Thanks Slawek > I just had feeling it is a bug or something has to with my hardware HP > proliant gen 7 might affect the performance of the L3 Agent. Bug where? In Neutron? I don't think so as Neutron is not deployment tool. I don't know exactly what tool are You using to deploy OpenStack but if there is any bug, You should look there. > > > On Fri, Mar 18, 2022 at 7:57 AM Slawek Kaplonski <skaplons(a)redhat.com> > wrote: > > > Hi, > > > > On czwartek, 17 marca 2022 22:19:22 CET Wada Akor wrote: > > > > > Good to all the openstack community, > > > > > Base on the above subject i was deploying openstack for a proof of > > concept > > > > > (POC) at the university of Jos ,Plateau State Nigeria . > > > > > > > > > > after deploying the neutron on the controller and compute node > > > > > then I ran the command # *openstack network agent list* > > > > > command output # is only 3 agent on the list as follow linuxbridge agent > > > > > ,metadata agent ,DHCP agent no l3 agent on the list > > > > > > > > > > 2) No log file for l3 agent at */var/log/neutron/**neuton*- linuxbridge > > > > > agent ,metadata agent ,DHCP agent on log no l3 agent . > > > > > > > > > > My deployment hardware is HP gen 7 for the POC > > > > > > > > > > please i need the community support > > > > > > > > > > thanks > > > > > > > > > > Wada k Jeremiah > > > > > > > > > L3 agent isn't something what is deployed automatically. You can deploy it > > on any node - sometimes You may want dedicated networking node with L3 > > agent for example. > > > > Please check our documentation [1] for more details. > > > > [1] https://docs.openstack.org/neutron/latest/install/index.html > > > > -- > > > > Slawek Kaplonski > > > > Principal Software Engineer > > > > Red Hat > > > -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

L3 agent issues
by Wada Akor 17 Mar '22

17 Mar '22

Good to all the openstack community, Base on the above subject i was deploying openstack for a proof of concept (POC) at the university of Jos ,Plateau State Nigeria . after deploying the neutron on the controller and compute node then I ran the command # *openstack network agent list* command output # is only 3 agent on the list as follow linuxbridge agent ,metadata agent ,DHCP agent no l3 agent on the list 2) No log file for l3 agent at */var/log/neutron/**neuton*- linuxbridge agent ,metadata agent ,DHCP agent on log no l3 agent . My deployment hardware is HP gen 7 for the POC please i need the community support thanks Wada k Jeremiah

3 2

are Gpu's needed to get fast openstack instances with GUI
by A Monster 17 Mar '22

17 Mar '22

I've deployed an openstack cloud using kolla-ansible, but the vm instances which has gui are very slow, do I need GPUs in order to get fast instances ?

2 1

[neutron] Drivers meeting agenda - 18.03.2022.
by Lajos Katona 17 Mar '22

17 Mar '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * Recheck gratuitous ARPs are not sent during master transition: ( https://bugs.launchpad.net/neutron/+bug/1952907) ** For this one there are a few wip patches: ** https://review.opendev.org/c/openstack/neutron/+/821434 ** https://review.opendev.org/c/openstack/neutron/+/821433 ** https://review.opendev.org/c/openstack/neutron/+/712474 * [QoS][OvS] implement QoS bandwidth limitation by leveraging ovs meter (#link https://bugs.launchpad.net/neutron/+bug/1964342 ) * DHCP agent scheduler filtering ignored when agent service restarted (#link https://bugs.launchpad.net/neutron/+bug/1964765 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[blazar][release][requirements] blazar-nova and nova requirements
by Pierre Riteau 17 Mar '22

17 Mar '22

Hello release team, blazar-nova is a package including a nova scheduler filter, which must be installed together with nova to be used. The blazar-nova deliverable for Yoga was tagged with 2.4.0 at the time of the final release for non-client libraries. A few days ago, stable/yoga patches were automatically proposed. This is when I discovered that the lower-constraints job was broken because nova bumped some requirements / lower-constraints after we released [1] [2]. Because blazar-nova and nova are installed together, we keep our requirements in sync for testing purposes. Now, I believe it is just the lower-constraints testing that is broken, since nova requirements are still compatible with what blazar-nova requires: nova just requires more recent versions of some packages. I can run "pip install blazar-nova git+ https://opendev.org/openstack/nova.git@master#egg=nova" fine. I fixed the issue on the blazar-nova master branch [3] and proposed a backport to stable/yoga [4], but realised this was probably breaking release policy. Should we leave stable/yoga as released and just drop the lower-constraints job? As an aside, would it be possible to requalify blazar-nova as a cycle-with-rc deliverable for the next release? It is typed as a library but nothing depends on it: if anything, it depends on nova itself. Thanks, Pierre Riteau (priteau) [1] https://review.opendev.org/c/openstack/nova/+/712139 [2] https://review.opendev.org/c/openstack/nova/+/821606 [3] https://review.opendev.org/c/openstack/blazar-nova/+/831741 [4] https://review.opendev.org/c/openstack/blazar-nova/+/831832

3 4

[all][tc] Technical Committee next weekly meeting on Mar 17th at 1500 UTC
by Ghanshyam Mann 16 Mar '22

16 Mar '22

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Mar 17th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Mar 16th, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[largescale-sig] Next meeting: Mar 16th, 15utc
by Thierry Carrez 16 Mar '22

16 Mar '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. Note that this means the meeting is one hour later than usual for people based in the US! You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220316T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[heat][rbac] Management of "system resources" with SRBAC enforced
by Takashi Kajinami 16 Mar '22

16 Mar '22

Hello, I've been working on updating policy rules in heat according to the latest guideline for SRBAC implementation. Based on the recent direction change[1], now only project users are allowed to create project-based resources like instances or networks. I'm updating policy rules in heat so that only project users can manage project resources in Heat like stacks or resources. [1] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… However this change reveals one potential issue with system resources. In heat there are some resource types like OS::Nova::Flavor or OS::Keystone::User which is allowed for only system users. (I'll call these resources as "system resources" here) Because heat uses user credentials to create resources in backend services, if we require project scope for stack/resource management then we are no longer able to create these system resources as part of stack. (*1) There are some options I can think of at this moment. 1. Deprecate and remove all resources which require system scope Pros - This is most easy solution to be implemented Cons - This one has the biggest user impact 2. Use service credential for resource creation Pros: - This might have smallest user impact Cons: - This requires a relatively big change in heat's architecture, which I've not yet evaluated. - We need to determine the project scope role to be allowed to do system operation. 3. Implement additional project-role in each service to allow creation via stack creation. Pros: - This would avoid user impact. Cons: - requires work in multiple components. - We need to determine the project scope role to be allowed to do system operation. I'm not quite sure which one would be the best. If I can ask for some feedback about these options (or any other new options) from heat's perspective and rbac's perspective then it would be nice. (*1) As of now, nova and neutron no longer allow creating system users to create project resources, so system users are no longer able to create stacks with project resources like instances or networks with default "new" policies. Thank you, Takashi

3 9

[announce][debian] OpenStack Yoga preview Debian packages are ready
by Thomas Goirand 16 Mar '22

16 Mar '22

Hi, Today, my first Yoga VM pings. I haven't done the Tempest/refstack work yet, but it's ongoing. In the mean time, anyone can already try and use the packages as a preview for the Yoga release. They are available through extrepo as usual, or from the osbpo.debian.net repo directly: apt-get install extrepo extrepo enable openstack_yoga apt-get update I'll make a proper announcement once we pass all Refstack tests. Note this is a record-breaking availability, as the RCs were published only at the end of last week. So thanks everyone for this very smooth release. Also to be noted: a few packages are missing, due to unit test failures: magnum, murano, trove, sahara and zaqar. Many of these unit tests fall in the debtcollector that wines about "tenant" not "projects". I'll investigate these later on, but they seem of no real consequence, so I may just skip them. See you in Berlin! Cheers, Thomas Goirand (zigo)

1 0

[cinder] festival of XS reviews 18 March 2022
by Brian Rosmaita 16 Mar '22

16 Mar '22

Hello Argonauts, Just in case there's anyone out there who has not used the handy ICS file [0] to have this event on their personal calendars: The most recent edition of the Cinder Festival of XS Reviews will be held on this coming Friday (18 March). who: Everyone! what: The Cinder Festival of XS Reviews when: Friday 18 March 2022 from 1400-1600 UTC where: https://meetpad.opendev.org/cinder-festival-of-reviews etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews See you there! brian [0] http://eavesdrop.openstack.org/calendars/cinder-festival-of-reviews.ics

1 0

[kolla] Using variable in ceph confs
by Imran Hussain 16 Mar '22

16 Mar '22

Hi All, I'm storing my kolla conf in git and I want to avoid committing secrets. As per the subject I'm using an external ceph. I've created a patchset for this to be possible https://review.opendev.org/c/openstack/kolla-ansible/+/824566 Jens replied to it pretty fast but beyond saying 'I don't understand why you would want to do this' (paraphrased) gave no feedback. I recently got some feedback from Michal after asking on IRC about it which was very helpful. But this doesn't seem to be going anywhere, any advice on next steps? Even if the feedback is 'no we don't want this' anything would be nice. Thanks, Imran

1 0

[dev] [trove] Bug fixed from master to stable branch and release?
by Hirotaka Wakabayashi 16 Mar '22

16 Mar '22

Hello, I am a Trove contributor. I proposed a cherry-pick and lxkong kindly merged it yesterday! Could someone release the new version as 13.0.1? Because I believe this bug is significant for users for some reasons. 1. I hit this bug :P 2. One relevant Issue from IRC https://meetings.opendev.org/irclogs/%23openstack-trove/%23openstack-trove.… 3. One relevant issue from https://storyboard.openstack.org/#!/story/2006996 This patch is cherry-picked from master branch and I think this patch has no risk of regression. Thanks in advance, Hirotaka

1 0

[PTG] April 2022 Teams List
by Kendall Nelson 15 Mar '22

15 Mar '22

Hello Everyone! The April 2022 Project Teams List is official! Ansible OpenStack modules Barbican Blazar Cinder CloudKitty Cyborg Designate Diversity & Inclusion WG First Contact SIG Glance Horizon Interop Ironic Keystone Kolla Kuryr Large Scale SIG Manila Neutron Nova/Placement Octavia OpenInfra Edge Computing Group OpenStack Charms OpenStack Technical Committee OpenStack-Ansible OpenStack-Helm QA Release Management SDK Security SIG StarlingX Swift Tacker TripleO If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Otherwise, please don't forget to register[1] because that's how you'll receive event details, passwords, and other relevant information about the PTG. Please let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTG Registration: https://openinfra-ptg.eventbrite.com

2 2

[openstack][keystone] Stepping down from core
by Gage Hugo 15 Mar '22

15 Mar '22

After some consideration and my focus shifting to other priorities, I cannot reliably devote enough time to keystone so I'll be stepping down from keystone core. I greatly appreciate the experiences I had to learn and grow thanks to everyone's help. Thanks to you all and I'm grateful for the opportunities I've had with the project and openstack as a whole. Hopefully we will get to collaborate again more in the future. Gage Hugo

2 2

[tc][release] Removing TC tags framework - next steps for release notes
by Radosław Piliszek 15 Mar '22

15 Mar '22

Hello Release Team, As you might have heard, the TC is removing the TC tags framework. [1] The first step has already been proposed and is being voted on. [2] The removal of certain parts seems to be affecting the release team tooling, especially with the usage of the stable:follows-policy tag to show a relevant banner. [3] The proposed change purposely avoids breaking the releases repo and awaits a "part 2" which cleans up everything TC-tags-framework-related. Thus, I am asking for your help to remove this dependency on the tags framework. I understand there might be several approaches to this and need your assistance to continue. The simplest approach is to drop the relevant code - assuming it is not actively used for release process purposes. Obviously, for anything else I need your input on what the options are. It is also possible that you would prefer to port this tag to your internal metadata. I am open to ideas and will help enact the changes. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025554.… [2] https://review.opendev.org/c/openstack/governance/+/822900 [3] https://opendev.org/openstack/releases/src/commit/768a12e233c23999db18c807c… Kind regards, -yoctozepto

3 4

[release] Independent release jobs are still using old release job templates
by Stephen Finucane 15 Mar '22

15 Mar '22

tl;dr: How do we get projects using the independent release process to use the openstack-python3 zuul job template corresponding to the latest release? I've noticed a couple of patches like [1] popping up for oslo-affiliated projects. These projects are currently using the python3 zuul job templates corresponding to an older release (e.g. Wallaby) and the author is correctly updating them to use the most recent release. These initially caught me off-guard since I'm used to seeing a bot propose these changes but I've realized that all affected projects are using the "independent" release process and therefore don't receive a new stable branch nor related bot-proposed commits. This leaves us in a bit of a pickle though. There are a lot of projects using this release process, and there's effectively zero chance that someone is going to remember to bump the jobs every single release. While some could argue that this is "working as designed", it seems important to me that we would be testing these projects against the supported runtimes for the release currently under development. As such, how should we try to address this? One option I see is to add a new generic 'openstack-python3-jobs' template which would always duplicate the jobs used for the current release. I've proposed that here [2]. There are some pros and cons to this approach: * PRO: Minimal effort from everyone. * CON: The HEAD of master for each project could be broken and we'd never know until some change was proposed to master (note: this is effectively the status quo right now, so it's not a big break) * CON: If those independent projects had an alternative to stable branches (i.e. semver branches), those would eventually break as the runtimes kept changing. The other option is to extend the openstack bot to propose release bump patches against these independent projects. This has the inverse pro/con balance: * PRO: We get a regular "check-up" on the health of the project whenever these patches are proposed. * PRO: Long-lived stable branches should stay working * CON: Lots of busy work for reviewers. What are everyone's thoughts? I'm in favour of the first approach (generic 'openstack-python3-jobs' template) but the bot enhancement would also wfm. If we go with the first approach, we'd probably want to script something to "fix" all the existing independent projects rather than attempt to find and fix them manually. Cheers, Stephen PS: Apologies if this has been discussed previously. I clearly missed that discussion. [1] https://review.opendev.org/c/openstack/os-api-ref/+/831560 [2] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833286

4 7

[infra] gerrit is:mergeable predicate
by Brian Rosmaita 15 Mar '22

15 Mar '22

Hello Infra team, In Gerrit 3.4, the is:mergeable predicate is disabled by default [0]. It was kind of handy to be able to screen out patches that are in merge conflict when looking for reviews. Is there an alternative way of doing this, or would you be averse to restoring the previous behavior? (I promise not to complain about gerrit performance.) cheers, brian [0] https://www.gerritcodereview.com/3.4.html#ismergeable-predicate-is-disabled…

2 3

[neutron] bug deputy report (Mar 7 - 13)
by Akihiro Motoki 15 Mar '22

15 Mar '22

Hi, Here is a bug deputy report last week. It was a quiet week too. = Needs attention - https://bugs.launchpad.net/neutron/+bug/1964339 [OVN Octavia Provider] OVN provider tests using too old version of OVN it looks like local.conf in ovn-octavia-provider-functional-release is not configured properly, so the bug reported here looks valid. Hopefully ovn-octavia-provider folks can look into it. = Gate Failures - https://bugs.launchpad.net/neutron/+bug/1963899 Rebuild server - notification about port UP isn't sent to nova properly Confirmed, Unassigned - https://bugs.launchpad.net/neutron/+bug/1964313 Functional tests fails due to missing namespace Confirmed, Unassigned = Assigned - https://bugs.launchpad.net/neutron/+bug/1964817 [ovn-octavia-provider] Deleted members remain in ERROR status = RFE - https://bugs.launchpad.net/neutron/+bug/1964765 DHCP agent scheduler filtering ignored when agent service restarted - https://bugs.launchpad.net/neutron/+bug/1964342 [QoS][OvS] implement QoS bandwidth limitation by leveraging ovs meter Thanks, Akihiro Motoki (amotoki)

1 0

Re: [release] Independent release jobs are still using old release job templates
by Stephen Finucane 15 Mar '22

15 Mar '22

On Fri, 2022-03-11 at 17:13 +0100, Előd Illés wrote: > Thanks for bringing this up Stephen! I am not aware of such discussions, > though i might missed it only. > > So this is about projects with 'independent release model' and their CI > jobs. I think it's a valid question and we should solve this somehow. > > I could also imagine a new task in our release process / schedule, when the > release team generates the new patches via some new scripts (which is > somewhat identical to your second option). This has the risk though that these > kind of patches just linger around without anyone reviewing / fixing / merging them > (similarly like the .gitreview and TOX_CONSTRAINTS_FILE patches, which > should be merged as soon as possible, but in lots of projects they just remain > there open forever, causing errors time to time). Considering this, maybe the 2nd > option is better but what you wrote as CON regarding special (ie. semver) > stable branches could be really problematic (I don't know actually, so > we need to ask for opinions from those projects that have such stable branches > in their projects with independent release model). I've thought about this more, and I don't think the issue with the special stable branches is actually a big issue. Firstly, I've no evidence that such things even exist so it's likely a purely theoretical issue at this point. However, assuming these branches _do_ exist, they would have to be created manually. There's no reason that the '.zuul.yaml' file couldn't be modified after this was done to use the job template from the current release (i.e. 'openstack-python3-zed-jobs'), ensuring things would age gracefully. If we have "how to request manual stable branch creation" docs somewhere, then we could simply note this there. I think the unversioned job is definitely the way to go now. I just need another approver for [1] to move forward with it. Stephen [1] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833286 > > Thanks, > > Előd > > On 2022. 03. 11. 13:26, Stephen Finucane wrote: > > tl;dr: How do we get projects using the independent release process to use the > > openstack-python3 zuul job template corresponding to the latest release? I've > > noticed a couple of patches like [1] popping up for oslo-affiliated projects. > > These projects are currently using the python3 zuul job templates corresponding > > to an older release (e.g. Wallaby) and the author is correctly updating them to > > use the most recent release. These initially caught me off-guard since I'm used > > to seeing a bot propose these changes but I've realized that all affected > > projects are using the "independent" release process and therefore don't receive > > a new stable branch nor related bot-proposed commits. This leaves us in a bit of > > a pickle though. There are a lot of projects using this release process, and > > there's effectively zero chance that someone is going to remember to bump the > > jobs every single release. > > > > While some could argue that this is "working as designed", it seems important to > > me that we would be testing these projects against the supported runtimes for > > the release currently under development. As such, how should we try to address > > this? One option I see is to add a new generic 'openstack-python3-jobs' template > > which would always duplicate the jobs used for the current release. I've > > proposed that here [2]. There are some pros and cons to this approach: > > > > * PRO: Minimal effort from everyone. > > * CON: The HEAD of master for each project could be broken and we'd never know > > until some change was proposed to master (note: this is effectively the > > status quo right now, so it's not a big break) > > * CON: If those independent projects had an alternative to stable branches > > (i.e. semver branches), those would eventually break as the runtimes kept > > changing. > > > > The other option is to extend the openstack bot to propose release bump patches > > against these independent projects. This has the inverse pro/con balance: > > > > * PRO: We get a regular "check-up" on the health of the project whenever these > > patches are proposed. > > * PRO: Long-lived stable branches should stay working > > * CON: Lots of busy work for reviewers. > > > > What are everyone's thoughts? I'm in favour of the first approach (generic > > 'openstack-python3-jobs' template) but the bot enhancement would also wfm. If we > > go with the first approach, we'd probably want to script something to "fix" all > > the existing independent projects rather than attempt to find and fix them > > manually. > > > > Cheers, > > Stephen > > > > PS: Apologies if this has been discussed previously. I clearly missed that > > discussion. > > > > [1] https://review.opendev.org/c/openstack/os-api-ref/+/831560 > > [2] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833286 > > > >

1 0

[VICTORIA] Not working SNAT over VXLAN?
by Gaël THEROND 15 Mar '22

15 Mar '22

Hi everyone! I’m facing a weird situation on a tenant of one of our Openstack cluster based on Victoria. On this tenant, the network topology is as follow: One DMZ network (192.168.0.0/24) linked to our public network through a neutron router where there is a VM acting as a bastion/router for the MGMT network. One MGMT network (172.16.31.0/24) where all VMs are linked to. On the DMZ network, there is a linux Debian 11, let’s call it VM-A with a Floating IP from the public pool, this VM is both attached to the DMZ network (ens3 / 192.168.0.12) AND the MGMT network (ens4 / 172.16.31.23). All other VMs, let’s call them VM-X are exclusively attached to the MGMT network (ens4). I’ve setup VM-A with ip_forward kernel module and the following iptables rule: # iptables -t nat -A POSTROUTING -o ens3 -J SNAT —to-source 192.168.0.12 My VM-X are on their own setup with a default gateway via VM-A: # ip route add default via 172.31.16.23 The setup seems to be working as if I don’t put the iptables rule and the kernel forwarding I can’t see any packets on my DMZ interface (ens3) on VM-A from VM-X. Ok so now that you get the whole schema, let dive into the issue. So when all rules, modules and gateway are set, I can fully see my VM-X traffic (ICMP ping to a dns server) going from VM-X (ens4) to VM-A (ens4) then forwarded to VM-A (ens3) and finally going to our public IP targeted service. What’s not working however is the response not reaching back to VM-X. I’ve tcpdump the whole traffic from VM-X to VM-A on each point of the platfrom: from inside the VM-X nic, on the tap device, on the qbr bridge, on the qvb veth, on the qvo second side of the veth through the ovs bridges and vice-versa. However the response packets aren’t reaching back further than on the VM-A qvo veth. Once it exit the VM-A the traffic never reaches the VM-X. What’s really suspicious in here is that a direct ping from VM-X (172.16.31.54) to VM-A (172.16.31.23) is coming back correctly, so it looks like if ovs detected that the response on a SNAT case isn’t legit or something similar. Is anyone able to get such setup working? Here are few additional information: Host runs on CentOS 8.5 latest update. Our platform is a Openstack Victoria deployed using kolla-ansible. We are using a OVS based deployment. Our tunnels are VXLAN. All VMs have a fully open secgroup applied and all ports have it (I checked it twice and even on host iptables). If you ever need additional information feel free to let me know !

2 10

[dev][trove] Self-introduction and request to merge PRs
by Hirotaka Wakabayashi 14 Mar '22

14 Mar '22

Hello, I am Hirotaka Wakabayashi from Tokyo. This is my first post to openstack-discuss. My goal in OpenStack Project is to learn the OpenStack Infrastructures anddevelop them together and to enlarge the community in Japan if I could. I am a software engineer. In this 10 years, I have been a backend developer in Yahoo Japan Corporation. I have been using FreeBSD, Fedora-based Linux Distros. I mostly use C/C++ and sometime use python recently. I am a Trove contributor from two years ago and I submitted the following PRs last week, but does anybody kindly merge them? I think they are verysmall code changes and easy to understand, but the #832786 and #833497are very important to make Trove on master branch work correctly. https://review.opendev.org/c/openstack/trove/+/832786 https://review.opendev.org/c/openstack/trove-dashboard/+/833497 https://review.opendev.org/c/openstack/trove/+/833361 https://review.opendev.org/c/openstack/trove/+/833501 I asked to merge them in #openstack-trove yesterday, but I got no response. So I posted this email here. Any questions are welcome! Thanks in advance, Hirotaka Wakabayashi GPG Key UID: "Hirotaka Wakabayashi <hiwkby(a)yahoo.com>" GPG fingerprint: "3F54 9D91 A73A 1F31 8CA8 8A9F 050F 5312 F0D7 DBCD"

1 0

VM instances too slow
by A Monster 14 Mar '22

14 Mar '22

After deploying openstack using Kolla ansible, the vm instances are too slow I'm using one node as controller and two nodes for compute Nodes have 64GB ram and two intel xeon e5 2660 CPUs.

4 3

Forum Brainstorming & Committee Setup
by Kendall Nelson 14 Mar '22

14 Mar '22

Hello Everyone! As the OpenInfra Summit approaches, so does the Forum! We would love 1 volunteer from the community for the Forum Selection Committee. Ideally, the volunteer would already be serving in some capacity in a governance role for your project. Please reach out to knelson(a)openinfra.dev if you're interested. Volunteers should respond on or before April 8, 2022. In addition to calling for volunteers for the Forum selection committee, this email kicks off the brainstorming period before the CFP tool opens for formal Forum submissions. The categories for brainstorming etherpads have already been setup here[1]. Please add your etherpads and ideas there! The CFP tool will open on March 21st and will close April 8th. For information on the upcoming Summit[2]. For more information on the Forum[3]. Thanks! - Kendall Nelson (diablo_rojo) [1] Forum 2022 Wiki: https://wiki.openstack.org/wiki/Forum/Berlin2022 [2] OpenInfra Summit Site: https://openinfra.dev/summit [3] General Forum Wiki: https://wiki.openstack.org/wiki/Forum

1 0

[charms] Can we update the Python runtimes for the 'openstack-python3-charms-jobs' template?
by Stephen Finucane 14 Mar '22

14 Mar '22

Related to the "Independent release jobs are still using old release job templates" email I just sent [1], I've proposed a change [2] that would modify the 'openstack-python3-charms-jobs' job template so that it mimics the behaviour of the proposed 'openstack-python3-jobs' template. That is, the 'openstack- python3-charms-jobs' release will now be updated at the start of each new release to test against the same runtimes proposed for this new release. However, frickler has noted that the use of older runtimes for the charms jobs may in fact be intentional. Could someone from the charms team please weigh in on [2]. If this is in fact intentional, it would be good to add a note to the job template indicating this fact to prevent people like me breaking it in the future :) Cheers, Stephen [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027676.ht… [2] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/833330/1

2 1

Opensearch service reinstallation - opensearch.logs.openstack.org
by Daniel Pawlik 14 Mar '22

14 Mar '22

Hi, We plan to reinstall the Opensearch (opensearch.logs.openstack.org) service on Saturday, 2021-03-12. The service will be unavailable for several hours. If someone has any concerns, please contact me. Regards, Dan

1 1

virt-v2v conversion error
by KK CHN 14 Mar '22

14 Mar '22

Hi , I am performing a migration of Windows 10 VM running on HyperV to OpenStack setup with Ussuri(qemu KVM) on Debian 10 nodes. I got the Windows VM exported disks as disk1.VHDX and disk2.avhdx files from my WIndows cloud Vendor. 1. As my understanding I need to convert these VM disks from HyperV using virt-v2v tool. ( Could someone explain what is the relevance of this step and is it mandatory for importing it to my Ussuri Openstack cloud which uses qemu-kvm hypervisor. 2. As I've read I tried to convert this disk1.VHDX file with the follwoing step #virt-v2v -i disk disk1.VHDX -o local -os /home/cloud this step fails with virt-v2v error : // Files system was mounted read only . even though we sked for it to be mounted read-write. This usually means that file system was not cleanly unmounted. Possible causes include trying to convert a guest which is running. or use Windows hibernation or Fast Restart . Original error message touch: open /8imepyi7: Read only file system ... Can anyone guide what causes this error and Is there a fix or work around available to solve this error in vrit-v2v conversion ? Thanks in advance krish

1 0

nvidia gpu
by Vikarna Tathe 12 Mar '22

12 Mar '22

Hello All, Can somebody help me with the procedure for GPU integration with openstack wallaby, Ubuntu 20.04. Below are the card details: da:00.0 VGA compatible controller: NVIDIA Corporation TU102GL [Quadro RTX 6000/8000] Vikarna

2 2

[all][tc] What's happening in Technical Committee: summary Mar 11th, 21: Reading: 10 min
by Ghanshyam Mann 11 Mar '22

11 Mar '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Mar 10th. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-03-10-15.00.log.html * Next week's meeting is on Mar 17th Thursday 15:00 UTC, feel free to add the topic on the agenda[1] by Mar 16th. Please note about the daylight time shift in US TZ happening this Sunday. 2. What we completed this week: ========================= * Release identification and release name ----------------------------------------------- Release naming/identification new proposal is merged[2]. Currently, it is adding the number in <year>.<1st or 2nd release of that year> format along with the release name. Please check the release naming process page for complete detail[3] * Add sushy-oem-idrac as Hardware Vendor SIG owned[4] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[5]. 3 out of 9 items are completed and many are in progress. Open Reviews ----------------- * Six open reviews for ongoing activities[6]. Direction on running FIPs goal/jobs ------------------------------------------ As you might have seen the FIPs work from Ade_lee and adding FIPs jobs in the check/gate pipeline which is not stable at this stage. We in TC meeting along with Ade_lee discussed the direction on making jobs stable and until then how we want to run jobs so that we do not overload infra resources with a lot of non-voting/unstable jobs. We agreed to run those as periodic (and experimental to trigger them manually) to make/check their stability [7]. Based on the job run data, in PTG we will discuss further on adding them as voting and selecting it as a goal. Zed cycle Leaderless projects ---------------------------------- We have 14 PTL assignments merged and 2 are in progress(Trove and Zaqar) [8]. With that only one project left to assign a leader (Adjutant) and we will wait until the end of March for Braden to get permission to maintain it[9]. PTG Preparation -------------------- TC slots are selected for coming PTG[10], please continue adding the topics in etherpad[11]. * Monday 14 - 16 UTC (TC + PTL for 2 hrs ) * Thursday 13-17 UTC (TC discussion for 4 hrs) * Friday 13-17 UTC (TC discussion for 4 hrs ) Dropping tags framework ------------------------------ part1 of this is merged[12], part-2 of updating release script and other tags migration is under-progress. TC position on release cadence ------------------------------------- Dan has sent the overview and things changed as per the new release model [13]. The next plan is: * Dan will explain/discuss it further in TC+PTL sessions on Monday [14]. * Projects can discuss it (from their project point of view) in their PTG sessions and collect the queries if any. * Join TC sessions on Thursday/Friday (I will schedule and update the exact time slot) to discuss those queries or plan the remaining work. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[15]. Project updates ------------------- * None for this week. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/829563 [3] https://governance.openstack.org/tc/reference/release-naming.html [4] https://review.opendev.org/c/openstack/governance/+/832264 [5] https://etherpad.opendev.org/p/tc-yoga-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://meetings.opendev.org/meetings/tc/2022/tc.2022-03-10-15.00.log.html#… [8] https://etherpad.opendev.org/p/zed-leaderless [9] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027626.ht… [10] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027584.ht… [11] https://etherpad.opendev.org/p/tc-zed-ptg [12] https://review.opendev.org/c/openstack/governance/+/822900 [13] http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027639.ht… [14] https://etherpad.opendev.org/p/tc-ptl-interaction-zed [15] https://etherpad.opendev.org/p/zuul-config-error-openstack [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-2, Mar 14 - 18
by Előd Illés 11 Mar '22

11 Mar '22

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the Yoga deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/yoga branch creation for all deliverables that have not branched yet, using the latest available Yoga release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/yoga branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/yoga branch before releasing out of the stable/yoga branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for Zed development, though the focus should still be on finishing up Yoga until the final release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final Yoga release. Finally, now is a good time to finalize release notes, if it is not done yet. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the Yoga version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: March 24th, 2022 (R-1 week) Final Yoga release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

3 2

[TripleO] Upgrade overcloud Nodes with Puppet Pacemaker Issue on Controller-0
by Anirudh Gupta 11 Mar '22

11 Mar '22

Hi Team I have deployed TripleO Train Undercloud and Overcloud in HA Mode. After which I Upgraded TripleO Undercloud to Ussuri Release. While upgrading the Overcloud Nodes, there were some minor hiccups initially, but after enabling internet and enabling Centos repositories, we resolved all the issues. After executing openstack overcloud upgrade run command for only the controllers, we get some puppet issues for pacemaker service for Controller-0 (Active DC) The same check passed for Controller-1 and Controller-2. All the overcloud nodes have been spawned with the same image, so there must not be any issue. Attaching the logs below: 2022-03-09 15:22:02.510128 | 525400f8-4aa7-5981-5af0-000000006a82 | TASK | Gather podman infos 2022-03-09 15:22:02.869577 | 525400f8-4aa7-5981-5af0-000000006a0f | CHANGED | Enable and start netns-placeholder | overcloud-controller-1 2022-03-09 15:22:02.873413 | 525400f8-4aa7-5981-5af0-000000006a0f | TIMING | tripleo_container_manage : Enable and start netns-placeholder | overcloud-controller-1 | 0:14:39.816795 | 0.97s 2022-03-09 15:22:02.901485 | 525400f8-4aa7-5981-5af0-000000006940 | TASK | Update container configs with new config hashes 2022-03-09 15:22:02.943620 | 525400f8-4aa7-5981-5af0-000000006940 | TIMING | tripleo_container_manage : Update container configs with new config hashes | overcloud-controller-1 | 0:14:39.887003 | 0.04s 2022-03-09 15:22:02.960739 | 1fecaf23-8a62-488a-87ab-a2ee3c307ae5 | INCLUDED | /usr/share/ansible/roles/tripleo_container_manage/tasks/puppet_config.yml | overcloud-controller-1 2022-03-09 15:22:02.988374 | 525400f8-4aa7-5981-5af0-000000006ab5 | TASK | Update config hashes for container startup configs 2022-03-09 15:22:03.380251 | 525400f8-4aa7-5981-5af0-000000006ab5 | OK | Update config hashes for container startup configs | overcloud-controller-1 2022-03-09 15:22:03.381768 | 525400f8-4aa7-5981-5af0-000000006ab5 | TIMING | tripleo_container_manage : Update config hashes for container startup configs | overcloud-controller-1 | 0:14:40.325159 | 0.39s 2022-03-09 15:22:03.409190 | 525400f8-4aa7-5981-5af0-000000006941 | TASK | Delete orphan containers from /var/lib/tripleo-config/container-startup-config/step_3 2022-03-09 15:22:03.453834 | 525400f8-4aa7-5981-5af0-000000006941 | TIMING | tripleo_container_manage : Delete orphan containers from /var/lib/tripleo-config/container-startup-config/step_3 | overcloud-controller-1 | 0:14:40.397197 | 0.04s 2022-03-09 15:22:03.470413 | 8e8040a9-b1ed-498c-becb-4a25381f487f | INCLUDED | /usr/share/ansible/roles/tripleo_container_manage/tasks/delete_orphan.yml | overcloud-controller-1 2022-03-09 15:22:03.498978 | 525400f8-4aa7-5981-5af0-000000006ad8 | TASK | Gather podman infos instead.\nTraceback (most recent call last):\n File \"/usr/lib/python3.6/site-packages/pcs/resource.py\", line 1039, in resource_update\n resource.getAttribute(\"type\"),\n File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/facade.py\", line 200, in facade_from_parsed_name\n parse_metadata(name, load_metadata(self._runner, name))\n File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/xml.py\", line 114, in load_metadata\n return _metadata_xml_to_dom(_load_metadata_xml(runner, agent_name))\n File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/xml.py\", line 52, in _load_metadata_xml\n raise UnableToGetAgentMetadata(agent_name.full_name, stderr.strip())\npcs.lib.resource_agent.error.UnableToGetAgentMetadata\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"/sbin/pcs\", line 11, in <module>\n load_entry_point('pcs===0.10.11.22-9d83b', 'console_scripts', 'pcs')()\n File \"/usr/lib/python3.6/site-packages/pcs/app.py\", line 278, in main\n utils.get_library_wrapper(), argv, utils.get_input_modifiers()\n File \"/usr/lib/python3.6/site-packages/pcs/cli/common/routing.py\", line 33, in _router\n return cmd_map[sub_cmd](lib, argv_next, modifiers)\n File \"/usr/lib/python3.6/site-packages/pcs/cli/common/routing.py\", line 33, in _router\n return cmd_map[sub_cmd](lib, argv_next, modifiers)\n File \"/usr/lib/python3.6/site-packages/pcs/resource.py\", line 1058, in resource_update\n [lib_ra.resource_agent_error_to_report_item(e, severity)]\n File \"/usr/lib/python3.6/site-packages/pcs/cli/reports/output.py\", line 38, in process_library_reports\n report_dto = report_item.to_dto()\n File \"/usr/lib/python3.6/site-packages/pcs/common/reports/item.py\", line 182, in to_dto\n severity=self.severity.to_dto(),\nAttributeError: 'str' object has no attribute 'to_dto'\nError: /Stage[main]/Tripleo::Profile::Pacemaker::Ovn_dbs_bundle/Pacemaker::Resource::Ocf[ovndb_servers]/Pcmk_resource[ovndb_servers]: Could not evaluate: pcmk_resource_has_changed? --force resource update ovndb_servers ocf:ovn:ovndb-servers master_ip=[fd00:fd00:fd00:2000::53] nb_master_port=6641 sb_master_port=6642 manage_northd=yes inactive_probe_interval=180000 listen_on_master_ip_only=yes meta notify=true container-attribute-target=host op start timeout=200s stop timeout=200s monitor interval=10s role=Master timeout=60s monitor interval=30s role=Slave timeout=60s bundle ovn-dbs-bundle returned error ovndb_servers. This should never happen.\nWarning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead.", "stderr_lines": ["Warning: /etc/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5", " (file: /etc/puppet/hiera.yaml)", "Warning: Undefined variable '::deploy_config_name'; ", " (file & line not available)", "Warning: The function 'hiera' is deprecated in favor of using 'lookup'. See https://puppet.com/docs/puppet/6.14/deprecated_language.html", " (file & line not available)", "*Warning: This method is deprecated, please use match expressions with Stdlib::Compat::Ipv6 instead. They are described at https://docs.puppet.com/puppet/latest/reference/lang_data_type.html#match-e… <https://docs.puppet.com/puppet/latest/reference/lang_data_type.html#match-e…>. at [\"/etc/puppet/modules/tripleo/manifests/profile/pacemaker/ovn_dbs_bundle.pp\", 336]:[\"unknown\", 1]", "* (location: /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:34:in `deprecation')", "Warning: This command is deprecated and will be removed. Please use 'pcs property config' instead.", "Warning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead.", "Warning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead.", "Traceback (most recent call last):", " File \"/usr/lib/python3.6/site-packages/pcs/resource.py\", line 1039, in resource_update", " resource.getAttribute(\"type\"),", " File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/facade.py\", line 200, in facade_from_parsed_name", " parse_metadata(name, load_metadata(self._runner, name))", " File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/xml.py\", line 114, in load_metadata", " return _metadata_xml_to_dom(_load_metadata_xml(runner, agent_name))", " File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/xml.py\", line 52, in _load_metadata_xml", " raise UnableToGetAgentMetadata(agent_name.full_name, stderr.strip())", "pcs.lib.resource_agent.error.UnableToGetAgentMetadata", "", "During handling of the above exception, another exception occurred:", "", "Traceback (most recent call last):", " File \"/sbin/pcs\", line 11, in <module>", " load_entry_point('pcs===0.10.11.22-9d83b', 'console_scripts', 'pcs')()", " File \"/usr/lib/python3.6/site-packages/pcs/app.py\", line 278, in main", " utils.get_library_wrapper(), argv, utils.get_input_modifiers()", " File \"/usr/lib/python3.6/site-packages/pcs/cli/common/routing.py\", line 33, in _router", " return cmd_map[sub_cmd](lib, argv_next, modifiers)", " File \"/usr/lib/python3.6/site-packages/pcs/cli/common/routing.py\", line 33, in _router", " return cmd_map[sub_cmd](lib, argv_next, modifiers)", " File \"/usr/lib/python3.6/site-packages/pcs/resource.py\", line 1058, in resource_update", " [lib_ra.resource_agent_error_to_report_item(e, severity)]", " File \"/usr/lib/python3.6/site-packages/pcs/cli/reports/output.py\", line 38, in process_library_reports", " report_dto = report_item.to_dto()", " File \"/usr/lib/python3.6/site-packages/pcs/common/reports/item.py\", line 182, in to_dto", " severity=self.severity.to_dto(),", "AttributeError: 'str' object has no attribute 'to_dto'", "Error: /Stage[main]/Tripleo::Profile::Pacemaker::Ovn_dbs_bundle/Pacemaker::Resource::Ocf[ovndb_servers]/Pcmk_resource[ovndb_servers]: Could not evaluate: pcmk_resource_has_changed? --force resource update ovndb_servers ocf:ovn:ovndb-servers master_ip=[fd00:fd00:fd00:2000::53] nb_master_port=6641 sb_master_port=6642 manage_northd=yes inactive_probe_interval=180000 listen_on_master_ip_only=yes meta notify=true container-attribute-target=host op start timeout=200s stop timeout=200s monitor interval=10s role=Master timeout=60s monitor interval=30s role=Slave timeout=60s bundle ovn-dbs-bundle returned error ovndb_servers. This should never happen.", "Warning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead."], "stdout": "Notice: Compiled catalog for overcloud-controller-0.localdomain in environment production in 0.75 seconds\nNotice: Applied catalog in 30.15 seconds\nChanges:\nEvents:\n Failure: 1\n Total: 1\nResources:\n Failed: 1\n Out of sync: 1\n Skipped: 26\n Total: 35\nTime:\n Config retrieval: 0.84\n Pcmk resource: 11.39\n Last run: 1646819523\n Pcmk constraint: 2.86\n Transaction evaluation: 30.09\n Catalog application: 30.15\n Pcmk bundle: 7.09\n Pcmk property: 8.43\n Total: 30.15\nVersion:\n Config: 1646819492\n Puppet: 6.14.0", "stdout_lines": ["Notice: Compiled catalog for overcloud-controller-0.localdomain in environment production in 0.75 seconds", "Notice: Applied catalog in 30.15 seconds", "Changes:", "Events:", " Failure: 1", " Total: 1", "Resources:", " Failed: 1", " Out of sync: 1", " Skipped: 26", " Total: 35", "Time:", " Config retrieval: 0.84", " Pcmk resource: 11.39", " Last run: 1646819523", " Pcmk constraint: 2.86", " Transaction evaluation: 30.09", " Catalog application: 30.15", " Pcmk bundle: 7.09", " Pcmk property: 8.43", " Total: 30.15", "Version:", " Config: 1646819492", " Puppet: 6.14.0"]} 2022-03-09 15:22:03.686083 | 525400f8-4aa7-5981-5af0-0000000067ae | FATAL | Run init bundle puppet on the host for ovn_dbs | overcloud-controller-0 | error={"changed": false, "cmd": "puppet apply --detailed-exitcodes --summarize --color=false --modulepath '/etc/puppet/modules:/opt/stack/puppet-modules:/usr/share/openstack-puppet/modules' --tags 'pacemaker::resource::bundle,pacemaker::property,pacemaker::resource::ip,pacemaker::resource::ocf,pacemaker::constraint::order,pacemaker::constraint::colocation' -e 'include ::tripleo::profile::base::pacemaker; include ::tripleo::profile::pacemaker::ovn_dbs_bundle'\n", "delta": "0:00:36.507726", "end": "2022-03-09 15:22:03.635619", "failed_when_result": true, "msg": "non-zero return code", "rc": 4, "start": "2022-03-09 15:21:27.127893", "stderr": "Warning: /etc/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5\n (file: /etc/puppet/hiera.yaml)\nWarning: Undefined variable '::deploy_config_name'; \n (file & line not available)\nWarning: The function 'hiera' is deprecated in favor of using 'lookup'. See https://puppet.com/docs/puppet/6.14/deprecated_language.html\n (file & line not available)\nWarning: This method is deprecated, please use match expressions with Stdlib::Compat::Ipv6 instead. They are described at https://docs.puppet.com/puppet/latest/reference/lang_data_type.html#match-e…. at [\"/etc/puppet/modules/tripleo/manifests/profile/pacemaker/ovn_dbs_bundle.pp\", 336]:[\"unknown\", 1]\n (location: /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:34:in `deprecation')\nWarning: This command is deprecated and will be removed. Please use 'pcs property config' instead.\nWarning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead.\nWarning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead.\nTraceback (most recent call last):\n File \"/usr/lib/python3.6/site-packages/pcs/resource.py\", line 1039, in resource_update\n resource.getAttribute(\"type\"),\n File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/facade.py\", line 200, in facade_from_parsed_name\n parse_metadata(name, load_metadata(self._runner, name))\n File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/xml.py\", line 114, in load_metadata\n return _metadata_xml_to_dom(_load_metadata_xml(runner, agent_name))\n File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/xml.py\", line 52, in _load_metadata_xml\n raise UnableToGetAgentMetadata(agent_name.full_name, stderr.strip())\npcs.lib.resource_agent.error.UnableToGetAgentMetadata\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"/sbin/pcs\", line 11, in <module>\n load_entry_point('pcs===0.10.11.22-9d83b', 'console_scripts', 'pcs')()\n File \"/usr/lib/python3.6/site-packages/pcs/app.py\", line 278, in main\n utils.get_library_wrapper(), argv, utils.get_input_modifiers()\n File \"/usr/lib/python3.6/site-packages/pcs/cli/common/routing.py\", line 33, in _router\n return cmd_map[sub_cmd](lib, argv_next, modifiers)\n File \"/usr/lib/python3.6/site-packages/pcs/cli/common/routing.py\", line 33, in _router\n return cmd_map[sub_cmd](lib, argv_next, modifiers)\n File \"/usr/lib/python3.6/site-packages/pcs/resource.py\", line 1058, in resource_update\n [lib_ra.resource_agent_error_to_report_item(e, severity)]\n File \"/usr/lib/python3.6/site-packages/pcs/cli/reports/output.py\", line 38, in process_library_reports\n report_dto = report_item.to_dto()\n File \"/usr/lib/python3.6/site-packages/pcs/common/reports/item.py\", line 182, in to_dto\n severity=self.severity.to_dto(),\nAttributeError: 'str' object has no attribute 'to_dto'\nError: /Stage[main]/Tripleo::Profile::Pacemaker::Ovn_dbs_bundle/Pacemaker::Resource::Ocf[ovndb_servers]/Pcmk_resource[ovndb_servers]: Could not evaluate: pcmk_resource_has_changed? --force resource update ovndb_servers ocf:ovn:ovndb-servers master_ip=[fd00:fd00:fd00:2000::53] nb_master_port=6641 sb_master_port=6642 manage_northd=yes inactive_probe_interval=180000 listen_on_master_ip_only=yes meta notify=true container-attribute-target=host op start timeout=200s stop timeout=200s monitor interval=10s role=Master timeout=60s monitor interval=30s role=Slave timeout=60s bundle ovn-dbs-bundle returned error ovndb_servers. This should never happen.\nWarning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead.", "stderr_lines": ["Warning: /etc/puppet/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5", " (file: /etc/puppet/hiera.yaml)", "Warning: Undefined variable '::deploy_config_name'; ", " (file & line not available)", "Warning: The function 'hiera' is deprecated in favor of using 'lookup'. See https://puppet.com/docs/puppet/6.14/deprecated_language.html", " (file & line not available)", "Warning: This method is deprecated, please use match expressions with Stdlib::Compat::Ipv6 instead. They are described at https://docs.puppet.com/puppet/latest/reference/lang_data_type.html#match-e…. at [\"/etc/puppet/modules/tripleo/manifests/profile/pacemaker/ovn_dbs_bundle.pp\", 336]:[\"unknown\", 1]", " (location: /etc/puppet/modules/stdlib/lib/puppet/functions/deprecation.rb:34:in `deprecation')", "Warning: This command is deprecated and will be removed. Please use 'pcs property config' instead.", "Warning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead.", "Warning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead.", "Traceback (most recent call last):", " File \"/usr/lib/python3.6/site-packages/pcs/resource.py\", line 1039, in resource_update", " resource.getAttribute(\"type\"),", " File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/facade.py\", line 200, in facade_from_parsed_name", " parse_metadata(name, load_metadata(self._runner, name))", " File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/xml.py\", line 114, in load_metadata", " return _metadata_xml_to_dom(_load_metadata_xml(runner, agent_name))", " File \"/usr/lib/python3.6/site-packages/pcs/lib/resource_agent/xml.py\", line 52, in _load_metadata_xml", " raise UnableToGetAgentMetadata(agent_name.full_name, stderr.strip())", "pcs.lib.resource_agent.error.UnableToGetAgentMetadata", "", "During handling of the above exception, another exception occurred:", "", "Traceback (most recent call last):", " File \"/sbin/pcs\", line 11, in <module>", " load_entry_point('pcs===0.10.11.22-9d83b', 'console_scripts', 'pcs')()", " File \"/usr/lib/python3.6/site-packages/pcs/app.py\", line 278, in main", " utils.get_library_wrapper(), argv, utils.get_input_modifiers()", " File \"/usr/lib/python3.6/site-packages/pcs/cli/common/routing.py\", line 33, in _router", " return cmd_map[sub_cmd](lib, argv_next, modifiers)", " File \"/usr/lib/python3.6/site-packages/pcs/cli/common/routing.py\", line 33, in _router", " return cmd_map[sub_cmd](lib, argv_next, modifiers)", " File \"/usr/lib/python3.6/site-packages/pcs/resource.py\", line 1058, in resource_update", " [lib_ra.resource_agent_error_to_report_item(e, severity)]", " File \"/usr/lib/python3.6/site-packages/pcs/cli/reports/output.py\", line 38, in process_library_reports", " report_dto = report_item.to_dto()", " File \"/usr/lib/python3.6/site-packages/pcs/common/reports/item.py\", line 182, in to_dto", " severity=self.severity.to_dto(),", "AttributeError: 'str' object has no attribute 'to_dto'", "Error: /Stage[main]/Tripleo::Profile::Pacemaker::Ovn_dbs_bundle/Pacemaker::Resource::Ocf[ovndb_servers]/Pcmk_resource[ovndb_servers]: Could not evaluate: pcmk_resource_has_changed? --force resource update ovndb_servers ocf:ovn:ovndb-servers master_ip=[fd00:fd00:fd00:2000::53] nb_master_port=6641 sb_master_port=6642 manage_northd=yes inactive_probe_interval=180000 listen_on_master_ip_only=yes meta notify=true container-attribute-target=host op start timeout=200s stop timeout=200s monitor interval=10s role=Master timeout=60s monitor interval=30s role=Slave timeout=60s bundle ovn-dbs-bundle returned error ovndb_servers. This should never happen.", *"Warning: This command is deprecated and will be removed. Please use 'pcs constraint config' instead."], "stdout":* "Notice: Compiled catalog for overcloud-controller-0.localdomain in environment production in 0.75 seconds\nNotice: Applied catalog in 30.15 seconds\nChanges:\nEvents:\n Failure: 1\n Total: 1\nResources:\n Failed: 1\n Out of sync: 1\n Skipped: 26\n Total: 35\nTime:\n Config retrieval: 0.84\n Pcmk resource: 11.39\n Last run: 1646819523\n Pcmk constraint: 2.86\n Transaction evaluation: 30.09\n Catalog application: 30.15\n Pcmk bundle: 7.09\n Pcmk property: 8.43\n Total: 30.15\nVersion:\n Config: 1646819492\n Puppet: 6.14.0", "stdout_lines": ["Notice: Compiled catalog for overcloud-controller-0.localdomain in environment production in 0.75 seconds", "Notice: Applied catalog in 30.15 seconds", "Changes:", "Events:", " Failure: 1", " Total: 1", "Resources:", " Failed: 1", " Out of sync: 1", " Skipped: 26", " Total: 35", "Time:", " Config retrieval: 0.84", " Pcmk resource: 11.39", " Last run: 1646819523", " Pcmk constraint: 2.86", " Transaction evaluation: 30.09", " Catalog application: 30.15", " Pcmk bundle: 7.09", " Pcmk property: 8.43", " Total: 30.15", "Version:", " Config: 1646819492", " Puppet: 6.14.0"]} 2022-03-09 15:22:03.690015 | 525400f8-4aa7-5981-5af0-0000000067ae | TIMING | tripleo_ha_wrapper : Run init bundle puppet on the host for ovn_dbs | overcloud-controller-0 | 0:14:40.633394 | 36.87s 2022-03-09 15:22:05.269139 | 525400f8-4aa7-5981-5af0-000000006a82 | OK | Gather podman infos | overcloud-controller-2 2022-03-09 15:22:05.270057 | 525400f8-4aa7-5981-5af0-000000006a82 | TIMING | tripleo_container_manage : Gather podman infos | overcloud-controller-2 | 0:14:42.213453 | 2.76s 2022-03-09 15:22:05.726794 | 525400f8-4aa7-5981-5af0-000000006a83 | TASK | Delete orphan containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 2022-03-09 15:22:05.786601 | 525400f8-4aa7-5981-5af0-000000006a83 | TIMING | Delete orphan containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3 | overcloud-controller-2 | 0:14:42.729983 | 0.06s 2022-03-09 15:22:06.038548 | 525400f8-4aa7-5981-5af0-000000006b27 | TIMING | tripleo_container_rm : include_tasks | overcloud-controller-2 | 0:14:42.981908 | 0.19s 2022-03-09 15:22:06.068012 | 525400f8-4aa7-5981-5af0-000000006942 | TASK | Create containers from /var/lib/tripleo-config/container-startup-config/step_3 2022-03-09 15:22:06.119081 | 525400f8-4aa7-5981-5af0-000000006942 | TIMING | tripleo_container_manage : Create containers from /var/lib/tripleo-config/container-startup-config/step_3 | overcloud-controller-2 | 0:14:43.062462 | 0.05s 2022-03-09 15:22:06.136762 | f2c26285-bf89-4ee3-a43f-cdf6e8722aaa | INCLUDED | /usr/share/ansible/roles/tripleo_container_manage/tasks/create.yml | overcloud-controller-2 Regards Anirudh Gupta

1 0

[designate] Architecture help for designate on multi-region/multi-AZ deployments
by Jean-Philippe Evrard 11 Mar '22

11 Mar '22

Hello folks, I currently have designate installed in a single region in a cloud. Now we are thinking about the next steps: A multi-region designate for a simple use case: Bring your own domain, have A/AAAA records for your instances regardless of the region. Side note: That requirement can be modified if what I am asking is impossible. I didn't find anything in the ML, nor in the bug tracker [1] outside a neutron bug [2] (am I blind?). I had a look at the designate documentation, but there are no best practices for multi-region (or am I blind again?) The only relevant part for integration with neutron is in [3], which is not region related. I am looking for advice from designate experts here, to see what we can do. Right now, we are thinking about two ways to deal with this: A) Install a separate openstack with designate, and make all the regions's neutrons configuration point to a single designate. Neutron would work, designate would be simple to manage (as we have a single designate). The downside here is the clear-cut separation of regions: I am afraid of how records are stored in the central designate, and if there won't be multi-tenancy issues (uuid could technically overlap, as different regions means different keystones here). B) Install a designate in each region, with DNS servers in each region. We have strict region separation this way. The downside is the user friendliness: A customer _can_ decide which region in which the domain will be hosted. That means that we now need to worry about synchronizing region's state (if you have created a domain in that region, you can't do it elsewhere). Am I misunderstanding/not seeing something obvious here? Thank you in advance. Jean-Philippe Evrard (evrardjp) [0]: https://www.google.com/search?q=designate+multi+region+site%3Ahttp%3A%2F%2F… [1]: https://bugs.launchpad.net/designate?field.searchtext=region [2]: https://review.opendev.org/c/openstack/neutron/+/684854/ [3]: https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.html

2 2

IPv6 deployment on OpenStack
by Marc-Antoine Godde 10 Mar '22

10 Mar '22

Hello. We are progressively adding support for IPv6 in my company. We decided to use SLAAC only for laptops, phones, … since DHCPv6 isn’t supported on Android. RDNSS support will also increase. We are now planning our deployment on OpenStack. We already know that we'll rely only on neutron but we are not yet fixed between DHCPv6 and SLAAC ? Do you have any arguments for one these for VMs ? Thanks, Marc-Antoine.

4 11

[neutron] Drivers meeting - Friday 11.3.2022 - cancelled
by Lajos Katona 10 Mar '22

10 Mar '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. Lajos Katona (lajoskatona)

1 0

Re: [trove][tc][all] Call for volunteers to be a PTL and maintainers
by Slawek Kaplonski 10 Mar '22

10 Mar '22

Hi, Once again thx for stepping up for this role in Trove. Patch for that is already proposed https://review.opendev.org/c/openstack/governance/+/833152[1] - we need now Your +1 on this patch to be able to approve it and to make You officially PTL of Trove. On czwartek, 10 marca 2022 12:27:43 CET W Ch wrote: > thanks > > Slawek Kaplonski <skaplons(a)redhat.com> 于2022年3月10日周四 19:06写道： > > > Hi, > > > > On czwartek, 10 marca 2022 11:46:11 CET W Ch wrote: > > > hi, Is anyone elected PTL for trove now ? If nobody, I'd like to > > maintain > > > the trove project, since we are using it in our production. > > > > Thx a lot for stepping up and willing to help with Trove. There are no > > other candidates yet AFAICT so we will discuss Your candidacy and will let > > You know about it soon. > > > > > > > > > > > > > > wu.chunyang > > > > > > Slawek Kaplonski <skaplons(a)redhat.com> 于2022年3月6日周日 01:33写道： > > > > > > > Hi, > > > > > > > > After last PTL elections [1] Trove project still don't have any PTL > > > > elected. > > > > So this is call for maintainers for Trove. If You are using it or > > > > interested in it, and if You are willing to help maintaining this > > project, > > > > please contact TC members through this mailing list or directly on the > > > > #openstack-tc channel @OFTC. We can talk possibilities to make someone > > a > > > > PTL of the project or going with this project to the Distributed > > Project > > > > Leadership [2] model. > > > > > > > > [1] > > > > > > http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027411… > > > > [2] > > > > > > https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… > > > > > > > > -- > > > > Slawek Kaplonski > > > > Principal Software Engineer > > > > Red Hat > > > > > > > > > > > -- > > Slawek Kaplonski > > Principal Software Engineer > > Red Hat > -- Slawek Kaplonski Principal Software Engineer Red Hat -------- [1] https://review.opendev.org/c/openstack/governance/+/833152

1 0

[nova] VM ending up in a different availability zone after resizing vm instance
by hai wu 10 Mar '22

10 Mar '22

VM ends up in a different availability zone after resizing the vm instance. The default openstack nova behavior should have prevented this from happening, correct? What could have caused this?

3 4

[oslo] [tooz] Deprecating etcd3 driver
by Tobias Urdin 10 Mar '22

10 Mar '22

Hello, I’m proposing that we deprecate the etcd3 driver https://review.opendev.org/c/openstack/tooz/+/833107 I will include the commit message below that describes the situation with the dependency the driver has on the python-etcd3 library. Please let me know what you think about this action, we would also like to know if you are using the driver. Best regards Tobias ——— Author: Tobias Urdin <tobias.urdin(a)binero.se<mailto:tobias.urdin@binero.se>> Date: Thu Mar 10 15:09:58 2022 +0000 Deprecate the etcd3 driver The etcd3 driver depends on the python-etcd3 [1] library that is currently stale and no has no active maintenance [2] with a non-working CI that blocks all PRs. It's also currently blocking Tooz from supporting newer versions of tenacity [3] that a lot of projects is now pinning because newer version of tenacity dropped old legacy compatibility code that has been in there for years. We currently have etcd3gw as an alternative driver where the library the driver depends on is a deliverable that we maintain. [1] https://github.com/kragniz/python-etcd3 [2] https://github.com/kragniz/python-etcd3/issues/1719 [3] https://review.opendev.org/c/openstack/tooz/+/829412 Change-Id: Iff0cd3b51cfc45ecbddc831c55267e80e9c79cac

2 1

[TC][PTL][ops][all] Release cadence, deprecation, and testing
by Dan Smith 10 Mar '22

10 Mar '22

Hi all, As you probably already know from gmann's reporting, the TC recently passed a resolution[1] regarding the release cadence. This, in response to some discussion around moving to different release cycle lengths, becomes mostly a change regarding our deprecation procedures, as well as a call to support the ability to skip certain releases (designated "tock" releases) while sticking on a yearly cycle (designated "tick" releases). In support of the goal of moving to this new cadence for the AA release (i.e. the yet unnamed release to come after Zed), I have introduced[2] a new grenade-skip-level job, which tests skipping "tock" releases and going straight from one tick to the following. We intend this to be a voting job in AA, making sure it works from Yoga->AA. Right now it tests Wallaby->Yoga for informational purposes. We would recommend projects enable that as voting, or define their own job to do similar testing as soon as possible. Manila has already started[3] this. Note that existing grenade testing between each adjacent release remains unchanged in this scheme. On the topic of deprecation, we moved the current definition of deprecation procedures from the soon-to-be-removed tag definition to a new document in project-team-guide[4]. This now describes the procedures in terms of the tick-tock release arrangement, and is worth a read. As the PTG is coming up, we will certainly discuss this topic in the PTL Interaction[5] session. It would also be advisable to discuss the project-specific details of this in the various project sessions. By identifying this plan early and setting our goals for AA, we have a good amount of time between now and then to get our heads wrapped around what (if any) things we need to be doing. Luckily, the introduction of the job to test this from wallaby to yoga required almost no project changes to get working, which is a good indicator that it won't be too laborious for most projects to adopt. --Dan 1: https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad… 2: https://review.opendev.org/c/openstack/grenade/+/826101 3: https://review.opendev.org/c/openstack/manila/+/830277 4: https://docs.openstack.org/project-team-guide/deprecation.html 5: https://etherpad.opendev.org/p/tc-ptl-interaction-zed

3 5

[ops][cinder] reminder: resource count survey - win fabulous prizes!
by Brian Rosmaita 10 Mar '22

10 Mar '22

Hello operators, Don't miss out on this chance to take the Cinder Resource Count Survey! Act now before the survey closes on Wednesday 30 March! https://rosmaita.wufoo.com/forms/cinder-resource-count-survey/ Details below: The Cinder project is working on the cinder quotas system in an effort to improve its accuracy and remove the necessity for operators to go through and clean it up occasionally when it gets out of sync with reality. One way to do this is to use dynamic database counting (instead of storing the usage info in a table where it can become outdated). Whether this will be a good change depends on how many records the database has to process during a transaction, which in turn depends on how many Cinder resources a project has. So we need to get some information from you. Please take this brief survey: https://rosmaita.wufoo.com/forms/cinder-resource-count-survey/ The survey closes on Wednesday 30 March at 1200 UTC, so that we can have data to discuss during the Zed PTG. But please don't procrastinate, it's only 6 questions and the answers are all positive integers. It shouldn't take long to fill out! Thanks! brian

1 0

[openstack][queens][cinder] volume retype errors
by Ignazio Cassano 10 Mar '22

10 Mar '22

Hello, sometimes the volume retype from a netapp nfs storage to another netapp nfs storage does not work. I do not know the reason but I think something is going wrong in nova: /var/log/nova/nova-compute.log:2022-02-02 14:23:39.992 194288 ERROR root [req-ebbf749f-359f-4282-94c5-0913cffe97a3 66adb965bef64eaaab2af93ade87e2ca 68feefdf7c5847388534e9214dc13366 - default default] Original exception being dropped: ['Traceback (most recent call last):\n', ' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 5655, in _swap_volume\n mountpoint, resize_to)\n', ' File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1647, in swap_volume\n self._disconnect_volume(context, new_connection_info, instance)\n', ' File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__\n self.force_reraise()\n', ' File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise\n six.reraise(self.type_, self.value, self.tb)\n', ' File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1644, in swap_volume\n self._swap_volume(guest, disk_dev, conf, resize_to)\n', ' File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 1593, in _swap_volume\n raise exception.VolumeRebaseFailed(reason=six.text_type(exc))\n', "VolumeRebaseFailed: Volume rebase failed: Requested operation is not valid: pivot of disk 'vda' requires an active copy job\n"]: VolumeAttachmentNotFound: Volume attachment 2cd820e0-85e8-498d-a62a-800260d0cf31 could not be found Must I try to change some parameters in nova.conf on compute nodes about volume attachment ? Thanks Ignazio

3 7

[trove][tc][all] Call for volunteers to be a PTL and maintainers
by Slawek Kaplonski 10 Mar '22

10 Mar '22

Hi, After last PTL elections [1] Trove project still don't have any PTL elected. So this is call for maintainers for Trove. If You are using it or interested in it, and if You are willing to help maintaining this project, please contact TC members through this mailing list or directly on the #openstack-tc channel @OFTC. We can talk possibilities to make someone a PTL of the project or going with this project to the Distributed Project Leadership [2] model. [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027411… [2] https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… -- Slawek Kaplonski Principal Software Engineer Red Hat

2 2

[kuryr] Zed PTG planning
by Maysa De Macedo Souza 10 Mar '22

10 Mar '22

Hello everyone, The virtual PTG will happen between 4th-8th April. I've created a doodle[1] to try finding a time slot that works for most of us. There is also an etherpad[2] to propose topics to be discussed, feel free to fill it if you have one. Thank you. Kind regards, Maysa Macedo. [1] https://doodle.com/meeting/participate/id/0dN1Movb [2] https://etherpad.opendev.org/p/kuryr-zed-ptg

1 1

Ussuri: Magnum failed to get the size of cluster
by Eugen Block 10 Mar '22

10 Mar '22

Hi *, sorry for the repost, I forgot to edit the subject line. I'm trying to get magnum to work in an Ussuri environment. There are some issues I'm facing and would like to ask you for some pointers what I might be doing wrong. The control nodes would have access to the internet through a proxy, I would like to avoid that but I don't know yet what my local registry needs to look like. So to get it working I'll go with the http_proxy. The first attempts failed due to various reasons, now I'm stuck at the invalid discovery_url. After some search I found that I need to create a new discovery_url like this: controller02:~ # curl --silent -H "Accept: text/plain" https://discovery.etcd.io/new?size=1 Using that new URL I try to create a cluster like this: controller02:~ # openstack coe cluster create kubernetes-cluster-8 --cluster-template 9c7cfeff-3807-4b06-a4e6-a76f2ae0f612 --master-count 1 --node-count 1 --keypair eblock --discovery-url https://discovery.etcd.io/<UUID> The template contains the http and https proxy. The resulting error is this: ---snip--- HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)): requests.exceptions.ConnectionError: HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)) [...] requests.exceptions.ConnectionError: HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)) [...] magnum.common.exception.GetClusterSizeFailed: Failed to get the size of cluster from 'https://discovery.etcd.io/<UUID>'. ---snip--- The stack trace is a little longer, of course, but this is the relevant part. Can anyone point me in the right direction? What am I missing? I also tried quay.io since discovery.etcd.io seems to be not maintained anymore, but there I can't even generate a new URL. Any help is greatly appreciated! Thanks Eugen

1 1

Ussuri: Magnum
by Eugen Block 10 Mar '22

10 Mar '22

Hi *, I'm trying to get magnum to work in an Ussuri environment. There are some issues I'm facing and would like to ask you for some pointers what I might be doing wrong. The control nodes would have access to the internet through a proxy, I would like to avoid that but I don't know yet what my local registry needs to look like. So to get it working I'll go with the http_proxy. The first attempts failed due to various reasons, now I'm stuck at the invalid discovery_url. After some search I found that I need to create a new discovery_url like this: controller02:~ # curl --silent -H "Accept: text/plain" https://discovery.etcd.io/new?size=1 Using that new URL I try to create a cluster like this: controller02:~ # openstack coe cluster create kubernetes-cluster-8 --cluster-template 9c7cfeff-3807-4b06-a4e6-a76f2ae0f612 --master-count 1 --node-count 1 --keypair eblock --discovery-url https://discovery.etcd.io/<UUID> The template contains the http and https proxy. The resulting error is this: ---snip--- HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)): requests.exceptions.ConnectionError: HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)) [...] requests.exceptions.ConnectionError: HTTPSConnectionPool(host='discovery.etcd.io', port=443): Max retries exceeded with url: /<UUID>/_config/size (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fd5e61dcfd0>: Failed to establish a new connection: [Errno 110] ETIMEDOUT',)) [...] magnum.common.exception.GetClusterSizeFailed: Failed to get the size of cluster from 'https://discovery.etcd.io/<UUID>'. ---snip--- The stack trace is a little longer, of course, but this is the relevant part. Can anyone point me in the right direction? What am I missing? I also tried quay.io since discovery.etcd.io seems to be not maintained anymore, but there I can't even generate a new URL. Any help is greatly appreciated! Thanks Eugen

1 0

[Neutron][Octavia][ovn-octavia-provider] proposing Luis Tomas Bolivar for ovn-octavia-provider core reviewer
by Lajos Katona 09 Mar '22

09 Mar '22

Hi I would like to propose Luis Tomas Bolivar (ltomasbo) as a core reviewer to the ovn-octavia-provider project. Luis is very active in the project (see [1] and [2]) and has experience with Kuryr side also which uses ovn-octavia-provider. As ovn-octavia-provider is a link between Neutron and Octavia I ask both Neutron and Octavia cores to vote by answering to this thread, to have a final decision. Thanks for your consideration [1]: https://review.opendev.org/q/owner:ltomasbo%2540redhat.com+branch:master [2]: https://www.stackalytics.io/report/contribution?module=neutron-group&projec… Cheers Lajos

8 8

[ironic] Zed PTG slots
by Iury Gregory 09 Mar '22

09 Mar '22

Hello Ironicers! For the Zed PTG I'm planning to have some slots that will allow APAC contributors to participate in the discussions. Keep in mind that we have some guidelines we should try to follow: 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Based on this I have the following proposals: (Feel free to provide more ideas also) =) *Option #1* *16hrs* Monday till Thursday 1h (APAC night + EMEA morning) 2hrs (EMEA afternoon + NA morning) 1hr (NA afternoon/night + APAC morning) *Option #2* *15hrs* Tuesday till Friday 1h (APAC night + EMEA morning) 2hrs (EMEA afternoon + NA morning) 1hr (NA afternoon/night + APAC morning) * On Friday the NA + APAC session won't happen because is saturday for APAC contributors * *Option #3* *16hrs* Monday till Thursday 3hrs (EMEA afternoon + NA morning) 1hr (NA afternoon/night + APAC morning) *Option #4* *15hrs* Tuesday till Friday 3hrs (EMEA afternoon + NA morning) 1hr (NA afternoon/night + APAC morning) * On Friday the NA + APAC session won't happen because is saturday for APAC contributors * Please choose two options and we will vote during our upstream meeting on March 7th. Thank you! -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and 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>*

3 3

[all][tc] Technical Committee next weekly meeting on Mar 10th at 1500 UTC
by Ghanshyam Mann 09 Mar '22

09 Mar '22

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Mar 10th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Mar 9th , at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[puppet] Gate blocker: CentOS 9 integration jobs are broken
by Takashi Kajinami 09 Mar '22

09 Mar '22

Hi, Please be aware that currently CentOS 9 integration jobs are broken because of the two problems caused by recent updates in c9s repos. https://bugs.launchpad.net/puppet-openstack-integration/+bug/1962506 https://bugs.launchpad.net/puppet-openstack-integration/+bug/1962507 I'm currently working on implementing workaround[1], but in case it would take some time, I'll make c9s integration jobs non-voting again to unblock our gate. [1] https://review.opendev.org/c/openstack/puppet-openstack-integration/+/831197 Please avoid approving changes which require integration jobs. Thank you, Takashi

2 4

[manila] Zed PTG Planning
by Carlos Silva 09 Mar '22

09 Mar '22

Hello dear Zorillas and interested stackers! As you might be aware, the virtual PTG will be held between April 4th and 8th. There is an etherpad to propose the topics to be discussed [1]. If you intend to participate, please add your name and your timezone to the attendees list on the etherpad. Please add your topics to the etherpad, and if you have a preference of time for due to your timezone, please let me know. [1] https://etherpad.opendev.org/p/zorilla-ptg-manila-planning Thanks, carloss

1 0

Why is Qinling no longer supported?
by Streander, Paul 09 Mar '22

09 Mar '22

Thanks This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited. Deloitte refers to a Deloitte member firm, one of its related entities, or Deloitte Touche Tohmatsu Limited ("DTTL"). Each Deloitte member firm is a separate legal entity and a member of DTTL. DTTL does not provide services to clients. Please see www.deloitte.com/about to learn more. v.E.1

3 2