August 2023 - openstack-discuss - lists.openstack.org

[publiccloud-sig] Reminder - next meeting August 30th - 0700 UTC
by Felix Kronlage-Dammers 29 Aug '23

29 Aug '23

Hi everyone, this Wednesday the next meeting of the public cloud sig is going to happen. We meet on IRC in #openstack-operators at 0700 UTC. A preliminary agenda can be found in the pad: https://etherpad.opendev.org/p/publiccloud-sig-meeting See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on Wednesday! felix -- Felix Kronlage-Dammers Product Owner IaaS & Operations Sovereign Cloud Stack Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

[Neutron] Default gateway for IPv6 is 0
by Xing Zhang 29 Aug '23

29 Aug '23

Hello everyone, In my test environment, I noticed that the default gateway for IPv6 is changed from 1 to 0, is this correct? Reproduce steps are: * openstack cli: openstack network create test-ipv6-net openstack subnet create --subnet-range 2001:db8::200:0/64 --ip-version 6 --ipv6-ra-mode dhcpv6-stateful --ipv6-address-mode dhcpv6-stateful --network test-ipv6-net test-ipv6-subnet # the gateway_ip in the output is 2001:db8::200: but 2001:db8::200:1 is the expected IP * neutron cli: neutron net-create test-v6 neutron subnet-create --name test-v6-subnet --ip-version 6 test-v6 2002:db8::200:0/64 # the gateway_ip in the output is 2001:db8::200: but 2001:db8::200:1 is the expected IP there are 3 versions of OpenStack I've tested, the results are: OpenStack Rocky: 2001:db8::200:1 OpenStack Train: 2001:db8::200:1 OpenStack Wallaby: 2001:db8::200: the virtual router will use the gateway ip for port, and some hardware networking sdn controller for neutron may not work.

2 1

[ptls][tc] OpenStack User Survey Updates
by Allison Price 29 Aug '23

29 Aug '23

Hi Everyone, Like Helena mentioned last week, we are closing the 2023 OpenStack User Survey in a few weeks and will then open the 2024 OpenStack User Survey. At this time, we want to offer the project teams and TC the opportunity to update your project specific questions that appear at the end of the survey. As a reminder, for the project-specific questions, these appear if a survey taker selects your project in their deployment and TC questions appear to all survey takers. If you and your team would like to update the question, please let me know by Friday, August 18. I know that this is a holiday time for many, so if any team needs some extra time, just let me know. I am also able to share the existing questions with any team that needs a refresher on what is currently in the survey. In the meantime, please continue to promote openstack.org/usersurvey to anyone (and everyone!) you know who is running OpenStack or planning to in the future. We want to get as much feedback as we possibly can. Cheers, Allison

7 24

[all][elections][ptl][tc] Combined PTL/TC 2024.1 cycle Election Nominations Last Days
by Tony Breeds 28 Aug '23

28 Aug '23

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Aug 30, 2023 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. All members of the community are encouraged to confirm their email address and opt in to the CIVS election as described at: https://governance.openstack.org/election/#electorate Election statistics[2]: Nominations started @ 2023-08-16 23:45:00 UTC Nominations end @ 2023-08-30 23:45:00 UTC Nominations duration : 14 days, 0:00:00 Nominations remaining : 1 day, 22:20:09 Nominations progress : 86.21% --------------------------------------------------- Projects[1] : 48 Projects with candidates : 18 ( 37.50%) Projects with election : 0 ( 0.00%) --------------------------------------------------- Need election : 0 () Need appointment : 30 (Adjutant Barbican Blazar Cinder Cloudkitty Cyborg Ec2_Api Glance Heat Horizon Keystone Kuryr Manila Mistral Monasca Octavia OpenStack_Helm Openstack_Chef Puppet_OpenStack Rally Sahara Senlin Skyline Storlets Sunbeam Swift Tacker Telemetry Trove Venus) --------------------------------------------------- TC Candidates : 4 (4 Required) =================================================== Stats gathered @ 2023-08-29 01:24:51 UTC This means that with approximately 2 days left, 30 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.opendev.org/q/project:openstack/election+is:open+file:candid… have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for… Yours Tony.

1 0

[nova][election] Self-nomination for 2024.1 Nova PTL
by Sylvain Bauza 28 Aug '23

28 Aug '23

Hey Nova and Placement folks, Yet again, I'm asking you to put myself on the Nova and Placement PTL seat. For the exact same reasons than last time (see my previous nomination e-mail), I was convinced to run again for this position, which hopefully will be the last one (despite having already said it once). Challenges are still upfront. Our gate is still coughing every single day and despite the excellent work that a very few awesome people did on stabilizing and which helped improving the situation (kudos to those who will recognize themselves), we are still urging to fix the most common patterns. As a PTL, I'll ensure to keep the energy to chase those issues and identify them so as a team we can fight them. Another concern to me is the reviewing pace. While we're continuing to deliver solid reviews on feature proposals and patches, our team isn't much evolving and we need fresh blood. In order to be able to deliver things, we need to ensure that we properly recognize those who dedicate a portion of their daytime to help others by providing valuable feedback (and I stress on the fact that this feedback *has to* be valuable in order to by worthy). As a PTL, I'll continue to encourage people to express their thoughts and concerns into Gerrit comments so that we are able to count on. The last challenge I have to mention here is the release cadence. Now that more people are getting noticed of the SLURP cadence, we'll be awaited on delivering our next SLURP release, which will be 2024.1 (Caracal). I'll take special attention to that, ensuring that our skip-level-upgrade process we have in Nova will conveniently work with Caracal and that our release notes correctly include the upgrade steps for those who skip 2023.2 (Bobcat). I'll just finish on a last word. While I really appreciated acting as a PTL for the last 4 cycles, I'd be more than happy if someone would like to step up and compete for the seat. I personnally prefer expansion over attrition and one of my favourite tasks is mentoring. Thanks, -Sylvain

1 0

Red Hat Open stack external IP pool change
by Adivya Singh 28 Aug '23

28 Aug '23

Hi Team, Does any body have seen this issue, I am running RHOSP 16 2023-08-28 13:24:29Z [overcloud-Networks-xtd6lzqc6hhx-ExternalNetwork-ssk732o4rze6.ExternalSubnet]: UPDATE_FAILED NotSupported: resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS::Neutron::Subnet) is not supported. 2023-08-28 13:24:29Z [overcloud-Networks-xtd6lzqc6hhx-ExternalNetwork-ssk732o4rze6]: UPDATE_FAILED Resource UPDATE failed: NotSupported: resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS::Neutron::Subnet) is not supported. 2023-08-28 13:24:30Z [overcloud-Networks-xtd6lzqc6hhx.ExternalNetwork]: UPDATE_FAILED NotSupported: resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. 2023-08-28 13:24:30Z [overcloud-Networks-xtd6lzqc6hhx]: UPDATE_FAILED Resource UPDATE failed: NotSupported: resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. 2023-08-28 13:24:30Z [Networks]: UPDATE_FAILED NotSupported: resources.Networks.resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. 2023-08-28 13:24:30Z [overcloud]: UPDATE_FAILED Resource UPDATE failed: NotSupported: resources.Networks.resources.ExternalNetwork.resources.ExternalSubnet: Update to properties cidr of ExternalSubnet (OS: : Neutron: : Subnet) is not supported. I delete the interface from OVS bridge and restart the OVS services and re push the templates Or I change the File manually, Configure any floating ip range , Add the route manually , and restart the Network services Any thought on this Regards Adivya Singh

1 0

[neutron] Bug Deputy Report August 21 - 27
by Nurmatov Mamatisa 28 Aug '23

28 Aug '23

Hi, Below is the week summary of bug deputy report for last week. Undecided bugs needs further triage. Details: High ---- - https://bugs.launchpad.net/neutron/+bug/2032738 - [os-ken] [CI] Jobs setting up os-ken from pypi instead of patch in review - Fixed: https://review.opendev.org/c/openstack/os-ken/+/892452 - Assigned to Yatin Karel - https://bugs.launchpad.net/neutron/+bug/2032817 - OVN: Distributed FIP packet drops when provider network MTU exceeds tenant network MTU - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/2033090 - Able to change vnic type on a bound port - In progress: https://review.opendev.org/c/openstack/neutron/+/892815 - Assigned to Jakub Libosvar Medium ------ - https://bugs.launchpad.net/neutron/+bug/2032169 - OVN synchronized too many segments - In progress: https://review.opendev.org/c/openstack/neutron/+/891930 - Assigned to Zhou Heng - https://bugs.launchpad.net/neutron/+bug/2032183 - [CI] UT py311 job failing, "libmysqlclient-dev" missing - Fixed: https://review.opendev.org/c/openstack/neutron/+/892142 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/2032765 - [L3][DVR]disable ARP response for vlan networks on compute node - Confirmed - Unassigned Low --- - https://bugs.launchpad.net/neutron/+bug/2032770 - [OVN] port creation with --enable-uplink-status-propagation does not work with OVN mechanism driver - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/2032929 - OVN security group logging burst limit has an unexpected value for stateless security groups - In progress: https://review.opendev.org/c/openstack/neutron/+/892648 - Assigned to Elvira García Ruiz - https://bugs.launchpad.net/neutron/+bug/2033203 - Quality of Service (QoS) in Neutron - Confirmed - Unassigned Undecided --------- - https://bugs.launchpad.net/neutron/+bug/2032973 - Neutron is not creating DNS records when recreating an instance with the same floating IP - https://bugs.launchpad.net/neutron/+bug/2033179 - Using .local as TLD in dns testing is breaking some scenarios Invalid ------ - https://bugs.launchpad.net/neutron/+bug/2033083 - [OVN] The router GW is "restoring" the NAT rule that disables SNAT - Ironic bug Best regards, Mamatisa Nurmatov Advanced Software Technology Lab / Cloud Technologies Research

1 0

TripleO deployment over IPV6
by Kushagr Gupta 25 Aug '23

25 Aug '23

Hi Team, We were trying to perform IPV6-based deployment of TripleO. We are following the link: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… As per our environment, we set the "ipv6_address_mode" to "dhcpv6-stateful" and tried undercloud deployment. It was successful. But when we try node introspection, openstack is not providing an IP that will be used for PXE booting the system. We have enabled PXE booting on the IPV6 network. On Dell machines, we get the following error: "PXE-E16: No offer received." For your reference, the undercloud file which we used is attached. We also tried to find the communication happening on the br-ctlplane interface when the machine tries to boot over IPV6 PXE boot. I am attaching those tcpdump records as well. We are unable to find the MAC address of our machines. *Questions:* 1. Is it even possible to perform tripleO deployment with IPV6? 2. Do we need to do some extra settings, so that our baremetal machines can be PXE booted? Thanks and Regards

3 9

Live migration between centos and ubuntu compute nodes
by Jim Kilborn 25 Aug '23

25 Aug '23

Openstack peers: I am migrating our production openstack environment from centos7 to ubuntu. I am on the train release currently, so I can have that release on both centos7 and ubuntu 18 The issue is that I need to live migrate the vms if it's possible. When I try, I get an error on the source compute node (centos 7). Live Migration failure: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory: libvirtError: Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory Any ideas how to get around this until I get my vms migrated? Maybe create a link on the ubuntu 18 host? I'm sure I am not the first to leave centos 7 for ubuntu Thanks for any help on this.

2 1

[keystone] outstanding reviews for federation fix
by Mohammed Naser 25 Aug '23

25 Aug '23

Hi there, Can I please get eyes on https://review.opendev.org/q/I665b7e0234650ba07e0d030a2d442d6599d0888a ? We’ve been carrying this down for too long and it’s a very simple fix. Thanks, Mohammed

2 1

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 25 Aug '23

25 Aug '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0

[release] Release countdown for week R-5, Aug 28 - Sep 01
by Thierry Carrez 25 Aug '23

25 Aug '23

Development Focus ----------------- We are getting close to the end of the 2023.2 Bobcat cycle! Next week on August 31st is the bobcat-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to the 2024.1 Caracal cycle. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on August 31st. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.2 branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… August 31st is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data that helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Bobcat-3 milestone (feature freeze): August 31st (R-5 week) RC1 deadline: September 14th (R-3 week) Final RC deadline: September 28th (R-1 week) Final 2023.2 Bobcat release: October 4th, 2023 -- Thierry Carrez (ttx)

1 0

[ptl][election][neutron] PTL candidacy for 2024.1
by Brian Haley 24 Aug '23

24 Aug '23

Hello Openstack Community, I am writing to submit my candidacy for the Neutron PTL position during the 2024.1 cycle. I have worked on Openstack since Diablo (2011), starting as a cloud operator doing L2 overlay development, along with agent performance and scalability on large-scale deployments. During that time I've become a core contributor (2015) and been part of the team making sure our stable branches continue to receive all the back-ports necessary to make downstream consumption easier. I currently work for Canonical in their Sustaining Engineering group, primarily addressing customer issues, with a focus on processes and tools to help us more quickly solve them. My priorities as PTL would be the following: * Always make sure the stable branches are consumable downstream. Distros and operators are, in my opinion, the lifeblood of Openstack, so we have to make sure they are top of mind when fixing bugs, and that back-ports are done in a timely manner. * Continue pursuing CI stability. During the past 6+ cycles the Neutron community has done a great job keeping its CI healthy, as well as actively updating jobs to make sure we use resources wisely and reduce re-checks. * Keep working on, or complete, ongoing specs. There are a number of larger specs that have a great deal of development in progress, I know we can get some of these completed this cycle: ** Active-active L3 Gateway with Multihoming (LP #2002687) ** Multiple back-end support for L3 routers in ML2/OVN (LP #2020823) ** Configurable Security Group rules added by default to new Security Groups (LP #1983053) ** ML2/OVN IPv6 Distributed routing (LP #1998609) * Continue reducing the bug backlog. Over the past few cycles we were able to fix and/or close about 1/3 of our backlog (~400 bugs), but it will slowly creep back up if we let it. We also have to continue looking forward by: * Keeping the Neutron stadium ecosystem alive and healthy. There are a number of diverse projects, some without a large number of resources. We must make sure those communities receive whatever help they need, whether it's making sure we address bugs affecting them, or helping keep their CIs green. * Address any SQLAlchemy 2.0 migration issues detected. We have done a great job during the last few releases with this work, let's keep that up in 2024.1. * Starting development on newly proposed specs ** OVN interconnection (LP #2027742) * Always welcoming new contributors. Thanks for your support. -Brian Haley (haleyb, haleyb.dev(a)gmail.com)

1 0

Cinder Bug Report 2023-08-23
by Jon Bernard 23 Aug '23

23 Aug '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Medium - Cinder-Backup stuck in creating after RBD export-diff existed and turned into zombie / <defunct> <https://bugs.launchpad.net/cinder/+bug/2031897> - Status: No comments or fix proposed Undecided - Cinder allows updating default volume type <https://bugs.launchpad.net/cinder/+bug/2031653> - Status: In Progress - Extending an attached volume leaves multipath device in inconsistent state <https://bugs.launchpad.net/os-brick/+bug/2032177> - Status: In Progress Thanks -- Jon

1 0

[puppet] Proposing core team clean up
by Takashi Kajinami 23 Aug '23

23 Aug '23

Hello, I went through the current core reviewers and found out that the current list includes some people no longer working in the OpenStack community. I'd like to propose removing the following persons from the core reviewer team as we haven't seen these people making any activity in the community recently. * Pradeep Kilambi - puppet-aodh, puppet-ceilometer, puppet-gnocchi, puppet-panko * Richard Megginson - puppet-keystone * Denis Egorenko - puppet-murano * Serg Melikyan - puppet-murano * Sergey Kolekonov - puppet-neutron * David Moreau Simard - puppet-openstack-integration * Yu xingchao - all modules Also, I confirmed that Wes Hayutin is no longer working for OpenStack and he agreed to retire from the core reviewer position. Thus I'll remove him as well. I'll be open for any feedback for one week to hear any thoughts/feedback about this removal. I'd like to take this moment to thank all people for their past work. We always welcome them back if they resume their work in this project. Thank you, Takashi KAJINAMI

3 4

Cyber Resilience Act: What Now? Aug 24 at 9 AM (CST) / 14:00 UTC
by Kristin Barrientos 23 Aug '23

23 Aug '23

Hi everyone, This week’s OpenInfra Live episode is brought to you by open source community leaders. Episode: On this episode of OpenInfra Live, we will discuss the EU Cyber Resilience Act's impact on open source software. The OpenInfra Foundation and many other open source organizations have expressed concerns about the proposed text, urging the European lawmakers to take into account the specificity of open source open collaboration in the legislation. Join and engage live with our expert panelists as they discuss the current state of the proposal, its potential consequences, what we can still do about it, and what other pieces of upcoming legislation we should watch for. Date and time: Aug 24, 2023 at 9:00 AM CST (14:00 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=u6Dh0nXivqM LinkedIn: https://www.linkedin.com/events/7095407763538763776/comments/ WeChat: The recording will be posted on OpenInfra Foundation WeChat after the live stream Speakers: Thierry Carrez, Allison Randal, Mike Milinkovich, Ciarán O'Riordan Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks, Kristin Barrientos Marketing Coordinator OpenInfra Foundation

1 0

[cinder] 2023.2 (Bobcat) R-6 virtual mid cycle on 23 Aug, 2023
by Rajat Dhasmana 23 Aug '23

23 Aug '23

Hello Argonauts, As discussed in last week's cinder upstream meeting[1], we will be conducting our second mid cycle of 2023.2 Bobcat on 23rd August, 2023 (R-6 week). Following are the details: Date: 23rd August, 2023 Time: 1400-1600 UTC Meeting link: https://meet.google.com/qqs-xjzg-ccm Etherpad: https://etherpad.opendev.org/p/cinder-bobcat-midcycles We have almost a week's time so please add your topics! [1] https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-…

1 2

[neutron][tap-as-a-service][release] Deletion old branches of taas
by Rodolfo Alonso Hernandez 23 Aug '23

23 Aug '23

Hello: I would like to revive the mail sent by Lajos about this topic: https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03127…. In a nutshell: we don't have releases from Ocata to Stein of TaaS because it was moved out from the stadium projects. However we still have issues with the zuul configs. Because we can't release an EOL patch, I would ask the release team to remove these 5 branches (Ocata, Pike, Queens, Rocky and Stein) from the git repository. If that is not possible, I'll send patches to these branches to remove the .zuul file. Regards. [1]https://zuul.opendev.org/t/openstack/config-errors

1 0

[ovn] VM in external network unable to arp
by Justin Lamp 22 Aug '23

22 Aug '23

Hey, we are using OVN 22.03 and face an issue where a VM that is directly connected to the provider network won't be accessible, because it cannot arp for the Gateway IP. OVN routers do reply to the arp request though. We know that this exact scenario works as we have it running in our staging environment. Oddly enough if the right MAC-IP Binding is manually defined within the VM and the Gateway, the traffic will begin to flow correctly according to the right SGs. I did an ovn-trace and were able to see that the traffic is supposed to be flooded to the right ports. The ovs-trace on the other hand did not show the same picture. It just did 4k recirculations and then dropped the packet. I already restarted the ovn-controller on the right hv, but that did not do anything. The LSP: $ ovn-nbctl list Logical_Switch_Port cfce175b-9d88-4c2e-a5cc-d76cd5c71deb _uuid : c5dfb248-941e-4d4e-af1a-9ccafc22db70 addresses : ["fa:16:3e:a2:d7:1a 2a02:ed80:0:3::341 91.198.2.33"<fa:16:3e:a2:d7:1a2a02:ed80:0:3::34191.198.2.33>] dhcpv4_options : 1922ee38-282f-4f5c-ade8-6cd157ee52e9 dhcpv6_options : [] dynamic_addresses : [] enabled : true external_ids : {"neutron:cidrs"<neutron:cidrs>="2a02:ed80:0:3::341/64 91.198.2.33/24", "neutron:device_id"<neutron:device_id>="8062ec61-0c68-41dd-b77c-e8b72ad16a88", "neutron:device_owner"<neutron:device_owner>="compute:AZ1"<compute:AZ1>, "neutron:network_name"<neutron:network_name>=neutron-210e26d7-942f-4e17-89b2-571eee87d7e4, "neutron:port_name"<neutron:port_name>="", "neutron:project_id"<neutron:project_id>="99fb21796a8f4cbda42ba5b9d1e307dd", "neutron:revision_number"<neutron:revision_number>="16", "neutron:security_group_ids"<neutron:security_group_ids>="3e41777f-7aa4-4368-9992-5ca7cc2a5372 873b3b62-0918-4b1e-be73-fdbed50d2ac2"} ha_chassis_group : [] name : "cfce175b-9d88-4c2e-a5cc-d76cd5c71deb" options : {mcast_flood_reports="true", requested-chassis=net-openstack-hv31} parent_name : [] port_security : ["fa:16:3e:a2:d7:1a 2a02:ed80:0:3::341 91.198.2.33"<fa:16:3e:a2:d7:1a2a02:ed80:0:3::34191.198.2.33>] tag : [] tag_request : [] type : "" up : true The PB: $ ovn-sbctl find Port_Binding logical_port=cfce175b-9d88-4c2e-a5cc-d76cd5c71deb _uuid : e9e5ce44-698f-4a29-acd1-2f24cc1d1950 chassis : c944c21a-3344-4fda-ab4e-a4cc07403125 datapath : 993b44d5-1629-4e9b-b44e-24096d8b3959 encap : [] external_ids : {"neutron:cidrs"<neutron:cidrs>="2a02:ed80:0:3::341/64 91.198.2.33/24", "neutron:device_id"<neutron:device_id>="8062ec61-0c68-41dd-b77c-e8b72ad16a88", "neutron:device_owner"<neutron:device_owner>="compute:AZ1"<compute:AZ1>, "neutron:network_name"<neutron:network_name>=neutron-210e26d7-942f-4e17-89b2-571eee87d7e4, "neutron:port_name"<neutron:port_name>="", "neutron:project_id"<neutron:project_id>="99fb21796a8f4cbda42ba5b9d1e307dd", "neutron:revision_number"<neutron:revision_number>="16", "neutron:security_group_ids"<neutron:security_group_ids>="3e41777f-7aa4-4368-9992-5ca7cc2a5372 873b3b62-0918-4b1e-be73-fdbed50d2ac2"} gateway_chassis : [] ha_chassis_group : [] logical_port : "cfce175b-9d88-4c2e-a5cc-d76cd5c71deb" mac : ["fa:16:3e:a2:d7:1a 2a02:ed80:0:3::341 91.198.2.33"<fa:16:3e:a2:d7:1a2a02:ed80:0:3::34191.198.2.33>] nat_addresses : [] options : {mcast_flood_reports="true", requested-chassis=net-openstack-hv31} parent_port : [] requested_chassis : c944c21a-3344-4fda-ab4e-a4cc07403125 tag : [] tunnel_key : 344 type : "" up : true virtual_parent : [] The LS: $ ovn-nbctl list Logical_Switch public-network _uuid : 56d8be55-462a-4b93-8710-3c79ca386213 acls : [] copp : [] dns_records : [] external_ids : {"neutron:mtu"<neutron:mtu>="1500", "neutron:network_name"<neutron:network_name>=public-network, "neutron:revision_number"<neutron:revision_number>="21"} forwarding_groups : [] load_balancer : [] load_balancer_group : [] name : neutron-210e26d7-942f-4e17-89b2-571eee87d7e4 other_config : {mcast_flood_unregistered="false", mcast_snoop="false"} ports : [00225774-8fbc-473f-ae5e-d486c54212c8, ..., c5dfb248-941e-4d4e-af1a-9ccafc22db70, ... qos_rules : [] The patchport: $ ovn-nbctl list Logical_Switch_Port provnet-aa35051c-6fc0-463a-8807-0cb28903be14 _uuid : f7259aeb-0e63-4d20-8a8e-54ebf454a524 addresses : [unknown] dhcpv4_options : [] dhcpv6_options : [] dynamic_addresses : [] enabled : [] external_ids : {} ha_chassis_group : [] name : provnet-aa35051c-6fc0-463a-8807-0cb28903be14 options : {mcast_flood="false", mcast_flood_reports="true", network_name=physnet1} parent_name : [] port_security : [] tag : [] tag_request : [] type : localnet up : false I hope I provided the needed context! Thanks in advance! Best regards, Justin Lamp -- 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 2023 - September - https://stackconf.eu ** ** OSMC 2023 - November - https://osmc.de ** ** NETWAYS Web Services - https://nws.netways.de ** ** NETWAYS Trainings - https://netways.de/trainings **

4 5

Need assistance
by Gk Gk 22 Aug '23

22 Aug '23

Hi All, We have an openstack ansible stein version setup. We had a vm on it which we deleted. The associated neutron port was also deleted and the vm uuid is gone from the nova as well. It had a provider network ip. Even after deleting the vm, we are still finding that ssh port 22 on that IP is responding. So I logged into the hypervisor (compute node) on which that vm was there before deletion and found that the libvirtd service was is error state with the following logs in the nova-compute service: --------- 2023-08-18 10:08:51.463 12587 INFO nova.service [-] Starting compute node (version 19.3.2) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host self.force_reraise() 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host six.reraise(self.type_, self.value, self.tb) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 442, in _get_connection 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host self._wrapped_conn = self._get_new_connection() 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 396, in _get_new_connection 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host wrapped_conn = self._connect(self._uri, self._read_only) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 252, in _connect 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host libvirt.openAuth, uri, auth, flags) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/eventlet/tpool.py", line 148, in proxy_call 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host rv = execute(f, *args, **kwargs) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/eventlet/tpool.py", line 129, in execute 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host six.reraise(c, e, tb) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/eventlet/tpool.py", line 83, in tworker 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host rv = meth(*args, **kwargs) 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/libvirt.py", line 104, in openAuth 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host if ret is None:raise libvirtError('virConnectOpenAuth() failed') 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused 2023-08-22 14:28:07.670 12587 ERROR nova.virt.libvirt.host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service [req-4108e9e2-2afd-472e-a4d9-fcccffc380dc - - - - -] Error starting thread.: HypervisorUnavailable: Connection to the hypervisor is broken on host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service Traceback (most recent call last): 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/oslo_service/service.py", line 810, in run_service 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service service.start() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/service.py", line 176, in start 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service self.manager.init_host() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/compute/manager.py", line 1225, in init_host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service self.driver.init_host(host=self.host) 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 503, in init_host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service self._do_quality_warnings() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 471, in _do_quality_warnings 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service caps = self._host.get_capabilities() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 664, in get_capabilities 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service xmlstr = self.get_connection().getCapabilities() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service File "/openstack/venvs/nova-stein-em/lib/python2.7/site-packages/nova/virt/libvirt/host.py", line 482, in get_connection 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service raise exception.HypervisorUnavailable() 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service HypervisorUnavailable: Connection to the hypervisor is broken on host 2023-08-22 14:28:07.676 12587 ERROR oslo_service.service 2023-08-22 14:28:07.678 12587 INFO nova.virt.libvirt.driver [-] Connection event '0' reason 'Failed to connect to libvirt: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused' ----- However that particular neutron port for that vm is also deleted. We cant find it in the neutron db. So how is it possible for that VM IP to be responding on port 22 even after it is deleted. Please help me here. Thanks Kumar

4 3

vPTG October 2023 Teams List
by Kendall Nelson 22 Aug '23

22 Aug '23

Hello Everyone! The October 2023 Project Teams List is official! Projects + Teams - OpenInfra Foundation Teams - - Diversity & Inclusion Working Group - OpenInfra Edge Computing Group - Environmental Sustainability Working Group - StarlingX - OpenStack - - Services - - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Kolla - Manila - Neutron - Nova - Octavia - OpenStack Charms - OpenStack-Helm - Quality Assurance - OpenStackSDK/CLI - Swift - Tacker - Other OpenStack Teams - - Interoperability Working Group - OpenStack Security SIG - PublicCloud SIG If your team was planning to meet and isn’t on 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] — It's FREE! As usual, feel free to let us know if you have any questions! Thanks! -Kendall (diablo_rojo) [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: http://ptg2023.openinfra.dev/

1 0

Collaborating Without Boundaries Working Group - Meeting #2 Tomorrow at 1500 UTC
by Helena Spease 22 Aug '23

22 Aug '23

Hi everyone! Tomorrow at 1500 UTC the OpenInfra Collaborating Without Boundaries Working Group is meeting! If you are a university or organization interested in OpenStack training come learn from Seongsoo Cho, how the Korean User Group is partnering with local universities to provide training opportunities to students. Etherpad : https://meetpad.opendev.org/etherpad/p/cwb <https://meetpad.opendev.org/etherpad/p/cwb> Meetpad: https://meetpad.opendev.org/CWB <https://meetpad.opendev.org/CWB> Cheers, Helena helena(a)openinfra.dev Marketing & Community Coordinator The OpenInfra Foundation

1 0

[tc] Technical Committee Next Weekly Meeting, Today on August 22, 2023
by Nikolla, Kristi 22 Aug '23

22 Aug '23

Hi all, This is a reminder that the next weekly Technical Committee meeting is to be held Today, on Tuesday, 22 August 2023 at 1800 UTC on #openstack-tc on OFTC IRC. The agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and attached below. • Roll call • Follow up on past action items • No action items • Gate health check • Documenting implementation processes for Unmaintained • With the resolution being merged, the next step is defining and documenting the processes and implementing the required tooling. • Open Discussion and Reviews • https://review.opendev.org/q/projects:openstack/governance+is:open Thank you, Kristi Nikolla

1 0

[dev][glance_storage][s3] improving download speed from s3 backend
by Gökhan Koçak 22 Aug '23

22 Aug '23

Hello everyone, I did not find any option to use something like multipart downloads (only uploads) or concurrency when downloading from s3 storage. So my first question is if this is correct? Second, I see that boto3 is being used: https://opendev.org/openstack/glance_store/src/branch/master/glance_store/_… and I wonder if it is possible to implement using the concurrency settings from boto: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/customiza… ? Best, Gökhan

1 0

[nova] Slow nvme performance for local storage instances
by Jan Wasilewski 22 Aug '23

22 Aug '23

Hi, I am reaching out to inquire about the performance of our local storage setup. Currently, I am conducting tests using NVMe disks; however, the results appear to be underwhelming. In terms of my setup, I have recently incorporated two NVMe disks into my compute node. These disks have been configured as RAID1 under md127 and subsequently mounted at /var/lib/nova/instances [1]. During benchmarking using the fio tool within this directory, I am achieving approximately 160,000 IOPS [2]. This figure serves as a satisfactory baseline and reference point for upcoming VM tests. As the next phase, I have established a flavor that employs a root disk for my virtual machine [3]. Regrettably, the resulting performance yields around 18,000 IOPS, which is nearly ten times poorer than the compute node results [4]. While I expected some degradation, a tenfold decrease seems excessive. Realistically, I anticipated no more than a twofold reduction compared to the compute node's performance. Hence, I am led to ask: what should be configured to enhance performance? I have already experimented with the settings recommended on the Ceph page for image properties [5]; however, these changes did not yield the desired improvements. In addition, I attempted to modify the CPU architecture within the nova.conf file, switching to Cascade Lake architecture, yet this endeavor also proved ineffective. For your convenience, I have included a link to my current dumpxml results [6]. Your insights and guidance would be greatly appreciated. I am confident that there is a solution to this performance disparity that I may have overlooked. Thank you in advance for your help. /Jan Wasilewski *References:* *[1] nvme allocation and raid configuration: https://paste.openstack.org/show/bMMgGqu5I6LWuoQWV7TV/ <https://paste.openstack.org/show/bMMgGqu5I6LWuoQWV7TV/>* *[2] fio performance inside compute node: https://paste.openstack.org/show/bcMi4zG7QZwuJZX8nyct/ <https://paste.openstack.org/show/bcMi4zG7QZwuJZX8nyct/>* *[3] Flavor configuration: https://paste.openstack.org/show/b7o9hCKilmJI3qyXsP5u/ <https://paste.openstack.org/show/b7o9hCKilmJI3qyXsP5u/>* *[4] fio performance inside VM: https://paste.openstack.org/show/bUjqxfU4nEtSFqTlU8oH/ <https://paste.openstack.org/show/bUjqxfU4nEtSFqTlU8oH/>* *[5] image properties: https://docs.ceph.com/en/pacific/rbd/rbd-openstack/#image-properties <https://docs.ceph.com/en/pacific/rbd/rbd-openstack/#image-properties>* *[6] dumpxml of vm: https://paste.openstack.org/show/bRECcaSMqa8TlrPp0xrT/ <https://paste.openstack.org/show/bRECcaSMqa8TlrPp0xrT/>*

5 18