March 2022 - openstack-discuss - lists.openstack.org

[release] Release countdown for week R-3, Mar 07 - 11
by Előd Illés 04 Mar '22

04 Mar '22

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, March 10th, 2022. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/yoga branch will be cut. This branch will track the Yoga release. Once stable/yoga has been created, the master branch will be ready to switch to Zed development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing Yoga plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/yoga branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/yoga branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be Zed) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any Yoga release so far. Finally, now is a good time to finalize release highlights if you have not already done so. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 10th, 2022 (R-3 week) Final RC deadline: March 24th, 2022 (R-1 week) Final Yoga release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

1 0

[requirements][release][rfe] sushy 4.1.1 for Yoga
by Iury Gregory 04 Mar '22

04 Mar '22

Hello Stackers, I would like to request a new release for sushy before creating the yoga branch, It contains some important fixes (e.g it will fix a problem when build sushy in Debian). The sushy lib is only used by ironic, so it shouldn't cause any problems updating the version in requirements. Thanks! -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

3 3

[Ironic] No suitable device was found for deployment
by 韩光宇 04 Mar '22

04 Mar '22

Dear all, I have a OpenStack Victoria environment, and tried to use ironic manage bare metal. But I got "- root device hints were not provided and all found block devices are smaller than 4294967296B." in deploy stage. 2022-02-09 17:57:56.492 3908982 ERROR ironic.drivers.modules.agent_base [-] Agent returned error for deploy step {'step': 'write_image', 'priority': 80, 'argsinfo': None, 'interface': 'deploy'} on node cc68c450-ce54-4e1c-be04-8b0a6169ef92 : No suitable device was found for deployment - root device hints were not provided and all found block devices are smaller than 4294967296B.. I used "openstack server create --flavor my-baremetal-flavor --nic net-id=$net_id --image $image testing" to deploy bare metal node. I download deploy images(ipa-centos8-master.kernel and ipa-centos8-master.initramfs) in https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/. The baremetal node info and flavor info as following: https://paste.opendev.org/show/bV7lgO6RkNQY6ZGPbT2e/ Ironic configure file as following: https://paste.opendev.org/show/bTgY9Kpn7KWqwQl73aEa/ Ironic-conductor log: https://paste.opendev.org/show/bFKZYlXmccxNxU8lEogk/ The log of ironic-python-agent in bare metal node: https://paste.opendev.org/show/btAuaMuV2IutV2Pa7YIa/ I see some old discussion about this, such as: https://bugzilla.redhat.com/show_bug.cgi?id=1312187. But those discussions took place a long time ago, not version V, and no solution was seen. Does anyone know how to solve this problem? I would appreciate any kind of guidance or help. Thank you, Han Guangyu

3 14

[nova][placement] Zed PTG preparation
by Sylvain Bauza 04 Mar '22

04 Mar '22

Hey folks, We have until Mar 11th [1]to communicate about our needs for the Zed PTG (I've already signed up our presence by the survey) .As you can see in [2], there are already projects that booked some timeslots. This time, I won't ask you to tell me over Doodle which times you can be around, but I'd rather propose you 3 options : Option A "The short one" : we ask for 3 days from Wednesday to Friday with 4 hours each (13UTC-17UTC) Option B "The week used": we ask for 4 days from Tuesday to Friday with 3 hours each (14UTC-17UTC) Option C "The largest one" : we ask for 4 days from Tuesday to Friday with 4 hours each (13UTC-17UTC) Option D "The Asian-nice one" : we ask for Wed to Friday with 3 hours each (14UTC-17UTC) but we also ask for Thursday with 2 hours (6UTC-8UTC) Please start to think about those options as we'll discuss this on next Tuesday meeting [3] and eventually we will vote on it. I also created a new etherpad for our PTG : https://etherpad.opendev.org/p/nova-zed-ptg If you want, you can start to collect some topics but also if you aren't able to attend next Nova meeting, you can also start to vote on the option above in there. Voila, that's it. Thanks and let's discuss it again on next meeting, -Sylvain [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027051… [2] https://ethercalc.openstack.org/7yxdas7suqnd [3] https://meetings.opendev.org/#Nova_Team_Meeting

1 0

[neutron] Drivers meeting agenda - 04.03.2022.
by Lajos Katona 03 Mar '22

03 Mar '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * Gratuitous ARPs are not sent during master transition: ( https://bugs.launchpad.net/neutron/+bug/1952907) ** For this one there are a few wip patches: ** https://review.opendev.org/c/openstack/neutron/+/821434 ** https://review.opendev.org/c/openstack/neutron/+/821433 ** https://review.opendev.org/c/openstack/neutron/+/712474 * On Demand agenda: (ralonsoh): https://bugs.launchpad.net/neutron/+bug/1962465. I want to discuss the scope of this bug and the possible fix. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

Openstack HPC storage suggestion
by Satish Patel 03 Mar '22

03 Mar '22

Folks, I built a 30 node HPC environment on openstack using mellanox infiniband nic for high speed MPI messaging. So far everything works. Now I am looking for a HPC PFS (parallel file system) similar to Luster which I can mount on all HPC vms to run MPI jobs. I was reading on google and saw some CERN videos and they are using Ceph (cephfs) for PFS. Also i was reading CephFS + Manila is a good choice for HPC on openstack design. Does anyone have any experience with HPC storage for Openstack? Please advice or share your experience :) Thanks in advance. ~S

4 4

[TripleO] Gate blocker for Centos 9 Wallaby
by Dariusz Smigiel 03 Mar '22

03 Mar '22

Currently TripleO gate is experiencing issues with building images [1] We're aware of the problem, and we're trying to resolve this issue. Please withhold from rechecking RDO Third Party CI. Thank you, Dariusz Smigiel (dasm) [1]: https://bugs.launchpad.net/tripleo/+bug/1962786

1 1

[Devstack][Gnocchi][Ceilometer] Not able to retrieve metrics using ceilometer and gnocchi
by Molka Gharbaoui 03 Mar '22

03 Mar '22

Hi all, I installed devstack and ceilometer by adding the following lines in the local.conf file: enable_plugin ceilometer https://opendev.org/openstack/ceilometer.git CEILOMETER_BACKEND=gnocchi Devstack (yoga) works correctly (I am able to create images, instances, etc.). The problem is that I cannot visualize the metrics. Using "gnocchi metric list" and "gnocchi resource list" commands the result is empty. When I use the "--debug" option, no errors are plotted but the body response is empty. "ceilometer-upgrade" gives the following error: DEBUG ceilometer.cmd.storage Upgrade Gnocchi resource types upgrade /opt/stack/ceilometer/ceilometer/cmd/storage.py:42 "ceilometer-polling" prints "The resource could not be found". I have a running instance. Could you help me in retrieving the metrics from openstack?

3 5

Neutron issue in current Xena Version of openstack
by Adivya Singh 03 Mar '22

03 Mar '22

hi Team, i am facing issue after installing XENA version of Openstack, where in the Same hosted Network node, some routers work, and some not, The real issue is the router which are not working, All floating IP assigned to the router does not work, but other routers hosted on same L3 agent Works I am seeing this king of error " "Could not generate persistent MAC: No data" , but i am not sure this is impacting the issue Regards Adivya Singh

2 1

[hwsig] sushy-oem-idrac for Hardware Vendor SIG
by Jaunteva, Aija 03 Mar '22

03 Mar '22

Hi, I would like to propose moving sushy-oem-idrac [1] that is used in Ironic project to Hardware Vendor SIG. sushy-oem-idrac is iDRAC specific OEM extension of vendor-independent sushy [2] library and both use Redfish to communicate with BMCs. Any feedback welcome. Regards, Aija [1] https://opendev.org/x/sushy-oem-idrac/ [2] https://opendev.org/openstack/sushy Internal Use - Confidential

2 1