August 2023 - openstack-discuss - lists.openstack.org

[release] Release countdown for week R-6, Aug 21 - 25
by Thierry Carrez 18 Aug '23

18 Aug '23

Development Focus ----------------- Work on libraries should be wrapping up, in preparation for the various library-related deadlines coming up. Now is a good time to make decisions on deferring feature work to the next development cycle in order to be able to focus on finishing already-started feature work. General Information ------------------- We are now getting close to the end of the cycle, and will be gradually freezing feature work on the various deliverables that make up the OpenStack release. This coming week is the deadline for general libraries (except client libraries): their last feature release needs to happen before "Non-client library freeze" on August 24th. Only bugfixes releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/2023.2 branching request with the review (as an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… In the next weeks we will have deadlines for: * Client libraries (think python-*client libraries), which need to have their last feature release before "Client library freeze" (August 31st) * Deliverables following a cycle-with-rc model (that would be most services), which observe a Feature freeze on that same date, August 31st. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. As we are getting to the point of creating stable/2023.2 branches, this would be a good point for teams to review membership in their $project-stable-maint groups. Once the stable/2023.2 branches are cut for a repo, the ability to approve any necessary backports into those branches for 2023.2 "Bobcat" final release will be limited to the members of that stable team. If there are any questions about stable policy or stable team membership, please reach out in the #openstack-stable channel. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: August 24th, 2023 (R-6 week) Client library freeze: August 31st, 2023 (R-5 week) Bobcat-3 milestone: August 31st, 2023 (R-5 week) Cycle Highlights Due: August 31st, 2023 (R-5 week) Final 2023.2 Bobcat release: October 4th, 2023 -- Thierry Carrez (ttx)

1 0

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 18 Aug '23

18 Aug '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting will be cancelled. Have a nice weekend. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda

1 0

Need assistance
by Gk Gk 18 Aug '23

18 Aug '23

Hi All, We have an openstack ansible setup. We are trying to collect statistics for mysql galera cluster. I am trying to use the following mysql prometheus exporter at https://github.com/prometheus/mysqld_exporter/releases . But when I install the exporter into each of the three mysql galera nodes, I am not finding any mysql client statistics on the metrics url. Also when I checked the mysql databases 'information_schema' and 'performance_schema' , they were empty. How to get the relevant galera stats for the mysql cluster in openstack ? Thanks Kumar

1 0

vPTG October 2023 Team Signup Deadline Approaching!
by Kendall Nelson 17 Aug '23

17 Aug '23

Hello Everyone, Sign up your team up for the next virtual Project Teams Gathering (PTG), which will be held from Monday, October 23 to Friday, October 27 2023! If you haven't already done so and your team is interested in participating, you need to complete the survey[1] by August 20, 2023 at 7:00 UTC. Then make sure to register[2] - it’s free :) Thanks! -Kendall (diablo_rojo) [1] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2023_ptg_team_signup [2] PTG Registration: http://ptg2023.openinfra.dev/

1 1

Call for Mentors & Projects - Boston University Students
by Kendall Nelson 17 Aug '23

17 Aug '23

Hello Everyone! As some of you might know, we have had a working relationship with Boston University once a year where students actively participate in our OpenInfra project communities. The semester in which the Fundamentals of Cloud Computing (the course where we collaborate with them)( is approaching. September 5 is when the course begins and it runs until December 21. The course is a senior/graduate-level class that includes a semester-long capstone-like project, with the projects being proposed and supervised by an industry mentor. The projects are completed in teams of 5-7 students, who are expected to spend 5-8 hours per week on the project over the 13-week term, with presentations to the class every two weeks to evaluate their progress. *So! If you know of a project you would like to propose, please let me know ASAP! The professor would like to have the finalized list of projects to offer students by the first week in September. * Let me know if you have any other questions! -Kendall Nelson

3 3

[kolla] openvswitch-netcontrold image removal
by Michał Nasiadka 17 Aug '23

17 Aug '23

Hello Koalas, The openvswitch-netcontrold image is being dropped, that means in Bobcat release Kolla will not build and publish this image. This image is not supported within kolla-ansible, so it’s not tested and it installs netcontrold outside of the regular kolla venv. It has been used in the past by TripleO - but TripleO will not support Bobcat and beyond. If there is anybody interested in maintaining this image - please come forward posting your comment in the patch [1], otherwise it will be dropped. [1]: https://review.opendev.org/c/openstack/kolla/+/891655 Michal

1 0

[openstack][nova] how check if exist instances were create with AZ or without AZ
by Nguyễn Hữu Khôi 16 Aug '23

16 Aug '23

Hello guys. I need to verify whether an existing instance was created with AZ or without AZ. How can we check on an existing instance? I did not setup default AZ scheduler before. At this time I plan to expand the system by a new AZ. as document If the server was not created in a specific zone then it is free to be moved to other zones, i.e. the AvailabilityZoneFilter <https://docs.openstack.org/nova/latest/admin/scheduling.html#availabilityzo…> is a no-op. I am worried about when I migrate instances and they will be free to be moved to other zones. Nguyen Huu Khoi

2 3

VM state wont update on power failure
by Shrey Chauhan 16 Aug '23

16 Aug '23

Hi, Currently I am running xena version of openstack. I am confused about one thing. Running a 3 node cluster. In case of a power failure my vm still shows as active (vm_state = active, power_state = running), even though in KVM they are in shutoff state. When I bring back the node and restart nova the state changes to 'shutoff'. What I am not understanding, is nova managing only local vms power states. Its a 3 node cluster, so nova compute running on other node should change the state in the database, isnt it? Am I missing any nova or linvirt configuration here? Thanks in advance for any kind of help here Thanks and regards, Shrey

2 1

[olso.messaging] RabbitMQ and streams
by Arnaud Morin 16 Aug '23

16 Aug '23

Hey all, Is there any chance that someone already worked on integrating RabbitMQ streams (see [1]) to replace fanouts in oslo rabbitmq driver? We are wondering if this would help lowering the rabbit usage, and maybe increase the rabbit stability? Our deployment is relying a lot on fanouts to delivers messages to computes (mostly neutron, e.g. secgroup update / remote cache population), this is leading to a massive number of messages beeing delivered by seconds. Cheers, Arnaud [1] https://www.rabbitmq.com/streams.html

2 2

[tripleo] [deployment] heat stack error
by Kamil Madac 16 Aug '23

16 Aug '23

Hi Brendan, thanks for the reply. Existing deployment has been done on different set of servers and on centos stream 8, wallaby, so on centos 9 we deployed a different tripleo repos (python3-tripleo-repos-0.1.1-0.20220214194341.cbbdde6.el8.noarch.rpm vs python3-tripleo-repos-0.1.1-0.20230111082402.c73cb0f.el9.noarch.rpm ) for undercloud deployment. Environment yamls were taken from that working deployment. We will try to remove environment yaml from deploy arguments one by one and will try to identify yaml which causes the issue. On Tue, Aug 15, 2023, 22:49 Brendan Shephard <bshephar(a)redhat.com> wrote: > Hey Kamil, > > There will be an error in one of the environment files that you’re > including in your overcloud deploy command. > > You said it’s your first deployment that was already prepared for you. > Does this mean that the environment has already been deployed and you are > trying to make a change now? If that’s the case, then I would check any of > the files that have changed between the initial deployment and what you’re > trying to do now. > > Regards, > Brendan Shephard > Senior Software Engineer > > > > On 15 Aug 2023, at 23:48, Kamil Madac <kamil.madac(a)gmail.com> wrote: > > > > > > Hello, > > I'm trying to deploy openstack wallaby on centos9. Undercloud is > running, but when I run "openstack overcloud deploy" it ends up with error: > > > > 2023-08-14 14:45:51.426 5 ERROR heat.engine.worker > > 2023-08-14 14:45:52.346 5 DEBUG heat.engine.scheduler > [req-fa1861f1-2a35-4754-8179-7ca9c8a209a8 admin admin - - -] Task create > from TemplateResource "ControllerServiceChain" Stack "keos9" > [18515e00-1d85-4 > > f16-91f7-a88c7553c1ed] running step > /usr/lib/python3.6/site-packages/heat/engine/scheduler.py:207 > > 2023-08-14 14:45:52.352 5 INFO heat.engine.resource > [req-fa1861f1-2a35-4754-8179-7ca9c8a209a8 admin admin - - -] CREATE: > TemplateResource "ControllerServiceChain" > [44cce696-f0ef-4975-88e5-5b4e2b69149c] St > > ack "keos9" [18515e00-1d85-4f16-91f7-a88c7553c1ed] > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource Traceback (most > recent call last): > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resource.py", line 916, in > _action_recorder > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource yield > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resource.py", line 1028, in > _do_action > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource yield from > self.action_handler_task(action, args=handler_args) > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resource.py", line 978, in > action_handler_task > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource done = > check(handler_data) > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resources/stack_resource.py", > line 408, in check_create_complete > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource return > self._check_status_complete(self.CREATE) > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource File > "/usr/lib/python3.6/site-packages/heat/engine/resources/stack_resource.py", > line 451, in _check_status_complete > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource action=action) > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource > heat.common.exception.ResourceFailure: resources.ControllerServiceChain: > Error in 24 output role_data: The values of the "for_each" argument to > "repeat > > " must be lists or maps > > 2023-08-14 14:45:52.352 5 ERROR heat.engine.resource > > 2023-08-14 14:45:52.366 5 INFO heat.engine.stack > [req-fa1861f1-2a35-4754-8179-7ca9c8a209a8 admin admin - - -] Stack CREATE > FAILED (keos9): Resource CREATE failed: resources.ControllerServiceChain: > Error i > > n 24 output role_data: The values of the "for_each" argument to "repeat" > must be lists or maps > > > > > > It is my first tripleo deployment which was already prepared by the > customer, but is not working currently. It is wallaby deployment on centos > stream 9. > > > > Can somebody give me advice on what is the best way to troubleshoot such > issues in heat stacks in tripleo? > > > > Role data has been successfully generated by command: > > > > $ openstack overcloud roles generate -o > /var/workdir/tripleo-environment/tripleo-heat-templates/custom_roles_data.yaml > Controller Compute > > > > and then used to generate heat templates: > > > > > /var/workdir/tripleo-heat-templates-upstream-wallaby/tools/process-templates.py > \ > > -p /var/workdir/tripleo-heat-templates-upstream-wallaby \ > > -r > /var/workdir/tripleo-environment/tripleo-heat-templates/custom_roles_data.yaml > \ > > -n > /var/workdir/tripleo-environment/tripleo-heat-templates/custom_network_data.yaml > \ > > -o /var/workdir/generated-tripleo-heat-templates \ > > --safe > > > > > > > > Kamil Madac > > > >

1 0