February 2024 - openstack-discuss

[neutron][vpnaas][ovn] Pushing VPNaaS support through OVN
by Mohammed Naser 12 Feb '24

12 Feb '24

Hi all! One of the biggest show stoppers for us for OVN is VPNaaS but I think it’s time that we’d like to be involved in getting it over the line, I want to thank Bodo who has shown a lot of patience in getting the code necessary, and it seems that the code works for them in production as well. I’d like to ask if possible for folks to review these two outstanding changes: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/847007 https://review.opendev.org/c/openstack/neutron-vpnaas/+/765353 I know Slawek had some concerns, so hoping that raising via the email list if Bodo can address those and over the next bit of time we can get this landed in, since it even has actual proper testing both in CI and with user feedback. Thanks! Mohammed

6 8

[neutron] Bugs deputy report February 5th to 11th
by Rodolfo Alonso Hernandez 12 Feb '24

12 Feb '24

Hello all: This is the bug list from the past week: Critical ======================== https://bugs.launchpad.net/neutron/+bug/2052509. "[CI][ovs/ovn sqlalchemy master] jobs broken with Exception: Not enough arguments given". Assigned. Patch: https://review.opendev.org/c/openstack/devstack/+/908572 https://bugs.launchpad.net/neutron/+bug/2052787. "SSH timeouts due to problems with metadata server in ML2/OVN backend". Assigned. High ======================== https://bugs.launchpad.net/neutron/+bug/2052628. "[stable-only][ovn-octavia-provider] Multiple listener-pool-member on IPv6 LB getting second pool in ERROR". Assigned. Patch: https://review.opendev.org/q/I37e660d5eaa45deb38ff127cf69195b0a9ef0846 (merged). Medium ======================== https://bugs.launchpad.net/neutron/+bug/2052484. "[DEFAULT] rpc_worker=0 leaves one rpc worker". Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/908173 https://bugs.launchpad.net/neutron/+bug/2052681. " Many stale neutron-keepalived-state-change processes left after upgrade to native pyroute2 state-change". Not assigned. https://bugs.launchpad.net/neutron/+bug/2052821. "[OVN] Pin a Logical_Router to a chassis when the external network is tunnelled". Assigned. https://bugs.launchpad.net/neutron/+bug/2052843. "[OVN Octavia Provider] subnet with multiple router gateways lb association". Assigned. Patch: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/908679 https://bugs.launchpad.net/neutron/+bug/2052419. "SG list retrieval is slow because we are always loading "synthetic_fields"". Assigned. Patches: https://review.opendev.org/q/I300464472f2348d148f2a3ddac384c883d9d815b Low ======================== https://bugs.launchpad.net/neutron/+bug/2052508. " [doc][troubleshooting] how to enable ovs vswitchd debug logs". Not assigned. https://bugs.launchpad.net/neutron/+bug/2052786. " Add "socket" to NUMA affinity policy". Assigned. Patch: https://review.opendev.org/c/openstack/neutron-lib/+/903531 Regards.

1 0

PTG April 2024 Team Signup Deadline Approaching!
by Kendall Nelson 12 Feb '24

12 Feb '24

Hello Everyone, This is your *last call *to sign up your team up for the next Project Teams Gathering (PTG)[1], which will be held from Monday, April 8 to Friday, April 12 2024! If you haven't already done so and your team is interested in participating, *you need to complete the survey[2] by February 18, 2024 at 7:00 UTC*. Thanks! -Kendall Nelson (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] Team Survey: https://openinfrafoundation.formstack.com/forms/april2024_ptg_survey

1 0

[openstack-ansible] [kolla-ansible] 2023.1 Antelope - In series upgrade - All/few neutron agents dead
by Shrishail K 11 Feb '24

11 Feb '24

Hi Team, I would like to seek some help regarding the issue I am facing while performing in series upgrade on the Antelope version. We have currently deployed our cluster with *2023.1 Antelope *version. The cluster was deployed on a clean environment by cleaning up any previous kolla openstack installation. We have not observed any issues with this environment so far. For a feature I am working on, I had to *put a patch into GLANCE image* and rebuild all *kolla images with a new tag*. I have attempted to upgrade the cluster using both *kolla-deploy *and *kolla-upgrade *methods, but both methods have left the *cluster in degraded condition*. The issue seems to be mainly with failure of communication between *neutron-server *and all/some *neutron-agents, *due to which the neutron-server sees *all/some* *neutron-agents dead*. *Rabbitmq *itself seems to be doing fine. The issue is very consistent. Is this a known behavior? And am I using the correct kolla tools to perform the in series upgrade. Appreciate any help. Thanks, Shrishail

1 0

OpenSUSE packages
by Kai Jellinghaus 11 Feb '24

11 Feb '24

Hello, I hope it's OK to ask a question like this here, not totally sure how else to reach someone knowledgeable from the community. I'm playing with OpenStack on OpenSUSE, but I'm a bit confused where to get the latest packages. From what I can tell 2023.2 is the latest (non-dev) version, sometimes also called "Bobcat", but the website only lists it as 2023.2, so I'm guessing codenames have been discontinued? This page: https://docs.openstack.org/install-guide/environment-packages-obs.html only goes up to Ussuri Browsing OBS I can find builds & repos for > Ussuri, but it seems builds are largely broken. I'd appreciate any help here, I'm not that experienced with OpenStack, OpenSUSE or mailinglists, so I hope I'm not doing/asking for something stupid. Please do point it out if I do, thank you! Kind Regards, Kai Jellinghaus

2 2

haproxy running configuration change openstack-ansible (ussuri)
by keshav bareja 10 Feb '24

10 Feb '24

Hi All I need to change haproxy configuration in the openstack-ussuri environment using openstack-ansible. for glance-api service I need to change backend load-balancing algorithm from source to least-connect I can see this configuration as part of group_vars of the source package* /opt/openstack-ansible <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/inventory <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/group_vars <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy.yml* -service: haproxy_service_name: glance_api haproxy_backend_nodes: "{{ groups['glance_api'] | default([]) }}" haproxy_ssl: "{{ haproxy_ssl }}" haproxy_port: 9292 *haproxy_balance_alg: source* haproxy_balance_type: http haproxy_backend_options: Can you please let me know how to do so?

2 3

Re: Welcome to the "openstack-discuss" mailing list
by keshav bareja 09 Feb '24

09 Feb '24

Hi All I need to change haproxy configuration in the openstack-ussuri environment using openstack-ansible. for glance-api service I need to change backend load-balancing algorithm from source to least-connect I can see this configuration as part of group_vars of the source package* /opt/openstack-ansible <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/inventory <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/group_vars <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy <https://opendev.org/openstack/openstack-ansible/src/commit/6520d0bb2c689ed7…>/haproxy.yml* -service: haproxy_service_name: glance_api haproxy_backend_nodes: "{{ groups['glance_api'] | default([]) }}" haproxy_ssl: "{{ haproxy_ssl }}" haproxy_port: 9292 *haproxy_balance_alg: source* haproxy_balance_type: http haproxy_backend_options: Can you please let me know how to do so? Regards Keshav On Fri, Feb 9, 2024 at 8:27 PM < openstack-discuss-request(a)lists.openstack.org> wrote: > Welcome to the "openstack-discuss" mailing list! > > To post to this list, send your message to: > > openstack-discuss(a)lists.openstack.org > > You can unsubscribe or make adjustments to your options via email by > sending a message to: > > openstack-discuss-request(a)lists.openstack.org > > with the word 'help' in the subject or body (don't include the > quotes), and you will get back a message with instructions. You will > need your password to change your options, but for security purposes, > this password is not included here. If you have forgotten your > password you will need to reset it via the web UI. >

2 1

[release] Release countdown for week R-7
by Thierry Carrez 09 Feb '24

09 Feb '24

Development Focus ----------------- We are entering the last weeks of the 2024.1 Caracal 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 15, 2024. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, February 15, 2024. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 22, 2024). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 29, 2024) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 29, 2024. 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 15, 2024) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 29, 2024) 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 7, 2024). 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 15, 2024 (R-7 week) Oslo feature freeze: February 15, 2024 (R-7 week) Non-client library freeze: February 22, 2024 (R-6 week) Client library freeze: February 29, 2024 (R-5 week) caracal-3 milestone: February 29, 2024 (R-5 week) Cycle highlights deadline: March 7, 2024 (R-4 week) Dalmatian PTG: April 8-12, 2024 -- Thierry Carrez (ttx)

1 0

[Neutron][OVN] Flat routed provider network has external traffic broadcasted to all VMs
by Daniel Failing 09 Feb '24

09 Feb '24

Dear all, I'm currently debugging a (testing) deployment with neutron/OVN, currently most ports in external flat network. So far I'm happy everything can communicate, but we see a strong performance degradation with increasing number of VMs/ports hosted on a hypervisor. The setup is similar to the one described in the routed provider networks docs [1]. For routing between the different segments, we have physical routers, that are not managed by neutron. Debugging the issue showed traffic originating from the DC router to VMs go perfectly as unicast traffic through OVN. Communicating from the VM to other networks via the DC router, however, will broadcast the traffic to all attached ports on the internal bridge. Is there a way to tell neutron/OVN to use a specific MAC address for the router and forward the traffic through the patch port instead of broadcasting it? I could not find any documentation of whether I am missing a neutron port or some other configuration on the hypervisor. Just to make sure: The VM and DC routers have the right ARP information of itself, the traffic that is duplicated is from VM to router/external network. (via default route to router) As far as I could see, this issue does not appear with private networks, since all MAC addresses are known to OVN/Neutron. Versions: Nova/Neutron: Yoga ovs-vswitchd (Open vSwitch) 3.1.4 ovn-northd 22.12.1 kernel 5.14.0-284.30.1.el9_2.x86_64 Best, Daniel [1] https://docs.openstack.org/neutron/latest/admin/config-routed-networks.html

2 4

[manila] multi az replication
by garcetto 08 Feb '24

08 Feb '24

good afternoon, i am using zed, on streched ceph as backend on multiple az. i would like to emulate aws efs multiple nfs mount points for each user tenant (one on each different az) using manila, is it possible? ideally i would like to expose to each users tenant a manila vm as nfs exporter to custormer' instances, and as backend (of manila) use a cinder volume on ceph (rbd? cephfs? nfs?) my problem is how can i create say 3 different manila service vms (one in each az) with different frontend ips all pointing to same rbd/cephfs volume? am i doing wrong? thank you.

2 1