- openstack-discuss - lists.openstack.org

[neutron] Proposal to deprecate and remove vlan_transparent config option
by Sławek Kapłoński 09 Jan '25

09 Jan '25

Hi, We have config option to enable vlan_transparent api extension currently. We will also have similar config option for vlan_qinq (it is now proposed in [1]). In both cases we have validation by mechanism drivers if option is or is not supported while networks are created. We can also filter out enabled API extensions by mechanism drivers, see [2] for example. So I proposed [3] to remove that config option and keep API extension to be loaded always if enabled ML2 drivers supports it. But before I will propose patch for that I would like to ask if there is maybe some use case for this config option really and maybe some of you somehow depends on it. In such case maybe we should keep it like it is now and don't remove it. Please let me know if you are using somehow this option. [1] https://review.opendev.org/c/openstack/neutron/+/937372 [2] https://github.com/openstack/neutron/blob/559672f777312d00c4358626650cc577e… [3] https://bugs.launchpad.net/neutron/+bug/2092174 -- Slawek Kaplonski Principal Software Engineer Red Hat

3 3

[Tempest] Devstack to configure tempest on a remote node
by Jakub Libosvar 09 Jan '25

09 Jan '25

Hello stackers, I have been attempting to deploy a “spine & leaf” like topology for upstream testing job of the ovn-bgp-agent [1]. The idea is to have an all-in-one devstack VM where all openstack services are running. This VM is plugged to two leaf switches respectively with its two interfaces, and each switch is connected to the “spine” switch. With the leaf switches behaving as route reflected we can validate routes are advertised to the spine. Now in order to validate that, I need to execute the tempest tests on the spine. That means I want to use devstack on the spine VM that calls OpenStack services API on the devstack all-in-one VM. The spine VM should not have any openstack service running. The problem I’m struggling with that the tempest is configured based on the ENABLED_SERVICES for the current box. I tried to hack the spine VM portion by calling configure_tempest with custom ENABLED_SERVICES from a local.sh [2] which seems to configure the tempest.conf correctly but the stack.sh script calls test-config [3] phase after local.sh is invoked, which re-configures tempest.conf back to the state as if no OpenStack services were enabled. I kinda hit the wall and ran out of ideas for hacks/workarounds with the current devstack codebase. I thought one way of solving this would be to decouple ENABLED_SERVICES into two separate variables, one being used to configure services and one for tempest purposes but before I dive into that, I wanted to ask if anybody has any experience doing something similar (configuring only tempest with devstack) or maybe there is already some variable I am not aware of. Thank you for any inputs, ideas or suggestions :) Kuba [1] https://review.opendev.org/c/openstack/ovn-bgp-agent/+/936968 [2] https://review.opendev.org/c/openstack/ovn-bgp-agent/+/936968/54/playbooks/… [3] https://opendev.org/openstack/devstack/src/branch/master/stack.sh#L1482-L15…

2 1

RDO User Survey
by Amy Marrich 09 Jan '25

09 Jan '25

Hi everyone, During today's RDO meeting we had a few topics that we need further information on in order to make decisions. As a result, we have created a 2 question survey[0] to collect the needed information. This survey will remain open for 2 weeks so we can make plans for the Epoxy release with the gathered information. The first question is in regards to CentOS Stream version(s) for the Epoxy release, CentOS Stream 9 only, 10 only, or both versions. The second question is to determine whether future RDO releases will continue to be all releases or only SLURP releases, if SLURP are the only releases folks are using. Thanks, Amy 0 - https://forms.gle/44atURvazYPXVvwZ8

1 0

[Neutron] Bug report last 2 weeks
by Rodolfo Alonso Hernandez 08 Jan '25

08 Jan '25

Hello Neutrinos: This is the bug report of the last 2 weeks. HIGH * Packet Logging Framework (OVN/ML2) ( https://bugs.launchpad.net/neutron/+bug/2092474) *Not assigned*. * with pyroute2 master dvr functional tests failing with route mismatch as returned routes are not from specific table ( https://bugs.launchpad.net/neutron/+bug/2092567) There is an open bug for pyroute2 (https://github.com/svinota/pyroute2/issues/1225) that should fix this problem. * with pyroute2 master dvr functional tests failing as pyroute.NetNS not honoring flags (https://bugs.launchpad.net/neutron/+bug/2092722) There is an open bug for pyroute2 (https://github.com/svinota/pyroute2/issues/1226) that should fix this problem. * Potential GPL violation in master branch due to GPL script embedded into Apache2 python code (https://bugs.launchpad.net/neutron/+bug/2092907) *Not assigned*. * Metadata service does not work when port security is disabled ( https://bugs.launchpad.net/neutron/+bug/2092971) *Not assigned*. MEDIUM * DeprecationWarning: create_subnetpool ( https://bugs.launchpad.net/neutron/+bug/2092657) *Not assigned*. * NoneType' object has no attribute 'registered_rules' ( https://bugs.launchpad.net/neutron/+bug/2092659) *Not assigned*. * OVN: Ports not activated on time when DPDK is used ( https://bugs.launchpad.net/neutron/+bug/2092407) Assigned to Ihar, patch proposed: https://review.opendev.org/c/openstack/neutron/+/938197. INCOMPLETE * deadlock： delete the network ( https://bugs.launchpad.net/neutron/+bug/2092983) Regards.

3 5

check Nova keyring file
by Michel Niyoyita 08 Jan '25

08 Jan '25

Hello Team, I am integrating Openstack 2024.1 with ceph cluster reef running on ubuntu 22.05, I have configured openstack global as follow: ceph_nova_keyring: "ceph.client.nova.keyring" ceph_nova_user: "nova" ceph_nova_pool_name: "vms" I have copied nova keyring too from /etc/ceph to /etc/kolla/config/nova ; /etc/kolla/config/nova$ ls -l total 16 -rw-r--r-- 1 stack stack 64 Jan 7 13:12 ceph.client.cinder.keyring -rw-r--r-- 1 stack stack 62 Jan 7 15:11 ceph.client.nova.keyring -rw-r--r-- 1 stack stack 283 Jan 7 14:51 ceph.conf -rw-rw-r-- 1 stack stack 182 Jan 7 15:14 nova.conf (kolla-ansible) stack@open-deployment:/etc/kolla/config/nova$ I have created nova user in ceph : sudo ceph auth get-or-create client.nova mon 'profile rbd' osd 'profile rbd pool=vms, profile rbd pool=images' mgr 'profile rbd pool=vms' -o /etc/ceph/ceph.client.nova.keyring But while deploying I am facing the following issue : TASK [nova-cell : Check nova keyring file] ******************************************************************************************** fatal: [compute1 -> localhost]: FAILED! => {"msg": "No file was found when using first_found."} fatal: [compute2 -> localhost]: FAILED! => {"msg": "No file was found when using first_found."} fatal: [compute3 -> localhost]: FAILED! => {"msg": "No file was found when using first_found."} the same error is occuring also when deploying allinone . I tried two different release : 2023.2 and 2024.1 , this is the ansible version installed : pip install 'ansible>=8,<9' tree /etc/kolla/config/ /etc/kolla/config/ ├── cinder │ ├── ceph.conf │ ├── cinder-backup │ │ ├── ceph.client.cinder-backup.keyring │ │ └── ceph.client.cinder.keyring │ └── cinder-volume │ └── ceph.client.cinder.keyring ├── glance │ ├── ceph.client.cinder.keyring │ ├── ceph.client.glance.keyring │ └── ceph.conf └── nova ├── ceph.client.cinder.keyring ├── ceph.client.nova.keyring └── ceph.conf Kindly help to solve the issue , it takes long time without solution. previously was not occured on 2023.1 Best Regards Michel

2 2

Nova create vm with special ipv4 and ipv6
by Alex Song (宋文平) 08 Jan '25

08 Jan '25

Hi Nova team, does nova support create vm with special ipv4 and ipv6? As port create with ipv4 and ipv6 works by: openstack port create 111 --network 10851e96-8995-4988-b819-0514b38d7353 --fixed-ip subnet=a564ac90-3ff3-47d7-8ae5-20e2666eaa3c,ip-address=172.24.4.54 --fixed-ip subnet=afa3c858-c3d3-4784-8964-2c46840b714d,ip-address=2001:db8::183 but vm create with ipv4 and ipv6 with the cmd openstack server create --flavor 1 --image 62254c92-a579-4c8a-a2f4-f2624cef8ec1 --nic net-id=10851e96-8995-4988-b819-0514b38d7353,v4-fixed-ip=172.24.4.53,v6-fixed-ip=2001:db8::188 test raise exception: openstack server create: error: argument --nic: Invalid argument net-id=10851e96-8995-4988-b819-0514b38d7353,v4-fixed-ip=172.24.4.53,v6-fixed-ip=2001:db8::188; either 'v4-fixed-ip' or 'v6-fixed-ip' should be specified but not both. So why nova doesnot support?

2 3

[ops][nova] How to make sure that on a hypervisor there is room for a VM with a specific flavor
by Massimo Sgaravatto 07 Jan '25

07 Jan '25

Dear all I have the following use case: I defined a flavor F for VMS with 10 VCPUs, 20 GB of RAM, 30 GB of root disk, 1 GPU XYZ. I use PCI passthrough to manage GPUs. I have only a XYZ GPU on my cluster (on a H hypervisor), so a VM using this flavor F must be "placed" to the compute node H (and this is not a problem: I know how to do that). H is very large: it has a lot of RAM and cores, so it can host other VMs that do not use GPUs. How can I make it so that VMs without GPU can go on H, but there must be room for a VM with flavor F (if it doesn't already exist)? Thanks, and happy new year ! Cheers, Massimo

3 3

[openstack][octavia]Resize a Load Balancer
by Nguyễn Hữu Khôi 07 Jan '25

07 Jan '25

Hello. I see that patch https://review.opendev.org/c/openstack/octavia/+/890215 Could I ask why we cannot merge it? Nguyen Huu Khoi

2 2

ERROR dpif_netlink|INFO|dpif_netlink_meter_transact OVS_METER_CMD_SET failed
by alibasafa18＠gmail.com 07 Jan '25

07 Jan '25

I have set up OpenStack using Kolla Ansible with OVS and OVN. On one compute node, meters are functioning correctly, but on another, I am encountering an issue. Both nodes use the system datapath, have the same kernel version, and run the same version of OVS. Despite this, the problem persists. Has anyone experienced a similar issue? What could be the root cause? For example, I have two compute nodes. One of them does not have any issues, but the other meter did not work . following compute meter does not working: > sudo docker exec -it openvswitch_vswitchd bash (openvswitch-vswitchd)[root@compute1 /]# lsmod | grep open openvswitch 172032 13 nsh 16384 1 openvswitch nf_conncount 24576 1 openvswitch nf_nat 49152 1 openvswitch nf_conntrack 172032 6 nf_nat,nfnetlink_cttimeout,openvswitch,nf_conntrack_netlink,nf_conncount,ip_vs nf_defrag_ipv6 24576 3 nf_conntrack,openvswitch,ip_vs libcrc32c 16384 6 nf_conntrack,nf_nat,openvswitch,btrfs,raid456,ip_vs (openvswitch-vswitchd)[root@compute1 /]# ovs-appctl dpif/show-dp-features br-int Masked set action: Yes Tunnel push pop: No Ufid: Yes Truncate action: Yes Clone action: Yes Sample nesting: 10 Conntrack eventmask: Yes Conntrack clear: Yes Max dp_hash algorithm: 0 Check pkt length action: Yes Conntrack timeout policy: Yes Explicit Drop action: No Optimized Balance TCP mode: No Conntrack all-zero IP SNAT: Yes MPLS Label add: Yes Max VLAN headers: 2 Max MPLS depth: 3 Recirc: Yes CT state: Yes CT zone: Yes CT mark: Yes CT label: Yes CT state NAT: Yes CT orig tuple: Yes CT orig tuple for IPv6: Yes IPv6 ND Extension: No (openvswitch-vswitchd)[root@compute1 /]# ovs-ofctl -OOpenFlow15 meter-features br-int OFPST_METER_FEATURES reply (OF1.5) (xid=0x2): max_meter:0 max_bands:0 max_color:0 band_types: 0 capabilities: 0 (openvswitch-vswitchd)[root@compute1 /]# ovs-vsctl --version ovs-vsctl (Open vSwitch) 3.3.2 DB Schema 8.5.0 (openvswitch-vswitchd)[root@compute1 /]# uname -r 5.15.0-86-generic (openvswitch-vswitchd)[root@compute1 /]# uptime 08:27:39 up 87 days, 19:51, 0 users, load average: 3.36, 4.58, 4.19 ====================== following compute working without issue: > sudo docker exec -it openvswitch_vswitchd bash (openvswitch-vswitchd)[root@compute2 /]# lsmod | grep open openvswitch 172032 23 nsh 16384 1 openvswitch nf_conncount 24576 1 openvswitch nf_nat 49152 1 openvswitch nf_conntrack 172032 6 nf_nat,nfnetlink_cttimeout,openvswitch,nf_conntrack_netlink,nf_conncount,ip_vs nf_defrag_ipv6 24576 3 nf_conntrack,openvswitch,ip_vs libcrc32c 16384 6 nf_conntrack,nf_nat,openvswitch,btrfs,raid456,ip_vs (openvswitch-vswitchd)[root@compute2 /]# ovs-appctl dpif/show-dp-features br-int Masked set action: Yes Tunnel push pop: No Ufid: Yes Truncate action: Yes Clone action: Yes Sample nesting: 10 Conntrack eventmask: Yes Conntrack clear: Yes Max dp_hash algorithm: 0 Check pkt length action: Yes Conntrack timeout policy: Yes Explicit Drop action: No Optimized Balance TCP mode: No Conntrack all-zero IP SNAT: Yes MPLS Label add: Yes Max VLAN headers: 2 Max MPLS depth: 3 Recirc: Yes CT state: Yes CT zone: Yes CT mark: Yes CT label: Yes CT state NAT: Yes CT orig tuple: Yes CT orig tuple for IPv6: Yes IPv6 ND Extension: No (openvswitch-vswitchd)[root@compute27 /]# ovs-ofctl -OOpenFlow15 meter-features br-int OFPST_METER_FEATURES reply (OF1.5) (xid=0x2): max_meter:200000 max_bands:1 max_color:0 band_types: drop capabilities: kbps pktps burst stats (openvswitch-vswitchd)[root@compute2 /]# ovs-vsctl --version ovs-vsctl (Open vSwitch) 3.3.2 DB Schema 8.5.0 (openvswitch-vswitchd)[root@compute2 /]# uname -r 5.15.0-86-generic (openvswitch-vswitchd)[root@compute2 /]# uptime 08:29:47 up 87 days, 19:53, 0 users, load average: 11.23, 13.13, 13.29

1 0

ERROR dpif_netlink|INFO|dpif_netlink_meter_transact OVS_METER_CMD_SET failed
by alibasafa18＠gmail.com 07 Jan '25

07 Jan '25

I have set up OpenStack using Kolla Ansible with OVS and OVN. On one compute node, meters are functioning correctly, but on another, I am encountering an issue. Both nodes use the system datapath, have the same kernel version, and run the same version of OVS. Despite this, the problem persists. Has anyone experienced a similar issue? What could be the root cause? i have both compute for example in the following. following compute node i have issue: > sudo docker exec -it openvswitch_vswitchd bash (openvswitch-vswitchd)[root@si1-compute1 /]# lsmod | grep open openvswitch 172032 13 nsh 16384 1 openvswitch nf_conncount 24576 1 openvswitch nf_nat 49152 1 openvswitch nf_conntrack 172032 6 nf_nat,nfnetlink_cttimeout,openvswitch,nf_conntrack_netlink,nf_conncount,ip_vs nf_defrag_ipv6 24576 3 nf_conntrack,openvswitch,ip_vs libcrc32c 16384 6 nf_conntrack,nf_nat,openvswitch,btrfs,raid456,ip_vs (openvswitch-vswitchd)[root@si1-compute4174 /]# ovs-appctl dpif/show-dp-features br-int Masked set action: Yes Tunnel push pop: No Ufid: Yes Truncate action: Yes Clone action: Yes Sample nesting: 10 Conntrack eventmask: Yes Conntrack clear: Yes Max dp_hash algorithm: 0 Check pkt length action: Yes Conntrack timeout policy: Yes Explicit Drop action: No Optimized Balance TCP mode: No Conntrack all-zero IP SNAT: Yes MPLS Label add: Yes Max VLAN headers: 2 Max MPLS depth: 3 Recirc: Yes CT state: Yes CT zone: Yes CT mark: Yes CT label: Yes CT state NAT: Yes CT orig tuple: Yes CT orig tuple for IPv6: Yes IPv6 ND Extension: No (openvswitch-vswitchd)[root@si1-compute1 /]# ovs-ofctl -OOpenFlow15 meter-features br-int OFPST_METER_FEATURES reply (OF1.5) (xid=0x2): max_meter:0 max_bands:0 max_color:0 band_types: 0 capabilities: 0 (openvswitch-vswitchd)[root@si1-compute1 /]# ovs-vsctl --version ovs-vsctl (Open vSwitch) 3.3.2 DB Schema 8.5.0 (openvswitch-vswitchd)[root@si1-compute1 /]# uname -r 5.15.0-86-generic (openvswitch-vswitchd)[root@si1-compute1 /]# uptime 08:27:39 up 87 days, 19:51, 0 users, load average: 3.36, 4.58, 4.19 ================================= following compute node working correctly: (openvswitch-vswitchd)[root@si1-compute2 /]# lsmod | grep open openvswitch 172032 23 nsh 16384 1 openvswitch nf_conncount 24576 1 openvswitch nf_nat 49152 1 openvswitch nf_conntrack 172032 6 nf_nat,nfnetlink_cttimeout,openvswitch,nf_conntrack_netlink,nf_conncount,ip_vs nf_defrag_ipv6 24576 3 nf_conntrack,openvswitch,ip_vs libcrc32c 16384 6 nf_conntrack,nf_nat,openvswitch,btrfs,raid456,ip_vs (openvswitch-vswitchd)[root@si1-compute2 /]# ovs-appctl dpif/show-dp-features br-int Masked set action: Yes Tunnel push pop: No Ufid: Yes Truncate action: Yes Clone action: Yes Sample nesting: 10 Conntrack eventmask: Yes Conntrack clear: Yes Max dp_hash algorithm: 0 Check pkt length action: Yes Conntrack timeout policy: Yes Explicit Drop action: No Optimized Balance TCP mode: No Conntrack all-zero IP SNAT: Yes MPLS Label add: Yes Max VLAN headers: 2 Max MPLS depth: 3 Recirc: Yes CT state: Yes CT zone: Yes CT mark: Yes CT label: Yes CT state NAT: Yes CT orig tuple: Yes CT orig tuple for IPv6: Yes IPv6 ND Extension: No (openvswitch-vswitchd)[root@si1-compute2 /]# ovs-ofctl -OOpenFlow15 meter-features br-int OFPST_METER_FEATURES reply (OF1.5) (xid=0x2): max_meter:200000 max_bands:1 max_color:0 band_types: drop capabilities: kbps pktps burst stats (openvswitch-vswitchd)[root@si1-compute2 /]# ovs-vsctl --version ovs-vsctl (Open vSwitch) 3.3.2 DB Schema 8.5.0 (openvswitch-vswitchd)[root@si1-compute2 /]# uname -r 5.15.0-86-generic (openvswitch-vswitchd)[root@si1-compute2 /]# uptime 08:29:47 up 87 days, 19:53, 0 users, load average: 11.23, 13.13, 13.29

1 0