- openstack-discuss - lists.openstack.org

[kolla-ansible] stuck at Discover nova hosts
by Satish Patel 08 Feb '25

08 Feb '25

Folks, I am deploying kolla-ansible 2024.1 but somehow it has been stuck here for the last 2 hours not giving me any kind of clue or error even when I run in -vvvv mode. Any idea what it's trying to discover and why there is no timeout for this task? TASK [nova-cell : Fail if cell settings not found] ************************************************************************************************************************ task path: /usr/local/share/kolla-ansible/ansible/roles/nova-cell/tasks/discover_computes.yml:7 skipping: [os-chn-gen-comp-001] => { "changed": false, "false_condition": "not nova_cell_settings", "skip_reason": "Conditional result was False" } TASK [nova-cell : Discover nova hosts] ************************************************************************************************************************************ task path: /usr/local/share/kolla-ansible/ansible/roles/nova-cell/tasks/discover_computes.yml:14 Using module file /usr/local/lib/python3.10/dist-packages/ansible/modules/command.py Pipelining is enabled. <os-chn-ctrl01> ESTABLISH SSH CONNECTION FOR USER: None <os-chn-ctrl01> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o 'ControlPath="/root/.ansible/cp/eaac57fe12"' os-chn-ctrl01 '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-pnxqbtjwqxuxexfjfrnpukckzrfbkegh ; /usr/bin/python3'"'"'"'"'"'"'"'"' && sleep 0'"'"'' Escalation succeeded

2 1

[release] Release countdown for week R-7
by Thierry Carrez 07 Feb '25

07 Feb '25

Development Focus ----------------- We are entering the last weeks of the 2025.1 Epoxy development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-AC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Contributor and allowed to vote. This is done by adding extra-acs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-AC freeze on February 13th. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, February 13th. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 20th). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 27th) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 27th. Any feature addition beyond that date should be discussed on the mailing list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 14th) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 28th) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to one week after Feature freeze (March 6th). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… jeremy [at] openstack.org/fungi on IRC is available if you need help selecting or writing your highlights. Upcoming Deadlines & Dates -------------------------- Extra-AC freeze: February 13th (R-7 week) Oslo feature freeze: February 13th (R-7 week) Non-client library freeze: February 20th (R-6 week) Client library freeze: February 27th (R-5 week) epoxy-3 milestone: February 27th (R-5 week) Cycle highlights deadline: March 6th (R-4 week) -- Thierry Carrez (ttx)

1 0

[openstack-ansible][masakari][yoga]pcs cluster not getting started
by Danish Khan 07 Feb '25

07 Feb '25

Dear All, I have upgraded my openstack cluster from wallaby to Yoga. And I am facing issue with masakari services. pacemaker service is running fine on all nodes but pacemaker_remote.service is not getting started on any of the nodes. And Masakari containers doesn't have any idea of it monitor nodes. I purged the masakari cluster and tried to deploy it again. Playbook is running successfully again and again but it is not setting up the cluster. Playbook is not installing corosync service on masakari containers and now pacemaker server is also not getting installed on masakari api containers. I idea to run masakari in a way that it can create the cluster and install required services on its own? I tried with below but that did not work:

1 2

[Monasca][Masakari][Requirements] Migrate of of oslosphinx
by Tony Breeds 06 Feb '25

06 Feb '25

Hello all, This is a heads up to let you know that the requirements team have approved 940215: Drop oslosphinx | https://review.opendev.org/c/openstack/requirements/+/940215 which will mean any changes to Monasca or Masakari that touch a requirements file will fail. The solution is to remove your dependency on oslosphinx, as many projects have done this I expect there is plenty of knowledge in git epos for what needs to be done. In the short term if your gate is blocked you can land a change that switches check-requirements to non-voting -- Yours Tony.

1 0

[neutron] Drivers meeting canceled Friday, February 7th
by Brian Haley 06 Feb '25

06 Feb '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as there is no agenda. Just a reminder there are still open specs that need review, list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

Having troubles with Mistral.
by Alvin Starr 06 Feb '25

06 Feb '25

I am trying to use Mistral to create a VM and I cannot seem to find the appropriate parameters. Here is part of my workflow. tasks: create_instance: action: nova.servers_create input: name: <% $.vm_name %> image: <% $.image %> flavor: <% $.flavor %> nics: - net-id: <% $.network %> key_name: <% $.keypair %> disk_config: AUTO availability_zone: nova meta: status: "pending" # Initial metadata value publish: instance_id: <% task(create_instance).result.id %> on-success: - get_vm_details I seem to keep getting a no suitable hypervisor found error. I have checked and i am sure I am not running into any resource constraints. any help or pointers would be greatly appreciated. -- Alvin Starr || land: (647)478-6285 Netvel Inc. || home: (905)513-7688 alvin(a)netvel.net ||

2 2

[nova][elections][ptl] Leaving my seat
by Sylvain Bauza 06 Feb '25

06 Feb '25

Hey Nova-ers That's a bit bittersweet but after running as a Nova PTL for 7 cycles, I preferred to leave this seat as I no longer have a lot of time for this. I'll continue to be around and I'll help our next PTL for sure :-) Thanks and see you at the PTG anyway :-) -Sylvain

2 1

[deployment] Is there a ranked list of automated deployment technologies (based on production usage)?
by Jordan Olin (OLINSolutions) 06 Feb '25

06 Feb '25

Hello, I’m trying to narrow my deployment focus on the most commonly used OpenStack automated deployment technologies/approaches. Does a ranked list or previous recent survey exist of currently available deployment automation solutions? If not, what is the correct approach for me to take to collect something like this? Thank you, Jordan. =========================== Jordan Olin, TOGAF EA President and Chief Solutioneer OLINSolutions, Inc. e: jordan(a)olinsolutions.com p: +1 508-982-4872 w: olinsolutions.com This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. This communication may contain material protected by government legislation. If you are not the intended recipient or the person responsible for delivering this email to the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender by replying to this email and then delete the email from your computer.

2 1

[openstack-ansible] Relocate ceph-mons to new hosts and decouple Ceph from openstack-ansible
by Jan Marquardt 06 Feb '25

06 Feb '25

Hi, We run a cluster with ~15 compute hosts and ~25 Ceph nodes. Everything was initially deployed with openstack-ansible. For some reasons we would like to decouple Ceph from openstack-ansbile and therefore move the ceph-mon containers to dedicated hosts. - Moving the containers seems straightforward, but how do we tell openstack-ansible that the containers are gone and that it can’t use the ip addresses anymore for other purposes? - How do we tell openstack-ansible which keyrings it has to deploy on compute hosts? Any recommendations? Has anyone done this before? Can you think of anything else that should be considered? Thanks in advance and best regards Jan

2 1

[Neutron] [FeatureRequest] Port AllowedIPs Subnet-Pool extension
by Justin Lamp 06 Feb '25

06 Feb '25

Hey there, I'd like to propose a feature to allow subnets to be added to Neutron ports and be allocated from a subnet-pool. We would have a couple of use cases for this. Please correct me if I am wrong, but right now we do not have a method to route a subnet to a VM without adding many fixed-ips from the subnet the VM is residing in. This is highly undesirable for us as our use case would be with Kubernetes. We'd like to be able to allocate a IPv6 subnet for every Kubernetes Node, so that every pod can get a fully routed v6 address without resorting to NAT. While searching the mailing list for IPv6 in general I found another person having a similar inquiry. In his case he wanted a subnet to use for his VPN-VM. This is also something we want to address and provide to our customers at some point. This is why I would like to propose that AllowedIP subnets can be created based on subnet pools, making it possible to route them externally. This will also make it possible for something like the OVN-BGP-Agent to expose them via BGP. Does anybody have any thoughts on this? Best regards, Justin -- Justin Lamp Systems Engineer NETWAYS Managed Services GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk, Sebastian Saemann | AG Nuernberg HRB25207 https://www.netways.de | justin.lamp(a)netways.de ** stackconf 2025 - April | Munich - https://stackconf.eu ** ** OSMC 2025 - November | Nuremberg - https://osmc.de ** ** NETWAYS Web Services - https://nws.netways.de ** ** NETWAYS Trainings - https://netways.de/trainings **

3 2

[tc][election] TC election Non-Candidacy
by Sławek Kapłoński 06 Feb '25

06 Feb '25

Hi, It's been 3 years for me already to be part of the OpenStack Technical Committee and as my 3rd cadence is getting to the end now, I just want to let You all know that I am not going to candidate again. This was a pleasure and great experience for me to be part of the TC for such a long time and I am really grateful that I was elected to serve in that role. But now I think it is time to give this place back to someone new who will bring fresh ideas to the TC. I will still be around and happy to help if needed of course. -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

Reviews for IBM SVf Cinder Driver
by Harsh Ailani 05 Feb '25

05 Feb '25

Hello community and core reviewers, We are from the IBM Team to develop the IBM SVf Cinder Driver for our community and on-prem customers. Till 2022 we were contributing and participating actively in the community development and review processes but due to internal organisational changes we were unable to participate in the community. Also, our CI/CD pipeline was disrupted for over a year which caused the major delay in our contribution. However, now the team is back on track along with the CI/CD pipeline and we have some huge line items that we need to upstream so that all our OpenStack customers could use those features with IBM Storages. Currently we have the following patches active which need your reviews so that they can be merged and be useable for the customers: Volume-group feature support patches: 1. [IBM SVf driver] Adding support for temporary volumegroup | https://review.opendev.org/c/openstack/cinder/+/925450 2. [IBM SVf Driver] Added support for volumegroup-snapshot for temporary volumegroup | https://review.opendev.org/c/openstack/cinder/+/926844 3. [IBM SVf Driver] Added support for restorefromsnapshot CLI for volumegroups | https://review.opendev.org/c/openstack/cinder/+/916722 4. [IBM SVf Driver] Added support of clone operation for volumegroup | https://review.opendev.org/c/openstack/cinder/+/938771 5. Doc: Documentation updates for ibm-svf-volumegroup feature. | https://review.opendev.org/c/openstack/cinder/+/929906 Our team is relatively new (except myself) and we are starting the process of reviewing other contributor’s patches as well. Requesting the core reviewers to please help use review these patches and get the merged in the community as we have more storage features in development pipeline which has dependencies on volume-group feature. Thanks and Regards, Harsh Ailani Openstack Developer - Flashsystem IBM

1 0

[all][elections][ptl][tc] Combined PTL/TC 2025.2 cycle Election Nominations Kickoff
by Slawomir Kaplonski 05 Feb '25

05 Feb '25

Hi, Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (5 positions) are now open and will remain open until Feb 19, 2025 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/2025.2/<Project_Name or "TC">/<email_address> (for example, "candidates/2025.2/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the 2024.2 to 2025.1 timeframe, Mar 15, 2024 00:00 UTC - Feb 19, 2025 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Feb 26, 2025 23:45 UTC through to Mar 19, 2025 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the 2024.2 to 2025.1 timeframe, Mar 15, 2024 00:00 UTC - Feb 19, 2025 00:00 UTC, as well as any Extra ACs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the 2024.2 to 2025.1 timeframe, Mar 15, 2024 00:00 UTC - Feb 19, 2025 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ACs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ACs. Please find below the timeline: PTL + TC nomination starts @ Feb 05, 2025 23:45 UTC PTL + TC nomination ends @ Feb 19, 2025 23:45 UTC TC campaigning starts @ Feb 19, 2025 23:45 UTC TC campaigning ends @ Feb 26, 2025 23:45 UTC PTL + TC elections start @ Feb 26, 2025 23:45 UTC PTL + TC elections end @ Mar 19, 2025 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2025-02-19 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials -- Best regards Slawek Kaplonski skaplons(a)redhat.com

1 0

[freezer] Moving project bug tracker to launchpad
by Dmitriy Rabotyagov 05 Feb '25

05 Feb '25

Hey there, In order to simplify and align with most OpenStack projects on bug tracker I aim to move Freezer from different Storyboard [1] projects back to unified Launchpad [2] tracker. However, historically the OpenStack Administrators [3] group was not added as Freezer project administrator/owner on Launchpad, which means that no current maintainer of the project has the necessary rights to manage the mentioned Launchpad project. I've added all current Launchpad admins for Freezer project to CC of this email, to either of you to add "openstack-admins" [3] to the Freezer Drivers [4] team, so that OpenStack Infra team could assist with further recovering/managing access to the Launchpad project. That will be very nice if some of you could spend couple of minutes on making this change and help us avoid cumbersome process of recovering access to the project Thanks in advance! [1] https://storyboard.openstack.org/#!/project/list?q=freezer [2] https://launchpad.net/freezer [3] https://launchpad.net/~openstack-admins [4] https://launchpad.net/~freezer-drivers

4 3

[qa][ptg] Call for 2025.2 vPTG QA topic
by Ghanshyam Mann 05 Feb '25

05 Feb '25

Hi All, I have created the etherpad to collect the QA topics for the coming vPTG (2025.2 cycle). Based on the topics, we will decide if we need any slot in PTG. Feel free to add your topics before Feb 19th. - https://etherpad.opendev.org/p/qa-2025.2-ptg -gmann

1 0

OpenStack's 15th Birthday!
by Helena Spease 05 Feb '25

05 Feb '25

Hello everyone, July 2025 marks OpenStack’s 15th Birthday! To celebrate we are working with our community organizers around the globe to throw birthday celebrations throughout the year. On the OpenStack Blog you will find a list of birthday celebrations being planned this year. This list is still evolving, so we will be periodically updating the blog post and also adding links to where you can find more details on the various celebrations. https://www.openstack.org/blog/celebrating-15-years-of-openstack/ If you don’t see your city on the list, reach out to me and we can work on getting a celebration scheduled. There are also lots of opportunities for your organization to support OpenStack’s 15th Birthday. The user groups organizing these celebrations are looking for venue hosts, cake sponsors, swag sponsors, and so on. Feel free to send me an email if your organization is interested in supporting an upcoming celebration. Here’s to 15 years of OpenStack! Cheers, Helena helena(a)openinfra.dev Community Programs Manager The OpenInfra Foundation I am always happy to jump on a call to answer questions, feel free to book some time on my calendar: https://calendar.app.google/QWJXNAEhfFxjYazr6 <https://openinfra.dev/>

1 0

Discussion of OpenStack development getting Error.
by Kiran Raja 05 Feb '25

05 Feb '25

Hi Team, We have deployed Open stack and when we are trying to access Neutron Gateway from the Controller node we are unable to access, but It is access able from Namespace Created in neutron , please help me on neutron configuration we are using Self-provision Network Option. root@controller:~# openstack router list +--------------------------------------+--------------+--------+-------+----------------------------------+-------------+-------+ | ID | Name | Status | State | Project | Distributed | HA | +--------------------------------------+--------------+--------+-------+----------------------------------+-------------+-------+ | 16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 | Admin_Router | ACTIVE | UP | 523711770d5243dd9af5b2356b540b07 | False | False | +--------------------------------------+--------------+--------+-------+----------------------------------+-------------+-------+ root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ip route default via 172.16.86.1 dev qg-afb1772f-2f proto static 172.16.86.0/24 dev qg-afb1772f-2f proto kernel scope link src 172.16.86.49 root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 172.16.86.1 0.0.0.0 UG 0 0 0 qg-afb1772f-2f 172.16.86.0 0.0.0.0 255.255.255.0 U 0 0 0 qg-afb1772f-2f root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ping 172.16.86.1 PING 172.16.86.1 (172.16.86.1) 56(84) bytes of data. ^C --- 172.16.86.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2042ms root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ip address 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 13: qg-afb1772f-2f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:d1:58:50 brd ff:ff:ff:ff:ff:ff inet 172.16.86.49/24 brd 172.16.86.255 scope global qg-afb1772f-2f valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fed1:5850/64 scope link valid_lft forever preferred_lft forever root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ping 172.16.86.49 PING 172.16.86.49 (172.16.86.49) 56(84) bytes of data. 64 bytes from 172.16.86.49: icmp_seq=1 ttl=64 time=0.073 ms 64 bytes from 172.16.86.49: icmp_seq=2 ttl=64 time=0.113 ms ^C --- 172.16.86.49 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1003ms rtt min/avg/max/mdev = 0.073/0.093/0.113/0.020 ms root@controller:~# ping 172.16.86.49 PING 172.16.86.49 (172.16.86.49) 56(84) bytes of data. ^C --- 172.16.86.49 ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1048ms root@controller:~# ip netns exec qrouter-16d92543-e9a3-4e97-bdb0-ccb3a8b8dd99 ip address 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 13: qg-afb1772f-2f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:d1:58:50 brd ff:ff:ff:ff:ff:ff inet 172.16.86.49/24 brd 172.16.86.255 scope global qg-afb1772f-2f valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fed1:5850/64 scope link valid_lft forever preferred_lft forever 15: qr-6be4aabd-b9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:df:a9:ad brd ff:ff:ff:ff:ff:ff inet 172.16.100.1/24 brd 172.16.100.255 scope global qr-6be4aabd-b9 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fedf:a9ad/64 scope link valid_lft forever preferred_lft forever root@controller:~# ping 172.16.86.1 PING 172.16.86.1 (172.16.86.1) 56(84) bytes of data. 64 bytes from 172.16.86.1: icmp_seq=1 ttl=64 time=0.204 ms ^C --- 172.16.86.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.204/0.204/0.204/0.000 ms root@controller:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0c:29:25:f8:21 brd ff:ff:ff:ff:ff:ff altname enp3s0 inet 172.16.85.11/24 brd 172.16.85.255 scope global ens160 valid_lft forever preferred_lft forever inet6 fe80::20c:29ff:fe25:f821/64 scope link valid_lft forever preferred_lft forever 3: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP group default qlen 1000 link/ether 00:0c:29:25:f8:2b brd ff:ff:ff:ff:ff:ff altname enp11s0 inet6 fe80::20c:29ff:fe25:f82b/64 scope link valid_lft forever preferred_lft forever 4: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 2e:14:3b:10:5d:42 brd ff:ff:ff:ff:ff:ff 5: br-tun: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 02:fb:f2:93:65:46 brd ff:ff:ff:ff:ff:ff inet6 fe80::fb:f2ff:fe93:6546/64 scope link valid_lft forever preferred_lft forever 6: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 00:0c:29:25:f8:2b brd ff:ff:ff:ff:ff:ff inet6 fe80::20c:29ff:fe25:f82b/64 scope link valid_lft forever preferred_lft forever 7: br-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 72:cb:66:8a:21:4c brd ff:ff:ff:ff:ff:ff inet6 fe80::70cb:66ff:fe8a:214c/64 scope link valid_lft forever preferred_lft forever root@controller:~# ovs-vsctl show 77dc413c-c4a0-4c7a-b3e2-3ba8ecf5bee7 Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port br-int Interface br-int type: internal Port qg-afb1772f-2f tag: 2 Interface qg-afb1772f-2f type: internal Port qr-6be4aabd-b9 tag: 3 Interface qr-6be4aabd-b9 type: internal Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port tap93e5731e-d9 tag: 2 Interface tap93e5731e-d9 type: internal Port tap52dcef2e-c9 tag: 3 Interface tap52dcef2e-c9 type: internal Port int-br-ex Interface int-br-ex type: patch options: {peer=phy-br-ex} Bridge br-tun Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port br-tun Interface br-tun type: internal Bridge br-ex Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port phy-br-ex Interface phy-br-ex type: patch options: {peer=int-br-ex} Port br-ex Interface br-ex type: internal Port ens192 Interface ens192 ovs_version: "3.4.0" Thanks and Regards CH Kiran Raja M: +91 9959503256 [cid:1df6874c-4456-494d-9e7c-aa3aed63e7af]<https://pidatacenters.com/> [cid:693f6ef0-1ee9-4ea9-a345-8488a3aa8c2b]<https://harbour1.in/> kiran.raja(a)pidatacenters.com<mailto:kiran.raja@pidatacenters.com> [cid:0770d139-f2b6-424b-a451-6ad2a391a96b]

3 3

[kolla] IRC meeting cancelled - 5 Feb 2025
by Bartosz Bezak 05 Feb '25

05 Feb '25

Hello, Unfortunately, this week’s Kolla IRC meeting is cancelled due to unavailability of most Kolla core members. Sorry for late notice. Best regards, Bartosz Bezak

1 0

OpenStack Hypervisor POC
by Prince Kumar 04 Feb '25

04 Feb '25

Hello Team, We are looking for alternate OpenStack hypervisor solutions. Could you please share subscription pricing list. Also we want to know how OpenStack support our infrastructure requirements. Thanks & Regards Prince Kumar AMERICAN EXPRESS Email: prince.kumar12(a)aexp.com<mailto:prince.kumar12@aexp.com> American Express made the following annotations This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. American Express Prospective and Existing Customers: For more information about how we protect your privacy, please visit www.americanexpress.com/privacy. If you are located outside the U.S., please select your location at www.americanexpress.com/change-country/ and access the privacy link at the bottom of the page. American Express a ajouté le commentaire suivant Ce courrier et toute pièce jointe qu'il contient sont réservés au seul destinataire indiqué et peuvent contenir des renseignements confidentiels et protégés par le secret professionnel. Si vous n'êtes pas le destinataire prévu, toute divulgation, duplication, utilisation ou distribution du courrier ou de toute pièce jointe est interdite. Si vous avez reçu cette communication par erreur, veuillez nous en aviser par courrier et détruire immédiatement le courrier et les pièces jointes. Clients et prospects d'American Express: Pour plus d'informations sur la façon dont nous protégeons votre vie privée, veuillez visiter www.americanexpress.com/privacy. Si vous êtes situé à l'extérieur des États-Unis, veuillez sélectionner votre emplacement à l'adresse www.americanexpress.com/change-country/ et accéder au lien de confidentialité en bas de la page.

3 3

[openstack-ansible][rabbitmq] nova and cinder queue got deleted from rabbitmq after upgarding from victoria to wallaby
by Danish Khan 04 Feb '25

04 Feb '25

Dear All, I have upgraded one of my cluster from Victoria to wallaby. All playbooks run successfully and the cluster is upgraded to wallaby. But I don't see any queue in rabbitmq "rabbitmqctl list_queues --vhost /cinder" and "rabbitmqctl list_queues --vhost /nova" returns empty results. I tried adding these queues manually and the command is running successfully as well but still queues are not getting created. #rabbitmqctl add_vhost /cinder #rabbitmqctl set_permissions -p /cinder cinder ".*" ".*" ".*" I have re-run all playbooks again but nothing is happening. And I am getting below error in galera which I guess I can ignore for now: error : Aborted connection 249 to db: 'cinder' user: 'cinder' host: 'infra1' (Got an error reading communication packets) Regards, Danish

2 2

VPNaaS
by Vincent Godin 04 Feb '25

04 Feb '25

Hello, The VPNaaS provided with Openstack is a Site-to-Site VPN made to interconnect two tenants or an external gateway with a tenant network. I would like to know if there are plans to offer a VPNaaS more like a Remote VPN. This would allow Openstack users to administer their instances securely. A user could mount this VPN from a roaming device, be assigned a local IP address, and then administer the instances of his tenant. Regards Vincent

3 2

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-8)
by Goutham Pacha Ravi 03 Feb '25

03 Feb '25

Hello Stackers, We're 8 weeks away from the coordinated 2025.1 ("Epoxy") release date [1]. On Feb 5th, election officials will begin accepting nominations for Project Team Leads for 41 teams for the 2025.2 ("Flamingo") release cycle, alongside 5 seats on the OpenStack Technical Committee with a one-year term. Together, these individuals form the indispensable leadership of this community. We seek to ensure that our community is cohesive, inclusive, and a level playing field where all voices are heard and anyone can rise to leadership positions [2]. This is an opportunity that I'd encourage you to capitalize on. Please see the election website [3] for details on how to submit your candidacy. In the news this week, the OpenStack Technical Committee resolved to include artifacts of the Disaster Recovery service ("Freezer") in the upcoming 2025.1 release [4]. We also merged a change to create a new DevStack plugin for Prometheus under the QA team. This repository will be useful for working with the OpenStack Resource Optimization service ("Watcher") in development environments. The project team driving the Watcher project also asserted their distributed project leadership for the 2025.2 release cycle. Members of the OpenStack community also participated in FOSDEM 2025 in Brussels. Amy Marrich (spotz) and Slawek Kaplonski (slaweq) from the OpenStack TC were in attendance. The release team ended and deleted the "unmaintained/victoria" branch on most OpenStack repositories this week. We have volunteers who have stepped up to maintain the branch in roughly 70 repositories for now [5]. === Weekly Meeting === The OpenStack TC meeting last week was brief [6]. We discussed governance changes highlighted below and nudged the change to begin closing old, unmaintained code branches [5]. We checked in on project teams that had adopted the "distributed project leadership" model in the current release cycle and encouraged teams to replace inactive liaisons or revert to the PTL model for the next release cycle. Some project team meetings have yet to resume since the end-of-year holidays, and getting feedback from each liaison has been a challenge. The next meeting of the OpenStack TC is today, 2025-02-04, at 1800 UTC. This meeting will be held simultaneously on Video (Zoom) and IRC (OFTC's #openstack-tc channel). Please find the agenda and Zoom link in the meeting wiki [7]. I look forward to seeing you there. === Governance Proposals === ==== Merged ==== - Adopt DPL model for Watcher 2025.2 | https://review.opendev.org/c/openstack/governance/+/940167 - Add devstack-plugin-prometheus repo to Quality Assurance repos | https://review.opendev.org/c/openstack/governance/+/939953 - Add resolution for late Freezer release | https://review.opendev.org/c/openstack/governance/+/939792 ==== Open for Review ==== - Define 2025 upstream investment opportunities | https://review.opendev.org/c/openstack/governance/+/939507 - Reset the DPL model for the Oslo project | https://review.opendev.org/c/openstack/governance/+/939485 - Add Watcher project update liaison | https://review.opendev.org/c/openstack/governance/+/940168 - Retire qdrouterd role | https://review.opendev.org/c/openstack/governance/+/938193 - Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 === Upcoming Events === - 2025-02-05: Nominations open for 2025.2 TC/PTL Elections: https://governance.openstack.org/election/ - 2025-02-28: 2025.1 ("Epoxy") Feature Freeze and Release Milestone 3 [1] - 2025-03-06: SCALE 2025 + OpenInfra Days NA (https://www.socallinuxexpo.org/scale/22x) Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] Open Community: https://opendev.org/openinfra/four-opens/src/branch/master/doc/source/openc… [3] How to submit your candidacy in OpenStack elections: https://governance.openstack.org/election/#how-to-submit-a-candidacy [4] Resolution for Freezer release in Epoxy: https://review.opendev.org/c/openstack/governance/+/939792 [5] Victoria EOL: https://review.opendev.org/c/openstack/releases/+/937515/3..7 [6] TC Meeting IRC Log 2025-01-28: https://meetings.opendev.org/meetings/tc/2025/tc.2025-01-28-18.00.log.html [7] TC Meeting Agenda, 2025-02-04: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[swift] Upgrade from Ussuri
by Mark Kirkwood 03 Feb '25

03 Feb '25

Hi, We are looking to upgrade Swift from Ussuri. Is it necessary to pass through Victoria, Wallaby, Xena ... or can we directly go to a later version (say) Zed? regards Mark

1 0

[watcher] core team expansion
by Sean Mooney 03 Feb '25

03 Feb '25

Hi everyone, As you may be aware a number of us from Redhat have been trying to revitalize the Watcher project. To enable that one of the changes that we previously discussed on the mailing list and ptg was the expansion of the core team. https://etherpad.opendev.org/p/r.79644f8f3cd04686c4f45c10aa35d8ac#L46 https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… In November the initial phase of that proposal was completed and I took an action to follow up in Q1 to see what steps are needed to rebuild a healthy core team. based on the activity of the last 90 days and the progress of work I think it is time to expand the core teams once again to enable effective maintenance and development of watcher https://openstack.biterg.io/app/dashboards#/view/95487340-6762-11e9-a198-67…:'Gerrit%20Approvals%20panel%20by%20Bitergia',filters:!(('$state':(store:appState),meta:(alias:Bots,disabled:!f,index:gerrit,key:author_bot,negate:!t,params:(query:!t),type:phrase),query:(match:(author_bot:(query:!t,type:phrase)))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:gerrit,key:project,negate:!f,params:(query:watcher),type:phrase),query:(match_phrase:(project:watcher)))),fullScreenMode:!f,options:(darkTheme:!f,hidePanelTitles:!f,useMargins:!t),query:(language:lucene,query:''),timeRestore:!f,title:'Gerrit%20Approvals',viewMode:view) tiny url version of ^ https://tinyurl.com/439wzbdk https://www.stackalytics.io/?module=watcher-group the current core teams are as follows * watcher-core https://review.opendev.org/admin/groups/77cd139bd57514e98e5e694a82f7e261b47… * watcher-dashboard-core https://review.opendev.org/admin/groups/bcc8588732437ceea3533249313e6e96148… * watcher-specs-core https://review.opendev.org/admin/groups/747af616eb8748aee5b17d9493f9ebbc49e… * watcher-tempest-core https://review.opendev.org/admin/groups/09a91d8e24af9ce44b80062c4851a1d2fa3… starting in order watcher-core: https://tinyurl.com/2p8sr7u4 https://www.stackalytics.io/?module=opendev.org/openstack/watcher - add Marios Andreou - add Douglas Viroel Marios and Doug both have past experience as core reviews in other OpenStack projects (triple-o and Manilla), over the last 90 days, they have engaged in reviews of bug fixes and the development of the new Prometheus data source. watcher-dashboard-core: https://tinyurl.com/4259h8nz https://www.stackalytics.io/?module=opendev.org/openstack/watcher-dashboard - add Marios Andreou - add Douglas Viroel as with Watcher itself Doug and Marios have spent time looking at the open review for the watcher-dashboard. watcher-spec-core: is tricky as we have effective only had one spec this cycle that was written by Marios with some minor patches for ci. As watcher core is a member of watcher-spec-core, Marios and Doug will inherit review rights on the specs repo. At this time I do not see a need to make any other changes to the group membership. watcher-tempest-core: https://tinyurl.com/4nbctef8 https://www.stackalytics.io/?module=opendev.org/openstack/watcher-tempest-p… - add Chandan Kumar - add Douglas Viroel - remove Martin Kopec As many of you may know Martin has taken up a new role in Redhat outside of OpenStack and will no longer be working directly on OpenStack. Over the last 90 days, Martin and Gmann have modernized the tempest plugin significantly paying down much of the tech debt. I want to thank them for the efforts they put in to help revive Watcher this cycle and if they return to the OpenStack community in the future I will gladly welcome them back. In their stead, I am proposing adding Chandan and Doug to augment the existing core group. As agreed in the Watcher team meeting earlier today we will review this mail thread in the next Watcher IRC meeting next week. I would like to invite others to provide feedback on this proposal over the next week. In the next PTG, I will also raise the composition of the core teams for discussion. It is my hope that with these additions we will have at least 3 active reviews on all deliverables of the watcher project mitigating the current bus factor and accelerating development. Regards Sean.

1 1

[Neutron] Bug Deputy Report Jan 27-Feb 2
by Miro Tomaska 03 Feb '25

03 Feb '25

Hello All, Here is the bug deputy report for neutron for January 27 until February 2 Critical: - https://bugs.launchpad.net/neutron/+bug/2096912 - Grenade jobs with NEUTRON_DEPLOY_MOD_WSGI = True don't restart neutron server services Assigned: Slawek Kaplonski ( implicitly :), since he proposed a patch) High: https://bugs.launchpad.net/neutron/+bug/2096941 - New Compute nodes are not added to their segment aggregate Assigned: Terry Wilson https://bugs.launchpad.net/neutron/+bug/2096983 - Error executing command (LspGetUpCommand) Unassigned - Need to sit down and rca source of the logs Low: https://bugs.launchpad.net/neutron/+bug/2097124 - Missing filter in "openstack neutron agent --agent-type" for OVN agents Unassigned - Low hanging fruit, just needs update in openstack client component Incomplete: https://bugs.launchpad.net/neutron/+bug/2096931 Duplicate packets with router between flat network and vlan network - Waiting for more info Undecided: https://bugs.launchpad.net/neutron/+bug/2097212 - Resolv.conf search domain is different from the network's dns_domain Best Regards, Miro Tomaska -- Miro Tomaska Senior Software Engineer

2 1