- openstack-discuss - lists.openstack.org

[mistral] Mistral maintenance and PTL
by Axel Vanzaghi 07 Dec '22

07 Dec '22

Hello everyone, Let me introduce myself, Axel Vanzaghi, first used OpenStack in 2015 and got back to it when I joined OVHCloud as SRE. Here at OVHCloud, we make an intensive use of Mistral in our internals processes, so we don't want to see it going deprecated [1] or abandonned. We decided to take action to maintain it, first by proposing someone to be the PTL for Mistral [2]. I proposed myself for this role. Yet, my experience with Mistral is only being an user of it, I worked on some of our workflow. However, I really liked what we could do with the tool so I'm willing to learn more and contribute on this project as I will be able to have time for it. Our first goal is to maintain the project alive, but new features will still be welcomed. Regards, Axel Vanzaghi [1] https://review.opendev.org/c/openstack/governance/+/866562 [2] https://lists.openstack.org/pipermail/openstack-discuss/2021-February/02015…

1 0

[neutron] Issue during the EOL of Queens, Rocky and Stein branches
by Rodolfo Alonso Hernandez 07 Dec '22

07 Dec '22

Hello all: In [1], the Neutron team transitioned all projects to EOL. However, because of a loose patch merged after the branch freeze, the automated tools can't finish the EOL task. Yesterday, during the Neutron team meeting [3], the attendants agreed to skip this last patch (that changes one line in the documentation) and comment on the affected stable release patches. This mail is to confirm that and to ask the QA team to manually perform this action. We'll be more careful in the future. Regards. [1]https://review.opendev.org/c/openstack/releases/+/862937 [2]https://review.opendev.org/q/Ie8dd684a7b79b0a322b1f2d17fffb4d58cfe94fc [3] https://meetings.opendev.org/meetings/networking/2022/networking.2022-12-06…

1 0

[heat][release] Proposing to EOL Rocky and Stein
by Brendan Shephard 07 Dec '22

07 Dec '22

Hi, We were discussing some of the older branches we have and thought it was about time we start moving some of them to EOL. Initially, I would like to move Rocky and Stein to EOL and have done so here: https://review.opendev.org/c/openstack/releases/+/866135 We would also like to move Train to EOL as well, pending a few changes being merged. I wanted to reach out and ensure there is no objections here to any of these branches being EOL’d. Feel free to voice any concerns, otherwise I will move forward with that next week. Cheers, Brendan Shephard Senior Software Engineer Red Hat Australia

2 1

[all][tc] Technical Committee next weekly meeting on 2022 Dec 7 at 1600 UTC
by Ghanshyam Mann 07 Dec '22

07 Dec '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2022 Dec 7, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Dec 6 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[openstack-ansible] Meetings on December 27 and January 3 cancelled
by Dmitriy Rabotyagov 07 Dec '22

07 Dec '22

Hi folks, During today's meeting we have agreed on cancelling our regular weekly meetings on December 27 2022 and January 3 2022. We still have meetings on December 13 and December 20 before this small break.

1 0

[openstack-ansible] CI is broken - hold on rechecks
by Dmitriy Rabotyagov 07 Dec '22

07 Dec '22

Hi folks, After merging [1] all our CI tests seem broken until we merge [2], so please hold on all your rechecks. With that being said, we need to focus on landing 862924 or merge temporary workaround to the integrated repo to define neutron_ml2_drivers_type and neutron_plugin_base for other checks to pass without [2]. [1] https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/865961 [2] https://review.opendev.org/c/openstack/openstack-ansible/+/862924

1 1

[publiccloud-sig] Bi-weekly meeting reminder
by Tobias Rydberg 06 Dec '22

06 Dec '22

Hi everyone, Tomorrow it's time again for our bi-weekly meeting, 0800 UTC in #openstack-operators. Etherpad can be found here [0]. Hope to chat with you tomorrow! [0] https://etherpad.opendev.org/p/publiccloud-sig-meeting BR, Tobias Rydberg

1 0

[keystone] Federation fix for numerical groups
by Mohammed Naser 06 Dec '22

06 Dec '22

Hi folks, I've pushed up this patch for a few weeks now with no response, could we please have a look at it? https://review.opendev.org/c/openstack/keystone/+/860726 Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 1

Need assistance
by Gk Gk 06 Dec '22

06 Dec '22

Hi, We have a SR-IOV guest whose xml looks like shown below: ------ <interface type='hostdev' managed='yes'> <mac address='fa:16:3e:3d:72:18'/> <driver name='vfio'/> <source> <address type='pci' domain='0x0000' bus='0x01' slot='0x12' function='0x7'/> </source> <vlan> <tag id='2'/> </vlan> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </interface> ---- How to find the network statistics for the virtual function assigned to the VM above from the ethtool -S output shown below: --- ethtool -S eno12409 NIC statistics: rx_unicast: 2890507 tx_unicast: 1279755 rx_multicast: 101903131 tx_multicast: 363832 rx_broadcast: 1496406 tx_broadcast: 1052 rx_bytes: 10084560360 tx_bytes: 225469520 rx_dropped: 0 rx_unknown_protocol: 0 rx_alloc_fail: 0 rx_pg_alloc_fail: 0 tx_errors: 0 tx_linearize: 0 tx_busy: 0 tx_restart: 0 tx_queue_0_packets: 120328 tx_queue_0_bytes: 15218021 tx_queue_1_packets: 185835 tx_queue_1_bytes: 33463904 tx_queue_2_packets: 255145 tx_queue_2_bytes: 62401952 tx_queue_3_packets: 73719 tx_queue_3_bytes: 9766278 tx_queue_4_packets: 75719 tx_queue_4_bytes: 13886665 tx_queue_5_packets: 756632 tx_queue_5_bytes: 64787766 tx_queue_6_packets: 127836 tx_queue_6_bytes: 13422778 tx_queue_7_packets: 49417 tx_queue_7_bytes: 7596442 rx_queue_0_packets: 103727545 rx_queue_0_bytes: 6961254601 rx_queue_1_packets: 326249 rx_queue_1_bytes: 454984714 rx_queue_2_packets: 242553 rx_queue_2_bytes: 339238020 rx_queue_3_packets: 183649 rx_queue_3_bytes: 244280310 rx_queue_4_packets: 405611 rx_queue_4_bytes: 495795368 rx_queue_5_packets: 227854 rx_queue_5_bytes: 236190286 rx_queue_6_packets: 193401 rx_queue_6_bytes: 271337926 rx_queue_7_packets: 982683 rx_queue_7_bytes: 447042416 rx_bytes.nic: 12401182418323 tx_bytes.nic: 74986406490 rx_unicast.nic: 8485232145 tx_unicast.nic: 761643543 rx_multicast.nic: 101957596 tx_multicast.nic: 388091 rx_broadcast.nic: 1495740 tx_broadcast.nic: 1718 tx_errors.nic: 0 tx_timeout.nic: 0 rx_size_64.nic: 167990805 tx_size_64.nic: 244373395 rx_size_127.nic: 240074370 tx_size_127.nic: 466106113 rx_size_255.nic: 39290324 tx_size_255.nic: 29943862 rx_size_511.nic: 6918699 tx_size_511.nic: 4570812 rx_size_1023.nic: 22389241 tx_size_1023.nic: 15207161 rx_size_1522.nic: 8112022042 tx_size_1522.nic: 1832009 rx_size_big.nic: 0 tx_size_big.nic: 0 link_xon_rx.nic: 0 link_xon_tx.nic: 0 link_xoff_rx.nic: 0 link_xoff_tx.nic: 0 tx_dropped_link_down.nic: 0 rx_undersize.nic: 0 rx_fragments.nic: 0 rx_oversize.nic: 0 rx_jabber.nic: 0 rx_csum_bad.nic: 0 rx_length_errors.nic: 0 rx_dropped.nic: 0 rx_crc_errors.nic: 0 illegal_bytes.nic: 0 mac_local_faults.nic: 0 mac_remote_faults.nic: 0 fdir_sb_match.nic: 0 fdir_sb_status.nic: 1 tx_priority_0_xon.nic: 0 tx_priority_0_xoff.nic: 0 tx_priority_1_xon.nic: 0 tx_priority_1_xoff.nic: 0 tx_priority_2_xon.nic: 0 tx_priority_2_xoff.nic: 0 tx_priority_3_xon.nic: 0 tx_priority_3_xoff.nic: 0 tx_priority_4_xon.nic: 0 tx_priority_4_xoff.nic: 0 tx_priority_5_xon.nic: 0 tx_priority_5_xoff.nic: 0 tx_priority_6_xon.nic: 0 tx_priority_6_xoff.nic: 0 tx_priority_7_xon.nic: 0 tx_priority_7_xoff.nic: 0 rx_priority_0_xon.nic: 0 rx_priority_0_xoff.nic: 0 rx_priority_1_xon.nic: 0 rx_priority_1_xoff.nic: 0 rx_priority_2_xon.nic: 0 rx_priority_2_xoff.nic: 0 rx_priority_3_xon.nic: 0 rx_priority_3_xoff.nic: 0 rx_priority_4_xon.nic: 0 rx_priority_4_xoff.nic: 0 rx_priority_5_xon.nic: 0 rx_priority_5_xoff.nic: 0 rx_priority_6_xon.nic: 0 rx_priority_6_xoff.nic: 0 rx_priority_7_xon.nic: 0 rx_priority_7_xoff.nic: 0 ----- Please help Thanks Kumar

2 1

[nova][placement][tempest] Hold your rechecks
by Sylvain Bauza 06 Dec '22

06 Dec '22

Sorry folks, that's kind of an email I hate writing but let's be honest : our gate is busted. Until we figure out a correct path for resolution, I hereby ask you to *NOT* recheck in order to not spill our precious CI resources for tests that are certain to fail. Long story story, there are currently two problems : #1 https://launchpad.net/bugs/1940425 nova-ovs-hybrid-plug and nova-next jobs 100% fail due to a port remaining in down state. #2 https://bugs.launchpad.net/nova/+bug/1960346 nova-lvm job 100% fails due to a volume detach failure probably due to QEMU #1 is currently investigated by the Neutron team meanwhile a patch [1] has been proposed against Zuul to skip the failing tests. Unfortunately, this patch [1] is unable to merge due to #2. #2 has a Tempest patch that's being worked on [2] but the current state of this patch is WIP. We somehow need to have an agreement on the way forward during this afternoon (UTC) to identify whether we can reasonably progress on [2] or skip the failing tests on nova-lvm. Again, sorry about the bad news and I'll keep you informed. -Sylvain [1] https://review.opendev.org/c/openstack/nova/+/865658/ [2] https://review.opendev.org/c/openstack/tempest/+/842240

2 5