September 2022 - openstack-discuss

[blazar][FFE] Improvements to ExternalServiceFilter
by Pierre Riteau 15 Sep '22

15 Sep '22

Hello, We have merged a new Blazar usage enforcement filter late into the cycle, but have since received a change from Radosław Piliszek (yoctozepto) improving it [1]. It is important for us to get this merged for Zed, as it changes the name of new configuration options. Not merging it now would require us to deprecate the newly added configuration options in Antelope. I am planning to grant an FFE for it just before issuing RC1. Cheers, Pierre Riteau (priteau) [1] https://review.opendev.org/c/openstack/blazar/+/856527

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Sept 15 at 1500 UTC
by Ghanshyam Mann 15 Sep '22

15 Sep '22

Hello Everyone, Below is the agenda for Today's TC meeting schedule at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * 2023.1 cycle PTG Planning ** TC + Leaders interaction sessions *** https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 ** TC PTG etherpad *** https://etherpad.opendev.org/p/tc-2023-1-ptg ** Schedule 'operator hours' *** https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… * 2023.1 cycle Technical Election & Leaderless projects ** https://governance.openstack.org/election/ ** https://etherpad.opendev.org/p/2023.1-leaderless ** https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0304… * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[tacker] Recent FT errors
by Yasufumi Ogawa 15 Sep '22

15 Sep '22

Hi tacker team, We've several unexpected failures on functional tests since last week or so. It might be because of new tests introduced in the recent some updates, and some lackness of resources on zuul tests we usually meet the same situation at the end of release possibly. Thanks to ueha to propose a patch [1] as a remedy for the issue, but it doesn't work for now unfortunately. For plan B, we can make the new tests non-voting for a while because it's not related to all reamined patches being reviewed now actually. We can revert it and focus on to fix the problem after RC1 is released. What do you think? [1] https://review.opendev.org/c/openstack/tacker/+/857551 Yasufumi

2 5

TC Election Double Ballots
by Amy Marrich 15 Sep '22

15 Sep '22

Hi everyone, As some of you have reported you have received 2 emails for the election. This was a result of our uploading the lists twice to make sure everyone who had to opt-in were included. Sorry for any confusion, Amy and the rest of the Election Officials

1 0

cpu metric not getting created for resource instance
by Swogat Pradhan 14 Sep '22

14 Sep '22

Hi, I am trying out the heat autoscalling and i am facing an issue where the instance created doesn't have cpu metric (enabled in ceilometer polling.yaml file) (overcloud) [stack@hkg2director ~]$ gnocchi resource show 130a0dfd-4e43-4373-ad0c-b5ffd4fcca95 +-----------------------+---------------------------------------------------------------------+ | Field | Value | +-----------------------+---------------------------------------------------------------------+ | created_by_project_id | 7c9659572662449da4906cc77b33f21b | | created_by_user_id | 4cb066d9701440dea941c5157186d06d | | creator | 4cb066d9701440dea941c5157186d06d:7c9659572662449da4906cc77b33f21b | | ended_at | None | | id | 130a0dfd-4e43-4373-ad0c-b5ffd4fcca95 | | metrics | compute.instance.booting.time: c0f77048-a85d-48a3-92cd-cdca50b341e8 | | | disk.ephemeral.size: 46d77e5d-aba1-4b93-92eb-3a97f9512a3c | | | disk.root.size: 3f60cb9f-9c06-4ccc-b47d-d2ca899fe5ea | | | memory: 97f796ed-c26c-4625-8670-64cf004a7b26 | | | vcpus: 513908f9-1bba-429e-8106-3bf933f04a76 | | original_resource_id | 130a0dfd-4e43-4373-ad0c-b5ffd4fcca95 | | project_id | 5d922243077045c48fe4b075e386551b | | revision_end | None | | revision_start | 2022-09-14T13:00:53.216445+00:00 | | started_at | 2022-09-14T12:57:21.846635+00:00 | | type | instance | | user_id | c1905e3c5a374924980e851840e7f028 | +-----------------------+---------------------------------------------------------------------+ For other instances also i do not see any cpu metric. Now the issue is as cpu metric is not getting created the alarm is not getting any data from the VM in terms of cpu usage and my autoscaling feature is failing. Please suggest how to fix this issue. With regards, Swogat Pradhan

2 3

[ironic] Ilya Etingof Passed Away
by Iury Gregory 14 Sep '22

14 Sep '22

With a heavy heart, I am sorry to announce that after a long struggle with an illness, Ilya Etingof (etingof on IRC) passed away on Wednesday, 10th August, 2022. He is survived by his mother and two daughters. Born in Russia, Ilya had moved to Czechia and in 2015 joined Red Hat. In 2017, Ilya started contributing to the Ironic project. He was the lead contributor to the Sushy project, Sushy Redfish emulator, an important contributor to Ironic and worked tirelessly to make hardware management reliable and consistent. His important contributions included boot management, out-of-band hardware inspection and virtual media boot. Outside of the OpenStack community, he has maintained Python packages with a particular focus on SNMP. For example: pysnmp, pysmi, pyasn1, softboxen and many others. Ilya was dedicated to helping younger and under-represented people. He used to run a virtualisation technologies course at the Masaryk University in Brno where he spoke about OpenStack and Kubernetes. He was also an active participant in the Outreachy program where he mentored those who contributed to Open Source projects. Goodbye Ilya from the Ironic community, may you rest in peace. -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

2 1

[largescale-sig] Next meeting: Sept 14th, 15utc
by Thierry Carrez 14 Sep '22

14 Sep '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can check how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220914T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[cinder] Bug Report 09-14-2022
by Sofia Enriquez 14 Sep '22

14 Sep '22

This is a bug report from 09-07-2022 to 09-14-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1989271 " revert_snapshot_will_destory_attachment_with_lvm_backend." Fix proposed to master but Zuul voted -1. - https://bugs.launchpad.net/cinder/+bug/1989281 "IPV6 with lightos driver won't work." Unassigned. Low - https://bugs.launchpad.net/cinder/+bug/1988942 "Failed to set image property. Invalid input for field/attribute simplestreams_metadata. Value: ... is too long (HTTP 400)." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1989280 "Wrong assertion methods in unit tests." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1989280 "Wrong assertion methods in unit tests." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1989176 "Hitachi driver: no message for resource lock." Fix proposed to master. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

RE: Re: [openstack yova][nova-spiceproxy] Spice proxy behind SSL termination: protocol mismatch error in horizon web UI
by 박경원 14 Sep '22

14 Sep '22

1 0

[vitrage] RCA not showing on dashboard
by Carlos Rodríguez 14 Sep '22

14 Sep '22

Hi, I hope find very well, We are using vitrage-dashboard, but right we are presenting problems displaying the RCA alarm graph. [image: vitrageerror.png] When clicking RCA button in any alarm, the graph is not displayed and the following error is shown in inspector: Error: layers[node.rank] is undefined Downgrading to vitrage-dashboard stable/train seems to solve the issue. For the latest releases, the issue is solved when the following commit is reverted: d181623f22 Replace embedded static files with XStatic-* It seems that there is some problem with the XStatic libraries. Tested in Chrome, Firefox, Edge. Openstack release: Victoria Are you working to solve this problem? Or do you have any solution to display the graph. Thanks for your time, kind regards.

1 0

Outreachy 2022 - 2023?
by Sofia Enriquez 13 Sep '22

13 Sep '22

Hello, I'd like to propose myself as a mentor for this Outreachy round. However, I haven't seen any email on the mailing list announcing that OpenStack is joining this round. Please let me know if Openstack is going to sponsor the next rounds. Thanks in advance, Best, Sofia -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

3 3

[neutron] bug deputy report (week of Sep 5)
by Akihiro Motoki 13 Sep '22

13 Sep '22

Hi, I was a bug deputy last week. It was a quiet week and only two new bugs are unassigned. ## Unassigned * https://bugs.launchpad.net/neutron/+bug/1988793 OVN as a Provider Driver for Octavia in ovn-octavia-provider This is a request to add a limitation corresponding to bug 1901936 (manual failure over is not supported) to the document. Hopefully ovn-octavia-driver folks can update the limitations section in the doc. * Neutron 20.2 Unknown Chassis Issue https://bugs.launchpad.net/neutron/+bug/1989155 ralonso suggested to file a bug on this to OVN upstream. It seems an issue in OVN core and perhaps we can mark it as invalid in neutron. ## In Progress * https://bugs.launchpad.net/neutron/+bug/1989391 [OVN] Allowed Address Pairs which is netmask doesn't work Thanks, Akihiro Motoki (amotoki)

1 0

Openstack.io is down
by Elvira Garcia Ruiz 13 Sep '22

13 Sep '22

Hi everyone! I noticed that stackalytics.io has been down for several days now. As far as I know this was widely used by the community, although it is not part of OpenInfra as a project. I'm not sure who was maintaining this, but I just wanted to make them aware of the problem, and also thank them for keeping it up and running. Kind regards! Elvira García (irc:elvira)

5 5

[openstack yova][nova-spiceproxy] Spice proxy behind SSL termination: protocol mismatch error in horizon web UI
by 박경원 13 Sep '22

13 Sep '22

2 1

[tripleo] puppetlabs-apache: soon a just a bad memory?
by Cédric Jeanneret 13 Sep '22

13 Sep '22

Hello Community! TLDR; puppetlabs-apache broke us so many times, I'm proposing a way to get rid of it, using plain ansible. Some work is needed, but it's "easy", and will allow us to keep a hand on the whole configuration code. Longer version: You probably saw mails about issues with puppetlabs-apache releases breaking the CI (and, by extension, TripleO). Over and over and over again. Well, good news: this may be just a bad memory - though it will require some work :). I've been working on a couple of ansible roles[1] in order to just get the needed pieces we really need in TripleO: file generation. Once we get those 2 roles in, we'll be able to switch, service by service, away from puppet management for apache/httpd. There's already an on-going example[2] with ironic. Of course, as you can see, there's some work to do, even on the puppet side. But it's not really complicated, and can be done quickly. I'll do my best to move things, but be prepared to get pings from time to time if help is needed. I can't do all by myself, can I? ;) And if anyone wants to jump in and work on the transition, please do, and don't hesitate to reach to me, either by mail, or on #tripleo - I go there as Tengu. Cheers, C. [1] https://review.opendev.org/c/openstack/tripleo-ansible/+/853481 [2] https://review.opendev.org/q/topic:standalone%252Fapache -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

1 0

[tripleo] Switching to nftables - it's coming soon!
by Cédric Jeanneret 13 Sep '22

13 Sep '22

Hello there, TLDR; we're about to switch to nftables[1], there are some changes described in the up-to-date doc. Reason is: faster, more modern interface, close to no possibility to get locked out of the system. Also, once it's switched, please use `nft list ruleset' instead of `iptables -L'. [1] https://review.opendev.org/c/openstack/tripleo-heat-templates/+/852808 Longer version: I've been working a good amount of time in order to get rid of the current tripleo_iptables custom action. On of the reasons here was the fact we could get locked out the overcloud if, for any reason, a network reset happens in ansible during the application of the rules. For the records, tripleo_iptables is calling the native "iptables" module from ansible, just doing a batching of the ruleset in an attempt to apply everything faster. It has some weird things, such as reversing the rule order before applying them using the "insert" action, meaning it will lock everything first, then open one by one the accesses. Knowing "ssh" is like 003 rule, you can imagine how things can go wrong. So, I took the opportunity to make some changes. While doing so, I saw `iptables' was just a compatibility wrapper for nftables - basically, `iptables' is a symlink to `iptables-nft', so I also took the opportunity to bypass it, and go straight for `nft'. Doing so, I created a new tripleo_nftables role in tripleo-ansible project; it's "just" creating files based on templates, then validates the whole lot of files, and applies all the rules in one single transaction. Compared to tripleo_iptables, it's really more robust, while being faster, and less prone to lock out and other unwanted things. The current state is: we're close, really close to switch things up. We're missing 2 patches in the CI to make the infra properly supported, and then, there's "the" switch itself. What will change: almost nothing: the way we create rules in tripleo-heat-templates and the different parameters therein doesn't change at all; the thing that will really change is the way to list the rules: instead of calling `iptables -vnL' or the like, you'll need to call `nft list ruleset'. Now, in order to make things easier, the doc is already up-to-date: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… As you will see, there will be some differences in the actual layout: all of the tripleo rules will be in dedicated chains, prefixed by TRIPLEO_ - for instance, TRIPLEO_INPUT, TRIPLEO_OUTPUT, TRIPLEO_FORWARD, and so on. This allows to get a cleaner layout, cleaner way to filter the output and, really important thing, to ensure we're cleaning dangling rules - the TRIPLEO_* chains will be flushed before the ruleset are added. All in one single transaction. Some more information/content: tripleo_nftables role: https://opendev.org/openstack/tripleo-ansible/src/branch/master/tripleo_ans… Doc: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… Debug files available in the CI: log of dropped packets: https://logserver.rdoproject.org/54/31954/87/check/periodic-tripleo-ci-cent… nftables configuration dump: https://logserver.rdoproject.org/54/31954/87/check/periodic-tripleo-ci-cent… nftables configuration: https://logserver.rdoproject.org/54/31954/87/check/periodic-tripleo-ci-cent… All of that can help understanding the potential issues you may encounter. As a side note, we've been testing the whole thing for about a month now, correcting issues, updating the doc and making sure at least all of the current CI jobs (yes: ALL) are green without any weird behavior. A doc has been created in order to list the current state, with what we've seen, what we've done: https://hackmd.io/F0W2gYw_SiaiWkowjFU9cw?view#NFTABLES-testing-results Brace yourself, the change is coming :). But it should be transparent ;). -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

1 0

[publiccloud-sig] Bi-weekly meeting reminder
by Tobias Rydberg 13 Sep '22

13 Sep '22

Hi all, Tomorrow we will have our bi-weekly meeting at 0800 UTC in #openstack-operators. Notes from previous meeting can be found here [0]. Please go in prior to the meeting and vote for for the naming conventions suggested, which you believe are the most important or if you think some of them should not be considered at all. Hope to chat with you tomorrow! [0] https://etherpad.opendev.org/p/publiccloud-sig-meeting BR, Tobias Rydberg

1 0

[ptl][tc][election][adjutant][barbican][OpenStackSDK][OpenStack_Charms][sahara][swift][venus] Leaderless project for 2023.1 cycle
by Ghanshyam Mann 13 Sep '22

13 Sep '22

Hello, As you know, 2023.1 cycle election nomination is ended and we end up with 11 leaderless projects. List is in the etherpad: https://etherpad.opendev.org/p/2023.1-leaderless Out of 11, we have found 4 projects leaders but 7 (in the subject list) projects still need some leaders to volunteer: 1. Adjutant 2. Barbican 3. OpenStackSDK 3. OpenStack_Charms 4. Sahara 5. Swift 6. Venus Please reply here or ping us in #openstack-tc channel if you would like to lead these projects. -gmann

2 4

[cinder][stable] cinder-stable-core additions
by Rajat Dhasmana 13 Sep '22

13 Sep '22

Hi All, After discussing with the current members of the cinder stable core team, I've decided to add the following members to the cinder stable core team. 1) Walter Boring - (Currently cinder core) 2) Sofia Enriquez - (Currently cinder core) Sofia and Walt have been long term contributors in the Cinder project and I'm happy to have them as part of the stable core team. I will proceed with making changes to the stable core team[1]. [1] https://review.opendev.org/admin/groups/1b3ca2faf07b15efff426901a387eb7c914… Thanks and Regards Rajat Dhasmana

1 0

[all][elections][ptl][tc] Conbined PTL/TC antelope cycle Election Voting Kickoff
by Ian Y. Choi 13 Sep '22

13 Sep '22

Polls for PTL and TC elections are now open and will remain open for you to cast your vote until Sep 19, 2022 23:45 UTC. We are selecting 4 TC members, and are having PTL elections for Ironic. Please rank all candidates in your order of preference. You are eligible to vote in the TC election if you are a Foundation individual member[0] that also has committed to any official project team's deliverable repositories[1] over the Sep 17, 2021 00:00 UTC - Sep 07, 2022 00:00 UTC timeframe (Yoga to Zed) or if you are in the list of extra-atcs[2] for any official project team. You are eligible to vote in a PTL election if you are a Foundation individual member[0] and had a commit in one of that team's deliverable repositories[1] over the Sep 17, 2021 00:00 UTC - Sep 07, 2022 00:00 UTC timeframe (Yoga to Zed) or if you are in that team's list of extra-atcs[2]. If you are eligible to vote in an election, you should find your email with a link to the Condorcet page to cast your vote in the inbox of your Gerrit preferred email[3]. What to do if you don't see the email and have a commit in at least one of the projects having an election: * check the trash or spam folders of your gerrit Preferred Email address, in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the project's deliverable repos[0] and email the election officials [4] * requires opt-in to CIVS polling to receive email communications from the voting system [5]. If we can confirm that you are entitled to vote, we will add you to the voters list for the appropriate election. Our democratic process is important to the health of OpenStack, please exercise your right to vote! Candidate statements/platforms can be found linked to Candidate names on this page: https://governance.openstack.org/election/ Happy voting, /Ian, as one of OpenStack Election Officials [0] https://www.openstack.org/community/members/ [1] The list of the repositories eligible for electoral status: https://opendev.org/openstack/governance/src/tag/oct-2022-elections/referen… [2] Look for the extra-atcs element in [1] [3] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your preferred email. That is where the ballot has been sent. [4] https://governance.openstack.org/election/#election-officials [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0304…

1 0

[baremetal-sig][ironic] Future of baremetal-sig
by Jay Faulkner 13 Sep '22

13 Sep '22

Stackers, An item came up in the Ironic meeting today regarding the future of the baremetal sig. Essentially, Arne was doing great work sourcing talks for it, but now he's going to be unable to continue hosting it and proactively sourcing talks. (A seriously big thanks is owed to Arne for doing a great job on this!) This led us to wonder if BM SIG in its current form remains sustainable. Some options we can consider include: - Keep the BM SIG as-is, cancel it months where there's not a talk available. - Change the BM SIG meetings to more of a meetup style for operators to talk about Ironic - Something else entirely we haven't thought about yet. What do you all think? - Jay Faulkner

1 0

OpenInfra Summit Vancouver 2023 Track Chair Nominations Now Open
by Helena Spease 12 Sep '22

12 Sep '22

Hey everyone! Track Chair nominations <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023 <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023>> for the 2023 OpenInfra Summit in Vancouver (June 13-15, 2023) are now open! Track Chairs for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2023 Summit Tracks: 5G/NFV & Edge AI/Machine Learning/HPC CI/CD Container Infrastructure Getting Started Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Hands On Workshops Full track descriptions are available here <https://openinfra.dev/summit/vancouver-2023/summit-tracks/ <https://openinfra.dev/summit/vancouver-2023/summit-tracks/>>. If you’re interested in nominating yourself or someone else to be a member of the Summit Track Chairs for a specific Track, please fill out the nomination form <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023 <https://openinfrafoundation.formstack.com/forms/trackchairnominations2023>>. Nominations will close on October 28th, 2022. Track Chairs selections will occur before we close the Call for Presentations (CFP) so that the Chairs can host office hours to consult on submissions, and help promote the event. CFP will be opening in November, registration <https://openinfrasummit2023.eventbrite.com/ <https://openinfrasummit2023.eventbrite.com/>> and sponsorship <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ <http://openinfra.dev/summit/vancouver-2023/summit-sponsor/>> information are already available. Please email speakersupport(a)openinfra.dev <mailto:speakersupport@openinfra.dev> with any questions or feedback. Cheers, Helena Spease

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Sept 15 at 1500 UTC
by Ghanshyam Mann 12 Sep '22

12 Sep '22

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

1 0

[tc][ptl][election][masakari] I volunteer to become Masakari PTL again
by Radosław Piliszek 12 Sep '22

12 Sep '22

As in the topic - I saw Masakari did not receive a candidate and I don't want to see this project disappear so I volunteer to be the PTL. I don't have any major plans regarding Masakari except for keeping it afloat and working where it works already. Cheers, Radek -yoctozepto

2 1

[horizon][QA][release] Cycle With Intermediary without recent deliverables
by Előd Illés 12 Sep '22

12 Sep '22

Hi, Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest Zed release available on release week. The following deliverables have done a Zed release, but it was not refreshed in the last two months: horizon tempest You should consider making a new one very soon, so that we don't use an outdated version for the final release. Előd Illés irc: elodilles

3 2

[neutron] [ovn] Distributed routing ingress traffic flow
by Roman Pomazanov 12 Sep '22

12 Sep '22

1 0

[monasca][kolla-ansible] Help for a monasca newbie to get metrics for instances needed
by Christian Stelter 12 Sep '22

12 Sep '22

Hi! I'm trying to explore monasca, but I'm bit lost in how to get metrics from a project/tenant collected. I'm using kolla-ansible in my test setup running ubuntu-source images. Ubuntu release is Yoga. Monasca seems to be up and running. I can see the default metrics with a appropriate user in the monasca_control_plane project. cpu.* disk.* io.* load.* mem.* monasca.* net.* ntp.* And I find measurements in the influxdb, but only metrics/measurements for the openstack hypervisor nodes yet. What I'm missing after searching the existing documentation is how I can enable a plugin as for libvirt for example or whatever the recommendation for monitoring the instances is. As I have found the plugins directory on the hypervisors under /etc/kolla/monasca-agent-collector/plugins I thought putting a config file like in the documentation [1] for the libvirt plugin and restart the monasca-agent-collector would be sufficient. But all I got was an error message: 2022-09-11 12:22:26,412 | ERROR | collector | monasca_agent.common.util(util.py:529) | Unable to import check module libvirt.py from checks_d Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.8/site-packages/monasca_agent/common/util.py", line 520, in load_check_directory check_module = load_module('checksd_%s' % check_name, check) File "/var/lib/kolla/venv/lib/python3.8/site-packages/monasca_agent/common/util.py", line 470, in load_module module_spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 848, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/var/lib/kolla/venv/lib/python3.8/site-packages/monasca_agent/common/../collector/checks_d/libvirt.py", line 20, in <module> import libvirt ModuleNotFoundError: No module named 'libvirt' As it seems the plugin system dependencies like libvirt-dev are missing. So I assume I have to rebuild the container myself and/or open an issue on opendev.org. Or is there another way to get metrics for instances? Next question: even if I had a running libvirt plugin. What has to be done to enable another user in a normal tenant project to use these metrics? Just add the monasca-read-only-user to user(s) which shall be enabled to manage alarm definitions, alarms and notifications? Will the tenant then see or at least use the metrics for his (and only his) project? I found a lot of high level documentation, (base) installation instructions, hints for developers on how to extend monasca, but nothing beyond the initial setup for monasca newbies like me. I queried the all-knowing, all-seeing trash heap, mailing lists, and the YT academy already. May be I just missed something. So hints are welcome! BTW. Is the kolla-ansible part of monasca still in active maintenance and development? I stumpled upon the same error as in [2] and I'm getting an HTTP 500 error when trying to open the monitoring overview and is still unassigned. Thanks in advance! Kind regards, Christian Stelter [1] https://github.com/openstack/monasca-agent/blob/master/docs/Libvirt.md#conf… [2] https://bugs.launchpad.net/kolla-ansible/+bug/1967278

2 2

[First Contact][SIG][PTG] Planning October 2022
by Kendall Nelson 12 Sep '22

12 Sep '22

Hello Party People, I started putting together the etherpad[1] for planning our time at the PTG! Add your topics and your name if you plan on attending :) If the time I selected doesn't work for folks, we can book other time (instead or in addition to), I just know historically we have been a mix of Americas/ APAC and so this time block should work for folks. Also, gentle reminder to register if you haven't already - it is free afterall [2]. -Kendall Nelson (diablo_rojo) [1] https://etherpad.opendev.org/p/oct2022-ptg-first-contact [2] https://openinfra-ptg.eventbrite.com/

1 0

[all] GovStack community seeking for infrastructure expertise
by Lueck, Nico GIZ 11 Sep '22

11 Sep '22

Do you believe in the potential of digital public goods for positive impact? Ever wished for more digitally-enabled government services? GovStack [1] is a community-driven initiative on a mission to accelerate the digital transformation of government services in order to better serve citizens - and we want you to join us! We create and maintain an openly licenced blueprint for a modular architecture based on reusable building blocks [2]. Our various working groups work to define the (non-)functional and API specifications for building blocks, leveraging existing standards such as OpenStack. These specifications are then used for implementations in our partner countries across the world, to facilitate the delivery of foundational, life-enhancing services. Learn more about the call for contributions here [3]. We are specifically looking for experts with experience in infrastructure and security. The initiative is founded by the German Federal Ministry for Economic Cooperation and Development, Deutsche Gesellschaft fuer Internationale Zusammenarbeit (GIZ), the Ministry of Foreign Affairs of the Republic of Estonia, the International Telecommunication Union (ITU) and the Digital Impact Alliance. Thank you to the team of the Open Infrastructure Foundation for their support. Also, thank you to the whole community and please feel free to directly contact us. Nico (Lueck) <nico.lueck(a)giz.de> [1] https://www.govstack.global/ [2] https://govstack.gitbook.io/ [3] https://www.govstack.global/call-for-expression-of-interest/ ________________________________ Deutsche Gesellschaft fuer Internationale Zusammenarbeit (GIZ) GmbH; Sitz der Gesellschaft Bonn und Eschborn/Registered offices Bonn and Eschborn, Germany; Registergericht/Registered at Amtsgericht Bonn, Germany; Eintragungs-Nr./Registration no. HRB 18384 und/and Amtsgericht Frankfurt am Main, Germany; Eintragungs-Nr./Registration no. HRB 12394; USt-IdNr./VAT ID no. DE 113891176; Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Jochen Flasbarth; Vorstand/Management Board: Tanja Goenner (Vorstandssprecherin/Chair of the Management Board), Ingrid-Gabriela Hoven, Thorsten Schaefer-Guembel

3 2

[designate] zone sharing between projects and how to create classless PTR
by Tomáš Bredár 10 Sep '22

10 Sep '22

Hi Folks, I have a few questions: 1. Is there a possibility to share DNS zones between tenants? I've found this [1] patchset, but it's not merged yet. 2. Is there a way to create a classless reverse zone? According to [2], it should work. Creating a zone is ok: openstack zone create --email tomas.bredar(a)gmail.com \ --ttl 3600 --description "in-addr.arpa. zone for reverse lookups for e-devel subnet 10.254.226.0/26" \ 0-26.226.254.10.in-addr.arpa. But when I try to add a recordset, I get an error: openstack recordset create --record testvm.bredytest.abc.com. --type PTR --ttl 600 0-26.226.254.10.in-addr.arpa. 1.226.254.10.in-addr.arpa. RecordSet is not contained within it's parent zone I'm using OpenStack Wallaby If this won't work, I'm considering using the neutron integration with external DNS. Thanks for your help Tomas [1] https://review.opendev.org/c/openstack/designate/+/726334 [2] https://docs.openstack.org/designate/latest/user/manage-ptr-records.html

3 4

[manila] Bugsquash postponed by one week
by Carlos Silva 10 Sep '22

10 Sep '22

Hello, Zorillas! I'm sending this email to inform you that the bugsquash we planned for this week will be postponed by one week. We currently have some FFEs and we could use the change owners and reviewers energy to get those changes moving forward. We hope to have the FFE changes merged by the end of this week, so next week we could use some focus time on the bugsquash. Regards, carloss

1 1

[release] Release countdown for week R-3, Sep 12 - 16
by Előd Illés 09 Sep '22

09 Sep '22

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, September 15th, 2022. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/zed branch will be cut. This branch will track the Zed release. Once stable/zed has been created, the master branch will be ready to switch to 2023.1 Antelope development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing Zed plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/zed branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/zed branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be 2023.1 Antelope) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any Zed release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 15th, 2022 (R-3 week) Final RC deadline: September 29th, 2022 (R-1 week) Final Zed release: October 5th, 2022 Virtual PTG: October 17-21, 2022 Előd Illés irc: elodilles

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Sept 9
by Slawek Kaplonski 09 Sep '22

09 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 08. Most of the meeting discussions are summarized in this email. Meeting logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-08-15.00.log.html * Next TC weekly meeting will be on Sept 15 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 14. 2. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[2], four are completed and others items are in-progress. Open Reviews ----------------- * Five open reviews for ongoing activities[3]. 2023.1 cycle Technical Election (TC + PTL) ------------------------------------------------------------- Nomination period is now over. We are currently in the campaign time. Please remember that there is an action required if You want to receive ballot from CIVS. Please check [4] for more details. Define 2023.1 cycle testing runtime ------------------------------------------- Testing runtime for the 2023.1 cycle is up for review [5]. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[6], * gmann created the TC PTG etherpad to collect the topic[7]. * gmann sent an email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[8]. 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[9]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[10][11]. Project updates ------------------- * Switch release management to distributed leadership[12] 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[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-zed-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0304… [5] https://review.opendev.org/c/openstack/governance/+/854375 [6] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [7] https://etherpad.opendev.org/p/tc-2023-1-ptg [8] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [9] https://review.opendev.org/c/openstack/governance/+/836888 [10] https://etherpad.opendev.org/p/zuul-config-error-openstack [11] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [12] https://review.opendev.org/c/openstack/governance/+/855276 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Drivers meeting agenda - 9.09.2022.
by Lajos Katona 09 Sep '22

09 Sep '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFE to discuss: [RFE] OVN support for vnic type virtio-forwarder (#link https://bugs.launchpad.net/neutron/+bug/1988542 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[rabbitmq][kolla-ansible] How to enable rabbitmq plugin via configuration file?
by A Tom 09 Sep '22

09 Sep '22

Hi, I’m trying to enable rabbitmq_tracing plugin in my kolla-ansible. In „typical” installation you have to enable plugin via rabbitmq-plugins enable and (in case of this particular plugin) add directory,username and password to rabbitmq.conf. These changes (adding username,password and directory) are obvious, but how do I enable particular plugin by kolla-ansible configuration file? Should I put something in globals.yaml? Best regards Adam Tomas

1 0

[baremetal-sig][ironic] No meeting in September
by Iury Gregory 08 Sep '22

08 Sep '22

Hello everyone, This email is just to let you know that we won't have any presentation/meeting for the Baremetal-sig this month. -- *Att[]'s* *Iury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Ironic PTL * *Senior Software Engineer at Red Hat Brazil* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 0

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations End
by Amy Marrich 08 Sep '22

08 Sep '22

Please note we are in the process of adding a standalone TC Campaigning period before opening the TC election for voting. This will allow the candidates to answer any questions and also people to opt-in to the CIVS system before we start the voting process. Pending a patch being added and merged we are looking at starting the voting early to mid next week. Thanks, Amy +++++++++++++++++++++++++++++++++++++++++++++++++++ The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 11 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Adjutant, Barbican, Keystone, Masakari, OpenStackSDK, OpenStack_Charms, Sahara, Senlin, Swift, Venus, Zun -- TC Election Details -- There are 1 projects that will have elections: Ironic. Now begins the campaigning period where candidates and electorate may debate their statements. Polling will start Sep 07, 2022 23:45 UTC. Thank you, [0] https://governance.openstack.org/election/#antelope-ptl-candidates [1] https://governance.openstack.org/election/#antelope-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

2 1

Retirement process openstack/training-labs
by gaspard varennes 08 Sep '22

08 Sep '22

Hello, I found on https://lists.openstack.org/pipermail/openstack-discuss/2021-October/025586… an email saying "If you are using it for your training please reply to this email pr ping us on #openstack-tc IRC OFTC channel otherwise we will start the retirement process." We (a digital school in France) are still using your training labs, so we write you this email. But we think the retirement process is already done because last commit of the repo https://opendev.org/openstack/training-labs.git is almost empty. I presume (but I'm not sure because I'm not a tech guy) that we still can use the previous version of the repo https://opendev.org/openstack/training-labs/src/commit/2585b12b879bae4c3fe4… to train on the labs, am I right? Thank you very much for your time and consideration. Gaspard VARENNES Pedagogical Engineer Content Excellency Department Epitech LILLE 5/9 rue du palais Rihour 59000 LILLE 06 69 33 83 30

2 1

[neutron] [openvswich-agent] Driver for security groups
by ETP 08 Sep '22

08 Sep '22

Hi, what is the recommended openvswich agent driver for security groups? Two options on my table are now OVS native firewall driver vs. OVSHybridIptablesFirewall driver Br, - Eki -

3 2

[elections][Keystone] PTL Candidacy for Antelope
by Dave Wilde 07 Sep '22

07 Sep '22

Hello all, I would like to let you know that I will be running for the PTL of the Keystone project for the Antelope cycle. I have been working closely with the current PTL and core reviewers on our initiatives to improve the speed at which we review code submissions and get things merged. I would like to continue focusing on this and continue to build momentum. I look forward to contributing back to the community and Keystone in general and would like to thank Douglas Mendizábal for his work and leadership. Thank you, -- /Dave

1 0

Join the OpenStack Community in Vancouver for the OpenInfra Summit!
by Helena Spease 07 Sep '22

07 Sep '22

Hi Everyone, Registration and sponsorships for the OpenInfra Summit Vancouver [1] are now open! This is your chance to collaborate directly with the people building and running OpenStack. Mark your calendars for June 13-15, 2023 and register early [2] to save your seat! Find information on sponsorships[3], the Summit travel support program[4], visa requirements[5], and track chair nominations[6]. Stay tuned for November when the Call for Presentations opens! Cheers, Helena [1] https://openinfra.dev/summit/vancouver-2023 [2] https://openinfrasummit2023.eventbrite.com/ [3] http://openinfra.dev/summit/vancouver-2023/summit-sponsor/ [4] https://openinfrafoundation.formstack.com/forms/openinfra_tsp [5] https://openinfrafoundation.formstack.com/forms/visa_yvrsummit2023 [6] https://openinfrafoundation.formstack.com/forms/trackchairnominations2023

1 0

Designate Installation in Openstack
by Adivya Singh 07 Sep '22

07 Sep '22

Hi Team, Any idea, what user variables we need to create in user_variables, for it to pick in Openstack Configuration using ansible. Regards Adivya Singh

2 1

[elections][tc] I'm running for TC
by Jay Faulkner 07 Sep '22

07 Sep '22

Hello, I wanted to announce I'm running for TC in the upcoming election. Please take a look at my candidate statement if you want some insight into my motivations and how I'd approach the position: https://opendev.org/openstack/election/raw/branch/master/candidates/antelop… . If you have any questions for me, feel free to ask them here. Thanks, Jay Faulkner

1 0

[oslo][tooz] Feature Freeze exception request
by Alan Bishop 07 Sep '22

07 Sep '22

I'd like to request an exception for https://review.opendev.org/c/openstack/releases/+/856128. <https://review.opendev.org/710539> This patch proposes a new tooz release for the purpose of picking up [1], which fixes a bug [2] (it's not a feature, per se) that otherwise prevents tooz's etcd3gw driver from working with recent versions of etcd. The issue was initially observed back in 2020 [3]. [1] https://review.opendev.org/c/openstack/tooz/+/827492 [2] https://bugs.launchpad.net/python-tooz/+bug/1983668 [3] https://github.com/dims/etcd3-gateway/issues/41#issuecomment-673558108 Thank you for your consideration, Alan Bishop (abishop)

2 1

[election][Glance] PTL Candidacy for Antelope
by Pranali Deore 07 Sep '22

07 Sep '22

Hello everyone, I would like to let you know that I will be PTL of Glance project for the Antelope cycle. I have been working closely with the previous PTL, Abhishek, since last cycle and I am hoping to contribute back to the community as a PTL while following his excellent example. The following will be my goals for Antelope cycle: 1. Bridge gap between python-glanceclient and openstackclient The CLI support for all glance APIS is already there in GlanceClient and the similar CLI support we need to have in OpenstackClient for the missing Glance APIs in this upcoming cycle. 2. Default Glance to configure multiple stores Glance has deprecated single stores configuration since Stein cycle and will remove the support of the same in the upcoming cycle. 3. Secure RBAC In Xena we have managed to move all policy checks to API layer and implemented project scope of metadef APIs. As per the revised community goal, in zed cycle we have made all policy rules set scope_types=['project'] for all project resources that have already implemented scope. Now we need to have manager role support once it's fully implemented in Keystone. 4. Community priorities Whatever community goals put forward by TC, as a PTL of Glance project will want to adopt these as a priority for the Antelope cycle. 5. Other As we are very short team at this moment, I would like to put some efforts in attracting some contributors, help them to understand how Glance functions and encourage them to contribute for Glance. Looking at how Abhishek, Erno and Brian have steadied the ship, I know it's a big task and with their help I will do my best not to fail the expectations. Thank you for consideration, Pranali Deore (pdeore)

4 3

[cinder] Bug Report - 08-31-2022 - 09-07-2022
by Sofia Enriquez 07 Sep '22

07 Sep '22

This is a bug report from 08-31-2022 to 09-07-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1988317 "Remove IET iSCSI target." Unassigned. Wishlist - https://bugs.launchpad.net/cinder/+bug/1988803 "With image-volume cache enabled backend, volume creation for a smaller volume than image-volume cache has the same size of the image-volume cache." Unassigned. Cheers, Sofia -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[DIB][diskimage-builder] Rocky Linux image build method
by Pierre Riteau 07 Sep '22

07 Sep '22

Hello, I am curious about the choice of providing only a rocky-container element in DIB, which works differently to the centos element, which uses cloud images. It makes it hard to produce working images for VMs or bare metal, as various packages that would normally be installed are missing, such as cloud-utils-growpart or openssh-server. See the kickstarts for reference [1] [2]. It seems to also occasionally cause complex failures such as the one that rendered Rocky Linux 8 images unbootable last week [3]. I am guessing this wouldn't have happened had the build been from a cloud image. Would the DIB community be open to also have a rocky element using GenericCloud images, like centos? Thanks, Pierre Riteau (priteau) [1] https://git.rockylinux.org/rocky/kickstarts/-/blob/r8/Rocky-8-Container-Bas… [2] https://git.rockylinux.org/rocky/kickstarts/-/blob/r8/Rocky-8-GenericCloud.… [3] https://review.opendev.org/c/openstack/diskimage-builder/+/851687

6 6

[election][Requirements] PTL candidacy
by Matthew Thode 07 Sep '22

07 Sep '22

I would like to announce my candidacy for PTL of the Requirements project. The project was recently updated to allow multiple PTLs this cycle and I imagine tony will be my better half. The following will be my goals for the cycle, in order of importance: 1. The primary goal is to keep a tight rein on global-requirements and upper-constraints updates. (Keep things working well) 2. Un-cap requirements where possible. 3. Fix some automation of generate contstraints (pkg-resources being added and setuptools being dropped) 4. Audit global-requirements and upper-constraints for redundancies. One of the rules we have for new entrants to global-requirements and/or upper-constraints is that they be non-redundant. Keeping that rule in mind, audit the list of requirements for possible redundancies and if possible, reduce the number of requirements we manage. 5. introduce better python version range support into constraints. An image with all the python versions we want is likely needed. I look forward to continue working with you in this cycle, as your PTL or not. Thanks for your time, -- Matthew Thode

3 5

[election][Ironic] PTL Candidacy
by Jay Faulkner 07 Sep '22

07 Sep '22

Hi all, I wanted to let you know I'm running for PTL of Ironic for the Antelope cycle. You can read my candidate statement[1] for full information, but feel free to ask me any questions you'd like here if you have them. Thanks, Jay Faulkner [1] - https://governance.openstack.org/election/#antelope-ptl-candidates

1 0

[horizon] instance filtering dropdown default
by John Ratliff 06 Sep '22

06 Sep '22

When I load certain pages in horizon, like the compute instances page, the default filter is "Instance ID". How can I change the default to "Instance Name" instead? Thanks. --John Ratliff

1 0

Horizon
by Atharva Dhanwate 06 Sep '22

06 Sep '22

4 3

[neutron] Bug deputy report for week of August 29th
by Brian Haley 06 Sep '22

06 Sep '22

Hi, I was Neutron bug deputy last week. Below is a short summary about the reported bugs. BTW, you don't have to wait for me to be deputy to file all your bugs :) -Brian Critical bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1988026 - Neutron should not create security group with project==None - Talked to Security Response Team and they decided to add a tracker to it since the quota system doesn't seem to limit how many random default security groups one can create. - https://review.opendev.org/c/openstack/neutron/+/855580 High bugs --------- * https://bugs.launchpad.net/neutron/+bug/1988037 - Neutron does not find an existing route - https://review.opendev.org/c/openstack/neutron/+/854986 * https://bugs.launchpad.net/neutron/+bug/1988296 - neutron-lib pep8 CI failing with pylint==2.15.0 - https://review.opendev.org/c/openstack/neutron-lib/+/855061 Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1988069 - neutron-dhcp-agent fails when small tenant network mtu is set - Could not reproduce issue reported with MTU as 70 for network, only saw that instances could not do DHCP with it so small. Looks like a potential kernel bug since this works on later versions. * https://bugs.launchpad.net/neutron/+bug/1988199 - https://review.opendev.org/c/openstack/neutron/+/855257 * https://bugs.launchpad.net/neutron/+bug/1988220 - large unused dependency ncclient + paramiko in os-ken - Assigned to Rodolfo since he made change to remove nose https://review.opendev.org/c/openstack/os-ken/+/850631 - closed (won't-fix) as ncclient is required for os-ken, just wasn't explicitly called-out in requirements. * https://bugs.launchpad.net/neutron/+bug/1988549 - Trunk status is down after a live-migration - Arnau Verdaguer took ownership Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/1988298 - [neutron-lib] "registry.has_resource_extenders" is the same as "resource_extend.has_resource_extenders" - Needs owner * https://bugs.launchpad.net/neutron/+bug/1586731 - restart neutron ovs agent will leave the fanout queue behind - Old bug re-opened - Partial patch posted, asked commenter to submit to master Misc bugs --------- * https://bugs.launchpad.net/neutron/+bug/1988281 - neutron dhcp agent state not consistent with real status - After a restart, the agent status is UP even though it is still doing a full-sync operation, is there a way to signify this status? See bug for further discussion. * https://bugs.launchpad.net/neutron/+bug/1988382 - L3 agent(agent_mode=dvr_snat) restart, fip namespace removed rfp-port, resulting in fip not connecting - Failure is seen in code from 2019, asked submitter to try tip of stable/victoria and reproduce since there have been fixed in this area since then. Wishlist bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1988077 - Noisy neutron-openvswitch-agent service - There are some deployments that wanted more logging which is why the agent is more verbose. Will have to have a further discussion to see if there is a way to address concern of log being noisy, besides using more aggressive log rotation as suggested. * https://bugs.launchpad.net/neutron/+bug/1988188 - Create an automated tool to retrieve the needed OVS version depending on the OVN one - Suggested by Rodolfo to help improve gate dependencies. * https://bugs.launchpad.net/neutron/+bug/1988542 - [RFE] OVN support for vnic type virtio-forwarder - Will need to add to Drivers meeting agenda

1 0

Two containers fail
by Derek O keeffe 06 Sep '22

06 Sep '22

Hi, I recently successfully installed OSA and I am now trying to install it again from scratch with all the configuration changes I needed in place. Unfortunately this time around it is failing on setup_hosts.yml here: TASK [lxc_container_create : Create container (dir)] ******************************************************************ok: [infra1_memcached_container-b92f4db7 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_rabbit_mq_container-d286a482 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_utility_container-05f756fc -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_galera_container-5beef059 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_aodh_container-639f5ad8 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_neutron_server_container-f67e972d -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_horizon_container-dfeaa0dc -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_placement_container-350e4ede -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_heat_api_container-82cbd764 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_nova_api_container-b30c38d1 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_repo_container-f16e50a9 -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_ceilometer_central_container-910a888f -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_keystone_container-32dcd68b -> infra1(CONTROLLER_IP_ADDRESS)]ok: [infra1_gnocchi_container-30ccb451 -> infra1(CONTROLLER_IP_ADDRESS)]fatal: [infra1_cinder_api_container-840a18bb -> infra1(CONTROLLER_IP_ADDRESS)]: FAILED! => {"changed": false, "error": "Failed to start container [ infra1_cinder_api_container-840a18bb ]", "lxc_container": {"init_pid": -1, "interfaces": [], "ips": [], "name": "infra1_cinder_api_container-840a18bb", "state": "stopped"}, "msg": "The container [ infra1_cinder_api_container-840a18bb ] failed to start. Check to lxc is available and that the container is in a functional state.", "rc": 1}fatal: [infra1_glance_container-b50e16a6 -> infra1(CONTROLLER_IP_ADDRESS)]: FAILED! => {"changed": false, "error": "Failed to start container [ infra1_glance_container-b50e16a6 ]", "lxc_container": {"init_pid": -1, "interfaces": [], "ips": [], "name": "infra1_glance_container-b50e16a6", "state": "stopped"}, "msg": "The container [ infra1_glance_container-b50e16a6 ] failed to start. Check to lxc is available and that the container is in a functional state.", "rc": 1} I don't understand how 14 containers are fine (can be attached to and commands run through lxc-attach) and 2 containers are failing. I have a deploy host, controller and two computes all with a fresh install of Ubuntu 20.04. The bootstrap_ansible script ran fine on the deploy host and the setup_hosts playbook ran through fully as after the above it skipped cinder and glance containers every where else. Can anybody please point me in the direction of getting more info or a possible cause. Thanks in advance.

2 2

[Octavia][release] Requesting exception for python-octaviaclient
by Gregory Thiemonge 06 Sep '22

06 Sep '22

Hi Folks, I am requesting a Feature Freeze Exception for the release of python-octaviaclient for Zed. One patch [0] was merged at the end of last week in python-octaviaclient (we were waiting for the related feature to get merged in the octavia repo) and a new release (3.1.0) was proposed for Zed in the release repo [1], but it wasn't merged in time. We would like to get the approval for this new release so we could base the stable/zed branch on this new tag (we would need to update [2]). Thanks, Gregory [0] https://review.opendev.org/c/openstack/python-octaviaclient/+/664473 [1] https://review.opendev.org/c/openstack/releases/+/855675 [2] https://review.opendev.org/c/openstack/releases/+/855912

2 1

[election][tripleo] PTL Candidacy for Antelope cycle
by Rabi Mishra 06 Sep '22

06 Sep '22

Hi All, I would like to nominate myself for Antelope cycle TripleO PTL. As some of you would know, I have been part of the OpenStack community for a long time and have been a core contributor for TripleO and Heat. I have also served as Heat PTL for Ocata cycle. James has done a great job as PTL for the last few cycles. I would like to take the opportunity to thank him for all his effort and we all would agree that he needs a well deserved break. I am looking forward to take the opportunity to help the community to achieve some of the already planned goals and in-progress workstreams like standalone roles, multi-rhel and other challenges that come along the way. Also, as before, our focus would continue to be on review prioritization, in progress work streams and collaboration on common priorities. Regards, Rabi Mishra

9 8

[nova]How to confirm whether a arm64 node supports hardware acceleration for virtual machines
by 韩光宇 06 Sep '22

06 Sep '22

Hello, I see `egrep -c '(vmx|svm)' /proc/cpuinfo` in nova install documentation[1]. It can be used to confirm whether a node supports hardware acceleration for virtual machines on x86 architecture. But it is not applicable in the ARM architecture. Do we have an officially recommended method to confirm in ARM architecture? Thanks, Han Guangyu [1]https://docs.openstack.org/nova/latest/install/compute-install-rdo.html#f…

3 2

[oslo][relmgmt][taskflow][nova] fasteners.ReaderWriterLock and oslo.concurrency's fair lock is broken if used in eventlet
by Balazs Gibizer 06 Sep '22

06 Sep '22

Hi, It is hard to properly figure out which OpenStack project is affected exactly. But I want to give a heads up. If the following is true for your project then you are affected: * using eventlet and * using oslo.concurrency fair internal lock (external lock or non fair locks are not affected) or using fasteners.ReaderWriterLock directly. I know that nova is affected and based on code search taskflow is affected at least. The oslo.concurrency's fair lock uses fasteners.ReaderWriterLock[1]. The fasteners.ReaderWriterLock relies on threading.current_thread to identify a thread and decide if a thread already has a lock and therefore can reenter the lock. However in an eventlet monkey patched environment, a thread that is created with eventlet.spawn_n() or the patched threading.Thread() the threading.current_thread call does not return an eventlet unique ID. This causes that the lock can be reentered from multiple eventlets at the same time. We have 4 ways forward: 0) Fix eventlet. There is an open issue in eventlet[3] for this open since October 2021. Based on the ticket this direction does not seems to feasible. 1) Sean recently opened an issue[4] on fasteners to restore a previously existing workaround that could fix our issues. If an new fasteners lib is released with the workaround[5] then at least oslo.concurrency requirements needs to be bumped and a new oslo release is pushed. 2) If the fasteners' maintainer does not accept [4][5] in time then I have an oslo.concurrency patch[6] that implements a workaround in oslo. This also requires a new olso.concurrency release. Also this means that projects that are using fasteners.ReaderWriterLock directly need to re-implement the fix locally. 3) If all odds fails I have a nova only patch[7] that implements the workaround locally in nova. Note that this issue is present in stable/yoga and on master. On stable/xena we uses fasteners < 0.15.0 which is not affected. Cheers, gibi [1] https://github.com/openstack/oslo.concurrency/blob/052b2f23572900601b0f4138… [2] https://bugs.launchpad.net/oslo.concurrency/+bug/1988311 [3] https://github.com/eventlet/eventlet/issues/731 [4] https://github.com/harlowja/fasteners/issues/96 [5] https://github.com/harlowja/fasteners/pull/97 [6] https://review.opendev.org/q/topic:bug/1988311+project:openstack/oslo.concu… [7] https://review.opendev.org/q/topic:bug/1988311+project:openstack/nova

2 2

[ops][largescale-sig] rabbitmq and the durability of reply_ queues
by Felix Hüttner 06 Sep '22

06 Sep '22

Hi everyone, the largescale-sig currently recommends the following rabbitmq policy [1]: '^(?!(amq\.)|(.*_fanout_)|(reply_)).*'. If I found the history of this setting correctly, it resulted from this mailinglist thread [2] which came to the conclusion: > * use durable-queue and replication for long-running queues/exchanges > * use non-durable-queue without replication for short (fanout, reply_) queues However I am unsure if reply_ queues are actually shorted lived than the "long-running" ones. If we take the example of the cinder-scheduler we have the following queues: * cinder-scheduler: Tied to the lifetime of the whole cinder-scheduler cluster; currently durable + replicated * cinder-scheduler.myhostname: Tied to the lifetime of the cinder-scheduler service, but not removed when the service stops; currently durable + replicated * cinder-scheduler_fanout_somerandomid: Tied to the lifetime of the cinder-scheduler service, but removed when the service stops; currently neither durable nor replicated * reply_somerandomid: Tied to the lifetime of the cinder-scheduler service, but removed when the service stops; currently neither durable nor replicated If I read got all of the above correctly then reply_ and fanout queues are actually not shorter lived than the normal queue to send requests to that service. The only difference is that we remove them when the service itself stops. Therefor I want to propose the question if we should not also make these queues durable and replicated. Thank you [1]: https://docs.openstack.org/large-scale/other/rabbitmq.html#pattern [2]: https://lists.openstack.org/pipermail/openstack-discuss/2020-August/016562.… -- Felix Huettner Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur für die Verwertung durch den vorgesehenen Empfänger bestimmt. Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den Absender bitte unverzüglich in Kenntnis und löschen diese E Mail. Hinweise zum Datenschutz finden Sie hier<https://www.datenschutz.schwarz>.

2 2

[puppet] Gate blocker: enabling neutron-ovn-metadata-agent consistently fails in CentOS Stream 9
by Takashi Kajinami 06 Sep '22

06 Sep '22

Hello, Currently we are facing a problem with integration jobs with ml2+ovn in CentOS Stream 9 ( puppet-openstack-integration-7-scenario00[35]-tempest-centos-9-stream ) and these jobs are consistently failing. Details can be found in https://launchpad.net/bugs/1988552 . I've already reported the issue to RDO and CentOS Stream to get their help while I'm also implementing a temporary workaround. https://review.opendev.org/c/openstack/puppet-openstack-integration/+/855617 Please avoid rechecking/approving patches until these jobs are fixed. Thank you, Takashi

1 1

Re: Secret getPayload() openstack4j
by Srinivasan T 06 Sep '22

06 Sep '22

Hi, Does anyone have any idea on this? >From the REST API documentation, it seems GET /v1/secret/{uuid} may not fetch the payload and we need to use a different endpoint GET /v1/secret/{uuid}/payload . Is there any equivalent Java API (openstack4j) for this? Regards, Srini On Mon, Sep 5, 2022 at 11:08 PM Srinivasan T <tsrini.alr(a)gmail.com> wrote: > Thanks Artem for the response. > > I face the same issue when using the below version as well (snippet from > pom.xml), > > <modelVersion>4.0.0</modelVersion> > <artifactId>openstack4j-core</artifactId> > <name>OpenStack4j Core</name> > <description>OpenStack Java API</description> > <url>http://github.com/openstack4j/openstack4j/</url> > > Regards, > Srini > > On Mon, Sep 5, 2022 at 9:48 PM Artem Goncharov <artem.goncharov(a)gmail.com> > wrote: > >> Hi, >> >> The library is not an official OpenStack delivery. I guess nobody here >> would be able to give you proper suggestion. Moreover it does not look like >> being actively maintained. >> >> Regards, >> Artem >> >> On 5. Sep 2022, at 18:03, Srinivasan T <tsrini.alr(a)gmail.com> wrote: >> >> Hi, >> >> I'm unable to get the secret's payload from openstack4j, it always >> returns null. >> >> Secret secret = os.barbican().secrets().get("19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60"); >> secret.getPayload(); //Always returns null >> >> The same works when using the OpenStack CLI, >> >> openstack secret get --payload_content_type 'application/octet-stream' --file secret-payload http://x.x.x.x:9311/v1/secrets/19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60 >> >> I'm using the below OpenStack4j version, >> >> Bundle-Name: OpenStack4j Core >> >> Bundle-Version: 3.6.0 >> >> OpenStack is in Queens version. >> >> Let me know if someone can help on this. >> Regards, >> Srini >> >> >>

1 0

Kolla-ansible all-in-one and Hyper Converged solution
by KK CHN 06 Sep '22

06 Sep '22

Hi, [1 ] I am aiming for a prototype of HCI on a DELL ( R650 2 CPU and 40 cores . 2.4 TB) server machine. The Operating System choice is Debian 10. [2] Right now I am successful in Kolla-ansible all-in-one installation of Wallaby/stable on a Debian 10 Virtual machine with the default configs enabled as in the documentation " https://docs.openstack.org/project-deploy-guide/kolla-ansible/wallaby/uicks… " in Virtualenv setup. Able to get the horizon dashboard with the default services enabled and created and tested the cirros VM launching .. working fine. [3 ] I have to repeat the same all-in-one deployment on the physical machine as in [1] with the default configs and then convert it as an HCI node. What all features do I need to configure / enable in all-in-on / globals.yml to convert this box as a working HCI node ? Any hints / directives for the essential configurations needed for this server box to convert it as an HCI node are most welcome. kindly shed some light on this and any reference documents/URLs to do this ? Thank you, Krish

5 5

Microstack - VM networking & installation probs
by Tim Kahlke 06 Sep '22

06 Sep '22

Hi, I tried to install microstack 245 via Canonical and am running into the “old” VM-can’t-connect-external-network problem. OS: Ubuntu 20.04 Microstack v245 Install seems to have worked ok using sudo snap install microstack --beta. However, journalctl -xe shows ovsdb-server[83528]: ovs|26322|socket_util|ERR|6642:0.0.0.0: bind: Address already in use But not sure if that’s related or not. Network setup is the default, i.e., external 10.20.20.0/24 and internal 192.168.1.0/24. From the host machine I can ping the VMs and vice versa, but I can’t get past the host from the VM. I tried to apply some of the solutions I found on the web, so far without success. This one seems to work for people but my microstack doesn’t seem to have the ovs-vsctl command anywhere. Any suggestions would be much appreciated. Tim

2 1

[manila] LVM shares are unmounted on reboot
by Vaibhav 06 Sep '22

06 Sep '22

Dear All, One of the host running Manila-share service has rebooted. After the reboot the LVMs are not mounted on the Manila mount points. I use LVM Driver with DHSS=False. default_share_type = default_share_type share_name_template = manila-%s rootwrap_config = /etc/manila/rootwrap.conf api_paste_config = /etc/manila/api-paste.ini auth_strategy = keystone my_ip=192.168.82.2 enabled_share_backends = lvm enabled_share_protocols = NFS state_path=/var/lib/manila [lvm] share_backend_name = LVM share_driver = manila.share.drivers.lvm.LVMShareDriver driver_handles_share_servers = False lvm_share_volume_group = VGZunManila lvm_share_export_ips = 192.168.82.2 lvm_share_export_root = $state_path/mnt After the reboot LVMs are there but they are mounted on their respective share location. Any way to solve this and this to be done automatically? Regards, Vaibhav

2 2

[all][elections][ptl][tc] Combined PTL/TC antelope cycle Election Nominations Last Days - FINAL REMINDER
by Amy Marrich 05 Sep '22

05 Sep '22

This is your last reminder for the election, I know the US , CA, and a few other countries are on holiday today. Please also read Jeremy's early email about the TC seats and governance. Thank, Amy\ ----------------------------------------------- A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Sep 07, 2022 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2022-08-24 23:45:00 UTC Nominations end @ 2022-09-07 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 2 days, 4:16:33 Nominations progress : 84.44% --------------------------------------------------- Projects[1] : 52 Projects with candidates : 35 ( 67.31%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 17 (Adjutant Barbican Keystone Masakari Mistral OpenStackSDK OpenStack_Charms Openstack_Chef Oslo Release_Management Requirements Sahara Senlin Skyline Swift Venus Zun) =================================================== Stats gathered @ 2022-09-05 19:28:27 UTC This means that with approximately 2 days left, 17 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. Thank you, [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

1 0

[neutron] Team meeting on Sept. 6 cancelled
by Lajos Katona 05 Sep '22

05 Sep '22

Hi, Sorry for late mail, but tomorrow I can't drive the team meeting, so I have to cancel it. I will be otherwise available tomorrow (except around the meeting time), so you can reach me on neutron channel for example. Lajos Katona (lajoskatona)

1 0

Error During installation devstack ModuleNotFoundError: No module named 'neutron'
by mahdi n 05 Sep '22

05 Sep '22

I was installing DevStack on Ubuntu 20.04 when I encountered this error It says that the Neutron module was not found while neutron is installed ++lib/neutron_plugins/ovn_agent:filter_network_api_extensions:439 > /usr/local/bin/python3.8 -c 'from neutron.common.ovn import extensions ;\ > > print(",".join(extensions.ML2_SUPPORTED_API_EXTENSIONS)) > ' > Traceback (most recent call last): > > File "<string>", line 1, in <module> > > ModuleNotFoundError: No module named 'neutron' > > +lib/neutron_plugins/ovn_agent:filter_network_api_extensions:439 > >

3 2

[all][election][tc] TC election at risk of single-employer majority
by Jeremy Stanley 05 Sep '22

05 Sep '22

The extended nomination period for the upcoming TC election closes in just over two days. We need to elect people to fill 4 of the 9 seats on the TC during this round. We currently have just enough candidates to fill the open seats, but in so doing we would end up with a majority of the TC members employed by the same company. Appendix 4 of the bylaws of the Open Infrastructure Foundation, the Technical Committee Member Policy[*], states: > In the event of a Technical Committee election that would result > in half or more of the members of the Technical Committee being > Affiliated, the Board of Directors may defer the effective date of > office of the newly elected Technical Committee members who are > Affiliated for a period not to exceed thirty (30) days after a > resolution by the Board of Directors approving such deferral. The > Board of Directors must pass such resolution within thirty (30) > days of the notice of election results from the Technical > Committee. During such period of deferral, the Technical Committee > and the Board of Directors shall work to resolve the issue by > agreement among themselves, such as by a resignation of one or > more Technical Committee members or having the Individual Member > with the next highest number of votes become a member of the > Technical Committee. If the Technical Committee and the Board of > Directors are not able to agree on a resolution within such thirty > (30) day period, the Board of Directors may require another > election for such positions. In order to avoid this outcome, we need additional nominees with a variety of affiliations immediately. If you've considered running for a seat on the OpenStack TC before, now is definitely the time. Please see earlier announcements[**] from the election officials for details on how to submit your nomination. Thanks! [*] https://openinfra.dev/legal/openstack-technical-committee-member-policy [**] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030094.… https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030241.… -- Jeremy Stanley

1 0

Secret getPayload() openstack4j
by Srinivasan T 05 Sep '22

05 Sep '22

Hi, I'm unable to get the secret's payload from openstack4j, it always returns null. Secret secret = os.barbican().secrets().get("19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60"); secret.getPayload(); //Always returns null The same works when using the OpenStack CLI, openstack secret get --payload_content_type 'application/octet-stream' --file secret-payload http://x.x.x.x:9311/v1/secrets/19cbc4e8-cd06-450b-aa5d-2a4d20bf7d60 I'm using the below OpenStack4j version, Bundle-Name: OpenStack4j Core Bundle-Version: 3.6.0 OpenStack is in Queens version. Let me know if someone can help on this. Regards, Srini

2 1

[adjutant][magnum][mistral][sahara][watcher][zaqar][tc] broken gate for deliverables
by Előd Illés 05 Sep '22

05 Sep '22

Hi, Now that we have passed Zed-3 milestone, Release team starts to check the health of deliverables via their gate healthiness. The 1st round of checks showed that the following deliverables seem to have blocked gates: python-adjutantclient [1] python-magnumclient [2] python-mistralclient [3] python-saharaclient [4] python-watcherclient [5] python-zaqarclient [6] We are asking the teams to fix their gates and propose a release after it is fixed as soon as possible, otherwise these deliverables might not be part of the official Zed release. [1] https://review.opendev.org/c/openstack/python-adjutantclient/+/855763 [2] https://review.opendev.org/c/openstack/python-magnumclient/+/855778 [3] https://review.opendev.org/c/openstack/python-mistralclient/+/855781 [4] https://review.opendev.org/c/openstack/python-zaqarclient/+/855796 [5] https://review.opendev.org/c/openstack/python-watcherclient/+/855795 [6] https://review.opendev.org/c/openstack/python-saharaclient/+/855787 Thanks, Előd Illés irc: elodilles

2 1

http proxy support
by Oliver Weinmann 02 Sep '22

02 Sep '22

Hi, I was wondering if there is a way to set a http proxy in kolla-ansible during deployment / update etc. Today I wanted to pull new containers and this saturates our internet connection. What we usually do is have machine that massively download stuff from the internet use a squid proxy that throttles their bandwidth. I found the following feature request: https://bugs.launchpad.net/kolla-ansible/+bug/1829586 And it seems some work had been done, but I can't seem to find any info if the change really made it into production: https://review.opendev.org/c/openstack/kolla-ansible/+/692006/ Any help or hints are highly appreciated. Cheers, Oliver

2 4

[all][tc] What's happening in Technical Committee: summary 2022 Sept 2: Reading: 5 min
by Ghanshyam Mann 02 Sep '22

02 Sep '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 01. Most of the meeting discussions are summarized in this email. Meeting full recording is available @ https://www.youtube.com/watch?v=WDfOx1m-wog and summary logs are available @https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-01-15.01.log.html * Next TC weekly meeting will be on Sept 08 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Sept 07. 2. What we completed this week: ========================= * Appointed Dale Smith as Adjutant PTL for Zed cycle[2] * Switched requirements to distributed leadership [3] * Added Exception for the combined 2023.1(Antelope) elections [4] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[5], four are completed and others items are in-progress. Open Reviews ----------------- * Four open reviews for ongoing activities[6]. 2023.1 cycle Technical Election (TC + PTL) planning ------------------------------------------------------------- By considering the holiday weeks, we decided to extend the nomination by a week[7]. The new deadline for nomination is Sept 7 [8]. We request you not to delay your nomination for PTL or TC. Define 2023.1 cycle testing runtime ------------------------------------------- Testing runtime for the 2023.1 cycle is up for review [9]. 2023.1 cycle TC PTG planning ------------------------------------ Updates on PTG planning: * "TC + Leader interaction" sessions is scheduled for Oct 17 Monday 15-17 UTC[10], * I have created the TC PTG etherpad to collect the topic[11]. * I sent email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[12] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[13]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[14]15]. Project updates ------------------- * Switch release management to distributed leadership[16] 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[17]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [18] 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/+/849606 [3] https://review.opendev.org/c/openstack/governance/+/854685 [4] https://review.opendev.org/c/openstack/governance/+/854624 [5] https://etherpad.opendev.org/p/tc-zed-tracker [6] https://review.opendev.org/q/projects:openstack/governance+status:open [7] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030241.… [8] https://governance.openstack.org/election/ [9] https://review.opendev.org/c/openstack/governance/+/854375 [10] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [11] https://etherpad.opendev.org/p/tc-2023-1-ptg [12] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [13] https://review.opendev.org/c/openstack/governance/+/836888 [14] https://etherpad.opendev.org/p/zuul-config-error-openstack [15] http://lists.openstack.org/pipermail/openstack-discuss/2022-May/028603.html [16] https://review.opendev.org/c/openstack/governance/+/855276 [17] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [18] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[tc][ptl] TC + Community Leaders interaction in 2023.1 Antelope Virtual PTG
by Ghanshyam Mann 02 Sep '22

02 Sep '22

Hello Everyone, We had successful TC+Community leaders interaction sessions in the last couple of PTG, and we will continue the same for 2023.1 cycle PTG also. I have created the poll to select the best suitable time. It will be for two hours (single or two sessions) either on Monday or Tuesday. Please add your preference in the below doodle poll (including TC members): - https://framadate.org/zsOqRxfVcmtjaPBC Also, I have created the below etherpad with the draft agenda, If you as PTL or project representatives or SIG Chair and would like to attend this session, please add your name: - https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 -gmann

1 1

[tripleo] gate blocker tripleo-ci-centos-9-content-provider
by Chandan Kumar 02 Sep '22

02 Sep '22

Hello tripleo, Please hold your recheck on master tripleo branch, we have a gate blocker for tripleo-ci-centos-9-content-provider. https://bugs.launchpad.net/tripleo/+bug/1988514 The team is currently working on fixing it. With Regards, Chandan Kumar

2 1

[PTL][release] Zed Cycle Highlights
by Előd Illés 02 Sep '22

02 Sep '22

Hi, This is a reminder, that *this week* is the week for Cycle highlights [1][2]! They need to be added to deliverable yamls so that they can be included in release marketing preparations. (See the details about how to add them at the project team guide [3].) [1]https://releases.openstack.org/zed/schedule.html [2]https://releases.openstack.org/zed/schedule.html#z-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles

4 6

[release] Release countdown for week R-4, Sep 05 - 09
by Előd Illés 02 Sep '22

02 Sep '22

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and feature freeze exceptions approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the Zed deliverables can be proposed, well ahead of the final Zed release date. General Information ------------------- We are still finishing up processing a few release requests, but the Zed release requirements are now frozen. If new library releases are needed to fix release-critical bugs in Zed, you must request a Requirements Freeze Exception (RFE) from the requirements team before we can do a new release to avoid having something released in Zed that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] RFE requested for $PROJECT_LIB Include justification/reasoning for why a RFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By September 15th, 2022 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions ------- stable/zed branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for Zed changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed Zed cycle-highlights yet, then it's time to do that as soon as possible. Please see the email for details: https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030223.… Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 15th, 2022 (R-3 week) Final RC deadline: September 29th, 2022 (R-1 week) Final Zed release: October 5th, 2022 PTG: October 17-21, 2022 (Virtual!) Előd Illés irc: elodilles

1 0

Kolla-ansible Openstack : Queries on Metering and Rating Module
by KK CHN 02 Sep '22

02 Sep '22

I have installed all-in-one using Kolla-ansible wallaby on a Virtual Machine (Debian 10) By default configurations up and running are able to create VMs .. with the default Cirros image. I want the Metering and Billing modules for a deployment scenario. So I used this setup as a PILOT and use ceilometer with cloudkitty and gnocchi.. I have enabled ( correct me If I am wrong or missing any other directives for metering and rating other than this if required => enable_ceilometer : "yes" enable_cloudkitty : "yes" enable_gnocchi : "yes" , enable_horizon_cloudkitty : "{{ enable_cloudkitty |bool }}" cloudkitty_collector_backend: "gnocchi" in /etc/kolla/globals.yml Then re deployed the all in one $ ( (venvopenstack) cloud@wallaby:~$ kolla-ansible -i ./all-in-one bootstrap-servers , (venvopenstack) cloud@Xena:~$ kolla-ansible -i ./all-in-one prechecks, (venvopenstack) cloud@Xena:~$ kolla-ansible -i ./all-in-one deploy ) .. All went well up and able to access horizon dashboard. How to view the metrics and ratings :: I am able to get Admin => Rating tab Enabled the three Rating Modules there. (Hashmap, noop, pyscripts) .. Rating Summary : I am getting as below All CloudTotal 0 LL <http://10.184.48.94/admin/rating_summary/ALL> Cloud Total <http://10.184.48.94/admin/rating_summary/ALL> 0 Hashmap and pyscrips tab nothing to view , its empty. How can I use this Rating module and how to get useful values there ? Or is there any other configurations I have to make to get a better metering and billing utility using these tools. Kindly share your tips and expertise with these tools. What / where to refer to get a nice Rating/metering configurations using these tools.( Or do I need to enable / configure more directives or resources ??) I have not seen a highly populated Rating Module interface in Horizon so it should be. Any reference images and configurations are most welcome. Thank you, Krish

3 5

[heat][elections] PTL Candidacy for Antelope Cycle
by Brendan Shephard 02 Sep '22

02 Sep '22

Hi all, I first wanted to thank Rico for his ongoing commitment to the project over the last cycles. He has provided lots of guidance and help to the Heat project for a long time and his contribution deserves recognition. I am proposing my candidacy for Heat PTL during the Antelope cycle. I have worked with the Heat project for several years both as a user and more recently over the last 2 years as a contributor. I see great potential in the project for our users and look forward to continuing work in order to support features and functionality of the project. Some of my objectives for the next few cycles are: Remove the dependencies on legacy python-*client libraries and instead shift to the openstacksdk client library. While the legacy libraries have served us well, they are starting to show their limitations and the delta in servicibilty will only increase as each project moves towards leveraging the openstacksdk. So this change, while quite extensive will ensure future compatibility with the other OpenStack project teams. Continue ensuring Heat supports the most up-to-date and recent features provided by each project. To ensure Heat is the default and best choice for our users, we need to ensure we are able to leverage the latest available features from the complimentary OpenStack projects. This is an ongoing challenge to stay up-to-date with the changes each cycle and work towards implementing them in Heat. Thank you all for you consideration, and I look forward to the next cycle and continuing to work with you all. Regards, Brendan

3 2

Unable to change the app-name / programname for barbican-api service
by Rohit Singh 02 Sep '22

02 Sep '22

Hi guys, I am facing issues with barbican-api logging with syslog. I have configured rsyslog for barbican service and want to write the logs on remote host based on %programname properties, But I observed that the barbican-api app-name is not set ,so by default it's logging into loadwsgi.py.log . Is there any way to set the app-name for barbican-api service ? Regards Rohit Singh Mob : +91- 88824 68891

1 0

Unable to change the app-name / programname for barbican-api service
by Rohit Kumar Singh 02 Sep '22

02 Sep '22

Hi guys, I am facing issues with barbican-api logging with syslog. I have configured rsyslog for barbican service and want to write the logs on remote host based on %programname properties, but i observed barbican-api app-name is not set ,so by default it's logging into loadwsgi.py.log . I s there any way to set the app-name for barbican-api service ?

1 0

[all][elections][tc] TC Election Non-Candidacy ...
by Jay Bryant 02 Sep '22

02 Sep '22

All, I wanted to take a moment to let everyone know that I am not going to be running for the TC, this time around. The last two years on the TC have been a great experience and I am grateful for the trust the community put in me. At this point, however, I think it is best to let others who may want to join the TC have the opportunity to do so. Again, thank you for this opportunity to support the community over the last couple of years! Sincerely, Jay Bryant (jungleboyj)

3 2

[manila] Feature freeze exceptions
by Carlos Silva 02 Sep '22

02 Sep '22

Hello, Zorillas and interested stackers! During today's Manila weekly meeting we went over the status of our open changes that are eligible for feature freeze. Some candidates for the deadline were successfully merged over the course of this week, but there are also a few other changes that are receiving feedback from reviewers. Those changes will need some extra time to get in. We are in a shortage of reviewers to take care of all of the changes at once, and we are extending the deadline by one week. The changes yet to be merged and receiving the feature freeze exception are: *Metadata for share snapshots [1]* During the Yoga cycle, Manila metadata APIs were changed to be more generic and be able to accommodate metadata for other resources. For Zed, we planned to have metadatas being added to the snapshot resources. This change has received some reviews and seems to be quite close to being merged. During the tests, the manipulation of metadata for share snapshots seems to work just fine, and we are only getting some final tweaks to the implementation. *Refactor the Ceph NFS driver to use Cephadm NFS [2]* This is a driver-only change and it does not impact the Manila core itself. It is important for people consuming the Ceph drivers, and does not impact the current driver implementation. *Support share transfer between project [3]* This change is currently under review and is a good addition to the Manila core. Due to the shortage of reviewers, we only got more people looking at the change and testing the functionality late in the cycle. The three changes aforementioned should be merged by next Thursday (08 september 2022). [1] https://review.opendev.org/c/openstack/manila/+/825008 [2] https://review.opendev.org/c/openstack/manila/+/848987 [3] https://review.opendev.org/c/openstack/manila/+/843832 In case you have questions or concerns, please let me know. Thank you, carloss

1 0

[all] [oslo.messaging] Interest in collaboration on a NATS driver
by Tobias Urdin 01 Sep '22

01 Sep '22

Hello everyone, Before continuing on, yes this kind of is a massive effort but it doesn’t have to be, it would be very cool to get a replacement for RabbitMQ as I’m probably not the only one not satisfied with it. I've proposed a very bare POC in [1] but it's long way from being finished, but atleast some basic devstack is passing. NATS [2] is a cloud-native scalable messaging system that supports the one-to-many and pub-sub methods that we can use to implement it as a oslo.messaging driver. This would make OpenStack easier to deploy in a highly available fashion, reduce outages related to RabbitMQ, free up memory and CPU usage by RabbitMQ (it’s insane when using clustering) and embrace a more cloud-native approach for our software that runs the cloud, alternatives is also welcome :) The POC has a lot of things that could be improved for example: • Do retries and acknowledgements in the library (since NATS does NOT persist messages like RabbitMQ could) • Handle reconnects or interruptions (for example resubscribe to topics etc) • Timeouts need to be implemented and handled • Investigate maximum message payload size • Find or maintain a NATS python library that doesn't use async like the official one does • Add a lot of testing • Cleanup everything noted as TODO in the POC code Now I couldn’t possibly pull this off myself without some collaboration with all of you, even though I’m very motivated to just dig in and do this for the rest of the year and migrate our test fleet there I unfortunately (like everyone else) is juggeling a lot of balls at the same time. If anybody, or any company, out there would be interested in collaborating in a project to bring this support and maintain it feel free to reach out. I’m hoping somebody will bite but atleast I’ve put it out there for all of you. Best regards Tobias [1] https://review.opendev.org/c/openstack/oslo.messaging/+/848338 [2] https://nats.io

4 7

[neutron] Drivers meeting - Friday 02.09.2022 - cancelled
by Lajos Katona 01 Sep '22

01 Sep '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

[cinder] experiences with S3 cinder-backup driver // client-side encryption feature
by Christian Rohmann 01 Sep '22

01 Sep '22

Hello openstack-discuss and cinder-backup users! There is an S3 driver available for cinder-backup since the Wallaby release already, see https://docs.openstack.org/releasenotes/cinder/wallaby.html#relnotes-18-0-0…. 1) I was wondering if anybody already used that on a somewhat larger scale and what you experiences are about performance, stability and compatibility? 2) What object storage implementation or external service were / are you using? 3) While there are options like "backup_s3_sse_customer_algorithm" and "backup_s3_sse_customer_key" make use of server-side-encryption (SSE), there seems to be no way to encrypt the data before actually sending it to the remote S3 (read: client-side encryption). Since the boto3 Python SDK by AWS is used, which does not actually implement CSE, like other language SDKs do (see my issue: https://github.com/boto/boto3/issues/3395) it seems obvious why that is not a totally low-hanging fruit. But there are ways to add this, check out the references to e.g. https://github.com/StephenSorriaux/s3-encryption in the mentioned boto3 issue. Encrypting data before sending it off to a potentially externally operated service seems like a nice feature. Even a single encryption key would then protect that data from having to trust a 3rd party. I know encrypted cinder volumes would also work, but they are not as commonly used. * Is CSE something that others would also like to see for the S3 driver? * Cinder devs, would this maybe be worth a spec for the next cycle? Regards Christian

1 0

[ovn-bgp-agent][neutron] - expose_tenant_networks bug
by Satish Patel 01 Sep '22

01 Sep '22

Folks, I am setting up ovn-bgp-agent lab in "BGP mode" and i found everything working great except expose tenant network https://ltomasbo.wordpress.com/2021/02/04/ovn-bgp-agent-testing-setup/ Lab Summary: 1 controller node 3 compute node ovn-bgp-agent running on all compute node because i am using "enable_distributed_floating_ip=True" ovn-bgp-agent config: [DEFAULT] debug=False expose_tenant_networks=True driver=ovn_bgp_driver reconcile_interval=120 ovsdb_connection=unix:/var/run/openvswitch/db.sock I am not seeing my vm on tenant ip getting exposed but when i attach FIP which gets exposed in loopback address. here is the full trace of debug logs: https://paste.opendev.org/show/buHiJ90nFgC1JkQxZwVk/

2 9

help: set ironic inspect autodiscovery failed
by 陈薇 01 Sep '22

01 Sep '22

Hi All, I'm trying the ironic inspect autodiscovery but failed. What I did: Set the inspector.conf 1. [discovery] enroll_node_driver = ipmi [processing] permit_active_introspection = true processing_hooks = $default_processing_hooks,extra_hardware,lldp_basic Configure the python agent: inspection_callback_url: There's no node automatically added. I enter the host and read the log of python agent, no inspect related log. Could anybody give any advice about how to triage or setup correctly? Thanks & Regards, Wei

1 1

[election][openstack-ansible] PTL candidacy for Antelope cycle
by Dmitriy Rabotyagov 01 Sep '22

01 Sep '22

Hello. I want to self-nominate for the role of OpenStack-Ansible PTL for the Antelope release cycle. As always, my goal will be to constantly improve existing code, make deployments and further operations as reliable as possible. For the previous cycle we have reached some of previously defined goals, like adding a `service` role, finally implementing service_token_roles and support of CentOS 9 Stream, but there is still room for improvement for role testing. With the return of live events I will do my best to ensure project presence on them and get in touch with operators to gain feedback for project future improvement. -- Kind regards, Dmitriy Rabotyagov

2 1