April 2022 - openstack-discuss - lists.openstack.org

[Browbeat]performance/load testing
by Vishwanath 28 Apr '22

28 Apr '22

Hello, I installed openstack using kolla-ansible, i would like to do load/performance testing, i came across below openstack page. https://docs.openstack.org/self-healing-sig/latest/testing/tools-list.html Browbeat looks like a perfect fit for what i want to do.I read browbeat documentation . Questions i have is: - as per the browbeat documentation, in order to install this we need to have openstack installation via tripleo (undercloud/overcloud) , does browbeat work with non triiplo openstack deployment? - I don’t have undercloud/overcloud setup. Regards Vish

1 0

Openstack Trove - Polling request timed out
by Manish Bharti 28 Apr '22

28 Apr '22

Dear Team, We are trying to deploy OpenStack environment for our application and while deploying trove service we are facing the below error(attached screenshot)- Traceback (most recent call last): File "/usr/lib/python3/dist-packages/trove/common/utils.py", line 207, in wait_for_task return polling_task.wait() File "/usr/lib/python3/dist-packages/eventlet/event.py", line 125, in wait result = hub.switch() File "/usr/lib/python3/dist-packages/eventlet/hubs/hub.py", line 313, in switch return self.greenlet.switch() File "/usr/lib/python3/dist-packages/oslo_service/loopingcall.py", line 154, in _run_loop idle = idle_for_func(result, self._elapsed(watch)) File "/usr/lib/python3/dist-packages/oslo_service/loopingcall.py", line 349, in _idle_for raise LoopingCallTimeOut( oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 870.99 seconds During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/trove/taskmanager/models.py", line 434, in wait_for_instance utils.poll_until(self._service_is_active, File "/usr/lib/python3/dist-packages/trove/common/utils.py", line 223, in poll_until return wait_for_task(task) File "/usr/lib/python3/dist-packages/trove/common/utils.py", line 209, in wait_for_task raise exception.PollTimeOut trove.common.exception.PollTimeOut: Polling request timed out. Please help us on this issue. -- Thank you , Manish Bharti Jodhpur, Raj - 342001. Contact:8875033000

2 1

[all][tc] Technical Committee next weekly meeting on April 28, 2022 at 1500 UTC
by Ghanshyam Mann 28 Apr '22

28 Apr '22

Hello Everyone, Technical Committee's next weekly meeting is scheduled for April 28, 2022 at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, April 27, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[openstack-helm] gnocchi chart removal
by Gage Hugo 28 Apr '22

28 Apr '22

Hey team, One of the topics from the last few PTGs have been reducing the scope of openstack-helm by evaluating which charts were being used and which ones have not been actively maintained and one of those charts that has been discussed was gnocchi. Besides a change to tolerations that was applied to most of the charts in the repo, the gnocchi chart has not seen much activity and there wasn't any immediate interest in maintaining it, so the current plan is to remove it from the repo. If you are someone who is actively using the gnocchi chart and would be interested in helping to maintain it, please let me know!

1 0

[all][qa] Dropping centos-8-stream support and testing
by Ghanshyam Mann 27 Apr '22

27 Apr '22

Hello Everyone, As you know, in zed cycle we are targeting centos-9-stream in testing runtime[1] and dropping the py3.6 support. By dropping the py3.6 support means stop testing the py3.6 and require "python_requires = >=3.8" , For example nova - https://github.com/openstack/nova/blob/5f5551448dcfcde26095963e223f973b90e6… With that centos-8-stream jobs are failing 100% and in qa meeting we decided to drop the support in devstack[2]. Dropping support in devstack means: 1. we will stop testing it[3] 2. Drop support from stack.sh. By disabling centos-8-stream from the supported_distro by default[4] in stack.sh (you can enable it by running with force flag). 1st is done and patch to remove the centos-8-stream job is merged (along with in Tempest and nova). For 2nd one we will wait for 1 more week and will discuss to do in next QA meeting. Please start removing or replacing the c8s jobs with c9s in your projects. You can keep gerrit topic 'drop-c8s-testing' to know the overall status. [1] https://governance.openstack.org/tc/reference/runtimes/zed.html [2] https://meetings.opendev.org/meetings/qa/2022/qa.2022-04-26-15.00.log.html#… [3] https://review.opendev.org/q/topic:drop-c8s-testing [4] https://github.com/openstack/devstack/blob/48417ca241cacff8f4398910792489a5… -gmann

3 4

[cinder] Bug deputy report for week of 04-26-2022
by Sofia Enriquez 27 Apr '22

27 Apr '22

This is a bug report from 04-20-2022 to 04-26-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/os-brick/+bug/1969794 "backport of the fix for bug #1947370 make lock_path a required config option when prvisouls it was optional." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1969373 "Simultaneous volume creation with the same image in multi-attach mode returns error." Assigned to Rajat. - https://bugs.launchpad.net/cinder/+bug/1969531 "NetApp NFS Storage Migration between backends is Failing." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1969643 "RBD: Unable to delete a volume which has snapshot/volume children." Assigned to Sofia Enriquez and Eric Harney. No fix proposed to master yet. - https://bugs.launchpad.net/cinder/+bug/1969784 "[Pure Storage] Replicated array communication failure not handled correctly." Assigned to Simon Dodsley. No fix proposed to master yet. Low - https://bugs.launchpad.net/cinder/+bug/1967683 "Wrong property to look up remote address." Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1970237 "[RBD] Multiple full backups cannot be created from one snapshot." Assigned to liuhuajie. No patch proposed to master yet. - https://bugs.launchpad.net/cinder/+bug/1969913 "[Documentation] Migration in cinder, lvm-rbd example is not correct." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1966904 "Complex config formula evaluation causes RecursionError." Fix proposed to master. Wishlist - https://bugs.launchpad.net/cinder/+bug/1970208 "Rebranding. Dell EMC must be renamed to Dell." Assigned to Alexander Malashenko. Fix proposed to master. - https://bugs.launchpad.net/cinder/+bug/1970115 " [Enhancement] No way to disable image conversion." Assigned to Rico Lin. No fix proposed to master yet. - https://bugs.launchpad.net/cinder/+bug/1970114 " [Enhancement] Image conversion with RBD is not efficient." Unassigned. No fix proposed to master yet. 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

RDO Yoga Released
by Amy Marrich 27 Apr '22

27 Apr '22

The RDO community is pleased to announce the general availability of the RDO build for OpenStack Yoga for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Yoga is the 25th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available on the CentOS mirror network: - For CentOS Stream 8 http://mirror.centos.org/centos/8-stream/cloud/x86_64/openstack-yoga - For CentOS Stream 9 http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-yoga/ The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. Interesting things in the Yoga release include: - RDO Yoga is the first RDO version built and tested for CentOS Stream 9. - In order to ease transition from CentOS Stream 8, RDO Yoga is also built and tested for CentOS Stream 8. Note that next release of RDO will be available only for CentOS Stream 9. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/yoga/highlights.html TripleO in the RDO Yoga release: Since the Xena development cycle, TripleO follows the Independent release model <https://specs.openstack.org/openstack/tripleo-specs/specs/xena/tripleo-inde…> and will only maintain branches for selected OpenStack releases. In the case of Yoga, TripleO will not support the Yoga release. For TripleO users in RDO, this means that: - RDO Yoga will include packages for TripleO tested at OpenStack Yoga GA time. - Those packages will not be updated during the entire Yoga maintenance cycle. - RDO will not be able to included patches required to fix bugs in TripleO on RDO Yoga. - The lifecycle for the non-TripleO packages will follow the code merged and tested in upstream stable/yoga branches. - There will not be any TripleO Yoga container images built/pushed, so interested users will have to do their own container builds when deploying Yoga. You can find details about this on the RDO Webpage <https://www.rdoproject.org/documentation/tripleo-in-xena/> *Contributors* During the Yoga cycle, we saw the following new RDO contributors: - Adriano Vieira Petrich - Andrea Bolognani - Dariusz Smigiel - David Vallee Delisle - Douglas Viroel - Jakob Meng - Lucas Alvares Gomes - Luis Tomas Bolivar - T. Nichole Williams - Karolina Kula Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 40 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories: - Adriano Vieira Petrich - Alan Bishop - Alan Pevec - Alex Schultz - Alfredo Moralejo - Amy Marrich (spotz) - Andrea Bolognani - Chandan Kumar - Daniel Alvarez Sanchez - Dariusz Smigiel - David Vallee Delisle - Douglas Viroel - Emma Foley - Gaël Chamoulaud - Gregory Thiemonge - Harald - Jakob Meng - James Slagle - Jiri Podivin - Joel Capitao - Jon Schlueter - Julia Kreger - Kashyap Chamarthy - Lee Yarwood - Lon Hohberger - Lucas Alvares Gomes - Luigi Toscano - Luis Tomas Bolivar - Martin Kopec - mathieu bultel - Matthias Runge - Riccardo Pittau - Sergey - Stephen Finucane - Steve Baker - Takashi Kajinami - T. Nichole Williams - Tobias Urdin - Karolina Kula - User otherwiseguy - Yatin Karel *The Next Release Cycle* At the end of one release, focus shifts immediately to the next release i.e Zed. *Get Started* To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. *Get Help* The RDO Project has the users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC. IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS and TripleO IRC channels (#centos, #centos-devel in Libera Chat network, and #tripleo on OFTC), however we have a more focused audience within the RDO venues. *Get Involved* To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and #tripleo on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube.

1 0

[magnum] Proposing Michal Nasiadka for core-reviewer
by Spyros Trigazis 27 Apr '22

27 Apr '22

Dear all, I would like to nominate Michal Nasiadka for core reviewer in the magnum project. Michal has been helping with reviews for the past cycles and proposed features and fixes regularly. He would be a great addition to the team. Cheers, Spyros

1 0

[cinder] This week's meeting (Today) will be in video+IRC
by Rajat Dhasmana 27 Apr '22

27 Apr '22

Hello Argonauts, This is a reminder email about this week's meeting i.e. Today (27 April) will be in video + IRC mode. The timings are same as regular cinder meeting i.e. 1400-1500 UTC. The meeting will be held in video[1] and IRC[2]. The reason to keep this in both ways is some people are more comfortable in written communication than verbal and vice versa so we can hold discussions in video or IRC as per author's wish. Also the roll call will happen on IRC and a summary will be given there as well so make sure you're connected to the IRC channel during the meeting. [1] connection info: https://bluejeans.com/556681290 [2] openstack-meeting-alt channel on IRC Thanks and regards Rajat Dhasmana

1 0

[openstack-ansible] Nominate Damian Dąbrowski for openstack-ansible core team
by Dmitriy Rabotyagov 27 Apr '22

27 Apr '22

Hi OSA Cores! I'm happy to nominate Damian Dąbrowski (damiandabrowski) to the core reviewers team. He has been doing a good job lately in reviewing incoming patches, helping out in IRC and participating in community activities, so I think he will be a good match for the Core Reviewers group. So I call for current Core Reviewers to support this nomination or raise objections to it until 22nd of April 2022. If no objections are raised we will add Damian to the team next week. -- Kind regards, Dmitriy Rabotyagov

5 5