January 2025 - openstack-discuss - lists.openstack.org

[telemetry] Stepping down from core team
by Yadnesh Kulkarni 22 Jan '25

22 Jan '25

Dear Team, Due to my role change I will no longer be able to contribute to the Telemetry projects. I’ve decided to step down from the core team. Working on the Telemetry projects has been a truly rewarding and enriching learning experience. I’ve thoroughly enjoyed being part of this incredible journey and have gained a lot from collaborating with such talented and supportive individuals. Thank you all for your guidance, collaboration, and support throughout this time. Wishing the team continued success and growth! -- Yadnesh Kulkarni

2 1

[tc][freezer][watcher][release][requirement][oslo] projects need to refresh the DPL model for the next cycle
by Ghanshyam Mann 21 Jan '25

21 Jan '25

Hi All, As you know, we have five projects (listed below) in the DPL model. As per process[1], we need to reset the DPL model every cycle. The project team either needs to opt-in to the DPL model (refer to the document for exact steps[1]) or plan for the PTL election. 1. Freezer: https://review.opendev.org/c/openstack/governance/+/939484 2. Watcher: https://review.opendev.org/c/openstack/governance/+/939488 3. Release: https://review.opendev.org/c/openstack/governance/+/939486 4. Requirement: https://review.opendev.org/c/openstack/governance/+/939487 5. Oslo: https://review.opendev.org/c/openstack/governance/+/939485 [1] https://governance.openstack.org/tc/reference/distributed-project-leadershi… -gmann

1 1

[nova] Seeking Advice on Adding Multiple CPU Models in One Aggregate for OpenStack
by mina.mohammadi367＠gmail.com 21 Jan '25

21 Jan '25

Hello friends, I am currently working on a deployment scenario in OpenStack where I need to group multiple CPU models within a single aggregate. I’m reaching out to the community to ask if anyone has experience with this type of setup or has any advice on best practices. I would greatly appreciate any input from the community regarding potential challenges or recommendations for managing multiple CPU models within a single aggregate. In particular, any advice on ensuring compatibility and optimizing instance scheduling based on traits would be extremely valuable. For reference, I am considering the solution outlined in the CPU Model Selection documentation: https://specs.openstack.org/openstack/nova-specs/specs/train/implemented/cp… Thank you in advance for your time and assistance.

1 0

Assistance with Configuring fdb_age_threshold in OVN with Kolla-Ansible
by Jan Wasilewski 21 Jan '25

21 Jan '25

Hi Stackers, Over the past few days, we encountered an issue during the migration of VMs from a customer environment to our OpenStack cloud. Both environments were connected via a cross-connect network (a VLAN-type network spanning the cloud and the customer environment), which resulted in duplicate MAC addresses in our OVN database. This occurred because the migrated VM retained the same MAC address as previously used in the customer's environment(so "ovn-sbctl list fdb" returned a port which was no-longer used and leads to such duplication) . To address the issue, we used the following command to clear the FDB database: ovn-sbctl --all destroy fdb While researching further, we came across the `fdb_age_threshold` configuration [1], which seemed to be a useful feature to prevent similar issues in the future. We attempted to implement it in our Kolla-Ansible environment by adding the following configuration to ` */etc/kolla/config/neutron/ml2_conf.ini*`: [ovn] fdb_age_threshold = 920 After deploying the changes, however, we noticed that the setting did not take effect in OVN. The configuration only applied successfully after we executed a manual script to propagate the setting directly to OVN [2]. Anyway such change is applicable only for exsisting networks, so it is far from perfect solution. Could you provide guidance on whether this behavior is due to incorrect documentation, an error in our configuration process, or an additional requirement needed to enable this feature? Any insights would be greatly appreciated. Thank you in advance for your support! /Jan Wasilewski **References:** [1] https://docs.openstack.org/neutron/latest/configuration/ml2-conf.html#ovn.f… [2] https://paste.openstack.org/show/b9xUcnG6GXmCdSbSReG0/

2 2

[openstack-ansible] issue
by Danish Khan 21 Jan '25

21 Jan '25

Dear All, Whenever I do any activity like Operating system upgrade of compute nodes or openstack major version update then the name of compute host gets updated. I have my compute node with name compute1,2,3.... but after the activity they sometimes become compute1.openstack.local or compute2.mgmt.local. Due to this I get duplicate resource providers. But only the latest provider works properly. and I had manually unset all the vm from old provider and added then into new provider. Is there a way I can avoid this? means I don't want my compute nodes to get renamed with domain. And is there a way I can unset a vm from all provider and heal them automatically instead adding them into new resource proivder? I tried below docs but the healing part is not working so I go with manual process for all vm which is too time consuming. https://docs.openstack.org/nova/yoga/admin/troubleshooting/orphaned-allocat… Regards, Danish Khan

3 2

[tc][all] OpenStack Technical Committee Weekly Summary and Meeting Agenda (2025.1/R-10)
by Goutham Pacha Ravi 20 Jan '25

20 Jan '25

Hello Stackers, We're 10 weeks away from the 2025.1 coordinated "Epoxy" release [1]. Starting this week, there are several deadlines that project teams have adopted to ensure that code, specifications, and documentation changes are adequately peer-reviewed. As Slawek Kaplonski (slaweq) shared to this mailing list [2], the nomination period for the upcoming Technical Committee and Project Team Leads elections will begin on 2025-02-05 and remain open until 2025-02-19. Early nominations are highly encouraged in case you'll be unavailable during this period. In the last week, the OpenStack Technical Committee selected a community goal to migrate away from the eventlet library across its codebase [3]. As with many community goals, this will be a multi-release goal and needs contributors. Please join the #openstack-eventlet-removal IRC channel on OFTC to participate in the discussion. === Weekly Meeting === Dmitriy Rabotyagov (noonedeadpunk) chaired the TC's weekly IRC meeting on 2025-01-14 [4]. We discussed the maintenance of the "openstackdocstheme" Sphinx plugin and called out some early attempts to switch documentation to a stock theme that's more maintainable and sustainable. We also reviewed a proposal from Freezer project maintainers to remove the project team from the "inactive" teams list [5]. The TC also considered requesting an exception for Freezer to release within 2025.1. In this vein, we also highlighted the need for consistent criteria to move projects out of inactive status and better tooling for indicating project health and activity. The next meeting of the OpenStack Technical Committee is today, 2025-01-21. This meeting will be hosted via IRC on OFTC's #openstack-tc channel. Please find the meeting agenda on the wiki [6]. I hope you'll be able to join us there. === Governance Proposals === ==== Merged ==== - Propose to select the eventlet-removal community goal | https://review.opendev.org/c/openstack/governance/+/934936 - Rework the eventlet-removal goal proposal | https://review.opendev.org/c/openstack/governance/+/931254 - Add ansible-role-httpd repo to OSA-owned projects | https://review.opendev.org/c/openstack/governance/+/935694 ==== Open for Review ==== - Resolve to adhere to non-biased language | https://review.opendev.org/c/openstack/governance/+/934907 - Retire Freezer DR | https://review.opendev.org/c/openstack/governance/+/938183 - Retire qdrouterd role | https://review.opendev.org/c/openstack/governance/+/938193 - Remove Freezer from inactive state | https://review.opendev.org/c/openstack/governance/+/938938 - Reset the DPL model for oslo project | https://review.opendev.org/c/openstack/governance/+/939485 - Reset the DPL model for Release project | https://review.opendev.org/c/openstack/governance/+/939486 - Reset the DPL model for Requirement project | https://review.opendev.org/c/openstack/governance/+/939487 - Reset the DPL model for Watcher project | https://review.opendev.org/c/openstack/governance/+/939488 - Define 2025 upstream investment opportunities | https://review.opendev.org/c/openstack/governance/+/939507 === Upcoming Events === - 2025-01-28: OpenInfra Board Monthly Meeting: https://board.openinfra.org/ - 2025-02-01: FOSDEM 2025 (https://fosdem.org/2025/) OpenStack's 15th Birthday Celebration - 2025-02-05: Nominations open for 2025.2 TC/PTL Elections: https://governance.openstack.org/election/ - 2025-02-28: 2025.1 ("Epoxy") Feature Freeze and release milestone 3 [1] - 2025-03-06: SCALE 2025 + OpenInfra Days NA (https://www.socallinuxexpo.org/scale/22x) Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [2] TC/PTL Election dates for the 2025.2 cycle: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] Goal to Remove Eventlet from OpenStack: https://governance.openstack.org/tc/goals/selected/remove-eventlet.html [4] TC Meeting IRC Log 2025-01-14: https://meetings.opendev.org/meetings/tc/2025/tc.2025-01-14-18.00.log.html [5] Remove Freezer from inactive state: https://review.opendev.org/c/openstack/governance/+/938938 [6] TC Meeting Agenda, 2025-01-21: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

1 0

[Horizon] Need Help - Error with Compress
by info＠patrick-omland.de 20 Jan '25

20 Jan '25

I need help with Horizon; when I run the following command ./manage.py compress, I get the following error: (venv) root@fsn1-controller01 /var/lib/horizon # ./manage.py compress /var/lib/horizon/venv/lib/python3.11/site-packages/debreach/__init__.py:6: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. version_info = version.StrictVersion(__version__).version CommandError: An error occurred during rendering _stylesheets.html: Error: File to import not found or unreadable: /horizon/lib/font_awesome/scss/font-awesome.scss. on line 12:1 of dashboard/scss/horizon.scss from line 6:9 of stdin >> @import "/horizon/lib/font_awesome/scss/font-awesome.scss"; ^ (venv) root@fsn1-controller01 /var/lib/horizon # ll total 124 -rw-r--r-- 1 root root 77 Jan 20 19:13 babel-django.cfg -rw-r--r-- 1 root root 258 Jan 20 19:13 babel-djangojs.cfg -rw-r--r-- 1 root root 233 Jan 20 19:13 bindep.txt -rw-r--r-- 1 root root 600 Jan 20 19:13 CONTRIBUTING.rst drwxr-xr-x 3 root root 4096 Jan 20 19:13 doc -rw-r--r-- 1 root root 579 Jan 20 19:13 HACKING.rst drwxr-xr-x 19 root root 4096 Jan 20 19:15 horizon -rw-r--r-- 1 root root 10143 Jan 20 19:13 LICENSE -rwxr-xr-x 1 root root 831 Jan 20 19:13 manage.py -rw-r--r-- 1 root root 634 Jan 20 19:13 MANIFEST.in drwxr-xr-x 6 root root 4096 Jan 20 19:15 openstack_auth drwxr-xr-x 18 root root 4096 Jan 20 19:15 openstack_dashboard -rw-r--r-- 1 root root 1023 Jan 20 19:13 package.json drwxr-xr-x 8 root root 4096 Jan 20 19:13 playbooks -rw-r--r-- 1 root root 2188 Jan 20 19:13 plugin-registry.csv -rw-r--r-- 1 root root 1920 Jan 20 19:13 README.rst drwxr-xr-x 4 root root 4096 Jan 20 19:13 releasenotes -rw-r--r-- 1 root root 120 Jan 20 19:13 reno.yaml -rw-r--r-- 1 root root 2664 Jan 20 19:13 requirements.txt drwxr-xr-x 5 root root 4096 Jan 20 19:13 roles -rw-r--r-- 1 root root 1937 Jan 20 19:13 setup.cfg -rw-r--r-- 1 root root 698 Jan 20 19:13 setup.py drwxr-xr-x 9 root root 4096 Jan 20 19:15 static -rw-r--r-- 1 root root 379 Jan 20 19:13 test-requirements.txt -rw-r--r-- 1 root root 3198 Jan 20 19:13 test-shim.js drwxr-xr-x 2 root root 4096 Jan 20 19:13 tools -rw-r--r-- 1 root root 7537 Jan 20 19:13 tox.ini drwxr-xr-x 6 root root 4096 Jan 20 19:13 venv (venv) root@fsn1-controller01 /var/lib/horizon # I have installed Horizon in a virtual Python 3 environment (Debian Bookworm) and I also clone the Horizon Github Repo, then I installed all requirements using pip install -r requirements.txt. Anyone have an idea?

1 0

[Horizon] Need Help - Error with Compress
by info＠patrick-omland.de 20 Jan '25

20 Jan '25

I need help with Horizon; when I run the following command ./manage.py compress, I get the following error: (venv) root@fsn1-controller01 /var/lib/horizon # ./manage.py compress /var/lib/horizon/venv/lib/python3.11/site-packages/debreach/__init__.py:6: DeprecationWarning: distutils Version classes are deprecated. Use packaging.version instead. version_info = version.StrictVersion(__version__).version CommandError: An error occurred during rendering _stylesheets.html: Error: File to import not found or unreadable: /horizon/lib/font_awesome/scss/font-awesome.scss. on line 12:1 of dashboard/scss/horizon.scss from line 6:9 of stdin >> @import "/horizon/lib/font_awesome/scss/font-awesome.scss"; ^ (venv) root@fsn1-controller01 /var/lib/horizon # ll total 124 -rw-r--r-- 1 root root 77 Jan 20 19:13 babel-django.cfg -rw-r--r-- 1 root root 258 Jan 20 19:13 babel-djangojs.cfg -rw-r--r-- 1 root root 233 Jan 20 19:13 bindep.txt -rw-r--r-- 1 root root 600 Jan 20 19:13 CONTRIBUTING.rst drwxr-xr-x 3 root root 4096 Jan 20 19:13 doc -rw-r--r-- 1 root root 579 Jan 20 19:13 HACKING.rst drwxr-xr-x 19 root root 4096 Jan 20 19:15 horizon -rw-r--r-- 1 root root 10143 Jan 20 19:13 LICENSE -rwxr-xr-x 1 root root 831 Jan 20 19:13 manage.py -rw-r--r-- 1 root root 634 Jan 20 19:13 MANIFEST.in drwxr-xr-x 6 root root 4096 Jan 20 19:15 openstack_auth drwxr-xr-x 18 root root 4096 Jan 20 19:15 openstack_dashboard -rw-r--r-- 1 root root 1023 Jan 20 19:13 package.json drwxr-xr-x 8 root root 4096 Jan 20 19:13 playbooks -rw-r--r-- 1 root root 2188 Jan 20 19:13 plugin-registry.csv -rw-r--r-- 1 root root 1920 Jan 20 19:13 README.rst drwxr-xr-x 4 root root 4096 Jan 20 19:13 releasenotes -rw-r--r-- 1 root root 120 Jan 20 19:13 reno.yaml -rw-r--r-- 1 root root 2664 Jan 20 19:13 requirements.txt drwxr-xr-x 5 root root 4096 Jan 20 19:13 roles -rw-r--r-- 1 root root 1937 Jan 20 19:13 setup.cfg -rw-r--r-- 1 root root 698 Jan 20 19:13 setup.py drwxr-xr-x 9 root root 4096 Jan 20 19:15 static -rw-r--r-- 1 root root 379 Jan 20 19:13 test-requirements.txt -rw-r--r-- 1 root root 3198 Jan 20 19:13 test-shim.js drwxr-xr-x 2 root root 4096 Jan 20 19:13 tools -rw-r--r-- 1 root root 7537 Jan 20 19:13 tox.ini drwxr-xr-x 6 root root 4096 Jan 20 19:13 venv (venv) root@fsn1-controller01 /var/lib/horizon # I have installed Horizon in a virtual Python 3 environment (Debian Bookworm) and I also clone the Horizon Github Repo, then I installed all requirements using pip install -r requirements.txt. Anyone have an idea?

1 0

How to know the openstack client's default microversion?
by berndbausch＠gmail.com 20 Jan '25

20 Jan '25

Without the version option e.g. --os-compute-api-version, the openstack client submits API requests with certain default microversions. The precise microversions vary with the openstack client's version and the specific task. For example, the --debug option reveals that openstack client 7.1.3 uses Nova microversion 2.89 when attaching a volume to an instance. Is there a simpler way than --debug to find out which microversions the client uses? Is there a command, or perhaps a website where this is documented? Thanks for your ideas! Bernd.

2 1

[openstack-ansible] : libvirtd debug logs after Wallaby upgrade
by Rambo Rambo 20 Jan '25

20 Jan '25

Hi Team I have recently done Victoria to Wallaby upgrade on my openstack-ansible installation. After the upgrade we observe that /var/log/libvirt/ size on all the computes was growing due to libvirtd.log file. Further checking this file it can be seen that there are debug logs. 2025-01-19 11:15:20.817+0000: 2943565: *debug *: virNetlinkEventCallback:862 : dispatching to max 0 clients, called from event watch 7 2025-01-19 11:15:20.817+0000: 2943565:* debug* : virNetlinkEventCallback:876 : event not handled. 2025-01-19 11:15:20.821+0000: 2943605: *debug :* udevHandleOneDevice:1492 : udev action: 'add' ... libvirtd configuration file on compute shows log_level=1 cat libvirtd.conf # Ansible managed # enabling debug mode according to http://wiki.libvirt.org/page/DebugLogs log_level = 1 log_filters="3:remote 4:event 3:json 3:rpc" log_outputs="1:file:/var/log/libvirt/libvirtd.log" listen_tls = 0 listen_tcp = 0 unix_sock_group = "libvirt" unix_sock_ro_perms = "0777" unix_sock_rw_perms = "0770" auth_unix_ro = "none" auth_unix_rw = "none" auth_tcp = "sasl" No related parameter was changed/updated in user_variable file during the upgrade? Any information what could have enabled the debug logs for libvirtd on all the computes? Also how can I turn-off this using the openstack-ansible and what could be impact during the procedure? Regards

2 3