September 2024 - openstack-discuss

[dev][ptl][release] Cycle highlights reminder (2024.2/Dalmatian)
by Jeremy Stanley 16 Sep '24

16 Sep '24

Just a reminder in case anyone missed it: we're technically a week past the deadline for merging 2024.2/Dalmatian release highlights, but if anyone has something they want to mention then now is the time to write, push and approve it! The OpenInfra marketing machine is getting ready to digest what they find at https://releases.openstack.org/dalmatian/highlights.html and put together a press release and package for news outlets. They're interested in whatever you're excited to include, but especially anything related to AI, digital sovereignty, security, or VMware feature parity. Please get your remaining highlights in ASAP!!! -- Jeremy Stanley

1 0

[cloudkitty] Proposing Matt Crees as core reviewer
by Pierre Riteau 16 Sep '24

16 Sep '24

Hello, I would like to nominate Matt Crees as core reviewer for the CloudKitty project. He has been involved for around a year now and has provided valuable contributions, both as reviews and commits. He is also actively participating in our bi-weekly meetings. Cheers, Pierre Riteau (priteau)

2 1

[all][elections][ptl][tc] Combined PTL/TC 2025.1 cycle Election Voting Last Days
by Slawek Kaplonski 16 Sep '24

16 Sep '24

Hi, We are coming down to the last hours for voting in the TC elections. Voting ends Sep 18, 2024 23:45 UTC. Search your Gerrit preferred email address[0] for the messages with subjects like... Poll: OpenStack 2025.1 Cycle Technical Committee Election Poll That is your ballot and links you to the voting application. Please vote. If you have voted, please encourage your colleagues to vote. Candidate statements are linked to the names of all confirmed candidates: https://governance.openstack.org/election/ What to do if you don't see the email and have a commit in at least one of the official project teams' deliverable repositories[1]: * check the trash of your gerrit Preferred Email address[0], in case it went into trash or spam * find the ID of at least one commit merged to an official deliverable repo[1] over the current and previous cycles, confirm you are an OpenStack Foundation Individual Member[2], and then email the election officials[3] or get in touch in the #openstack-elections channel on the OFTC IRC network. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Please vote! Thank you, [0] Sign into review.openstack.org and go to Settings > Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. [1] https://opendev.org/openstack/governance/src/tag/to-be-released/reference/p… [2] https://www.openstack.org/profile/ [3] https://governance.openstack.org/election/#election-officials -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[sdk] possible bug in the openstacksdk/cloud?
by astepanov2007＠gmail.com 16 Sep '24

16 Sep '24

Hello, Recently, I was debugging an issue related to the ansible openstack.cloud.server module while creating an instance with floating ip attached. A part of stack trace goes below: ... File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_compute.py", line 1013, in create_server server = self.wait_for_server( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_compute.py", line 1153, in wait_for_server server = self.get_active_server( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_compute.py", line 1200, in get_active_server return self.add_ips_to_server( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_network_common.py", line 1412, in add_ips_to_server server = self._add_ip_from_pool( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_network_common.py", line 1247, in _add_ip_from_pool f_ip = self.create_floating_ip( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_network_common.py", line 765, in create_floating_ip return self._neutron_create_floating_ip( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_network_common.py", line 824, in _neutron_create_floating_ip network_id = network['id'] ~~~~~~~^^^^^^ TypeError: 'NoneType' object is not subscriptable Tracing this down to openstacksdk python module I have found a suspicious place in the openstacksdk code: if network_name_or_id: try: network = self.network.find_network(network_name_or_id) except exceptions.NotFoundException: raise exceptions.NotFoundException( "unable to find network for floating ips with ID " "{}".format(network_name_or_id) ) network_id = network['id'] https://github.com/openstack/openstacksdk/blob/de07fd02639eb565f10956b612ed… I suppose that this call to self.network.find_network lacks "ignore_missing=True" param. E.g.: network = self.network.find_network(network_name_or_id, ignore_missing=True) This fixed my issue with floating ips, but I'm not sure such patch is suitable for the mainline code of the openstacksdk. Am I correct? Regards, Alexander.

2 2

[neutron] Bug Deputy Report September 9 - 15
by Lucas Alvares Gomes 16 Sep '24

16 Sep '24

Hi, This is the Neutron bug report from September 9th to 15th. *High:* * https://bugs.launchpad.net/neutron/+bug/2080072 - "Failed to delete vpnaas ipsec-site-connections with 502 error, ORM session: SQL execution without transaction in progress" Unassigned * https://bugs.launchpad.net/neutron/+bug/2080199 - "Functional jobs failing with "Too many open files"" Assigned to: Lajos Katona * https://bugs.launchpad.net/neutron/+bug/2080447 - "Update firewall policy interface timeout when it's associated with a large number of rules " Assigned to: dongdong *Medium:* * https://bugs.launchpad.net/neutron/+bug/2080314 - "ML2 plugin: No consumers for q-agent-notifier-port-delete_fanout exchange result in unroutable RabbitMQ messages" Unassigned *Low:* * https://bugs.launchpad.net/neutron/+bug/2079996 - "[OVN] OVN metadata agent check to restart the HAProxy container" Assigned to: Rodolfo Alonso *Needs further triage:* * https://bugs.launchpad.net/neutron/+bug/2080492 - "[OVN] VIP port does not come up when its virtual-parents are trunk sub-ports" Cheers, Lucas

1 0

Re: Migratekit: near-live migrations from VMware to OpenStack
by Oliver Weinmann 14 Sep '24

14 Sep '24

Hi Mohammed, We struggled using virt-v2v directly with OpenStack. Our approach was using ovftool to export the VM as OVA and then create a qcow2 image that we can import in OpenStack. So many manual steps involved. So I tested your tool aganst vsphere 7.x vcenter. But I just can't manage to get it working. It keeps complaining about the path of the source VM. I can use the following just fine with virt-v2v: virt-v2v -v -x --password-file pass.txt -ic vpx:// user123(a)vcenter.somedomain.local /GE%Office%20One/Projects/esx01.somedomain.local?no_verify=1 test-vm-01 Using the same in your tool: docker run -it --rm --privileged \ -v /dev:/dev \ -v /usr/lib64/vmware-vix-disklib/:/usr/lib64/vmware-vix-disklib:ro \ --env-file <(env | grep OS_) registry.atmosphere.dev/library/migratekit:latest migrate \ --vmware-endpoint vcenter.somedomain.local \ --vmware-username user123 \ --vmware-password XXXXXX \ --vmware-path /GE%Office%20One/Projects/esx01.somedomain.local/test-vm-01 Results in: Error: vm '/GE%Office%20One/Projects/ esx01.somedomain.local/test-vm-01 ' not found I tried many different variants of the path none has worked. Is there a way to lookup the path of a VM? I can also use: virsh -c 'vpx:// user123(a)vcenter.somedomain.local /GE%Office%20One/Projects/esx01.somedomain.local?no_verify=1 list --all which shows me all VMs running on that particular ESXi host. Best Regards, Oliver

2 9

neutron
by Saeed 13 Sep '24

13 Sep '24

I run some scenarios with ML2/OVN and ML2/OVS (in all tests security-group has no rule) With the OVN backend, when port security is enabled I can NOT watch the unicast traffic of other instances by tcpdump, but when port security is disabled I can watch other unicast traffic for other instances. I also run the same scenarios when the backend is Openvswitch only (not OVN) I can watch unicast traffic of other instances (enabling or disabling port security has no impact). Is there any link or reference that explicitly explains this issue and the impact of OVN in OpenStack for dropping other traffic? I dump flow rules from openvswitch and compare them, and I'm pretty sure that the OVN adds some rules to drop other unicast traffic. Can I drop the unicast traffic of other instances in Openvswitch when I do not use OVN as the backend? (automatically or by configuration)

1 0

[neutron] OpenStack compute nodes L3 agent reconfiguration `dvr` mode to `dvr_no_external`
by frantisek.reznicek.szn＠gmail.com 13 Sep '24

13 Sep '24

Dear upstream OpenStack colleagues, we recently identified a lot of allocated "network:floatingip_agent_gateway ports" as we were running in pure dvr / dvr_snat modes (compute/network nodes) as also discussed in thread [1]. As we want to reduce amount of "network:floatingip_agent_gateway ports", our approach is to migrate majority of compute nodes from L3 agent `dvr` to `dvr_no_external` mode. Although we have success with empty nodes where we can see the node working as expected so north/south traffic now goes via network nodes on the non-empty compute nodes we struggle. The reconfiguration steps we are taking: 1. our maintenance per each compute node (still in `dvr` mode) 1.1. we first identify all VMs with FIP addresses, keep track of the FIPs and connected ports 1.2. we disconnect each FIP from port 1.3. all VMs on the compute node does not have FIPs 1.4. compute node L3 agent configuration is switched `dvr` -> `dvr_no_external` 1.5 delete `hypervisor network:floatingip_agent_gateway` port 1.6. re-attach all tracked FIPs 1.7. test FIP traffic At the step 1.7. we can see FIPs are not accessible after L3 agent re-configuration. Revert of the L3 agent configuration into `dvr` mode helps to get back the FIP connectivity. Our questions are: 1. Principally, can we get rid of `hypervisor network:floatingip_agent_gateway` ports by switching L3 agent to dvr_no_external mode? Can you think of a better way? 2. Would you recommend other steps how to migrate drom `dvr` to `dvr_no_external`? [2] Is it necesary to restart whole neutron / OVS or reconfigured L3 agent is just enough? Hope for your reply. ;-) Kind Regards, František [1] https://lists.openstack.org/pipermail/openstack-dev/2016-June/096384.html [2] https://opendev.org/openstack/neutron/src/branch/master/releasenotes/notes/…

3 2

[release] Release countdown for week R-2
by Thierry Carrez 13 Sep '24

13 Sep '24

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the 2024.2 Dalmatian deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/2024.2 branch creation for all deliverables that have not branched yet, using the latest available 2024.2 Dalmatian release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/2024.2 branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/2024.2 branch before releasing out of the stable/2024.2 branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for 2025.1 Epoxy development, though the focus should still be on finishing up 2024.2 (Dalmatian) until the final release. Opening up the new development cycle is also a good opportunity to teams to revise their zuul jobs and used nodesets and clean up all unnecessary ones. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final 2024.2 Dalmatian release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the 2024.2 Dalmatian version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: September 26th, 2024 (R-1 week) Final 2024.2 Dalmatian release: October 2nd, 2024 2025.1 Epoxy Project Teams Gathering: October 21-25, 2024 -- Thierry Carrez (ttx)

1 0

PTG October 2024 Teams List
by Kendall Nelson 13 Sep '24

13 Sep '24

Hello Everyone! The October 2024 Project Teams List is official! The following teams will be attending our Project Team Gathering, taking place October 21-25, 2024! Projects + Teams - OpenInfra Foundation Teams - - Diversity WG - Kata Containers - StarlingX - OpenStack - - Services - - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Keystone - Kolla - Manila - Neutron - Nova - Octavia - OpenStack-Ansible - OpenStack-Helm - QA - SDK/CLI - Sunbeam - Tacker - Other OpenStack Teams - OpenStack Security SIG - OpenStack Technical Committee - Public Cloud SIG - Adjacent Open Source Communities - - OceanBase If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — its FREE! As usual, feel free to let us know if you have any questions! Thanks! [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: http://ptg.openinfra.dev/

1 0