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

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

[all][elections][ptl][tc] Combined PTL/TC 2024.1 cycle Election Nominations Kickoff
by Ian Y. Choi 15 Aug '23

15 Aug '23

Nominations for OpenStack PTLs (Project Team Leads) and TC (Technical Committee) positions (4 positions) are now open and will remain open until Aug 30, 2023 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained at https://governance.openstack.org/election/#how-to-submit-a-candidacy Please make sure to follow the candidacy file naming convention: candidates/2024.1/<Project_Name or "TC">/<email_address> (for example, "candidates/2024.1/TC/stacker(a)example.org"). The name of the file should match an email address for your current OpenStack Foundation Individual Membership. Take this opportunity to ensure that your OSF member profile contains current information: https://www.openstack.org/profile/ Any OpenStack Foundation Individual Member can propose their candidacy for an available, directly-elected seat on the Technical Committee. In order to be an eligible candidate for PTL you must be an OpenStack Foundation Individual Member. PTL candidates must also have contributed to the corresponding team during the 2023.1 to 2023.2 timeframe, Sep 16, 2022 00:00 UTC - Aug 30, 2023 00:00 UTC. Your Gerrit account must also have a verified email address matching the one used in your candidacy filename. Both PTL and TC elections will be held from Sep 06, 2023 23:45 UTC through to Sep 20, 2023 23:45 UTC. The electorate for the TC election are the OpenStack Foundation Individual Members who have a code contribution to one of the official teams over the 2023.1 to 2023.2 timeframe, Sep 16, 2022 00:00 UTC - Aug 30, 2023 00:00 UTC, as well as any Extra ATCs who are acknowledged by the TC. The electorate for a PTL election are the OpenStack Foundation Individual Members who have a code contribution over the 2023.1 to 2023.2 timeframe, Sep 16, 2022 00:00 UTC - Aug 30, 2023 00:00 UTC, in a deliverable repository maintained by the team which the PTL would lead, as well as the Extra ATCs who are acknowledged by the TC for that specific team. The list of project teams can be found at https://governance.openstack.org/tc/reference/projects/ and their individual team pages include lists of corresponding Extra ATCs. Please find below the timeline: PTL + TC nomination starts @ Aug 16, 2023 23:45 UTC PTL + TC nomination ends @ Aug 30, 2023 23:45 UTC TC campaigning starts @ Aug 30, 2023 23:45 UTC TC campaigning ends @ Sep 06, 2023 23:45 UTC PTL + TC elections start @ Sep 06, 2023 23:45 UTC PTL + TC elections end @ Sep 20, 2023 23:45 UTC Shortly after election officials approve candidates, they will be listed on the https://governance.openstack.org/election/ page. The electorate is requested to confirm their email addresses in Gerrit prior to 2023-08-30 00:00:00+00:00, so that the emailed ballots are sent to the correct email address. This email address should match one which was provided in your foundation member profile as well. Gerrit account information and OSF member profiles can be updated at https://review.openstack.org/#/settings/contact and https://www.openstack.org/profile/ accordingly. If you have any questions please be sure to either ask them on the mailing list or to the elections officials: https://governance.openstack.org/election/#election-officials

1 1

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

15 Aug '23

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

2 1

[puppet] Planning deprecation of puppet-qdr
by Takashi Kajinami 15 Aug '23

15 Aug '23

Hello, In Puppet OpenStack projects, we maintain the puppet-qdr module, which manages the QPID Dispatcher Router (aka. qdr). We've been using this module to deploy the qdr service in one of our CentOS jobs so that we can test deployment with the amqp1 messaging driver. However, the amqp1 driver was recently deprecated[1] because of lack of packages built for Ubuntu and Debian. [1] https://review.opendev.org/c/openstack/oslo.messaging/+/861070 While I'm now deprecating support for amqp1 driver in our module and removing usage of the deprecated driver in our CI, I'm also planning to deprecate the puppet-qdr module because we no longer have requirements to manage the qdr service within OpenStack deployments. I'm sending this email to hear any feedback about the module deprecation before we decide its actual timeline. In case you have any thought/concern/etc then please let me know. NOTE: Because the puppet-qdr module has been used by TripleO, my current plan is to deprecate the project instead of retiring it, which keeps its stable branches open. Thank you, Takashi Kajinami

1 0