May 2024 - openstack-discuss - lists.openstack.org

[kolla-ansible] How to pin pip3 module in kolla-ansible
by Satish Patel 22 May '24

22 May '24

Folks, I have deployed kolla-ansible using public images so far everything is good until I hit this bug [1] requests pip module had a minor bug. Now my question is if I want to pin requests==2.31.0 version in kolla-ansible then what file should I be adding to the pin version? This is not an image building related module because it deployed on a metal host so nothing to do with building kolla images. It's a pure docker issue. 1. https://github.com/docker/docker-py/pull/3257

3 3

[tc][all][sahara] Retiring the Sahara project
by Ghanshyam Mann 21 May '24

21 May '24

Hello everyone, As you might know, the Sahara project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Sahara retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

3 9

[openstack][nova]about instance-state when resizing failed
by Nguyễn Hữu Khôi 21 May '24

21 May '24

Hello. I would like to know why we set instance-state to ERROR when resizing/migrating failed? I have a problem with resizing/migrating instances. I must reset state then shelve and unshelve instances to make it come back. Thank you for your time. Nguyen Huu Khoi

5 14

[openstack-ansible][Yoga] Unable to deploy masakari on openstack-ansible
by Danish Khan 21 May '24

21 May '24

Dear Team, My masakari playbook is failing with below error: TASK [pacemaker_corosync : Creates corosync config] **************************************************************************************************** Tuesday 21 May 2024 16:24:32 +0530 (0:00:00.369) 0:00:08.576 *********** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt' fatal: [bbs-p-swaas-compute1]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt'"} Below is few lines from /etc/ansible/roles/pacemaker_corosync/templates/corosync.conf.j2 {% if inventory_hostname in groups[pacemaker_corosync_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_corosync_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% elif pacemaker_remote_group in groups and inventory_hostname in groups[pacemaker_remote_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_remote_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% endif %} Regards, Danish Khan

2 3

[ops] Investigating Shelving/Unshelving of Instances in OpenStack with Asynchronous Functions
by Shubham Kumar Yadav 21 May '24

21 May '24

Hi, I have a customer using a Pyrhon script to shelve/unshelve instance periodicly in the openstack, *He use openstack's std library for python and thus call * if (novaC.servers.get(server).status=='ACTIVE'): (novaC, cinderC, server, 'stop') -> nova.servers.stop() while (novaC.servers.get(server).status!='SHUTOFF'): time.sleep(10) if (novaC.servers.get(server).status=='SHUTOFF'): controlServer(novaC, cinderC, server, 'shelve') -> nova.servers.shelve() seems that script uses async function, which I supose be the problem.It is possible from nova API manipulate async requests ?

1 0

[ops] help with manila ceph backend
by Shubham Kumar Yadav 21 May '24

21 May '24

Hi, im trying to install manila in my openstack cluster, but i see some logs in the manila-share pod which i dont understand much logs: *2024-05-20 07:30:13.731 8 ERROR manila.share.manager [None req-712d1a81-bbfe-4e90-a2c8-8b7ae3650eff - - - - - -] Error encountered during initialization of driver CephFSDriver@lab-11053-26006-ceph-1@cephfsnative1: manila.exception.ShareBackendException: Share backend error: Error reading ceph version to set the default target. Please check your Ceph backend is reachable. 2024-05-20 07:30:13.731 8 ERROR manila.share.manager Traceback (most recent call last): 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 362, in setup_default_ceph_cmd_target 2024-05-20 07:30:13.731 8 ERROR manila.share.manager ceph_major_version = self.ceph_mon_version['major'] 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 382, in ceph_mon_version2024-05-20 07:30:13.731 8 ERROR manila.share.manager output = rados_command(self.rados_client, "version", target=('mon', )) 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 402, in rados_client2024-05-20 07:30:13.731 8 ERROR manila.share.manager self._rados_client = rados.Rados( 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "rados.pyx", line 398, in rados.Rados.__init__ 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "rados.pyx", line 459, in rados.Rados.__setup 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "rados.pyx", line 540, in rados.Rados.conf_read_file 2024-05-20 07:30:13.731 8 ERROR manila.share.manager rados.ObjectNotFound: [errno 2] RADOS object not found (error calling conf_read_file) 2024-05-20 07:30:13.731 8 ERROR manila.share.manager 2024-05-20 07:30:13.731 8 ERROR manila.share.manager During handling of the above exception, another exception occurred: 2024-05-20 07:30:13.731 8 ERROR manila.share.manager 2024-05-20 07:30:13.731 8 ERROR manila.share.manager Traceback (most recent call last): 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/manager.py", line 366, in _driver_setup 2024-05-20 07:30:13.731 8 ERROR manila.share.manager self.driver.do_setup(ctxt) 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 269, in do_setup 2024-05-20 07:30:13.731 8 ERROR manila.share.manager self.setup_default_ceph_cmd_target() 2024-05-20 07:30:13.731 8 ERROR manila.share.manager File "/var/lib/openstack/lib/python3.10/site-packages/manila/share/drivers/cephfs/driver.py", line 366, in setup_default_ceph_cmd_target 2024-05-20 07:30:13.731 8 ERROR manila.share.manager raise exception.ShareBackendException(msg=msg) 2024-05-20 07:30:13.731 8 ERROR manila.share.manager manila.exception.ShareBackendException: Share backend error: Error reading ceph version to set the default target. Please check your Ceph backend is reachable. 2024-05-20 07:30:13.731 8 ERROR manila.share.manager 2024-05-20 07:30:14.305 7 ERROR manila.share.drivers.generic [None req-3ade5267-d42c-4ce1-abba-74b154cdd903 - - - - - -] Failed to get Nova VM. No server with a name or ID of 'None' exists.: manila.exception.ManilaException: Failed to get Nova VM. No server with a name or ID of 'None' exists. 2024-05-20 07:30:15.736 8 ERROR manila.share.manager [None req-712d1a81-bbfe-4e90-a2c8-8b7ae3650eff - - - - - -] Error encountered during initialization of driver CephFSDriver@lab-11053-26006-ceph-1@cephfsnative1: rados.ObjectNotFound: [errno 2] RADOS object not found (error calling conf_read_file)* i have added in manila conf(manifest) : [cephfsnative1]driver_handles_share_servers = Falseshare_backend_name = CEPHFSNATIVE1share_driver = manila.share.drivers.cephfs.driver.CephFSDrivercephfs_conf_path = /etc/ceph/ceph.confcephfs_protocol_helper_type = CEPHFScephfs_auth_id = manilacephfs_cluster_name = cephcephfs_filesystem_name = cephfs could you please help we understanding the issue and resolving it please. Hope to hear from you soon Thank you!

2 1

Subject: [tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-19)
by Goutham Pacha Ravi 20 May '24

20 May '24

Hello Stackers, We're counting down 19 weeks to the 2024.2 (Dalmatian) release [1], and it's been a week of spring cleaning at the OpenStack Technical Committee. This is likely the case with project repositories across the board. There have been a few governance changes in the past week that I'd like to brief you on. At the outset, we merged an update to the upper-constraints, allowing SQLAlchemy 2.0, dropping sqlalchemy-migrate, and bumping the version of Alembic [2]. If you happen to meet Stephen Finucane (sfinucane) in person, do buy him a beverage of his choice, or several. This was no small effort. Thanks, Stephen! Over the past several releases, we've seen decreased activity in some OpenStack projects. We tagged these projects as "Inactive" [3] during past release cycles. We pursued the retirement of some of these projects in the past week. A shout out to Ghanshyam Mann (gmann) for driving this effort! We followed our process on project team removals [4]. It's possible, however, that there are unexpected side effects of deleting code in these project repositories. This could be CI jobs failing in actively maintained projects because they relied on deleted code from retired repositories or documentation updates that we missed. Please bear with us as we learn and adjust, and do let us know if we could improve the tooling or our retirement process. === Weekly Meeting === Last week's IRC meeting coincided with the Sovereign Cloud Stack Summit (May 14th) and the Open Infra Day (May 15th) in Berlin, Germany. However, we had a quorum and were able to go through a number of important discussion items [5]. - We discussed the removal of eventlet and migration to other concurrency/threading patterns. The consensus remained that shared tooling like oslo libraries should not dictate a specific threading model. A suggestion was made for the TC to provide recommendations rather than enforce a specific model. We're looking for help with this! All projects currently relying on eventlet must be finding ways to remove their use of it, and we're looking to use your expertise to frame a recommendation across the board. - On the topic of cleaning up additional maintainers on OpenStack packages on PyPi, Clark Boylan (clarkb) and Jeremy Stanley (fungi) helped me isolate PyPi repositories that "openstackci" didn't have permissions to make edits. We have earmarked [6] packages where we'll be removing additional maintainers this week. There's more work to be done here. So please keep an eye on future updates. - Dan Smith (dansmith) revived an old effort to setup OSC as a service on devstack; the patch has now merged [7]. Please consider using it locally and on CI jobs if you would like the speedup. There are some CI changes popping up already [8]. Our next weekly IRC meeting is tomorrow. The agenda for this meeting is up [9]. Please join us, and remember, you can always add new meeting items! === Governance Proposals === ==== Merged ==== Retire Solum project | https://review.opendev.org/c/openstack/governance/+/919211 Retire Murano project | https://review.opendev.org/c/openstack/governance/+/919358 Retire Sahara project | https://review.opendev.org/c/openstack/governance/+/919374 Retire Senlin project | https://review.opendev.org/c/openstack/governance/+/919347 Retire ec2-api project | https://review.opendev.org/c/openstack/governance/+/919394 Neutron: Retire networking-ovn | https://review.opendev.org/c/openstack/governance/+/919700 ==== Open for review/discussion ==== Migrate eventlet usages to asyncio | https://review.opendev.org/c/openstack/governance/+/902585 Clarify the project retirement vs project's repository retirement | https://review.opendev.org/c/openstack/governance/+/919984 Retire devstack-gate | https://review.opendev.org/c/openstack/governance/+/919629 Update to include docs and miscellaneous repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833 And finally, the OpenStack Technical Committee serves you! We're always willing to chat with you and would love feedback. === How to contact the TC === You can reach out to the TC in multiple ways: 1. Email: you can send an email with the tag [tc] on this email list. 2. Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel. 3. Join us at our weekly meeting: The Technical Committee meets every week on Tuesdays at 1800 UTC [9]. Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://review.opendev.org/c/openstack/requirements/+/879743 [3] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [4] https://governance.openstack.org/tc/reference/dropping-projects.html [5] https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-14-18.00.log.html [6] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup#L52 [7] https://review.opendev.org/c/openstack/devstack/+/676016 [8] https://review.opendev.org/q/topic:%22ocaas%22 [9] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

Issue in Devstack Setup
by Lohit S 20 May '24

20 May '24

Hi Team, I had tried to set the DevStack in the local Linux Ubuntu machine. During that time I had executed the ./stack.sh file. Following issue is generated. How to fix this issue. Collecting fixtures>=3.0.0 (from stestr>=1.0.0->os-testr) Using cached fixtures-3.0.0-py2.py3-none-any.whl.metadata (19 kB) Collecting PyYAML>=3.10.0 (from stestr>=1.0.0->os-testr) Using cached PyYAML-5.4.1.tar.gz (175 kB) Installing build dependencies ... done Getting requirements to build wheel ... error error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> [54 lines of output] running egg_info writing lib3/PyYAML.egg-info/PKG-INFO writing dependency_links to lib3/PyYAML.egg-info/dependency_links.txt writing top-level names to lib3/PyYAML.egg-info/top_level.txt Traceback (most recent call last): File "/opt/stack/data/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module> main() File "/opt/stack/data/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main json_out['return_val'] = hook(**hook_input['kwargs']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/stack/data/venv/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel return hook(config_settings) ^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=['wheel']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires self.run_setup() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 311, in run_setup exec(code, locals()) File "<string>", line 271, in <module> File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/__init__.py", line 104, in setup return distutils.core.setup(**attrs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 184, in setup return run_commands(dist) ^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 200, in run_commands dist.run_commands() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands self.run_command(cmd) File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 967, in run_command super().run_command(command) File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 988, in run_command cmd_obj.run() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 321, in run self.find_sources() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 329, in find_sources mm.run() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 550, in run self.add_defaults() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/egg_info.py", line 588, in add_defaults sdist.add_defaults(self) File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/command/sdist.py", line 102, in add_defaults super().add_defaults() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/command/sdist.py", line 250, in add_defaults self._add_defaults_ext() File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/command/sdist.py", line 335, in _add_defaults_ext self.filelist.extend(build_ext.get_source_files()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<string>", line 201, in get_source_files File "/tmp/pip-build-env-vadud0tf/overlay/lib/python3.12/site-packages/setuptools/_distutils/cmd.py", line 107, in __getattr__ raise AttributeError(attr) AttributeError: cython_sources [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. +inc/python:pip_install:1 exit_trap +./stack.sh:exit_trap:549 local r=1 ++./stack.sh:exit_trap:550 jobs -p +./stack.sh:exit_trap:550 jobs= +./stack.sh:exit_trap:553 [[ -n '' ]] +./stack.sh:exit_trap:559 '[' -f '' ']' +./stack.sh:exit_trap:564 kill_spinner +./stack.sh:kill_spinner:459 '[' '!' -z '' ']' +./stack.sh:exit_trap:566 [[ 1 -ne 0 ]] +./stack.sh:exit_trap:567 echo 'Error on exit' Error on exit +./stack.sh:exit_trap:569 type -p generate-subunit +./stack.sh:exit_trap:572 [[ -z /opt/stack/logs ]] +./stack.sh:exit_trap:575 /opt/stack/data/venv/bin/python3 /home/lohit/OpenSource/openstack/Org/devStack/devstack/tools/worlddump.py -d /opt/stack/logs World dumping... see /opt/stack/logs/worlddump-2024-05-14-161809.txt for details +./stack.sh:exit_trap:584 exit 1

5 7

[magnum] Cancelling meeting 22 May
by Jake Yip 20 May '24

20 May '24

Hi all, I will have to cancel this week's meeting due to work commitments. Regards, Jake

1 0

Heat problem
by Mohamed Ridha ZOUAREG 19 May '24

19 May '24

Hi, I'm trying to run a magnum cluster on Linux:Ubuntu 22.04 Openstack 2023.1 I've installed all the principal services + cinder And I'm facing now a problem with kub master creation after checking heat engine logs I found this one : Resource ResourceGroup "kube_masters" [010ab794-10cc-10cc-4348-b154-06fc729c6357] Stack "test-ix2mxcfq6vy6" [d38b91a2-0fa2-42d9-be3f-d815d18a3de8] is locked or does not exist And also heat.common.exception.ResourceFailure: resources[0]: Stack CREATE cancelled

1 0

Fwd: Problem with magnum cluster creation
by Mohamed Ridha ZOUAREG 19 May '24

19 May '24

Hi, I'm trying to run a magnum cluster on Linux:Ubuntu 22.04 Openstack 2023.1 I've installed all the principal services + cinder And I'm facing now a problem with kub master creation after checking heat engine logs I found this one : Resource ResourceGroup "kube_masters" [010ab794-10cc-10cc-4348-b154-06fc729c6357] Stack "test-ix2mxcfq6vy6" [d38b91a2-0fa2-42d9-be3f-d815d18a3de8] is locked or does not exist And failure resource[0] as you can see in the photos

1 0

[mistral] Reusing “pypi.org/projects/mistral”
by Renat Akhmerov 18 May '24

18 May '24

Hi! I’m Renat who originally created the Mistral Workflow project and I was a PTL for many cycles. I’ve not been in the loop for more than 3 years now so I’m not sure what’s going on in the community now. Neither in OpenStack, nor particularly in Mistral. I heard the rumors though that Mistral upstream life is not longer active. I’d love to hear some feedback on that. The reason I’m asking is that I’ve been asked to let other folks with a big business to reuse the pypi name “mistral”. Seemingly, there’s no many unique active users now, but there are some probably. So before answering to them “no”, I’d like to understand if it’s really impossible (broken OpenStack CI pipelines, other businesses potentially suffering etc etc). Would it make sense also to consider moving “mistral” to something like “mistral-workflow” on pypi? Would appreciate any input. Thanks Renat Akhmerov

4 4

Horizon UI Theme.
by Michael Knox 17 May '24

17 May '24

I am looking to do a custom theme with Horizon. I looked some on github etc, but I am noticing on the login screen a "header" bar and I can't see where it's coming from. Even the default theme has it. It looks like something in the class for "login" or maybe it's the "container", I am not a CSS guy, more suited to crayons. Any pointers would be appreciated. Cheers. Knox.

3 4

[release] Release countdown for week R-19, May 20-24
by Elõd Illés 17 May '24

17 May '24

Development Focus ----------------- We are now past the Dalmatian-1 milestone. Teams should now be focused on feature development. General Information ------------------- Our next milestone in this development cycle will be Dalmatian-2, on July 4th, 2024. This milestone is when we freeze the list of deliverables that will be included in the 2024.2 Dalmatian final release, so if you plan to introduce new deliverables in this release, please propose a change to add an empty deliverable file in the deliverables/dalmatian directory of the openstack/releases repository. Now is also generally a good time to look at bugfixes that were introduced in the master branch that might make sense to be backported and released in a stable release. If you have any question around the OpenStack release process, feel free to ask on this mailing-list or on the #openstack-release channel on IRC. Upcoming Deadlines & Dates -------------------------- Dalmatian-2 Milestone: July 4th, 2024 Előd Illés irc: elodilles @ #openstack-release

1 0

[neutron] bug deputy report for week of 2024-05-13
by Bence Romsics 17 May '24

17 May '24

Hi Team, I'm sending this deputy report on Friday already, because this weekend and the whole next week I'll be away from computers. In the last 5 days the following new bugs were reported. We have 3 unassigned, please have a look! [critical] * https://bugs.launchpad.net/neutron/+bug/2065821 cover job started to fail with Killed unassigned, gate failure [high] * https://bugs.launchpad.net/neutron/+bug/2065701 set_gateway_mtu fails if one of the lrp is deleted while it's running fix and backports are in progress: https://review.opendev.org/q/topic:bug/2065701 * https://bugs.launchpad.net/neutron/+bug/2065707 Trunk plugin fails to push trunk object through OVO rpc endpoint on AFTER_DELETE fix in progress: https://review.opendev.org/c/openstack/neutron/+/919858, https://review.opendev.org/c/openstack/neutron/+/9198589 [medium] * https://bugs.launchpad.net/neutron/+bug/2065743 CLI arguments for rbac create are misleading and possibly incorrect unassigned, fix needed both in neutron and openstackclient [ovn-octavia-provider] * https://bugs.launchpad.net/neutron/+bug/2065566 [ovn-octavia-provider] Return DELETED on member_delete for non-existing members fix in progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/919482 * https://bugs.launchpad.net/neutron/+bug/2065822 [ovn-octavia-provider] functional job fails with "oslo_db.exception.DBReferenceError: (sqlite3.IntegrityError) FOREIGN KEY constraint failed when inserting port bindings unassigned, low frequency gate failure [taas] * https://bugs.launchpad.net/tap-as-a-service/+bug/2065924 [OSP][TaaS][sqlalchemy] sqlalchemy updated to 2.0 breaks TaaS fix in progress: https://review.opendev.org/c/openstack/tap-as-a-service/+/919934 [needs further analysis] * https://bugs.launchpad.net/neutron/+bug/2065577 [ml2/ovs]Empty binding_levels=[] cause ovs-agent skipped to process port Cheers, Bence

1 0

[publiccloud-sig] Summary Foundation Forum @ OpenInfra Day Berlin 2024
by Felix Kronlage-Dammers 17 May '24

17 May '24

Hi, this Wednesday the OpenInfra Day Berlin 2024 happened. Thanks to the various people (such as Nils Magnus, Kurt Garloff, Robert Holling and Friederike Zelke) who were involved in organizing this event. As part of the OpenInfra Day there was a Forum-style session on Interoperability between clouds. The session was initiated by Josephine Seifert, Artem Goncharov, Tobias Rydberg, Adrien Cunin and myself. The etherpad is here: https://etherpad.opendev.org/p/Interop-Forum The intro slides to the session are here: https://input.scs.community/p/KWywBKwBW#/ The 45 minutes we had quickly passed in the discussion - it (once again) did show that this is a topic that does need to be dealt with and it is not enough to just do it every now and then (doh!) - these topics will be picked up as part of the Public-Cloud SIG. However, the Public-Cloud SIG needs more people joining (which was another part of the idea of this session: make advertisement for our work in the Public-Cloud SIG and get more people to join). Tobias and I will see that we will schedule some Public-Cloud SIG calls that are timezone-friendly for the US-/Canada people as well. The next regular call of the Public-Cloud SIG will be on May 29th at 0700 UTC (but a reminder will be sent out couple days in advance). felix

1 0

[nova] May 22th meeting is CANCELLED
by Sylvain Bauza 17 May '24

17 May '24

As said above, the weekly nova meeting on May 22 2024 is CANCELLED. You can join us in #openstack-nova if you have some questions. Thanks, -Sylvain

1 0

[ptl][tc] OpenStack packages PyPi additional external maintainers audit & cleanup
by Ghanshyam Mann 16 May '24

16 May '24

Hi PTLs, As you might know or have seen for your project package on PyPi, OpenStack deliverables on PyPi have additional maintainers, For example, https://pypi.org/project/murano/, https://pypi.org/project/glance/ We should keep only 'openstackci' as a maintainer in PyPi so that releases of OpenStack deliverables can be managed in a single place. Otherwise, we might face the two sets of maintainers' places and packages might get released in PyPi by additional maintainers without the OpenStack project team knowing about it. One such case is in Horizon repo 'xstatic-font-awesome' where a new maintainer is added by an existing additional maintainer and this package was released without the Horizon team knowing about the changes and release. - https://github.com/openstack/xstatic-font-awesome/pull/2 To avoid the 'xstatic-font-awesome' case for other packages, TC discussed it in their weekly meetings[1] and agreed to audit all the OpenStack packages and then clean up the additional maintainers in PyPi (keep only 'openstackci' as maintainers). To help in this task, TC requests project PTL to perform the audit for their project's repo and add comments in the below etherpad. - https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup Thanks to knikolla to automate the listing of the OpenStack packages with additional maintainers in PyPi which you can find the result in output.txt at the bottom of this link. I have added the project list of who needs to check their repo in etherpad. - https://gist.github.com/knikolla/7303a65a5ddaa2be553fc6e54619a7a1 Please complete the audit for your project before March 15 so that TC can discuss the next step in vPTG. [1] https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-11-16.00.log.html#… -gmann

18 27

openstack / sahara Project
by Moein Engineer 15 May '24

15 May '24

Hello Greetings We have decided to use platform openstack / sahara to set up a big data cluster in our company. Has the support and development of project openstack / sahara ended? I checked the last commit is for the last 6 months and for version 19. If project openstack / sahara is not developed and ends, what project has replaced it? Regards

2 1

openstack / sahara
by Moein 15 May '24

15 May '24

1 0

Logscraper host and OpenSearch service upgrade
by Daniel Pawlik 15 May '24

15 May '24

Hello, We would like to notify you that the OpenSearch service [1] would be updated to a newer version on 2024-05-15 at 01:00 PM UTC. This procedure might take a while, depending of the cluster size. During that time, the OpenSearch service would not be available. If anyone has any doubts, please reply to the email. Dan [1] - https://opensearch.logs.openstack.org/_dashboards/app/home

1 1

[kolla-ansible] support for FWaaS/LBaaS?
by garcetto 15 May '24

15 May '24

good morning, does kolla support fwaas or lbaas? thank you

3 4

Antelope compute: failure to live migrate VMs from Yoga compute
by Michel Jouvin 15 May '24

15 May '24

Hi, In a Yoga cloud, I upgraded all the core services and 1 compute to Antelope (directly from Yoga, using a SLURP upgrade). This cloud has 4 compute servers, all using the same HW (Dell FX2/FC630 with Broadwell CPUs). After the upgrade, any attempt to live migrate a VM from a Yoga compute to the Antelope compute fails with the following error in destination/Antelope nova-compute.log: nova.exception.MigrationPreCheckError: Migration pre-check error: Unacceptable CPU info: CPU doesn't have compatibility. This looks weird. I don't see anything in the release notes related to this problem, except a mention that the API used to do the comparison has changed ("This change replaces the usage of older API, compareCPU(), with the new one, compareHypervisorCPU()."). "virsh capabilities" reports the same thing for a Yoga and an Antelope compute, except the addition of a feature 'flush-l1d' in Antelope and the addition of 2 new attributes in the '<cpu>' section: <signature family='6' model='79' stepping='1'/> <maxphysaddr mode='emulate' bits='46'/> I tend to think that additions are not a problem in general and so it doesn't seem to explain the problem I'm facing. Anybody with a similar experience? It seems to me a different problem that the one that has been faced in the past (before Nova 20 if I'm right) and described in several posts, with CPU model improperly detected (in particular Broadwell vs. Icelake). Thanks in advance for any hint/suggestion. Best regards, Michel

3 4

[largescale-sig] Next meeting: May 15, 9utc
by Thierry Carrez 15 May '24

15 May '24

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 9UTC. You can doublecheck how that UTC time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240515T09 Feel free to add topics to the agenda: https://etherpad.opendev.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

2 2

launch vm and its LVM cinder volumes on same host
by Morteza FarkhondePour 15 May '24

15 May '24

0 <https://serverfault.com/posts/1159435/timeline> I have an OpenStack *Antelope* version installed via Kolla-Ansible, and I have several compute hosts with LVM volume types. When I create an instance using an LVM volume, I expect both the volume and the instance create on the same host. However, they end up on different hosts. For example, the volume is located on d13-compute43@localA#localA, whereas the instance is on d13-compute51

1 0

[kolla] Weekly meeting today (15th May 2024) cancelled
by Michał Nasiadka 14 May '24

14 May '24

Hello Koalas, Weekly meeting today is cancelled due to key participants (including me) not being able to attend. Let’s meet next week (22nd May 2024) - see you then! Michal

1 0

OpenInfra Summit Asia'24 CFP closing in two weeks
by Jeremy Stanley 14 May '24

14 May '24

The OpenInfra Summit Asia'24 is the first community-led Summit[0], hosted by the OpenInfra Korea User Group in collaboration with other OpenInfra user groups throughout Asia. The CFP is currently open and accepting applications until May 29, 2024, so there's only two weeks left to get your proposals submitted[1]. Keep in mind that Summit talks are often professionally recorded and re-watched by a much larger global audience, having a broad impact for years after the event concludes, so your reach can be far greater than just the people who happen to be in the room at that moment. This time, the Summit will be co-located with the OCP (opencompute.org) Regional Summit APAC and will showcase the latest advancements in open source infrastructure software and hardware. If you want to present but are struggling to to come up with ideas, "beginner" content is always a crowd pleaser (setting up your first environment, tips for new contributors), but this could also be of particular interest for the growing local community in Korea. Since this event is occurring alongside one for the Open Compute Project, hardware-related topics might serve to draw in participants from their community and help grow our own through the sort of collaboration we're best known for. Upgrade stories and talks about reducing complexity are also something our users are especially keen to hear about. For that matter, talks about Networking (including 5G telephony) or integration with adjacent community tech (Ceph, Kubernetes, OVN) would be great to show how OpenStack is really an integral piece of the larger open source ecosystem. If you want to attend and your employer cannot fund your travel, the OpenInfra Foundation is continuing the OpenInfra Travel Support program. You can apply for travel support[1] until May 29. If you have any questions or want help (even if it's just to bounce ideas off me for a talk you're thinking about proposing), feel free to reply or find me (fungi) in the #openstack channel on the OFTC IRC network. [0] Register for the OpenInfra Summit Asia: https://2024.openinfraasia.org/ [1] Submit to the CFP: https://openinfrafoundation.formstack.com/forms/openinfra_asia_summit_2024 [2] Apply for the OpenInfra Travel Support Program: https://openinfrafoundation.formstack.com/forms/openinfra_tsp -- Jeremy Stanley

1 0

Boot an uefi volume that migrated from VMware ESXI
by luckydog xf 14 May '24

14 May '24

Hi, list, I migrated a volume from VMware ESXI VMDK, and originally on VMware platform it's EFI boot mode and secure boot enabled. I cloned the entire VMDK by clonzilla and restored on OpenStack as a volume. I referred to this link https://docs.openstack.org/nova/latest/admin/secure-boot.html and uploaded that volume as an image. Then set properties. Finally, I launched an instance with a target image, however, it cannot boot up with a blank and dark screen. What's the right way to implement this? Thanks.

2 11

[nova] Our first spec review day for Dalmatian
by Sylvain Bauza 14 May '24

14 May '24

Hey folks, As agreed during the PTG, we'll have two spec review days this cycle. Next Tuesday, ie. May 14 2024, we'll have the first one. Please make sure you can upload your spec before this and please be around on IRC on Tuesday (if you can) so we could discuss your spec change if we need. Thanks, -Sylvain

1 1

[openstack][kolla-ansible][keystone]upgrade from yoga to zed error keystone database
by Nguyễn Hữu Khôi 13 May '24

13 May '24

Hello. I upgraded from yoga to zed but i encounter this error as a keystone log. https://www.editpad.org/?edit-id=CNujHK962K70e93ae8 I tried to remove this table but this error still appears with other tables. My env: ubuntu22.04 openstack with kolla ansible as the deployment tool Thank you. Regards Nguyen Huu Khoi

2 4

[neutron] Bug deputy report for week of May 6th
by Miguel Lavalle 13 May '24

13 May '24

Hi, I was the Neutron bugs deputy last week. Following is a brief summary of the reported bugs: Critical bugs ----------------- None High bugs -------------- https://bugs.launchpad.net/neutron/+bug/2065094 OVN revision number is bumped on noop port update. Assignee Jakub Libosvar. Released fix: https://review.opendev.org/c/openstack/neutron/+/918492 https://bugs.launchpad.net/neutron/+bug/2065459 ovn-octvia-provider: RuntimeError: cannot join current thread. In progress. Assignee Terry Wilson. Proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/919229 https://bugs.launchpad.net/neutron/+bug/2065460 ovn-octavia-provider results in a new OVSDB connection for every Octavia API request. In progress. Assignee Terry Wilson. Proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/919229 https://bugs.launchpad.net/neutron/+bug/2065566 [ovn-octavia-provider] Return DELETED on member_delete for non-existing members. In progress. Assignee Fernando Royo/ Proposed fix: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/919482 Medium bugs ------------------ * https://bugs.launchpad.net/neutron/+bug/2065145 AttributeError: 'MetadataDriver' object has no attribute 'monitors' in L3 agent logs, Assignee Brian Haley. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/918674 Low bugs ------------- None Wishlist bugs ------------------ https://bugs.launchpad.net/neutron/+bug/2065198. Allow ml2 MechanismDrivers to start own rpc listeners. Gathering more input from submitter at the moment

1 0

Nova filters
by Gk Gk 13 May '24

13 May '24

Hi, In the Antelope version nova scheduler, is there an option for filtering hypervisors based on available disk space ? I cant find the option "DiskFilter' in the latest documentation for antelope. How to achieve this ? Thanks G.K

2 4

[DNS] RFH: Something is answering DNS PTR queries with UDP and not EDNS
by Philipp Hahn 13 May '24

13 May '24

Hello, I'm new to this list and relatively new to OpenStack, so please be patient with me. Our infrastructure provider is hosting OpenStack for us and I observed the following irritating behavior: If my Linux VM does a reverse-IP-lookup (PTR) something™ seems to intercept those PTR queries on their way from the VM to the *configured* DNS server and answers them itself, returning the name of the VM inside some pre-configured domain: > # dig +nocmd +nocomments +nostats +noedns -x 10.201.0.211 > ;211.0.201.10.in-addr.arpa. IN PTR > 211.0.201.10.in-addr.arpa. 3600 IN PTR jenkins-ucs-5-0-ucs-5-0-7-autotestjoinopenstack-sambaversion-no.a.customers.regiocloud.tech. > > # getent hosts 10.201.0.211 > 10.201.0.211 jenkins-ucs-5-0-ucs-5-0-7-autotestjoinopenstack-sambaversion-no.a.customers.regiocloud.tech > > # python3 -c 'import DNS;req=DNS.DnsRequest("211.0.201.10.in-addr.arpa.",qtype="PTR",server=["10.201.0.211"], protocol="udp");res=req.req();print(res.answers[0]["data"])' > jenkins-ucs-5-0-ucs-5-0-7-autotestjoinopenstack-sambaversion-no.a.customers.regiocloud.tech > > # python3 -c 'import dns.resolver;r=dns.resolver.Resolver(configure=False);r.nameservers=["10.201.0.211"];r.edns=False;a=r.query("211.0.201.10.in-addr.arpa.","PTR",tcp=False);print(list(a))' > [<DNS IN PTR rdata: jenkins-ucs-5-0-ucs-5-0-7-autotestjoinopenstack-sambaversion-no.a.customers.regiocloud.tech.>] This only happens when UDP is used an EDNS is disabled: As soon as I use TCP or force EDNS my queries arrives at the configured DNS server and I get back the expected answer: > # dig +nocmd +nocomments +nostats +edns -x 10.201.0.211 > ;211.0.201.10.in-addr.arpa. IN PTR > 211.0.201.10.in-addr.arpa. 172800 IN PTR master096.autotest096.test. > 201.10.in-addr.arpa. 10800 IN NS master096.autotest096.test. > master096.autotest096.test. 80600 IN A 10.201.0.211 > > # dig +nocmd +nocomments +nostats +edns +tcp -p 53 -x 10.201.0.211 > ;211.0.201.10.in-addr.arpa. IN PTR > 211.0.201.10.in-addr.arpa. 172800 IN PTR master096.autotest096.test. > 201.10.in-addr.arpa. 10800 IN NS master096.autotest096.test. > master096.autotest096.test. 80600 IN A 10.201.0.211 > > # dig +nocmd +nocomments +nostats +noedns +tcp -p 53 -x 10.201.0.211 > ;211.0.201.10.in-addr.arpa. IN PTR > 211.0.201.10.in-addr.arpa. 172800 IN PTR master096.autotest096.test. > 201.10.in-addr.arpa. 10800 IN NS master096.autotest096.test. > master096.autotest096.test. 80600 IN A 10.201.0.211 > > # python3 -c 'import DNS;req=DNS.DnsRequest("211.0.201.10.in-addr.arpa.",qtype="PTR",server=["10.201.0.211"], protocol="tcp");res=req.req();print(res.answers[0]["data"])' > master096.autotest096.test > > # python3 -c 'import dns.resolver;r=dns.resolver.Resolver(configure=False);r.nameservers=["10.201.0.211"];r.edns=False;a=r.query("211.0.201.10.in-addr.arpa.","PTR",tcp=True);print(list(a))' > [<DNS IN PTR rdata: master096.autotest096.test.>] > > # python3 -c 'import dns.resolver;r=dns.resolver.Resolver(configure=False);r.nameservers=["10.201.0.211"];r.edns=True;a=r.query("211.0.201.10.in-addr.arpa.","PTR",tcp=True);print(list(a))' > [<DNS IN PTR rdata: master096.autotest096.test.>] > > # python3 -c 'import dns.resolver;r=dns.resolver.Resolver(configure=False);r.nameservers=["10.201.0.211"];r.edns=True;a=r.query("211.0.201.10.in-addr.arpa.","PTR",tcp=False);print(list(a))' > [<DNS IN PTR rdata: master096.autotest096.test.>] I already talked to out provider and spend multiple hours searching the internet or even having a look at the source code of Neutron myself, but did not find any clue so far. Can someone please enlighten me and tell me, how I (or our provider) can disable that "UDP DNS intercept behavior" as that breaks our current use-case, especially as I seldomly can configure our applications to (not) use UDP / EDNS, so depending on which resolver library they use they get different answers to the same query. Thank you in advance. Philipp Hahn -- Philipp Hahn Open Source Software Engineer Univention GmbH Mary-Somerville-Str. 1 28359 Bremen Germany | Deutschland Phone: +49 (0)421 22232-0 | E-Mail: info(a)univention.de https://www.univention.de | https://www.univention.com Managing Directors: Peter H. Ganten, Stefan Gohmann Local court: Amtsgericht Bremen HRB 20755 | Ust-ID: DE220051310 If you are not the intended recipient of this mail, please contact the sender and delete this message. Any unauthorized copying of this message or unauthorized distribution of the information contained herein is prohibited.Information on the processing of your personal data can be found here: https://www.univention.com/privacy-statement

2 1

Re: CAD applications on OpenStack
by Francesco Di Nucci 13 May '24

13 May '24

You're welcome have you also thought about having a chat with CAD vendor's team? Maybe they encountered it as a problem, as it's more about the CAD and less about having Windows VMs on OpenStack By the way, when a conversation is in a list, reply to all to include the list ;) Best regards Francesco Di Nucci On 13/05/24 12:20, Arne Wiebalck wrote: > Thanks, Francesco! > > Licenses are a concern and we're looking at that. > > What we're not really clear on if this approach works latency- / concurrency wise. > We will probably simply try :) > > Thanks again! > Arne > > -- > Dr. Arne Wiebalck > Group Leader, Compute and Devices Group > CERN IT > > ________________________________________ > From: Francesco Di Nucci <francesco.dinucci(a)na.infn.it> > Sent: Thursday, 9 May 2024 08:12 > To: Arne Wiebalck > Subject: Re: CAD applications on OpenStack > > Hi, > > former CAD user here - first of all I'd advice to clear with your legal > department if your license allows you to use the CAD in VMs. > > AFAIK CATIA runs on Windows, so containerization is not possible unless > you manage to get the CAD running in Wine, and you should configure PCI > passthrough > > (https://docs.openstack.org/nova/2024.1/admin/pci-passthrough.html) to > use a graphic card in the VMs. > > Regards > > Francesco Di Nucci > > On 05/05/24 12:04, Arne Wiebalck wrote: >> Dear all, >> >> We're looking into integrating the use case of CAD applications, such as CATIA V5/6 or CATIA 3DEXPERIENCE, into our OpenStack deployment, with the goals of increased resource sharing >> and to reduce the park of individual workstations we have for this at the moment. >> >> If anyone has experience running such applications on top of OpenStack (on individual VMs >> with GPU access, on bare metal servers with concurrent sessions, maybe even containerised ...) >> and would like to share what they have done, it'd be great if you got in touch with me. >> >> Thanks! >> Arne >> >> -- >> Arne Wiebalck >> CERN IT >> >> > >

1 0

Re: Nova filters
by Gk Gk 13 May '24

13 May '24

Hi, In the Antelope version nova scheduler, is there an option for filtering hypervisors based on available disk space ? I cant find the option "DiskFilter' in the latest documentation for antelope. How to achieve this ? Thanks G.K

1 0

Rabbit mq connections keep on going up, why channels and connections not closing?
by Shrey Chauhan 13 May '24

13 May '24

Hi all, I am observing a behaviour which I am not sure is right or wrong, or something I should be concerned about? Currently I am using openstack xena with rabbit-mq message broker. rabbit mq version is 3.8.3 amqp version 5.0.8 I have installed rabbit management plugin on my cluster, and I observe whenever I perform any task like a resize. My connection and channel counts go up, and with every operation it goes up. I am worried that at some point I will hit some kind of connection threshold. I just want to understand if services like nova, cinder reuse an open rabbit mq connection or reopen for every operation, and if they open msg queue connection for every operation do they close the connection once the action is done Am I missing configuration in my setup of rabbit mq with openstack? Please help me understand this scenario. Thanks for help in advance. Thanks, Shrey Chauhan

1 0

[ops] Inquiry Regarding Addition of DH Groups in OpenStack VPNaaS
by Shubham Yadav 13 May '24

13 May '24

Hello , I hope this message finds you well. I am reaching out to inquire about the possibility of adding additional DH (Diffie-Hellman) groups to the VPNaaS (VPN as a Service) project in OpenStack. Currently, our setup involves using DH groups 14, 16, 20, and 21 on Fortigate routers. However, the available DH groups at the OpenStack Web UI for creating IPSEC policies are limited to groups 2, 5, and 14. Could you please provide insights into whether there are plans to introduce more DH groups into the VPNaaS project? This addition would greatly benefit our configurations and improve compatibility with our existing infrastructure. Thank you in advance for any information or guidance you can provide on this matter. Best regards, Shubham

2 1

[oslo][release] Changing back release model of tooz ?
by Takashi Kajinami 13 May '24

13 May '24

Hello, As you may know, tooz was moved to the independent release model[1] after wallaby release because of its stable code base at that time. However, we introduced several features/improvements in tooz during a few cycles and I'm wondering if we can revisit its status now. One actual problem I'm seeing now is that, we recently got a bug report[2] about the redis sentinel support which we added during 2024.1 cycle but we can't backport the required bug fix to 2024.1 because of no stable branch. Given the situation, I'm wondering if it makes sense (and is possible) to move tooz back to the cycle-with-intermediary model, and create 2024.1 branch from 6.1.0 (the last release during 2024.1 cycle) now, so that we can maintain 2024.1 releases with future bug fixes brackported. [1] https://review.opendev.org/c/openstack/releases/+/788230 [2] https://bugs.launchpad.net/python-tooz/+bug/2063857 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

4 5

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2024.2/R-20)
by Goutham Pacha Ravi 12 May '24

12 May '24

Hello Stackers, We're officially in milestone-1 week for the 2024.2 (Dalmatian) release cycle [1]. Teams are actively planning design specification freezes, hackathons, and bug squashes. I'm delighted to announce that three Outreachy interns have been funded to work with the OpenStack community [2]. Please join me in welcoming Mohd Ariq (tspyderboy), Okeke Christian Chima (cokeke), and Abby Nduta (AbbyNduta). Mohd Ariq and Christian will be working with members of the OpenStack Manila project team, while Abby will be working with members of the OpenStack Horizon project team. Congratulations, interns! These internships begins at the end of May and will conclude at the end of August. There have been a few governance changes in the past week that I'd like to brief you about: The "Consistent and Secure Default RBAC" goal has new milestone requirements. All projects are expected to transition oslo.policy's "enforce_scope" and "enforce_new_defaults" options to True during the 2024.2 release cycle. These options will be removed from oslo.policy during the 2025.1 release cycle. [3] openstack/kuryr and openstack/kuryr-libnetwork are now under the maintainership of the openstack/zun ("Container as a service") team. The TC has adopted a house rule to mark projects that have identified no leadership as "inactive" projects [4]. We've merged slaweq's summary of the 2023 OpenStack User Survey [5]. Thanks, slaweq, and to all of you who took the survey. === Weekly Meeting === Last week's TC meeting was held simultaneously on Zoom (a recording is on YouTube [6]) and IRC on May 7th, 2024. The meeting was logged to eavesdrop [7]. Over the years, we've come to realize that monitoring project activity through objective tools wasn't representing the picture accurately. Several mature/feature-complete projects will seemingly be "inactive," and what we're interested in assessing is whether there are active maintainers tackling security and project infrastructure concerns. Artem Goncharov (gtema) will write up a proposal to tag inactive projects more prominently. We discussed a proposal to change the Distributed Project Leadership model to require DPL liaisons to re-assert their interest at the beginning of each cycle. The proposal also suggests appointing liaisons from the TC to monitor projects that have this leadership model. TC Members would be welcome to nominate themselves as liaisons for projects following DPL if this proposal is accepted. We took some AIs to continue the cleanup of maintainers on OpenStack's packages on PyPI - an ongoing community-wide effort [8]. We discussed the open goal proposal to replace eventlet. The Technical Committee wants to ensure that we're not advocating for a one-size-fits-all solution to the problem of threading in OpenStack projects. Hence, we'd prefer not to merge the proposal to replace eventlet with asyncio. Instead, we want to encourage projects to independently explore solutions that make sense to their individual architecture - which could be asyncio, native threads, or any other threading paradigm/library. We are supportive of ensuring there's no imposition of any specific library or threading mechanism imposed via oslo libraries. JayF will be summarizing this view to this mailing list soon. The meeting concluded with an open discussion on DevStack setup time and an outdated (but relevant) proposal related to OSC as a service on DevStack. Tomorrow's meeting is back on OFTC/IRC, and the call details and agenda are at [9]. We look forward to seeing you there. The TC is always honored to chat with you, so please join us, and feel free to add anything to the agenda that you'd like to chat with us about! === Goal Proposals === As stated above, this goal proposal needs your weigh-in: - Migrate eventlet usages to asyncio (https://review.opendev.org/c/openstack/governance/+/902585) === Governance Proposals === ==== Merged ==== - Remove ref of bylaw Appendix 4 | https://review.opendev.org/c/openstack/governance/+/916942 - Add timeline to remove enforce_scope in RBAC goal | https://review.opendev.org/c/openstack/governance/+/915179 - Move openstack/kuryr and openstack/kuryr-libnetwork to Zun | https://review.opendev.org/c/openstack/governance/+/917517 - 2023 User Survey TC Question Analysis | https://review.opendev.org/c/openstack/governance/+/900516 - Add option to move leaderless project to Inactive status | https://review.opendev.org/c/openstack/governance/+/914726 ==== Open for review/discussion ==== - Update to include docs and miscellaneuos repos for AC status | https://review.opendev.org/c/openstack/governance/+/915021 - Add DPL model & liaison reset policy | https://review.opendev.org/c/openstack/governance/+/916833 Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://www.outreachy.org/alums/2024-05/#:~:text=Openstack [3] https://governance.openstack.org/tc/goals/selected/consistent-and-secure-rb… [4] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [5] https://governance.openstack.org/tc/user_survey/analysis-2023.html [6] https://youtu.be/-WZT7PC3sig [7] https://meetings.opendev.org/meetings/tc/2024/tc.2024-05-07-18.00.log.html [8] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [9] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

openstack boot an instance from an IDE volume migrated from VMware
by luckydog xf 10 May '24

10 May '24

hi, list, I'm going to boot an instance from an existing volume, and it is a Windows 2016 migrated from VMware. So the bus must be set to 'ide' mode, otherwise it fails to boot up. Let's assume this volume UUID is xyz and it's bootable. I cloned it by clonezilla from VMware ESXI. since virtio drive wasn't installed in Windows, so it must be set to ide. So what's the right way to boot it from this volume and set it to IDE? I have tried lots of ways, like --- openstack server create test-windows --flavor 4 --nic net-id=7b57ee99-136f-4aa7-b3fe-a4958ec8c644 --block-device id=xxxx:disk_bus=ide and ... --block-device-mapping. But unfortunately, none of them work. And there are too many outdated docs like disk_bus=ide and bus=ide. Not sure which one works. This is fairly frustrating. I'm still struggling with this issue and need your help. Thanks a lot.

3 7

[tc][all][ec2-api] Retiring the ec2-api project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the ec2-api project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the ec2-api retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[tc][all][senlin] Retiring the Senlin project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the Senlin project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Senlin retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[tc][all][solum] Retiring the Solum project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the Solum project is not active and was marked 'inactive' since 2024.1 cycle[1]. In this cycle also, this project is leaderless[2] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[2], the next step is to retire the project. I'm sending this email to propose the Solum retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[tc][all][murano] Retiring the Murano project
by Ghanshyam Mann 10 May '24

10 May '24

Hello everyone, As you might know, the Murano project is not active and was marked 'inactive' since 2024.1 cycle[1]. Due to a critical bug in Murano, the TC needs to pass a resolution to stop its 2024.1 release[2]. In this cycle also, this project is leaderless[3] and no maintainer stepped up to maintain it. As discussed in the Leaderless project etherpad[3], the next step is to retire the project. I'm sending this email to propose the Murano retirement and based on the response, I will proceed next. [1] https://governance.openstack.org/tc/reference/emerging-technology-and-inact… [2] https://governance.openstack.org/tc/resolutions/20240227-remove-murano-from… [3] https://etherpad.opendev.org/p/2024.2-leaderless#L72 -gmann

1 1

[magnum][magnum-cluster-api] Scalling Master Node
by pahrialtkj＠gmail.com 10 May '24

10 May '24

Hello all, I created a k8s cluster with 1 master and 1 worker node, I want to increase the master node to 2 or 3, I tried to do it with cluster resize/update and nodegroup create seems to be not supported and does not work, it works for the worker node, has anyone tried scaling the master node?

3 3

Re: How to check the free RAM or CPU or Disk in openstack python module
by Lajos Katona 10 May '24

10 May '24

Hi, No I meant something like this: $ openstack resource provider list +--------------------------------------+-------+------------+--------------------------------------+----------------------+ | uuid | name | generation | root_provider_uuid | parent_provider_uuid | +--------------------------------------+-------+------------+--------------------------------------+----------------------+ | 0f916a23-403f-43c3-ac57-e109bc371dba | jammy | 2 | 0f916a23-403f-43c3-ac57-e109bc371dba | None | +--------------------------------------+-------+------------+--------------------------------------+----------------------+ $ openstack resource provider inventory list 0f916a23-403f-43c3-ac57-e109bc371dba +----------------+------------------+----------+----------+----------+-----------+-------+------+ | resource_class | allocation_ratio | min_unit | max_unit | reserved | step_size | total | used | +----------------+------------------+----------+----------+----------+-----------+-------+------+ | VCPU | 4.0 | 1 | 6 | 0 | 1 | 6 | 0 | | MEMORY_MB | 1.0 | 1 | 7936 | 512 | 1 | 7936 | 0 | | DISK_GB | 1.0 | 1 | 28 | 0 | 1 | 28 | 0 | +----------------+------------------+----------+----------+----------+-----------+-------+------+ $ openstack resource provider inventory list 0f916a23-403f-43c3-ac57-e109bc371dba +----------------+------------------+----------+----------+----------+-----------+-------+------+ | resource_class | allocation_ratio | min_unit | max_unit | reserved | step_size | total | used | +----------------+------------------+----------+----------+----------+-----------+-------+------+ | VCPU | 4.0 | 1 | 6 | 0 | 1 | 6 | 1 | | MEMORY_MB | 1.0 | 1 | 7936 | 512 | 1 | 7936 | 256 | | DISK_GB | 1.0 | 1 | 28 | 0 | 1 | 28 | 1 | +----------------+------------------+----------+----------+----------+-----------+-------+------+ Recently this API was also added to Horizon (the web gui for Openstack) as hypervisor API and the compute db behind it is not preferred. Best wishes Lajos Katona (lajoskatona) Saeed <s.fazl73(a)gmail.com> ezt írta (időpont: 2024. máj. 10., P, 13:12): > Hello, > > Thanks a lot, but I didn't find the proper way for this. > > In CLI, I run *openstack hypervisor show hypervisor.domain.com > <http://hypervisor.domain.com>*, it then shows all the needed information > and data. > I run *openstack service list*, I see this: > > > +----------------------------------+------------------+-------------------------+ > | ID | Name | Type > | > > +----------------------------------+------------------+-------------------------+ > | 0a289a58588d4d00ac27ef92da8128de | keystone | identity > | > | 2cdf38eca0c0467fa856f1f1d91f8de3 | heat | orchestration > | > | 44393da92532478abd2dc1bdba1454ce | nova_legacy | compute_legacy > | > | 4cee55fd6c524134b010c65a7d406857 | ironic | baremetal > | > | 4f47c9bd69a34b5a9e0ef149823b7785 | neutron | network > | > | 59053bba36ed4944aaac7e8eb0f9ac01 | freezer | backup > | > | 670cb0faa6c64f8f82f0d19315e085a5 | trove | database > | > | 828ba6c2709349d597e469bf7fa55766 | glance | image > | > | 8c2671e5ddde47e4ae1accd2ce2eb696 | placement | placement > | > | 8c6357e12abb40e5a46b10be5f950c79 | heat-cfn | cloudformation > | > | c211ea65a3d440d1bb2add6f74423056 | watcher | infra-optim > | > | ceba54fa82f543579b245569b9fc127e | masakari | instance-ha > | > | d5c2952cc6904a0385cb20e5d39d1afe | nova | compute > | > | e238634b10db492a942e27714ee9d9b1 | gnocchi | metric > | > | f545381f4aa649a39122a258f48833fc | ironic-inspector | > baremetal-introspection | > > +----------------------------------+------------------+-------------------------+ > > If I do understand your reply correctly, you mean I should run a single > command for each server to find its free memory or CPU? For example if I > have 100 servers, I should run 100 times a command with different server > names? > > On Fri, 10 May 2024 at 10:33, Lajos Katona <katonalala(a)gmail.com> wrote: > >> Hi, >> Instead of Compute API, Placement is used for such statistics, see the >> API reference: >> https://docs.openstack.org/api-ref/placement/ >> >> You have to follow the resource providers on your compute, and resource >> providers can be in a tree with a root provider. >> For the available resources (resource classes) you have to list the >> resource provider inventories, and for >> the used resource you have to follow the allocations. >> Check the API ref and see the possibilities with CLI first perhaps. Be >> careful Placement API is microversioned like Compute API. >> >> From python SDK you can find the relevant methods here: >> >> https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/plac… >> >> Best wishes >> Lajos Katona (lajoskatona) >> >> Saeed <s.fazl73(a)gmail.com> ezt írta (időpont: 2024. máj. 9., Cs, 19:06): >> >>> Hello, >>> >>> This is my python code: >>> >>>> import openstack >>> >>> openstack.enable_logging(debug=False) >>> >>> hypervisors = [] >>> >>> conn = openstack.connect(cloud='region1') >>> >>> for hypervisor in conn.compute.hypervisors(details=True): >>> >>> hypervisors.append(hypervisor.to_dict()) >>> >>> >>> I also run this: >>> >>>> for hypervisor in hypervisors: >>> >>> print(hypervisor) >>> >>> >>> This is the last result (other results are similar this): >>> >>>> {'cpu_info': None, 'host_ip': '1.1.1.1', 'hypervisor_type': 'QEMU', >>>> 'hypervisor_version': 6002000, 'name': 'some.fqdn.com', >>>> 'service_details': {'id': 'some-random-id', 'host': 'some.fqdn.com', >>>> 'disabled_reason': 'test'}, 'servers': None, 'state': 'up', 'status': >>>> 'disabled', 'uptime': ' 00:27:11 up 31 days, 10:14, 2 users, load >>>> average: 3.52, 3.20, 3.36\n', 'current_workload': None, 'disk_available': >>>> None, 'local_disk_used': None, 'local_disk_size': None, 'local_disk_free': >>>> None, 'memory_used': None, 'memory_size': None, 'memory_free': None, >>>> 'running_vms': None, 'vcpus_used': None, 'vcpus': None, 'id': >>>> 'some-random-id', 'location': Munch({'cloud': 'region1', 'region_name': >>>> 'Region1', 'zone': None, 'project': Munch({'id': 'somerandomid', 'name': >>>> None, 'domain_id': None, 'domain_name': None})})} >>> >>> >>> As you see, values like *cpu_info*, *disk_available*, *local_disk_used* >>> , *local_disk_size*, *local_disk_free*, *memory_used*, etc are *None*. >>> >>> How can I have the following values? In the Openstack UI I see it says >>> the free available disk, memory and CPU, but I don't know how to have them >>> in python. >>> >>> I see here >>> <https://docs.openstack.org/openstacksdk/latest/user/resources/compute/v2/hy…> >>> the above values, but for me all are None. >>> >>> Regards, >>> Saeed >>> >>

3 2

[manila][cinder][glance][nova][devstack][qa] Add ashrod98 to devstack-plugin-ceph core
by Goutham Pacha Ravi 10 May '24

10 May '24

Dear Stackers, I'd like to nominate Ashley Rodriguez to join the devstack-plugin-ceph core team. She has made significant contributions to Ceph integration and testing, especially with the Manila project. Ashley's work includes CI fixes and improvements to the cephadm installer, enabling multi-node installations and integrating ceph's new ingress service in our test jobs. She has also tackled tech debt in Manila's Ceph testing. If there are no objections, I'll add Ashley to the gerrit group next week. Ashley, your hard work is truly appreciated! Best regards, Goutham

4 4

[horizon] Next two weekly meetings cancellation
by Tatiana Ovchinnikova 10 May '24

10 May '24

Hello team, I'm on holiday for the next two weeks, so I'm cancelling weekly meetings on May 15 and 22. See you on May 29. Regards, Tatiana

1 0

[neutron] Drivers meeting canceled next Friday, May 17th
by Brian Haley 10 May '24

10 May '24

Hello Neutrinos: I'm going to preemptively cancel next Friday's drivers meeting as I will be traveling all week. I will be available intermittently on irc, so please send me an email if you need a quicker answer or if I don't respond to pings. -Brian

1 0

[kolla-ansible][Antelope][Heat] Issues with ASG and Zaqar Trigger
by Devin Patterson 10 May '24

10 May '24

Hello, We are implementing the auto-healing workflow captured here - https://github.com/openstack/heat-templates/tree/master/hot/autohealing We are deploying a Heat auto-scaling group that scales a template that contains the needed services and the Nova resource. The template contains a Zaqar queue, Mistral trigger and Mistral workflow. We are also using a scaling policy to scale up and down the template resources. This is working fine, but we are experiencing an issue with scaling up the auto-scaling group via 'openstack stack resource signal <stack> <scaling_policy>. If the Heat stack is update with a larger value, the resources are added correctly. It is only when using the scaling policy. Logs show a forbidden error when attempting to create the Zaqer Mistral trigger. Any ideas? 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.gxvscbt3q3ga]: UPDATE_COMPLETE Stack UPDATE completed successfully 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.5rjz74hujhxh.alarm_subscription]: CREATE_FAILED ServiceUnavailableError: resources.alarm_subscription: Error response from Zaqar. Code: 503. Title: Service temporarily unavailable. Description: Subscription could not be created. Please try again in a few seconds.. 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.5rjz74hujhxh]: CREATE_FAILED Resource CREATE failed: ServiceUnavailableError: resources.alarm_subscription: Error response from Zaqar. Code: 503. Title: Service temporarily unavailable. Description: Subscription could not be created. Please try again in a few seconds.. 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.5rjz74hujhxh]: CREATE_FAILED ServiceUnavailableError: resources.5rjz74hujhxh.resources.alarm_subscription: Error response from Zaqar. Code: 503. Title: Service temporarily unavailable. Description: Subscription could not be created. Please try again in a few seconds.. 2024-05-09 15:10:41Z [stack_1-DmMTV.asg]: UPDATE_FAILED Resource CREATE failed: ServiceUnavailableError: resources.5rjz74hujhxh.resources.alarm_subscription: Error response from Zaqar. Code: 503. Title: Service temporarily unavailable. Description: Subscription could not be created. Please try again in a few s 2024-05-09 15:10:41Z [stack_1-DmMTV.asg.gxvscbt3q3ga]: UPDATE_COMPLETE state changed 2024-05-09 15:10:42Z [stack_1-DmMTV.asg.nzixbsxmb5mt]: UPDATE_COMPLETE Stack UPDATE completed successfully 2024-05-09 15:10:42Z [stack_1-DmMTV.asg.nzixbsxmb5mt]: UPDATE_COMPLETE state changed 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions [] Subscription could not be created.: keystoneauth1.exceptions.http.Forbidden: Remaining redelegation depth of 0 out of allowed range of [0..10] (Disable insecure_debug mode to suppress these details.) (HTTP 403) (Request-ID: ) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions Traceback (most recent call last): 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/zaqar/transport/wsgi/v2_0/subscriptions.py", line 193, in on_post 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions mgr.driver.register(subscriber, options, ttl, project_id, req_data) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/zaqar/notification/tasks/trust.py", line 60, in register 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions trust_id = auth.create_trust_id( 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/zaqar/common/auth.py", line 67, in create_trust_id 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions trust = client.trusts.create(trustor_user=trustor_user_id, 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneclient/v3/contrib/trusts.py", line 74, in create 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return super(TrustManager, self).create( 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneclient/base.py", line 86, in func 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return f(*args, **new_kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneclient/base.py", line 383, in create 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return self._post( 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneclient/base.py", line 192, in _post 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions resp, body = self.client.post(url, body=body, **kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneauth1/adapter.py", line 401, in post 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return self.request(url, 'POST', **kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneauth1/adapter.py", line 554, in request 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions resp = super(LegacyJsonAdapter, self).request(*args, **kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneauth1/adapter.py", line 257, in request 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions return self.session.request(url, method, **kwargs) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystoneauth1/session.py", line 986, in request 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions raise exceptions.from_response(resp, method, url) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions keystoneauth1.exceptions.http.Forbidden: Remaining redelegation depth of 0 out of allowed range of [0..10] (Disable insecure_debug mode to suppress these details.) (HTTP 403) (Request-ID: ) 2024-05-09 14:43:47.510 731 ERROR zaqar.transport.wsgi.v2_0.subscriptions Regards, Devin

1 0