- openstack-discuss - lists.openstack.org

[all][tc][ptg] OpenStack TC Flamingo PTG Schedule, Etherpad and Weekly Meeting updates
by Goutham Pacha Ravi 04 Apr '25

04 Apr '25

Hello Stackers, The OpenStack Technical Committee has scheduled discussions at the following time slots next week: - April 7 2025: 1300 UTC to 1500 UTC - April 11 2025: 1500 UTC to 1700 UTC You can find the discussion times and meeting details on this etherpad: https://etherpad.opendev.org/p/apr2025-ptg-os-tc Of special importance is the TC/Community Leaders forum session on 2025-04-11 at 1500 UTC. The list of topics for this forum session can expand over the week. If you're a maintainer on any OpenStack repository, or an aspiring maintainer, please do join us there. The etherpad, the schedule and a link to the meeting room can also be found on the PTG website [1]. At this time, if you'd like to add more topics, please reach out to me, or chime-in on the #openstack-tc channel on OFTC. In lieu of the PTG, we'll not have the regular weekly IRC meeting next week. The IRC meeting will be back on 2025-04-15 [2]. Thank you, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://ptg.opendev.org/ptg.html [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee

1 0

[nova] vGPU not attached to VM using Cyborg with OpenStack Caracal
by ts.jung＠okestro.com 04 Apr '25

04 Apr '25

Hello, I'm facing an issue with vGPU assignment through Cyborg in OpenStack Caracal. Although Cyborg reports that the ARQ is bound successfully, the vGPU device is not attached to the VM in Nova. - Environment: OS: Ubuntu 22.04.3 LTS Kernel: 5.15.0-78-generic Nova API: 29.2.0 Cyborg API: 14.1.0.dev1 GPU: NVIDIA A100 PCIe 40GB - Device Profile: openstack accelerator device profile list +--------------------------------------+------+-----------------------------------------------------------------------------+ | uuid | name | groups | +--------------------------------------+------+-----------------------------------------------------------------------------+ | 8425925f-7a3c-4336-8a1c-270f481a28ae | vgpu | [{'resources:VGPU': '1', 'trait:CUSTOM_NVIDIA_20F1_A100_1_5C': 'required'}] | +--------------------------------------+------+-----------------------------------------------------------------------------+ Flavor: openstack flavor show vgpu --column properties +------------+-----------------------------+ | Field | Value | +------------+-----------------------------+ | properties | accel:device_profile='vgpu' | +------------+-----------------------------+ Result After VM Creation: openstack accelerator arq list +--------------------------------------+------+-----------------------------------------------------------------------------+ | uuid | name | groups | +--------------------------------------+------+-----------------------------------------------------------------------------+ | 8425925f-7a3c-4336-8a1c-270f481a28ae | vgpu | [{'resources:VGPU': '1', 'trait:CUSTOM_NVIDIA_20F1_A100_1_5C': 'required'}] | +--------------------------------------+------+-----------------------------------------------------------------------------+ ARQ shows Bound with an attach_handle_type of MDEV, but the GPU device is not visible inside the VM. mdevctl list # Shows UUID and mdev type virsh dumpxml instance-xxxx # No mdev device listed Logs (Summary) Cyborg logs indicate ARQ binding was successful and attach handle allocated (MDEV). Nova-compute logs show: Ignoring accelerator requests for instance ... Supported Attach handle types: {'PCI'}. But got these unsupported types: {'MDEV'}. Question. Is there something I’m missing in the integration between Cyborg and Nova for MDEV attach_handle_type? It seems like Nova is not yet supporting MDEV, even though Cyborg bound the ARQ correctly. Any suggestions or known workarounds would be appreciated. Thank you!

2 1

[i18n] i18n SIG - 2025.2 (Flamingo) Virtual PTG Schedule
by Ian Y. Choi 04 Apr '25

04 Apr '25

Hi, I would like to share the i18n SIG schedule for the upcoming PTG. Dates and locations are: • April 9th, 1400 ~ 1500 UTC at kilo-WedB2 (Please find https://ptg.opendev.org/ptg.html for real time information) Note that I18n PTG Etherpad link is: https://etherpad.opendev.org/p/apr2025-ptg-i18n . Looking forward to the meeting and interactions during the PTG! Thank you, /Ian

1 0

[Octavia] Active/Standby with AZ
by Vincent Godin 04 Apr '25

04 Apr '25

Hello, To address the Octavia and Cinder backend mismatch, I'm going to temporarily create a Cinder backend stretched across all three AZs. Now I have another question: is it possible to use Octavia AZs to set up an active/standby load balancer so that the active load balancer is on one AZ and the standby load balancer is on another one ? Of course, the network is stretched across all three AZs, so the VRRP mechanism is possible. Vincent

3 2

Neutron
by Bowley, Jonathan T 04 Apr '25

04 Apr '25

Hey I've been struggling with trying to get my kolla-ansible openstack multinode deployment working with my external trunked port i have openstack connected to and also using my external dhcp server. Does anyone have any thoughts on what I could be missing? I grasping at straws at this point and ill buy ya dinner if you can help me! when I launch a vm i see it assigning vms an ip but its no way its coming from my external dhcp server i think its just coming from its own pools. Also to add I'm using 2024.2 My global yaml - enable_neutron_provider_networks: "yes" neutron_external_interface: "bond0" network_interface: "eno3" when running ip a i see which i have no clue if they are suppose to say down in my head it doesn't seem right but im not sure because i havent had a successful deployment yet so not sure what its suppose to look like. bond0 <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovs-system state UP group default qlen 1000 ovs-system ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 br-ex: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 extra conf files /etc/kolla/config/neutron/ml2_conf.ini [ml2] type_drivers = vlan tenant_network_types = vlan mechanism_drivers = openvswitch extension_drivers = port_security [ml2_type_vlan] network_vlan_ranges = physnet1:100:100,physnet1:144:144,physnet1:513:513 /etc/kolla/config/neutron/openvswitch_agent.ini [ovs] bridge_mappings = physnet1:br-ex Thanks, Jonathan Bowley IT Specialist / DevOps Engineer / SysAdmin IT Services National Geospatial Technical Operations Center (NGTOC<http://ngtoc.usgs.gov/>) U.S. Geological Survey Rolla, Missouri

2 1

Non predictable device name/path in libvirt/qemu config with multipath
by Gilles Mocellin 03 Apr '25

03 Apr '25

Hello Stackers, Today I had a stressful problem. While doing system upgrades on my Ubuntu based OpenStask-Ansible deployment, with Pure Storage cinder driver and boot from volume instances, I faced that problem : While migrating instances to evacuate a compute node, several instances never wanted to live migrate (Kubernetes workers with 16GB RAM). After restarting several times, attempting to change some nova/libvirt configuration (certainly not taken, because qemu was not restarted on source host), I decider to cold migrate thoses instances. So I simply use : openstack server migrate instance-uuid The instances tried to start on other compute node, but failed. Two have the same problem I would talk about, the third just didn't find the volume/LUN on the storage Array (also very weird). So, why the other two didn't start ? They wanted to use a multipath map that was already in use. And really in use from another instance. the multipath -f mpathxy was tried and make the multipath map unusable for the instance which used it. It was the database of an important app, to add a little bit of stress. This is not happening with successful live migration, I only see it with cold migrations. But with some instances, I really don't manage to have a successful live migration, so it can be useful to also have a working cold migration (I mean stop, migrate, and start the instance). So, my questions are : 1. Should multipath.conf enable or not user friendly names ? I didn't find a recommended multipath config. I saw both in kolla templates (not using friendly names) or starlingX ones or old bugs (using friendly names, for data flush to really be effective on paths...) Didn't find yet if openstack-ansible is managing multipath or not. I would say that without friendly names, we have predictable names in /dev/ mapper/ (with WWN), that if used couldn't lead to device "steal" if every instance record that predictable device. 2. Is there some configuration for libvirt/qemu ? Because, in the libvirt/qemu instance config file, the devices are not the multipath map but the /dev/dm-XY where the multipath map symlinks to... Also not predictable and changing, especially when changing compute hosts with different number of accessible volumes... Did someone already had those problems, and how do you handled it ?

1 0

[manila] Cancelling Apr 10th and Apr 17th weekly meetings
by Carlos Silva 03 Apr '25

03 Apr '25

Hello, As traditionally done around the PTG time frame, we are cancelling the Manila upstream weekly meeting for the PTG week and the week after. We will get back to our weekly meetings on Apr 24th. Wishing everyone a very productive PTG! Regards, carloss

1 0

[manila] PTG schedule
by Carlos Silva 03 Apr '25

03 Apr '25

Hello Zorillas and interested stackers, Earlier in the weekly meeting I presented the tentative schedule for the next week's PTG [1]. Please take a look at it and let me know in case you'd like any time slot changes. I'll do my best to address it by tomorrow. [1] https://etherpad.opendev.org/p/flamingo-ptg-manila I'm looking forward to seeing you in the next week's PTG! Regards, carloss

1 0

Help needed: How to deploy DevStack with HTTPS enabled
by saikumar pulluri 03 Apr '25

03 Apr '25

Hi everyone, I am reaching out to seek assistance regarding the deployment of DevStack with HTTPS enabled. I would greatly appreciate any guidance provided on this. Thanks in Advance!! Best regards, Sai

2 2

Roles in documentation vs. actual permissions
by Jani Heikkinen 03 Apr '25

03 Apr '25

I have been installing Openstack Dalmation 2024.2 on Debian Bookworm. I've noticed when creating an user on default domain on a demo project, and run 'openstack role add --project demo --user myuser admin', this user will have the whole system-wide admin rights thereafter. Is this intended? Documentation[1]. claims that an admin could have project-wide scope only. Is there some underlying assumption that I create myself the project_admin, domain_admin, domain_manager, project_manager roles and modify policies in keystone, and this would be the reason why the scopes do not work? Same issues seem to be touching the "manager" role, of which I already opened a bug report. Best, Jani [1.] https://docs.openstack.org/keystone/latest/admin/service-api-protection.html Berner Fachhochschule / Bern University of Applied Sciences IT-Services / Team Linux & Infrastructure Services Jani Heikkinen IT Linux Engineer ___________________________________________________________ Dammweg 3, CH-3013 Bern Telefon direkt +41 31 848 68 14 Telefon Servicedesk +41 31 848 48 48 jani.heikkinen(a)bfh.ch

1 0