February 2023 - openstack-discuss

Live migration to host with advanced cpu results in instance inheriting incorrect cpu_model, even when overridden in nova.conf
by Andy Speagle 14 Feb '23

14 Feb '23

Hey Folks, We have a number of nodes in our openstack cluster who have the same family CPU (IvyBridge-IBRS) ... and one advanced CPU (Broadwell-IBRS). We have set the cpu_mode to custom and overridden the cpu_model to IvyBridge-IBRS so that all of the hosts would be compatible. This seems to work for instances started on the advanced host... we can live migrate off of the host. But... when we live migrate instances TO the advanced host... they seem to inherit the wrong CPU type. Example: If I live migrated onto the advanced host and then try to live migrate off of it... nova-compute logs on the older host throw: Error: Migration pre-check error: Unacceptable CPU info: CPU doesn't have compatibility. And the output clearly shows that it thinks it was launched on the Broadwell CPU: Instance launched has CPU info: {"arch": "x86_64", "model": "Broadwell- IBRS", "vendor": "Intel" ... With that instance on the advanced host, if I restart it... magically it comes up with the correct cpu_model and can be live migrated off... We're running ussuri ... does anyone know if this is known behavior? Could I have a misconfiguration somewhere? Thanks. -- Andy Speagle

1 0

[election][tc] TC candidacy for 2023
by Brian Rosmaita 14 Feb '23

14 Feb '23

Hello OpenStack Community, I am declaring my candidacy for a second term on the Technical Committee. I've been working on OpenStack since Folsom and currently serve as a core reviewer for the Glance and Cinder projects. In the past, I've been PTL of Glance and Cinder, and I am just now completing my first term on the Technical Committee. As I said last time, I don't have an agenda other than to represent active technical contributors to OpenStack and to participate in the TC in a manner consistent with its charter. Additionally, during my first term, I have been working with the OpenStack i18n SIG to refresh the translations infrastructure, and I would like to continue that work into the Bobcat development cycle. Thank you for considering my candidacy for the OpenStack Technical Committee. - Brian Rosmaita (rosmaita)

1 0

[publiccloud-sig] Reminder - next meeting Feb 15th - 0800 UTC
by Felix Kronlage-Dammers 14 Feb '23

14 Feb '23

Hi everyone, The next meeting of the Public Cloud SIG is on February 15th (this wednesday) at 0800 UTC. We meet on IRC in #openstack-operators. See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on wednesday! felix

1 0

[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