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

[nova] [libvirt] About libvirt autoconverge
by hai wu 17 Oct '23

17 Oct '23

Do you enable auto-converge for nova instance live migration on all production hypervisor hosts?

2 4

[OPENSTACK][rabbitmq] using quorum queues
by Nguyễn Hữu Khôi 17 Oct '23

17 Oct '23

Hello guys. IS there any guy who uses the quorum queue for openstack? Could you give some feedback to compare with classic queue? Thank you. Nguyen Huu Khoi

9 19

[neutron] bug deputy report (Oct 9-15)
by Akihiro Motoki 17 Oct '23

17 Oct '23

Hi, I was a bug deputy last week. Here is a report on bugs last week. Three unassigned bugs are worth investigating. We also had three bugs on fwaas related to gate failures. It would be nice if FWaaS folks can look into them. # New disallowed by policy error when user try to create_port with fixed_Ips https://bugs.launchpad.net/neutron/+bug/2039464 This may need a detail investigation. There might be a gap between network RBAC and policy handling like "create_port:fixed_ips". [OVN] Floating IP <=> Floating IP across subnets https://bugs.launchpad.net/neutron/+bug/2038978 Unassigned, but mnaser shared a workaround and proposed a WIP patch. ovsfw: OVS br-int rule disappears from the table=60 after stop/start VM https://bugs.launchpad.net/neutron/+bug/2038931 This needs to be investigated. Liu had an initial look ## FWaaS [neutron-fwaas] "neutron-fwaas-fullstack" job broken https://bugs.launchpad.net/neutron/+bug/2039285 [fwaas] Scenario job fails randomly https://bugs.launchpad.net/neutron/+bug/2039012 [fwaas] CI job "neutron-fwaas-v2-dsvm-tempest-multinode" failing https://bugs.launchpad.net/neutron/+bug/2038936 # In Progress [fullstack] The "dhclient" kill command can take more than 90 seconds https://bugs.launchpad.net/neutron/+bug/2039038 Assigned to ralonsoh openstacksdk-functional-devstack-networking periodic job broken in xena/yoga/zed https://bugs.launchpad.net/neutron/+bug/2039066 Assigned to yatin A patch to skip these tests was merged in yoga and zed. xena job was also fixed not to use the master branch. Looks completed but I would like to wait for yatin. # Fix Released tempest nftables jobs are not running in periodic queue https://bugs.launchpad.net/neutron/+bug/2039027 Thanks, Akihiro Motoki (amotoki)

1 0

[openstack][nova][glance][cinder] Openstack Edge Computing
by Nguyễn Hữu Khôi 17 Oct '23

17 Oct '23

Hello guys. I am studying about Openstack Edge Computing from https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… http://theansibleguy.com/openstack-glance-with-cinder-multistores-scurry-in… I can separate AZ. Main AZ and Edge AZ for Nova, Neutron and Cinder. Glance Multistore also. But I cannot figure how we can configure to specify which Glance Stored will be used for launch instances from Edge Site. And one more question, Will we need setup glance service in Edge sites too? It will be nice if Glance can be set AZ. I tried GG but not many docs about it. Could someone give me some suggestions about ii? Thank you so much Nguyen Huu Khoi

1 1

[manila] About deleted service network
by Mesut Bayrak 16 Oct '23

16 Oct '23

Hi, Our service network of manila got deleted accidentally, Is there a way to recreate it ? If not, do i have to re-deploy the entire manila operation Thank you guys.

2 1

[tc] Weekly Meeting Tomorrow, Oct 17 1800 UTC
by Jay Faulkner 16 Oct '23

16 Oct '23

Hi OpenStackers, The TC will be meeting for our weekly meeting tomorrow, 1800 UTC, in #openstack-tc on OFTC. Please see the proposed agenda below. Agenda - Roll call - Follow up on tracked action items: https://meetings.opendev.org/meetings/tc/2023/tc.2023-10-10-18.01.html - JayF: Before next video meeting, write up a short document on pros/cons of moving TC video meetings to jitsi-meet. - knikolla Investigate or delegate research on DB usage patterns in Keystone in devstack. Due before PTG. - slaweq to sync with Monasca potential PTL candidate and report back to TC next meeting - rosmaita to engage i18n sig about possibilty of translating governance docs - Gate health check - Leaderless projects (gmann) - PTG Reminder - Open Discussion and Reviews Thanks, Jay Faulkner Technical Committee Chair

1 0

[ironic] Meeting next week cancelled; PTG instead!
by Jay Faulkner 16 Oct '23

16 Oct '23

Hi all, Our regular meeting is cancelled in favor of an entire week of meetings :D. See you at the PTG! - Jay Faulkner Ironic PTG

1 0

[tc] dropping python 3.8 support for 2024.1
by Brian Rosmaita 13 Oct '23

13 Oct '23

I thought about this issue some more after yesterday's TC meeting, and tried to articulate why I think keeping python 3.8 support for 2024.1 is a bad idea on the patch: https://review.opendev.org/c/openstack/governance/+/895160 I don't know if my argument there will change anyone's mind, but since a lot of people have already voted on the gerrit review, I wanted to make sure that people are at least aware of it, to wit: I just don't see that py38 support for 2024.1 makes sense. It's not a default version in Ubuntu 22.04, Debian 12, Debian 11, CentOS Stream 9, or Rocky Linux 9, which are the distros specifically called out in the current 2024.1 PTI that this proposal is patching. While we can use Ubuntu 20.04 to run unit tests, we can't run master (2024.1 development) devstack in it, so it doesn't seem to me that Ubuntu 20.04 is a distribution that we can feasibly use for meaningful 2024.1 testing. This implies, in my opinion, that there is a solid reason for dropping python 3.8 support in advance of it going EOL, as required by [0]. Looking at the Python Update Process resolution [1], python 3.8 does not meet the three criteria set out in the "Unit Tests" section: 1. it's not the latest version of Python 3 available in any distro we can feasibly use for testing 2. It's not the default in any of the Linux distros identified in the 2024.1 PTI 3. It isn't used to run integration tests at the beginning of the 2024.1 (Caracal) cycle Add to that the fact that libraries are beginning to drop support [2], add further that py38 will go EOL roughly 6 months after the 2024.1 release (no more security updates), I don't see a reason to wait until a key library forces us to make a change during the development cycle. I'd prefer to do it now. [0] https://governance.openstack.org/tc/reference/pti/python.html#specific-comm… [1] https://governance.openstack.org/tc/resolutions/20181024-python-update-proc… [2] https://review.opendev.org/c/openstack/requirements/+/884564

8 19

[rally] Need Rally PTL/DPL for this release cycle.
by Ghanshyam Mann 13 Oct '23

13 Oct '23

Hi Andrey, Anyone interested in Rally PTL role, As you know, Rally is leaderless project in this cycle[1], in case you missed the PTL election or any new PTL volunteer, please reply to this email or add your name in below etherpad, or even propose the PTL appointment in governance model. - https://etherpad.opendev.org/p/2024.1-leaderless Also, think about DPL model if election are little overhead for this project with solo maintainer. - https://governance.openstack.org/tc/resolutions/20200803-distributed-projec… -gmann

3 4

[all][infra][tact-sig] Mailman v3 migration for OpenStack mailing lists 2023-10-12
by Jeremy Stanley 12 Oct '23

12 Oct '23

On Thursday, October 12 at 15:30 UTC, the OpenDev Collaboratory systems administrators will be migrating the lists.openstack.org mailing list site from the aging Mailman 2.1.29 server to a newer Mailman 3.3.8 deployment. This maintenance window is expected to last approximately four hours. The key takeaways are as follows: * There will be an extended outage for the site while DNS is updated and configuration, subscriber lists and message archives are imported, but incoming messages should correctly queue at the sender's end and arrive at the conclusion of our work * Because this is on a new server, there are new IP addresses from which list mail will be originating: 162.209.78.70 and 2001:4800:7813:516:be76:4eff:fe04:5423 * Moderation queues will not be copied to the new server, so moderators are encouraged to process any held messages prior to the migration time in order to avoid losing them * Anyone wishing to adjust their list subscriptions, or handle moderation or list configuration after the migration, needs to use the Sign Up button on the Web page to create a new account; it will be linked to your imported roles as soon as you confirm by following a URL from an E-mail message the server sends you, and is global for all sites on the server so you only need to do this once * The software providing Web front-ends for list management and archive browsing is entirely new in Mailman v3 and therefore has a much different appearance, though we've added appropriate redirects and frozen copies of old archives in order to accommodate existing hyperlinks If you have any questions or concerns, feel free to follow up on the service-discuss mailing list or find us in the #opendev channel on the OFTC IRC network. -- Jeremy Stanley

1 2