- openstack-discuss - lists.openstack.org

Cinder Bug Report 2023-10-11
by Jon Bernard 11 Oct '23

11 Oct '23

Hello Argonauts, Cinder Bug Meeting Etherpad <https://etherpad.opendev.org/p/cinder-bug-squad-meeting> Undecided - Storwize SVC: Logging chap secret in DEBUG logs <https://bugs.launchpad.net/cinder/+bug/2038466> - Status: New - IBM SVC: Logging error when failed to create SVC host <https://bugs.launchpad.net/cinder/+bug/2038481> - Status: New - i want ask a question, but the label closed <https://bugs.launchpad.net/cinder/+bug/2038714> - Status: New - Reader and member users can list and show group-type <https://bugs.launchpad.net/cinder/+bug/2038805> - Status: New - Volume retype does not have any visibility into its progress <https://bugs.launchpad.net/cinder/+bug/2039015> - Status: New Thanks, -- Jon

1 0

[cinder][stable] proposing Jon Bernard for cinder-stable-maint
by Brian Rosmaita 11 Oct '23

11 Oct '23

Hello Argonauts, Jon Bernard has been acting as the cinder release manager for a few cycles now and is familiar with the OpenStack Stable Policy [0] and the cinder project backport policy [1]. I'd like to propose that he be added to the cinder-stable-maint team, which will give him +2 powers on the stable branches. cheers, brian [0] https://docs.openstack.org/project-team-guide/stable-branches.html [1] https://docs.openstack.org/cinder/latest/contributor/backporting.html

4 4

[magnum] Cancelling IRC meeting today
by Jake Yip 11 Oct '23

11 Oct '23

Hi all, Unfortunately I would have to cancel today's meeting due to personal matters. Apologies for the late notice. Regards, Jake

1 0

[all][elections][ptl] Project Team Lead Election Conclusion and Results
by Tony Breeds 10 Oct '23

10 Oct '23

Thank you to the electorate, to all those who voted and to all candidates who put their name forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability thank you to all those who make this process possible. Now for the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant : Dale Smith * Barbican : Grzegorz Grasza * Blazar : Pierre Riteau * Cinder : Rajat Dhasmana * Cloudkitty : Rafael Weingartner * Designate : Michael Johnson * Freezer : ge cong * Glance : Pranali Deore * Heat : Takashi Kajinami * Horizon : Vishal Manchanda * Ironic : Jay Faulkner * Keystone : Dave Wilde * Kolla : Michal Nasiadka * Kuryr : Roman Dobosz * Magnum : Jake Yip * Manila : Carlos Silva * Masakari : sam sue * Murano : Rong Zhu * Neutron : Brian Haley * Nova : Sylvain Bauza * Octavia : Gregory Thiemonge * OpenStack Charms : Felipe Reyes * OpenStack Helm : Vladimir Kozhukalov * OpenStackAnsible : Dmitriy Rabotyagov * OpenStackSDK : Artem Goncharov * Puppet OpenStack : Takashi Kajinami * Quality Assurance : Martin Kopec * Solum : Rong Zhu * Storlets : Takashi Kajinami * Swift : Tim Burke * Tacker : Yasufumi Ogawa * Telemetry : Erno Kuvaja * Vitrage : Dmitriy Rabotyagov * Watcher : chen ke * Zaqar : Hao Wang * Zun : Hongbin Lu Elections: * OpenStack_Helm: https://civs1.civs.us/cgi-bin/results.pl?id=E_3cf498bb10adc5b8 Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all involved in the PTL election process, Yours Tony.

6 8

[puppet] Openstack & puppet
by Albert Shih 10 Oct '23

10 Oct '23

Hi everyone, Few year ago I've deploy a very small openstack cluster with puppet, but to learn how openstack work I've build my own module (very simple module mostly with file + template + hiera). Now after few year I will need to re-install everything properly for production. Because all my infrastructure are all manage with puppet, I will not happy to use something like ansible, chef, etc. I also see they are something like Kolla who use docker/container, something I like because of the capability to revert a upgrade. So I've few questions about puppet & openstack : What are the status of «supporting» puppet ? I know it's opensource project so I'm perfectly aware «tomorrow» everything can be stop, but still is they are any plan already to leave puppet for something else. Is it a good idea to start a new installation for openstack with puppet ? I see Kolla work with ansible, is they are any plan to do the same with puppet ? Regards -- Albert SHIH 🦫 🐸 Heure locale/Local time: ven. 06 oct. 2023 16:06:28 CEST

4 3

[kolla] change default domain
by Vivian Rook 10 Oct '23

10 Oct '23

I'm looking for a setting to change the default domain name from "default" to "kolla" Does such an option exist in globals.yml? Thank you! -- *Vivian Rook (They/Them)* Site Reliability Engineer Wikimedia Foundation <https://wikimediafoundation.org/>

3 3

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

09 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 09 Oct '23

09 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