October 2023 - openstack-discuss - lists.openstack.org

[publiccloud-sig] Reminder - next meeting October 11th - 0700 UTC
by Felix Kronlage-Dammers 10 Oct '23

10 Oct '23

Hi everyone, this Wednesday the next meeting of the public cloud sig is going to happen. This time we will meet in video again. (As previously mentioned here [1]). We will meet at 0700 UTC here: https://conf.scs.koeln:8443/OIF-public-cloud-sig In parallel we will be on irc on #openstack-operators as well of course. I started an agenda (https://etherpad.opendev.org/p/publiccloud-sig-meeting) one of the items I’d like to cover is the upcoming vPTG. Am very much looking forward to wednesday morning! :) felix [1] <url: https://lists.openstack.org/pipermail/openstack-discuss/2023-August/034934.…> -- 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

[tc] Technical Committee next weekly meeting Tuesday, October 10, 2023
by Jay Faulkner 10 Oct '23

10 Oct '23

Hello, This is a reminder that the weekly Technical Committee meeting is to be held Tuesday, October 10 at 1800 UTC. It will be held in #openstack-tc on OFTC. The proposed agenda is as follows: - Roll call - Follow up on tracked action items: https://meetings.opendev.org/meetings/tc/2023/tc.2023-10-03-18.00.html - JayF - Schedule a cross-project performance session at the PTG centered around apparent heavy DB usage in devstack from Keystone and Neutron; ensure sqlalchemy + oslo.db maintainers are invited. - Appoint Rosmaita as vice chair - Before next video meeting, write up a short document on pros/cons of moving TC video meetings to jitsi-meet. - Knikolla - Complete documentation for unmaintained branch policy in releases.openstack.org - Investigate or delegate research on DB usage patterns in Keystone in devstack. Due before PTG. - Slaweq - To propose a patch to openstack/governance for TC consideration to mark monasca inactive - Gate health check - Leaderless projects (gmann) - PTG Scheduling and agenda - Open Discussion and Reviews Thank you, Jay Faulkner TC Chair

1 0

[kolla-ansible][masakari] how segment works
by Nguyễn Hữu Khôi 09 Oct '23

09 Oct '23

Hello guys. I deployed masakari with kolla-ansible but I has a question: Can you explain for me about segment because my masakari works same attitude with one or more segments. https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/wall… "With Masakari, compute nodes are grouped into failover segments. In the event of a compute node failure, that node’s instances are moved onto another compute node within the same segment" I have 2 segments: Compute01 >> Compute03 on segment 1 Compute04 >> Compute06 on segment 2 I think that instances only evacuate on its segment but they can go cross segment. Pls correct me if I'm wrong. Thank you. Nguyen Huu Khoi

1 1

RE: openstack-discuss Digest, Vol 60, Issue 10 ~ Fwaas in Openstack 2023.1 antelope
by Asma Naz Shariq 09 Oct '23

09 Oct '23

Hi Openstack Community! I have set up OpenStack release 2023.1 antelope with Kolla-Ansible . However, I noticed that there is no enable_plugin option in the /etc/kolla/global.yml file. Now, I am trying to install FWaaS (Firewall-as-a-Service) following the instructions provided in this OpenStack's Firewall-as-a-Service (FWaaS) v2 scenario documentation. The documentation states, On Ubuntu and CentOS, modify the [fwaas] section in the /etc/neutron/fwaas_driver.ini file instead of /etc/neutron/neutron.conf. Unfortunately, I cannot find the fwaas_driver.ini file in the neutron-server, neutron-l3-agent, or neutron-openvswitch-agent containers Can someone guide me on how to properly install FWaaS in a Kolla environment using the information from the provided link? Best, -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Friday, October 6, 2023 1:27 PM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 60, Issue 10 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss or, via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: [ops] [nova] "invalid argument: shares xxx must be in range [1, 10000]" after 1:25.2.0 to 1.25.2.1. update (Massimo Sgaravatto) 2. [TC][Monasca] Proposal to mark Monasca as an inactive project (S?awek Kap?o?ski) 3. [neutron] Neutron drivers meeting cancelled (Rodolfo Alonso Hernandez) ---------------------------------------------------------------------- Message: 1 Date: Fri, 6 Oct 2023 09:10:47 +0200 From: Massimo Sgaravatto <massimo.sgaravatto(a)gmail.com> To: Franciszek Przewo?ny <fprzewozny(a)opera.com> Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org>, smooney(a)redhat.com Subject: Re: [ops] [nova] "invalid argument: shares xxx must be in range [1, 10000]" after 1:25.2.0 to 1.25.2.1. update Message-ID: <CALaZjRGh6xnzX12cMgDTYx2yJYddUD9X3oh60JWnrB33ZdEf_Q(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Thanks a lot Franciszek ! I was indeed seeing the problem with a VM big 56 vcpus while I didn't see the issue with a tiny instance Thanks again ! Cheers, Massimo On Fri, Oct 6, 2023 at 8:58?AM Franciszek Przewo?ny <fprzewozny(a)opera.com> wrote: > Hi Massimo, > > We are using Ubuntu for our environments and we experienced the same > issue during upgrade from Yoga/Focal to Yoga/Jammy. On Yoga/Focal > cgroups_v1 were used, and cpu_shares parameter value was cpu count * > 1024. From Jammy > cgroups_v2 have been implemented, and cpu_shares value has been set by > default to 100. It has hard limit of 10000, so flavors with more than > 9vCPUs won't fit. If you need to fix this issue without stopping VMs, > you can set cpu_shares with libvirt command: virsh schedinfo $domain > --live > cpu_shares=100 > for more details about virsh schedinfo visit: > https://libvirt.org/manpages/virsh.html#schedinfo > > BR, > Franciszek > > On 5 Oct 2023, at 21:17, smooney(a)redhat.com wrote: > > On Thu, 2023-10-05 at 16:53 +0200, Massimo Sgaravatto wrote: > > Dear all > > We have recently updated openstack nova on some AlmaLinux9 compute > nodes running Yoga from 1:25.2.0 to 1.25.2.1. After this operation > some VMs don't start anymore. In the log it is reported: > > libvirt.libvirtError: invalid argument: shares \'57344\' must be in > range [1, 10000]\n'} > > libvirt version is 9.0.0-10.3 > > > A quick google search suggests that it is something related to cgroups > and it is fixed in libvirt >= 9.1 (which is not yet in the almalinux9 repos). > Did I get it right ? > > not quite > > it is reated to cgroups but the cause is that in cgroups_v1 the > maxvlaue of shares i.e. cpu_shares changed form make int to 10000 in > cgroups_v2 so the issue is teh vm requested a cpu share value of 57344 > which is not vlaid on an OS that is useing cgroups_v2 libvirt will not > clamp the value nor will nova. > you have to change the volue in your flavor and resize the vm. > > > > > Thanks, Massimo > > > > >

2 1

[neutron] Bug deputy report from week of the 2.10.2023
by Sławek Kapłoński 09 Oct '23

09 Oct '23

Hi, I was bug deputy last week. Here's summary of the bugs from this week: ## Critical * https://bugs.launchpad.net/neutron/+bug/2038541 - LinuxBridgeARPSpoofTestCase functional tests fails with latest jammy kernel 5.15.0-86.96 - fix proposed by Rodolfo https://review.opendev.org/c/openstack/neutron/+/897412 ## High * https://bugs.launchpad.net/neutron/+bug/2038234 - PortBindingChassisEvent matches all port types - assigned to jlibosva ## Medium * https://bugs.launchpad.net/neutron/+bug/2038091 - [OVN] Manual sync misidentifies Octavia OVN Load Balancer health monitor port and deletes metadata port - assigned to Fernando Royo * https://bugs.launchpad.net/neutron/+bug/2038413 - [OVN] host id in NB database not updated correctly for virtual ports, assigned to Michel Nederlof and fix proposed: https://review.opendev.org/c/openstack/neutron/+/896883 * https://bugs.launchpad.net/neutron/+bug/2038422 - [OVN] virtual ports not working upon failover, assigned to Michel Nederlof and fix proposed: https://review.opendev.org/c/openstack/neutron/+/896884 * https://bugs.launchpad.net/neutron/+bug/2038646 - [RBAC] Update "subnet" policies - assigned to Rodolfo, patch proposed https://review.opendev.org/c/openstack/neutron/+/897540 * https://bugs.launchpad.net/neutron/+bug/2038655 - DHCP agent scheduler API extension should be supported by ML2/OVN backend - assigned to Slawek, patch proposed https://review.opendev.org/c/openstack/neutron/+/897528 but there will be also neutron-tempest-plugin change needed ## Low * https://bugs.launchpad.net/neutron/+bug/2038373 - Segment unit tests are not mocking properly, unassigned, for me looks like low-hanging-fruit bug * https://bugs.launchpad.net/neutron/+bug/2038520 - [UT] Error accesing to row.external_ids in ``TestOvnSbIdlNotifyHandler`` tests, assigned to Rodolfo, fix proposed https://review.opendev.org/c/openstack/neutron/+/897407 * https://bugs.launchpad.net/neutron/+bug/2038555 - Remove unused tables, assigned to Rodolfo, fix proposed https://review.opendev.org/c/openstack/neutron/+/897472 -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Masakari issue
by Karera Tony 07 Oct '23

07 Oct '23

Hello Team, I have an openstack Wallaby Environment deployed using kolla-ansible. So, I shutdown all the VMs on the compute nodes becauseI wanted to upgrade the nodes kernel. After I rebooted them and all was fine apart from the fact that all the hosts in instance-ha segment are in maitenance mode. When I try to turn to false. I get the error below. *Error: *Failed to update host. Details <http://10.10.13.31/masakaridashboard/hosts/#message_details> ConflictException: 409: Client Error for url: http://x.x.x.x:15868/v1/segments/8d042245-5610-4b84-b611-b633f8f8367c/hosts…, Host 066c5654-dd1a-4fa9-a664-dad10b89e202 can't be updated as it is in-use to process notifications. Regards Tony Karera

2 1

[ptl][tc][ops][ptg] Operator + Developers interaction (operator-hours) slots in 2024.1 Caracel PTG
by Amy Marrich 07 Oct '23

07 Oct '23

Hello Everyone/PTL, To promote interaction/feedback from operators, the OpenStack TC would like to bring operators and developers together again at the upcoming PTG. To make it easy for operators and less conflict among projects, the TC is requesting projects to book 'operator hours' in non-conflicting slots(different time/day slots). How project can reserve/book these 'operator hour' (Action item for projects PTL/PTG planner): ----------------------------------------------------------------------------------------------------------------- 1. Request Kendall(diablo_rojo) or Fungi (in #openinfra-events IRC channel) or email ptg(a)openinfra.dev to register the new track 'operator-hour-<your project name>' for example, 'operator-hour-nova' 2. Once track is registered, pick one of the available 'operator-hour-placeholder' slot and book it with newly registered track 'operator-hour-<your project name>'. For example #operator-hour-nova book essex-WedB1 * The idea is to book these slots as 'operator-hour-<your project name>' is to give operators a easy way to find and join. Otherwise it will be difficult for them to find such slot/time from etherpads. We request every project to book at least one 'operator hours' slot for operators to join your PTG slot. Ping me in #openstack-tc or #openinfra-events IRC channel for any query. [1] https://ptg.opendev.org/ptg.html Amy(spotz)

1 0

[ptl][tc][ops][ptg] Operator + Developers interaction (operator-hours) slots in 2024.1 Caracel PTG
by Amy Marrich 07 Oct '23

07 Oct '23

Hello Everyone/PTL, To promote interaction/feedback from operators, the OpenStack TC would like to bring operators and developers together again at the upcoming PTG. To make it easy for operators and less conflict among projects, the TC is requesting projects to book 'operator hours' in non-conflicting slots(different time/day slots). How project can reserve/book these 'operator hour' (Action item for projects PTL/PTG planner): ----------------------------------------------------------------------------------------------------------------- 1. Request Kendall(diablo_rojo) or Fungi (in #openinfra-events IRC channel) or email ptg(a)openinfra.dev to register the new track 'operator-hour-<your project name>' for example, 'operator-hour-nova' 2. Once track is registered, pick one of the available 'operator-hour-placeholder' slot and book it with newly registered track 'operator-hour-<your project name>'. For example #operator-hour-nova book essex-WedB1 * The idea is to book these slots as 'operator-hour-<your project name>' is to give operators a easy way to find and join. Otherwise it will be difficult for them to find such slot/time from etherpads. We request every project to book at least one 'operator hours' slot for operators to join your PTG slot. Ping me in #openstack-tc or #openinfra-events IRC channel for any query. [1] https://ptg.opendev.org/ptg.html Amy(spotz)

1 0

[ptl][tc][ops][ptg] Operator + Developers interaction (operator-hours) slots in 2024.1 Caracel PTG
by Amy Marrich 07 Oct '23

07 Oct '23

Hello Everyone/PTL, To promote interaction/feedback from operators, the OpenStack TC would like to bring operators and developers together again at the upcoming PTG. To make it easy for operators and less conflict among projects, the TC is requesting projects to book 'operator hours' in non-conflicting slots(different time/day slots). How project can reserve/book these 'operator hour' (Action item for projects PTL/PTG planner): ----------------------------------------------------------------------------------------------------------------- 1. Request Kendall(diablo_rojo) or Fungi (in #openinfra-events IRC channel) or email ptg(a)openinfra.dev to register the new track 'operator-hour-<your project name>' for example, 'operator-hour-nova' 2. Once track is registered, pick one of the available 'operator-hour-placeholder' slot and book it with newly registered track 'operator-hour-<your project name>'. For example #operator-hour-nova book essex-WedB1 * The idea is to book these slots as 'operator-hour-<your project name>' is to give operators a easy way to find and join. Otherwise it will be difficult for them to find such slot/time from etherpads. We request every project to book at least one 'operator hours' slot for operators to join your PTG slot. Ping me in #openstack-tc or #openinfra-events IRC channel for any query. [1] https://ptg.opendev.org/ptg.html Amy(spotz)

1 0

[tc] Congratulations to Brian Rosmaita, Vice Chair
by Jay Faulkner 06 Oct '23

06 Oct '23

Hi all, Brian Rosmaita graciously volunteered to serve as Vice-Chair of the Technical Committee for the next cycle. Congratulations Brian, and thank you! -- Jay Faulkner TC Chair

5 4