August 2021 - openstack-discuss - lists.openstack.org

[neutron] Drivers meeting agenda for 27.08.2021
by Slawek Kaplonski 26 Aug '21

26 Aug '21

Hi, Agenda for tomorrow's drivers meeting is at [1]. We have 2 RFEs to disuss: * https://bugs.launchpad.net/neutron/+bug/1936408 - [RFE] Neutron quota change should check available existing resources * https://bugs.launchpad.net/neutron/+bug/1939602 - [RFE] Add a memory profiler See You on the meeting tomorrow. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

why cannot launch the instance ?
by Tommy Sway 26 Aug '21

26 Aug '21

After the success deploy, I try to create a instance and launch it. But it failed. The error is : Message Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance b238edf6-093b-41ce-bd59-a349f8e8fa12. Code 500 Details Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 665, in build_instances raise exception.MaxRetriesExceeded(reason=msg) nova.exception.MaxRetriesExceeded: Exceeded maximum number of retries. Exhausted all hosts available for retrying build failures for instance b238edf6-093b-41ce-bd59-a349f8e8fa12. Created Aug. 25, 2021, 3:23 p.m. Why ? Thanks.

2 6

[all][tc] Technical Committee next weekly meeting on Aug 26th at 1500 UTC
by Ghanshyam Mann 25 Aug '21

25 Aug '21

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

1 1

Need help deploying Openstack
by wodel youchi 25 Aug '21

25 Aug '21

Hi, I am trying to deploy openstack with tripleO using VMs and nested-KVM for the compute node. This is for test and learning purposes. I am using the Train version and following some tutorials. I prepared my different template files and started the deployment, but I got these errors : *Failed to provision instance fc40457e-4b3c-4402-ae9d-c528f2c2ad30: Asynchronous exception: Node failed to deploy. Exception: Agent API for node 6d3724fc-6f13-4588-bbe5-56bc4f9a4f87 returned HTTP status code 404 with error: Not found: Extension with id iscsi not found. for node* and *Got HTTP 409: {"errors": [{"status": 409, "title": "Conflict", "detail": "There was a conflict when trying to complete your request.\n\n Unable to allocate inventory: Unable to create allocation for 'CUSTOM_BAREMETAL' on resource provider '6d3724fc-6f13-4588-bbe5-56bc4f9a4f87'. The requested amount would exceed the capacity. ",* Could you help understand what those errors mean? I couldn't find anything similar on the net. Thanks in advance. Regards.

5 11

[ops] [cinder] Cinder driver for Dell EMC PS Series on Train
by Massimo Sgaravatto 25 Aug '21

25 Aug '21

Dear all In our Cloud we have multiple backends for Cinder. One of them is using the Dell EMC PS Series volume driver My understanding (reading https://docs.openstack.org/releasenotes/cinder/ussuri.html) is that the driver doesn't work anymore in >= Ussuri A while ago we migrated to Train (using CentOS7 as operating system) and everything kept working fine. We are now trying to migrate to CentOS8 (still using Train) and the cinder volume service for the equallogic backend doesn't work anymore In the log file I found something like this [*] We already planned to dismiss that backend (but we planned to do that before next Openstack update). Does anyone know if that driver is supposed to work with Train and CentOS8 (and therefore python3) ? Thanks, Massimo [*] 021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps [req-9fee10a8-4ad4-4bb3-a04c-46ef6919bb0f - - - - -] Error running command.: TypeError: must be str, not bytes 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps Traceback (most recent call last): 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/dell_emc/ps.py", line 248, in _run_ssh 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps timeout=self.configuration.ssh_conn_timeout) 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/dell_emc/ps.py", line 72, in __inner 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps res = gt.wait() 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps File "/usr/lib/python3.6/site-packages/eventlet/greenthread.py", line 181, in wait 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps return self._exit_event.wait() 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps File "/usr/lib/python3.6/site-packages/eventlet/event.py", line 125, in wait 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps result = hub.switch() 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps File "/usr/lib/python3.6/site-packages/eventlet/hubs/hub.py", line 298, in switch 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps return self.greenlet.switch() 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps File "/usr/lib/python3.6/site-packages/eventlet/greenthread.py", line 221, in main 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps result = function(*args, **kwargs) 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/dell_emc/ps.py", line 196, in _ssh_execute 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps self._get_output(chan) 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps File "/usr/lib/python3.6/site-packages/cinder/volume/drivers/dell_emc/ps.py", line 175, in _get_output 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps out += ret 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps TypeError: must be str, not bytes 2021-08-25 10:13:06.637 30932 ERROR cinder.volume.drivers.dell_emc.ps

2 2

[cinder] Bug deputy report for week of 2021-25-08
by Sofia Enriquez 25 Aug '21

25 Aug '21

This is a bug report from 2021-18-08 to 2021-25-08. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1940540 "[oslo.utils] Usage of human output is deprecated in QemuImgInfo". Assigned to Takashi Kajinam. - https://bugs.launchpad.net/os-brick/+bug/1940608 "flush failed when both host and vm use lvm the multipath". Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/1941011 "Tests: Swift + S3 backup driver unit tests fail w/ RunTimeError". Unassigned. Wishlist - https://bugs.launchpad.net/cinder/+bug/1940669 "Add unit tests to check url and parameter for importing backups". Unassigned - https://bugs.launchpad.net/cinder/+bug/1940466 "Simultaneous volume creation with the same image in multiattach mode returns error". Assigned to Mitya Eremeev. - https://bugs.launchpad.net/cinder/+bug/1941062 " [Doc] Cinder retype installation is missing nova config". Unassigned. Incomplete - https://bugs.launchpad.net/cinder/+bug/1940859 "[Stein] Multipathd delivers the wrong path to Cinde". Unassigned. Invalid - https://bugs.launchpad.net/cinder/+bug/1941068 "cinder-manage commands crash during db sync". Unassigned. Cheers, -- L. 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

[Kolla-Ansible][Ironic] Baremetal node Cleaning fails in UEFI mode, but succeeds in Legacy Bios Mode
by Anirudh Gupta 25 Aug '21

25 Aug '21

Hi Team, I am trying to provision Baremetal node using IRONIC with KOLLA-ANSIBLE. I have enabled the support of "IPXE" in kolla-ansible as well. I am getting an issue that when my baremetal node is booted in UEFI Mode, it is not able to find file *"ipxe.efi"* as a result of which cleaning of the node fails [image: image.png] But when I change the BIOS Mode of my Baremetal Node to Legacy.BIOS, it looks for the file "*undionly.kpxe"* for which the acknowledgment is received and Data Packets are transferred. Eventually the cleaning of node is also a success. [image: image.png] Is there any limitation of IRONIC or KOLLA-ANSIBLE side that provisioning of Baremetal Node can only be done in Legacy Bios Mode? For bare metal provisioning in UEFI mode, is there any other parameter that needs to be enabled. Regards Anirudh Gupta

4 9

[kolla][wallaby] update images stop all vms
by Ignazio Cassano 25 Aug '21

25 Aug '21

Hello All, I am new in kolla so probably my procedure is not correct. Last week I installed wallaby and I deployed on my openstack only two virtual machines. Today I tried to updated images so: 1 pulled new images on my local registry 2 pushed new images on my local registry 3 pushed new images from my local registry to controllers and compute nodes (kolla-ansible pull --limit control,compute 4 run kolla-ansible deploy All virtual machines went in shutoff state. What is wrong in my procedure ? Regards Ignazio

2 6

What is this error, does it effect the install?
by Tommy Sway 25 Aug '21

25 Aug '21

I try to install Openstack using kolla, but it's a error when I check the system before installation : # kolla-ansible -i ./multinode prechecks PLAY RECAP **************************************************************************** *********************************** compute01 : ok=28 changed=0 unreachable=0 failed=0 skipped=24 rescued=0 ignored=0 control01 : ok=65 changed=0 unreachable=0 failed=0 skipped=59 rescued=0 ignored=0 control02 : ok=62 changed=0 unreachable=0 failed=0 skipped=53 rescued=0 ignored=0 control03 : ok=62 changed=0 unreachable=0 failed=0 skipped=53 rescued=0 ignored=0 localhost : ok=6 changed=0 unreachable=0 failed=1 skipped=2 rescued=0 ignored=0 monitoring01 : ok=18 changed=0 unreachable=0 failed=0 skipped=15 rescued=0 ignored=0 network01 : ok=47 changed=0 unreachable=0 failed=0 skipped=109 rescued=0 ignored=0 network02 : ok=47 changed=0 unreachable=0 failed=0 skipped=105 rescued=0 ignored=0 storage01 : ok=18 changed=0 unreachable=0 failed=0 skipped=15 rescued=0 ignored=0 The error is : The full traceback is: Traceback (most recent call last): File "/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-263600932037331/Ans iballZ_kolla_container_facts.py", line 102, in <module> _ansiballz_main() File "/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-263600932037331/Ans iballZ_kolla_container_facts.py", line 94, in _ansiballz_main invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS) File "/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-263600932037331/Ans iballZ_kolla_container_facts.py", line 40, in invoke_module runpy.run_module(mod_name='ansible.modules.kolla_container_facts', init_globals=None, run_name='__main__', alter_sys=True) File "/usr/lib64/python3.6/runpy.py", line 205, in run_module return _run_module_code(code, init_globals, run_name, mod_spec) File "/usr/lib64/python3.6/runpy.py", line 96, in _run_module_code mod_name, mod_spec, pkg_name, script_name) File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/tmp/ansible_kolla_container_facts_payload_v95779u3/ansible_kolla_container _facts_payload.zip/ansible/modules/kolla_container_facts.py", line 18, in <module> ModuleNotFoundError: No module named 'docker' fatal: [localhost]: FAILED! => { "changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-263600932037331/An siballZ_kolla_container_facts.py\", line 102, in <module>\n _ansiballz_main()\n File \"/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-263600932037331/An siballZ_kolla_container_facts.py\", line 94, in _ansiballz_main\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n File \"/root/.ansible/tmp/ansible-tmp-1629813578.505786-101978-263600932037331/An siballZ_kolla_container_facts.py\", line 40, in invoke_module\n runpy.run_module(mod_name='ansible.modules.kolla_container_facts', init_globals=None, run_name='__main__', alter_sys=True)\n File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\n mod_name, mod_spec, pkg_name, script_name)\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_kolla_container_facts_payload_v95779u3/ansible_kolla_containe r_facts_payload.zip/ansible/modules/kolla_container_facts.py\", line 18, in <module>\nModuleNotFoundError: No module named 'docker'\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1 } I installed the docker package on the deploy localhost and run again, but it still raise the same error. What is it ? And does it effect the install ? Thanks!

3 7

[all][elections][tc] Technical Committee Election Results
by Amy Marrich 25 Aug '21

25 Aug '21

As there were 4 empty seats and 4 candidates for those TC positions, no campaigning or voting was necessary. Please join me in congratulating the 4 returning members of the Technical Committee (TC). Dan Smith () Ghanshyam Mann (gmann) Jay Bryant (jungleboyj) Kendall Nelson (diablo_rojo) Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates and if you are considering running in the future please join the #openstack-tc channel and see what is involved if you haven't already. Thanks, Amy (spotz) on behalf of all the Election Officials

1 0

[all][elections][tc] TC Campaigning Kickoff
by Ian Y. Choi 25 Aug '21

25 Aug '21

Developers, The TC Election Campaigning Period has now started [1]. During the next couple days, you are all encouraged to ask the candidates questions about their platforms [2], opinions on OpenStack, community governance, and anything else that will help you to better determine how you will vote. This is the time to raise any issues you wish the future TC to consider, and to evaluate the opinions of the nominees prior to their election. Candidates, Each of you has posted a platform [2], and announced your nomination to the developers. From this point, you are encouraged to ask each other questions about the posted platforms, and begin discussion of any points that you feel are particularly important during the next cycle. While you are not yet TC members, your voices and opinions about the issues raised in your platforms and questions raised by the wider community will help ensure that the future TC has the widest possible input on the matters of community concern, and the electorate has the best information to determine the ideal TC composition to address these and other issues that may arise. Ian Y. Choi (ianychoi) On behalf of all the Election Officials [1] https://governance.openstack.org/election/ [2] https://opendev.org/openstack/election/src/branch/master/candidates/yoga/TC

1 0

[election][swift] PTL candidacy for Yoga
by Timothy Burke 24 Aug '21

24 Aug '21

It would be my pleasure to continue serving as Swift PTL for the Yoga cycle. This past cycle, we have continued our commitment to operational excellence. We've improved several features vital to large clusters, such as container sharding, partition power increases, and storage-policy reconciliation. We've improved the durability of erasure-coded data immediately after a write. We've made our logs, metrics, and errors more useful. We focus on operators for several reasons. Operators are at the junction of the software we write, the hardware we use, and the clients we serve. They have perhaps the best perspective to see the value-to-effort ratio of prospective improvements. They run the experiments that establish and optimize deployment patterns. They manage the drives and networking that allow us to serve hundreds of petabytes at terabits per second, and their projections tell us that storage must become bigger and faster. Thinking like an operator, there are several areas where Swift should improve. Replication and reconstruction continue to be a delicate balancing act between moving data for the sake of expansion vs. ensuring durability. We need a better handle on which data gets accessed, how frequently, and with what sort of performance -- ideally indexed by tenant and even user. As more clusters are stood up in more regions, we need to improve monitoring and recovery such that clusters can run with minimal human intervention. I look forward to working with the community to bring Swift into a future of ever-larger and ever-more-numerous clusters. Tim

1 0

[all][elections][ptl][tc] Combined PTL/TC Nominations ending in less than 24 hours
by Amy Marrich 24 Aug '21

24 Aug '21

A quick reminder that we are in the last hours for declaring PTL and TC candidacies. Nominations are open until Aug 24, 2021 23:45 UTC. If you want to stand for election, don't delay, follow the instructions at [1] to make sure the community knows your intentions. Make sure your nomination has been submitted to the openstack/election repository and approved by election officials. Election statistics[2]: Nominations started @ 2021-08-17 23:45:00 UTC Nominations end @ 2021-08-24 23:45:00 UTC Nominations duration : 7 days, 0:00:00 Nominations remaining : 1 day, 7:37:12 Nominations progress : 81.18% --------------------------------------------------- Projects[1] : 47 Projects with candidates : 28 ( 52.00%) Projects with election : 1 ( 2.00%) --------------------------------------------------- Need election : 1 (Cyborg) Need appointment : 19 (Adjutant Cinder Cloudkitty Designate Heat Ironic Magnum Manila Monasca OpenStack_Charms Openstack_Chef Puppet_OpenStack Release_Management Requirements Sahara Storlets Swift Tripleo Zun) =================================================== Stats gathered @ 2021-08-23 16:07:48 UTC This means that with approximately 2 days left, 23 projects will be deemed leaderless. In this case the TC will oversee PTL selection as described by [3]. There are also currently 4 confirmed candidates for the 4 open Technical Committee. Thank you, Amy (spotz) On behalf of all the Election Officials [1] https://governance.openstack.org/election/#how-to-submit-a-candidacy [2] Any open reviews at https://review.openstack.org/#/q/is:open+project:openstack/election have not been factored into these stats. [3] https://governance.openstack.org/resolutions/20141128-elections-process-for…

2 1

[cinder] reminder: this week's meeting in video+IRC
by Brian Rosmaita 24 Aug '21

24 Aug '21

Quick reminder that this week's Cinder team meeting on Wednesday 25 August, being the final meeting of the month, will be held in both videoconference and IRC at the regularly scheduled time of 1400 UTC. These are the video meeting rules we've agreed to: * Everyone will keep IRC open during the meeting. * We'll take notes in IRC to leave a record similar to what we have for our regular IRC meetings. * Some people are more comfortable communicating in written English. So at any point, any attendee may request that the discussion of the current topic be conducted entirely in IRC. * The meeting will be recorded. connection info: https://bluejeans.com/3228528973 meeting agenda: https://etherpad.opendev.org/p/cinder-xena-meetings cheers, brian

1 0

[election][Release_Management] PTL candidacy for Yoga
by Előd Illés 24 Aug '21

24 Aug '21

Hello OpenStack Community, I would like to announce my candidacy for PTL of the Release Management team for the Yoga cycle. I became core member in the Release Management team during Wallaby cycle to help the work of the team with release patch reviews, but I was involved in the release process for some time already as my focus has been Stable Maintenance (especially around the introduction of the Extended Maintenance process) as being member of the stable-maint-core group. Thanks to the great work of the former PTLs and team members of the Release Management team, now the process is fairly automated and should be straightforward to follow. During the Yoga cycle I'm planning to get familiar with all the aspects of the release management (with the help of the more experienced team members) and continue the work that my predecessors started and keep things maintained. Thanks for your consideration, Előd Illés (elodilles)

1 0

[election][cinder] PTL Candidacy for Yoga
by Brian Rosmaita 24 Aug '21

24 Aug '21

Hello everyone, I'd like to announce my candidacy for Cinder PTL for the Yoga cycle. The primary challenge we face in the Cinder community continues to be that our reviewing bandwidth has declined at the same time third-party driver contributions have not decreased. As I see it, the problem is that many vendors who maintain third-party drivers do not appear to be clear on the concept of community participation. (For what it's worth, I think this is more a manager problem than a developer problem, but the effect on Cinder is the same, namely, lots of request for reviews and not much doing of reviews. The Cinder documentation has information about how to review, how you don't need to be a core to do valuable reviews, etc., but it's not clear that many people have actually read them.) The Cinder community has tried to address this participation deficit in Xena by providing more upstream activities for contributors (for example, the monthly Festival of XS reviews [0] and the weekly Bug Squad meetings [1]), and these have had decent participation. In Yoga, I'd like to explore having some kind of Review Squad meeting to give people a chance to get "live" feedback on features under development. Some people do use the weekly Cinder meeting for this, but not everyone takes advantage of that, plus weekly meeting time is limited. I hate to propose yet another team meeting, but on the other hand, the bug squad and festival of reviews meetings are extremely productive, so I don't mind proposing another *productive* meeting. (We'll simply cancel it if it turns out that people don't take advantage. Also, I'm open to other ideas ... the key issue is providing faster feedback and more visibility for people developing cinder features, and allowing cinder cores to use their review time productively. So two key issues.) On the positive side, we did add a new cinder core during Xena and there's another person right on the verge of being proposed as a core. So that will help address review bandwidth, though I want to stress that non-core reviews are extremely important to the project as well. Our core reviewers also develop features and fix bugs--they are not full-time code reviewers. And the way to become a cinder core is to review widely in the project and demonstrate a good breadth of knowledge of the software. (As always, anyone currently working on cinder project who's interested becoming a cinder core, please contact me (or any of the current cores) to discuss what the expectations are.) Also on the good side is that we've done quite a bit of work on the Cinder CI this cycle. (I'm not going to tempt fate by saying anything more about that.) With respect to the details of Cinder development in Yoga, I expect those to emerge from our virtual PTG discussions in October. You can help set the agenda here: https://etherpad.opendev.org/p/yoga-ptg-cinder-planning To summarize, I would like to continue working on improving the review throughput of the Cinder team and find additional ways to get people more thoroughly involved in the project. Thanks for reading this far, and thank you for your consideration. Brian Rosmaita (rosmaita) [0] http://eavesdrop.openstack.org/#Cinder_Festival_of_XS_Reviews [1] http://eavesdrop.openstack.org/#Cinder_Bug_Squad_Meeting

1 0

[election][requirements][ptl] PTL Candidacy for Yoga
by Matthew Thode 24 Aug '21

24 Aug '21

I would like to announce my candidacy for PTL of the Requirements project for the Yoga cycle. The following will be my goals for the cycle, in order of importance: 1. The primary goal is to keep a tight rein on global-requirements and upper-constraints updates. (Keep things working well) 2. Un-cap requirements where possible (stuff like prettytable). 3. Fix some automation of generate contstraints (pkg-resources being added and setuptools being dropped) 4. Audit global-requirements and upper-constraints for redundancies. One of the rules we have for new entrants to global-requirements and/or upper-constraints is that they be non-redundant. Keeping that rule in mind, audit the list of requirements for possible redundancies and if possible, reduce the number of requirements we manage. I look forward to continue working with you in this cycle, as your PTL or not. IRC: prometheanfire -- Matthew Thode

1 0

[election][manila][ptl] PTL Candidacy for Yoga
by Goutham Pacha Ravi 24 Aug '21

24 Aug '21

Hello fellow zorillas and other interested stackers, I'm expressing interest to continue serving as PTL for the OpenStack Manila team through the Yoga cycle. I've used my great privilege in this role to affect the community in many small and significant ways over the past four cycles. It has been a smooth ride because of stellar contributors who're beyond motivated and enthusiastic to develop and maintain impactful software while having fun. The enthusiasm is bolstered by grit to be a team with a difference. We jump at the opportunity to help a user or mentor and welcome new contributors or back each other up and help get stuff done, regardless of the "barriers" of affiliation. I enjoy being the occasional enabler to this camaraderie. During the Xena cycle, we mentored two Outreachy interns and on-boarded several new contributors. We added sub team core maintainers in the manila-tempest-plugin project and a new core maintainer across the manila repos. We drove down bug backlogs through bug squash weeks, swarmed to work on the OpenStackClient with a hack-a-thon and crushed the goal to drive down tech debt. We kept the momentum on several multi-cycle efforts such as OpenStackSDK integration, Secure RBAC, Active/Active HA. The Yoga cycle will be critical in our efforts to drive some of these multi-cycle efforts to closure. So, if you will have me, I wish to serve you through the Yoga cycle and get things done. I would tell you it's going to be the best release ever; but I would hold out the distinction for the Zorilla cycle - yes that's what we'll name it, what other cool name will we have anyway :) Thank you for your support, Goutham Pacha Ravi <gouthampravi(a)gmail.com> IRC: gouthamr

3 2

[infra][devstack][CI] pmlogger service fails to start
by Balazs Gibizer 24 Aug '21

24 Aug '21

Hi, Is there any work ongoing to figure out why devstack fails with? Job for pmlogger.service failed because a timeout was exceeded. We have 120 hits in the last 7 days. Recent example [1], logstash signature [2]. cheers, gibi [1] https://zuul.opendev.org/t/openstack/build/a36289ff4fc34b18af70b5b29d38bdf4… [2] http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3…

1 0

[storlets] Transition stable/stein and older branches to EOL
by Takashi Kajinami 24 Aug '21

24 Aug '21

Hi all, I recently noticed that our project still has many old stable branches, from Newton (!!). Because I've never seen any interests to backporting changes to very old branches, I'll propose transitioning stable/stein and older stable branches to EOL. If you have any concerns with that transition please let me know in the following gerrit review. https://review.opendev.org/c/openstack/releases/+/804562 Note that Newton and Ocata will be anywary marked as EOL now since these branches are globally marked as EOL, IIUC. Thank you, Takashi

1 0

[ironic] Not running for PTL this cycle
by Julia Kreger 24 Aug '21

24 Aug '21

Greetings everyone, I know I've repeatedly stated over the last few PTGs and midcycle sessions that I wouldn't be running this cycle, but I also realized this morning I had not sent an email. I've served as Ironic's PTL for 7 cycles, and after three and a half years, it is far past time to step down for at least a cycle. Serving the community has been a privilege and an honor, and I'm not planning on going anywhere, but a single person can only take on and handle so much stress. Changes in leadership are also a good thing as it can bring fresh perspective and voices into a project. I encourage Ironic contributors to consider if they would like to serve as the PTL, and to go ahead and submit their candidacy to the elections repository. The only thing I ask is we remain mindful of the needs of the community. I'll be there to help, to guide, and resolve conflicts if necessary. Much as Dmitry, Jim, and Aeva did before me. -Julia

8 7

[election][storlets] PTL Candidacy for Yoga
by Takashi Kajinami 24 Aug '21

24 Aug '21

Hi All, I'd like to announce my candidacy to continue the PTL role for Storlets project in the Yoga cycle. After inactive recent cycles, we fortunately got some interest around the project again. So I'll propose the items below as our focus during the next cycle. - Keep compatibility with Swift. This is always top-priority - Merge some patches still open to achieve easier operation and improve resource efficiency Thank you for your consideration. Thank you, Takashi

1 0

[horizon][dev] Auto-Refresh Feature Proposal
by Santos, Gustavo Faganello 24 Aug '21

24 Aug '21

Hello, everyone. I'm here to find out what you think about the addition of a feature in OpenStack Horizon. As you may know, Horizon requires the user to manually update the page in order to get the most recent data in the system, e.g. if an instance is created, deleted or renamed before the page is reloaded, the user has to hit the refresh button in their browser to see those changes in the page. This applies to the majority of Horizon's pages, including, but not limited to, Instances, Volumes, Users and so on. With that in mind, our team has implemented and tested a prototype of an auto-refresh feature for Horizon. We've been using it for a while now and have received positive feedback from our clients. It automatically updates the information in tables, pie charts (such as the Compute Overview page graphs) and details pages every five seconds, without the need for manually refreshing the page. The information displayed on the page will be replaced by the most recent data without any action from the user or any page reloading. It essentially works by requesting, in the background, the opened page again and again every few seconds through AJAX, and then replacing the old information with the new one if they differ. The feature affects every element in Horizon, except AngularJS ones - the tables in the Compute Images, Key Pairs and Server Groups pages are AngularJS elements and will not be affected by auto-refresh, for example. We are open to looking into this issue in the future, though. Could you please let us know if you would be open to adding such a feature to Horizon? If so, we'd be willing to do the upstream implementation in OpenStack, and we think it would be a great addition to the end users. Kind regards. Gustavo Santos

5 5

[election][ironic] PTL Candidacy for Yoga
by Iury Gregory 23 Aug '21

23 Aug '21

Hello Stackers, I would like to nominate myself to serve as Ironic PTL for the Yoga cycle. I've been working with OpenStack since 2015 and contributing to ironic since Oct 2018 (Stein release). I hope that we as a community can continue to achieve goals together, let's not forget that our main objective is to take over the world and make operator's life easier! We should also aim to grow our contributor base and continue to spread the word about Ironic (blog posts, social media, etc). Features that I think we should aim for during the next cycle: Virtual Media visibility, Security Interface using Keylime. Best regards, -- *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>*

2 1

No meeting tomorrow
by Gage Hugo 23 Aug '21

23 Aug '21

Hey team, Since there are no agenda items [0] for the IRC meeting tomorrow, the meeting is cancelled. Our next meeting will be Aug 31st. Thanks [0] https://etherpad.opendev.org/p/openstack-helm-weekly-meeting

1 0