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

Installing OpenStack with limited switch ports
by John van Ommen 17 Oct '23

17 Oct '23

Is there an OpenStack installer that offers the option of using tagged VLANs during the installation? I'm building an OpenStack environment that uses redundant hardware, but I have limited space for switches. The idea that I had was to use tagged VLANs for the external network. But all of the installers that I've seen, they only work if each physical port on the server corresponds to a network. IE, one of my physical ports on my server needs to be connected to a management switch, another port needs to be connected to the switch for the external network, etc. I'd like to reduce the physical footprint of the switches, by using a single switch with tagged VLAN: 1) one VLAN for the management network 2) one tagged VLAN for the external network 3) etc Taken to the extreme, it seems like it might be possible to use as few as one or two physical ports for all of the OpenStack networks. Is this possible, and if so, which OpenStack distribution offers this?

3 2

[magnum] Cancelling weekly meetings for 18 and 25 Oct
by Jake Yip 17 Oct '23

17 Oct '23

Hi all, Unfortunately, we will have to cancel the meeting this week as I will be away for a conference. Next week is our vPTG, we will have it at a separate timeslot so the weekly meeting will be cancelled too. I will send vPTG details in a separate email. Regards, Jake

1 0

[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