February 2023 - openstack-discuss

[election][ptl][openstack-ansible] Candidacy for 2023.2 Bobcat
by Dmitriy Rabotyagov 13 Feb '23

13 Feb '23

Hello everyone! I would like to announce my candidacy for the role of PTL of OpenStack-Ansible during the Bobcat/2023.2 cycle. I have been serving as the OpenStack PTL for quite a while now so with announcing my candidacy I also want to encourage other active contributors to participate in elections for keeping a healthy community and plurality of opinions in the project leadership. For the next cycle I would like to focus project development on: * Implementing SLURP upgrades both in terms of CI testing and upgrade script adjustment * Continue integration and improvement of PKI role with services * Keep up with latest supported versions of infrastructure software, like MariaDB, RabbitMQ and Ansible * Have progress on better functional testing of different scenarios for roles * Improve timing for our releases by decreasing the gap between OpenStack coordinated release and OSA trailing one. Thank you for your consideration!

1 0

[election][ptl][manila] Candidacy for 2023.2 Bobcat
by Carlos Silva 13 Feb '23

13 Feb '23

Hello everyone! I would like to announce my candidacy for the role of PTL of Manila during the Bobcat/2023.2 cycle. I have been serving as the Manila PTL for 2 cycles in a row and I would like to continue serving as PTL to this amazing community. During the last two cycles we have been focusing on closing the feature gap between the core of Manila and OpenStack Client, SDK and Manila UI, as well as engaging and encouraging contributor participation through mentoring and promoting collaborative activities, focusing on tech debt, and enhancing the tests coverage for various areas of Manila. We have also been putting efforts on making sure that relevant new features, fixes and enhancements are landing every single release. For the next cycle I would like to continue the great work we have been doing so far, but also have some focus on: * Continue encouraging active maintainers to actively do reviews so we can enhance our review bandwidth; mentor people to become core reviewers, as well as promote and participate in mentoring opportunities such as Outreachy, GHC and so on. * Continue to promote events like hackathons or bug squashes that will not only help us to achieve our goals such as enhancing our functional tests coverage and reduce the bug stats, but will also strengthen the community and get contributors to collaborate and create great learning opportunities. * Continue past cycles efforts to collaboratively cover the lack of documentation we have on third party CI setups for Manila, helping potential new vendors to quickly set up their CI systems. * Pursue the remaining changes keeping us from starting the deprecation of manilaclient in favor of the OpenStack client. Thank you for your consideration! Carlos da Silva IRC: carloss

1 0

[openstack-helm] switching to using service's user for requests
by Mohammed Naser 13 Feb '23

13 Feb '23

Hi team, I'm wondering if it makes sense for us to make a change in all of OpenStack Helm's code in order to make it use the service user for all requests. For example, right now, we are using the placement user in the `[placement]` section in Neutron, or the Neutron user in the `[neutron]` section in Nova. However, all of these users have the same exact role and permissions, so I believe it would help a lot in locking down services (let's say placement gets compromised, you can lock it's user only). I also think it will significantly simplify all of our code for endpoints for the different services, since we'll just be re-using the same credentials. Let me know what everyone thinks. Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 2

[election][ptl][designate] Candidacy for 2023.2 Bobcat
by Michael Johnson 13 Feb '23

13 Feb '23

Hello OpenStack community, I would like to announce my candidacy for PTL of Designate for the Bobcat cycle. I would like to continue to support the Designate team for the Bobcat release. For the Antelope release, we have continued our code stability work and focused development on a major new feature "Shared Zones". Looking forward to the Bobcat development cycle I expect to see a lot of work around updating for SQLAlchemy 2.x and introducing the "catalog zones" feature. Thank you for your support and your consideration for Bobcat, Michael Johnson (johnsom)

1 0

[cinder] Review Priorities R-5 (17th Feb, 2023)
by Rajat Dhasmana 13 Feb '23

13 Feb '23

Hello Argonauts, We've multiple deadlines this week (R-5 - 17th Feb, 2023) hence I would like to focus the team's review bandwidth towards the important reviews. 1) Cinderclient: 4 patches, 1 approved, 3 have +2s Important reviews: https://etherpad.opendev.org/p/cinderclient-antelope-release 2) python-brick-cinderclient-ext: 1 patch with +2 https://review.opendev.org/c/openstack/python-brick-cinderclient-ext/+/8735… 3) Feature Freeze: 12 features, 2 merged, 10 need reviews https://etherpad.opendev.org/p/cinder-antelope-features 4) Requirements Freeze: 4 patches but 2 potential ones https://review.opendev.org/q/(project:openstack/cinder+OR+project:openstack… Kindly focus on the above changes as they need to be merged this week for making into 2023.1 (Antelope) release. Thanks Rajat Dhasmana

1 0

[skyline] Is there a billing module available to integrate with Skyline?
by Roger Rivera 13 Feb '23

13 Feb '23

Hello, Skyline seems like an awesome contribution. We noticed there are price references on the video presentation of the Skyline dashboard. Does anybody know if there is an existing billing module that integrates with Skyline to add this functionality as seen in the bottom part of the screenshot? Any guidance to make this would be highly appreciated. Thank you -- *Roger Rivera*

3 2

[election][ptl][neutron] Candidacy for 2023.2 Bobcat
by Rodolfo Alonso Hernandez 13 Feb '23

13 Feb '23

Hello all: I would like to announce my candidacy for the role of PTL of Neutron for the Bobcat/2023.2 cycle. Let me introduce myself first. I started contributing to OpenStack in Liberty release (2015). I've contributed to several projects, mainly Neutron, neutron-lib, os-ken and os-vif, in addition to Nova and devstack. During the last two years I've been focused on the ML2/OVN integration, QoS and Placement related features and helping on the Neutron CI improvement and stabilization. For this new release, those are the main goals I would like to focus on: * Continue with the improvement of CI stability. This has been a very high time consuming task for the Neutron community, but the improvements can be seen in the number of rechecks and CI time used by Neutron. We must continue with this effort during the next release. * Keep working on the smart NIC / hardware offload testing. This is something I personally started during the last cycle but with little success, but we should continue with this effort. * Keep working on the approved (or active) specs with active developments: ** Metadata rate limit (LP#1989199) ** Expose backend hints in the port API, hint ovs-tx-steering (LP#1990842) ** ML2/OVN IPv6 Distributed routing (LP#1998609) ** Active-active L3 Gateway with Multihoming (LP#2002687) ** Configurable Security Group rules added by default to the new Security Groups (LP#1983053) Apart from those main goals, we should always keep an eye on: * The SQLAlchemy 2.0 migration and any possible issue detected. During the last two releases we found and solved several issues related to the migration to SQLAlchemy 2.0. We need to keep watching for new possible issues. * The Neutron's stadium ecosystem is alive and healthy: this is a permanent goal in any release. The Neutron ecosystem is wide and diverse and it is maintained with few resources. We should focus on those active projects and communities that support their respective repositories. * Still closing (or surpassing) the ML2/OVS - ML2/OVN feature gap. * The spec tracking and review, in order to continue adding new functionalities. Thank you in advance. Rodolfo Alonso Hernandez (ralonsoh, ralonsoh(a)redhat.com) Link: https://review.opendev.org/c/openstack/election/+/873508

1 0

[election][ptl][nova][placement] Candidacy for 2023.2 Bobcat
by Sylvain Bauza 13 Feb '23

13 Feb '23

Hey Nova and Placement folks, Despite me saying that Antelope would have been my last cycle as PTL, I have to fight the evidence : our project needs more contributors and we're struggled by our current dynamics. That's why I'm hereby proposing to act as PTL for this Bobcat release. When looking at the mirror, we tried a couple of things te lower the entry barrier in order to contribute to the Nova/Placement community : - we had a productive meet-and-greet session at the Berlin summit - we introduced a Review-Priority Gerrit label for identifying upstream interest - people volunteered for upstream bug triage on a weekly basis - we tried to minimize merge conflicts by ordering API changes Those different efforts worked pretty well for helping the Nova project to get more hands willing to solve problems, but it didn't helped that far the reviewing dynamics. Yes, we not only need contributors that contribute but we also need contributors that review what others contribute. During this Bobcat cycle, I'll propose a couple of incentives in that direction. This release is also special because it will be our first 'not-SLURP' [1] one. As a PTL, I'll take an attention to track all the developments so we can identify the necessary knobs in order to make this 'skipped' release a painless experience for our operators. Last but certainly not the least, the recent weeks showed us how fragile we are when our Zuul gate gets cold. I'll continue to propose help, support and visibility for our beloved firefighters that dig into those problems, including the stable branches which are crucial for many consumers of those branches. Anyway, nothing can happen magically, we need hands. Thanks, -Sylvain [1] https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…

1 0

[neutron] Bug Deputy Report February 6 - 12
by Elvira Garcia Ruiz 13 Feb '23

13 Feb '23

Hi! Here you have the Neutron bug report from February 6th to 12th: Critical --------- - https://bugs.launchpad.net/neutron/+bug/2004656 - "rpc_workers" config variable needs to be registered in stadium projects Fix proposed https://review.opendev.org/c/openstack/neutron/+/872644 Assigned to ralonsoh High ------ - https://bugs.launchpad.net/neutron/+bug/2006112 - [OVN] Error during execution of "add_vnic_type_and_pb_capabilities_to_lsp" Fix proposed: https://bugs.launchpad.net/neutron/+bug/2006112 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006603 - [FT] Test "OVSInterfaceEventTestCase.test_port_creation_and_deletion" randomly failing Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873118 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006612 - [FT] Test "TestOVNNeutronAgent.test_ovs_and_ovs_events" failing randomly Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873126 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006734 - [OVN] OVN trunk driver is not bumping the OVN LSP "external_ids:revision_number" Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873296 - https://bugs.launchpad.net/neutron/+bug/2006735 - [OVN] OVN trunk driver is not bumping the OVN LSP "external_ids:revision_number" Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873247 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006264 - [CI] tox-py311 job timing out some times Unassigned https://bugs.launchpad.net/neutron/+bug/2006953 - [stable/wallaby] test_established_tcp_session_after_re_attachinging_sg is unstable on ML2/OVS iptables_hybrid job Unassigned - https://bugs.launchpad.net/neutron/+bug/2006683 - fwaas scenario job fails randomly Unassigned Medium ----------- - https://bugs.launchpad.net/neutron/+bug/2004581 - Neutron API query error, implicit cast does not exist in postgresql Fix proposed: https://review.opendev.org/c/openstack/neutron/+/872745 Assigned to ralonsoh - https://bugs.launchpad.net/neutron/+bug/2006496 - [L3-HA] "max_l3_agents_per_router" not honored when the redundancy is reduced Fix proposed: https://review.opendev.org/c/openstack/neutron/+/873107 Assigned to ralonsoh https://bugs.launchpad.net/neutron/+bug/2006949 - SLAAC and stateless DHCP are not working with stateless SG Assigned to Ihar Low ----- https://bugs.launchpad.net/neutron/+bug/2006122 - ExternalGatewayForFloatingIPNotFound returns misleading http status code Fix proposed: https://review.opendev.org/c/openstack/neutron-lib/+/872748 Assigned to Felix Huettner Undecided -------------- - https://bugs.launchpad.net/neutron/+bug/2006145 - BGP Speaker peer sessions down when rabbitmq offline I looked for the l3 bgp lieutenants for better triaging but I was not able to find them online. Kind regards, Elvira

1 0

[kolla]RabbitMQ HA policies define
by Satish Patel 13 Feb '23

13 Feb '23

Folks, I have deployed 3 node kolla controllers and notice rabbitMQ doesn't have any HA policy for queues. when i rebooted one of the nodes and found some messages got lost. Any reason kolla doesn't use HA policies by default? If i want to add policies then where should i specify them or any doc you can point me to define policies.

4 11