February 2023 - openstack-discuss

[neutron] New pylint 2.16.0 version
by Rodolfo Alonso Hernandez 02 Feb '23

02 Feb '23

Hello Neutrinos: There is a new pylint version released that is breaking some pep8 CI jobs (so far [1]). If you find any error, please do not recheck and report a launchpad bug or ping us in #openstack-neutron channel. Thanks! [1]https://bugs.launchpad.net/neutron/+bug/2004538

1 0

[ironic][elections] Nominating myself to remain as Ironic PTL
by Jay Faulkner 01 Feb '23

01 Feb '23

Hi all, I've nominated myself to serve another term as PTL for Ironic. I also welcome and encourage other community members to run if they'd like as well -- choice is good! I would prefer 2023.2 be my last cycle as PTL for now; I think it's healthy for a project to cycle leaders and a year is a nice round number. If there are any members of the community interested in being PTL for 2024.1, (if I win this election) I'd love for us to connect and figure out a good way to hand things over. Ironic is a healthy project with lots of people who can help run it; I don't want to monopolize all the fun :). Thanks, Jay Faulkner Ironic PTL (Antelope) TC Member

1 0

[tc] Reminder: 2023-02-08 OpenInfra Board Sync
by Jeremy Stanley 01 Feb '23

01 Feb '23

The Open Infrastructure Foundation Board of Directors is endeavoring to engage in regular check-ins with official OpenInfra projects. The goal is for a loosely structured discussion one-hour in length, involving members of the board and the OpenStack TC, along with other interested community members. This is not intended to be a formal presentation, and no materials need to be prepared in advance. I've started an Etherpad where participants can brainstorm potential topics of conversation, time-permitting: https://etherpad.opendev.org/p/2023-02-board-openstack-sync At the conclusion of the November 16 discussion, we agreed to schedule the next call for 20:00 UTC on Wednesday, February 8. A link to the conference bridge is included in the pad. -- Jeremy Stanley

1 0

[cinder] Bug Report from 02-01-2023
by Sofia Enriquez 01 Feb '23

01 Feb '23

This is a bug report from 01-25-2023 to 02-01-2023. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/2004239 "Quotas rollback error when retype failed." Unassigned. - https://bugs.launchpad.net/cinder/+bug/2004140 "Hitachi: Cinder scheduler is down if backend is down." Assigned to Atsushi Kawai. Low - https://bugs.launchpad.net/cinder/+bug/2004174 "Replace plain Mock() calls with autospec=True or Mock(spec)." Unassigned. - https://bugs.launchpad.net/cinder/+bug/2004419 "[doc] Update 'Introduction to the Block Storage service in cinder'." Unassigned. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

Combining Upgrades: Experience and Information
by Denis Krienbühl 01 Feb '23

01 Feb '23

Hi We’re running Rocky at work, deployed using OpenStack Ansible, and would like to upgrade to something a lot more current. We are currently researching the best way to accomplish this. Apart from doing upgrades one by one, we are looking into combining upgrades. Say by upgrading from Rocky to Ussuri, then upgrading Ubuntu 18.04 to 20.04, followed by Ussuri to Yoga. I found some information about this here, but it’s not a lot: * https://wiki.openstack.org/wiki/Fast_forward_upgrades * https://wiki.openstack.org/wiki/Oath_FFU_Juno_To_Ocata * https://www.9bitwizard.eu/liberty-to-newton Would you know of any other experiences, articles, talks about this? If you combined upgrades in the past, how was your experience, and how many upgrades did you combine together? Thanks for your reply, Denis

1 0

Ansible OpenStack Collection 2.0.0 has been released 🥳
by Jakob Meng 01 Feb '23

01 Feb '23

Hello contributors and users, version 2.0.0 [0] of our Ansible collection for OpenStack clouds aka openstack.cloud has been released 🥂 It is a complete overhaul of our code base and brings full compatibility with openstacksdk 1.0.0 🤩 Highlights of this release are: - three new modules which for example provide a generic and uniform API for interacting with OpenStack cloud resources [1], [2], - a complete refactoring of all existing modules bringing dozens of bugfixes, new features as well as consistent and properly documented module results and options, - 100% compatibility with openstacksdk's first major release 1.0.0, - new guides for contributors [3] from devstack setup over coding guidelines to our release process and - massively increased CI coverage with many new integration tests, now covering all modules and plugins [4]. Note, this 2.0.0 release *breaks backward compatibility* with previous 1.x.x releases [5] ⚠️ - 2.x.x releases of this collection are compatible with openstacksdk 1.x.x and later *only*, - 1.x.x releases of this collection are compatible with openstacksdk 0.x.x prior to 0.99.0 *only*, - 2.x.x releases of are not backward compatible with 1.x.x releases [0], - 1.x.x release series will be in maintenance mode now and receive bugfixes only. However, this collection as well as openstacksdk continue to be backward compatible with clouds running on older OpenStack releases. For example, it is fine and a fully supported use case to use this 2.0.0 release with clouds based on OpenStack Train, Wallaby or Zed. Feel encouraged to always use the latest releases of this collection and openstacksdk regardless of which version of OpenStack is installed in your cloud. This collection is compatible with and tested with Ansible 2.9 and later. However, support for old short module names such as os_server have been dropped with this release. You have to call modules using their FQCN such as openstack.cloud.server instead. Many thanks to all contributors who made this release possible. Tens of thousands LOCs have been reviewed and changed and fixed and tested throughout last year. You rock! [0] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [1] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [2] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [3] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [4] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [5] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… Best, Jakob

1 0

[all][tc] Technical Committee next weekly meeting on 2023 Feb 1 at 1600 UTC
by Ghanshyam Mann 31 Jan '23

31 Jan '23

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

1 1