September 2024 - openstack-discuss

[manila] Propose Gireesh Awasthi to manila core
by Carlos Silva 24 Sep '24

24 Sep '24

Hello everyone, I would like to add Gireesh Awasthi to the OpenStack Manila core team. Gireesh started his OpenStack journey a couple of cycles ago, and caused great impact from the get go while working on some complex features that impacted all of the manila code base. He's also been consistently participative in the latest PTGs. With the knowledge acquired in the code base, he then started contributing more to reviews, and became a go-to person for providing feedback on the NetApp ONTAP driver changes, and/or third party driver changes. It is important to note that this is yet another step into maintaining a healthy community with people from different affiliations sharing the responsibility of maintaining an open source project. In case there are no objections, I will add him to the core team in 1 week from now. [1] https://bit.ly/manila-reviews-90-days Thank you! Regards, carloss

2 2

[cyborg][zun][masakari][tacker][venus] Pending removal of LegacyEngineFacade
by Stephen Finucane 24 Sep '24

24 Sep '24

o/ Just a heads up to the listed projects that oslo.db's LegacyEngineFacade is pending removal in the Epoxy cycle. I would encourage you to migrate asap to avoid a broken CI. For a minimal example of how to do this, I'd encourage you to look at [1]. Cheers, Stephen [1] https://review.opendev.org/c/openstack/mistral/+/926420

1 0

Looking forward to work with Real-world project!
by Artemio Mendoza 23 Sep '24

23 Sep '24

Hi OpenStackers, As a new OpenStack community member, I read your email very carefully and looking for an opportunity that I can support. After graduating from university, I got a BS degree in computer science. I have been working on web/mobile app development for 10 years and have some reasonable experience in AWS, Azure, and other cloud environments. But I was really interested in OpenStack cloud computing so I started researching this last year and I'm actively keeping an eye on this community email, and trying to find some clues and new ideas about what I am going to do. I'm especially interested in Ceph and VDI development based on OpenStack. For my experience, I have tried to set up devstack on my laptop(20 core i7th, 32GB RAM), and tried run Bumblebee ( https://github.com/NeCTAR-RC/bumblebee) but failed. :( So for now, I'm still going to learn OpenStack doc. But I want to practice myself by jumping into real-world projects. If you are interested in me or looking for someone who can collaborate/research, then I will absolutely dedicate myself to that as a volunteer. Looking forward to hearing many good suggestions. Please feel free to reach out to me through Skype (huknamatata21) or this number (+15124877569) Regards, Artemio (Hony)

1 0

[Neutron] Bug deputy Sept 16 - 23
by Jakub Libosvar 23 Sep '24

23 Sep '24

Hi, I was the bug deputy last week. Was calm, only 3 bugs reported. Here is the breakdown: High ---- * security-groups-rules-belongs-to-default-sg slows down SG GET operations - https://bugs.launchpad.net/neutron/+bug/2081173 - I marked it as high because it’s a performance regression Medium ------ * Tighten / improve rally SG tests to catch performance regressions - mostly a placeholder to improve rally scenarios to prevent regressing in performance - https://bugs.launchpad.net/neutron/+bug/2081108 Wishlist -------- * Neutron OVN support for CARP - https://bugs.launchpad.net/neutron/+bug/2081643 - sounds like a new feature but it also requires some enhancements in the core OVN first

1 0

[publiccloud-sig] Heads-Up: next meeting September 25th - 0700 UTC
by Felix Kronlage-Dammers 23 Sep '24

23 Sep '24

Hi everyone, We are adjusting the schedule for the publiccloud-sig and will switch to odd instead of even weeks. This Wednesday (September 25th) the next meeting of the publiccloud-sig is going to happen. Thanks to Artem (gtema) and Joern (joek-office) who helped prepare the meeting agenda for this wednesday: - Housekeeping - Upcoming vPTG - Reminder to sign up for PTG: https://openinfra.dev/ptg/ - IAM Federation - combination of functional requirements (every CSP is having unique use case so we want to find similarities and differencies to determine the roadmap for Keystone) If you’re interesting in IAM federation, be sure to join! We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig <https://meetpad.opendev.org/publiccloud-sig> See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG <https://wiki.openstack.org/wiki/PublicCloudSIG> See you on Wednesday! felix -- Felix Kronlage-Dammers Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

Openstack power off/on process
by Michael Knox 23 Sep '24

23 Sep '24

Hey Folks. I am working through a scenario that requires us to have Openstack in a Pelican Case and deployed in the "field" on a semi regular basis. I guess, portal "edge cloud" if you will? The problem I am trying to clean up is the startup process. We use kolla-ansible and rocky with zed (though we have one with ubuntu and wallaby) in this specific use case. We do the shutdown nicely, kolla-ansible -i inventory stop, then power off the control nodes (we have 3 in the setup). The problem is on the start up. All the containers start and then we still *have* to run the kolla-ansible -i inventory mariadb_recovery step to get the cloud back into a usable state. No matter the order of shut down or start up, MariaDB seems to always need a recovery. Are there any people here doing this or something similar? Is there a more efficient startup process I am not aware of or should consider? The folks in the field aren't Openstack admins, so hoping to figure out a solution that is less dependent on their knowledge of Openstack's undercloud tooling. Thanks in advance Michael

2 2

[cinder][CI] Can't start zuul service
by xuq.fnstxz＠fujitsu.com 22 Sep '24

22 Sep '24

Hello every one, I'm building a CI system on my ubuntu 22 system. Now I've installed the zuul using 'pip install zuul' and configured it. But after running command 'zuul-scheduler', I saw a lot of errors like following in the log. It seems that there is something error in my config file that prevents access to the repo. > 2024-09-20 13:05:06,010 ERROR zuul.TenantParser: Error processing cat job > Traceback (most recent call last): > File "/home/stack/.local/lib/python3.10/site-packages/zuul/configloader.py", line 2157, in _cacheTenantYAML > self._processCatJob(abide, tenant, loading_errors, job, > File "/home/stack/.local/lib/python3.10/site-packages/zuul/configloader.py", line 2249, in _processCatJob > raise TimeoutError(f"Cat job {job} timed out; consider setting " > TimeoutError: Cat job <zuul.zk.event_queues.JobResultFuture object at 0x7fb770341510> timed out; consider setting merger.git_timeout in zuul.conf Following is my zuul.conf. > [zookeeper] > hosts=ZOOKEEPER_HOST > tls_cert=/cert/client-cert.pem > tls_key=/cert/client-key.pem > tls_ca=/cert/ca-cert.pem > > [database] > # Use variable interpolation to supply the password from the > # docker-compose file. > # https://zuul-ci.org/docs/zuul/latest/configuration.html > dburi=mysql+pymysql://DB_USER:DB_PASS@DB_HOST/ZUUL_DB > > [keystore] > password=secret > > [web] > listen_address=0.0.0.0 > port=9000 > root=http://localhost:9000 > log_config=/etc/zuul/logging.conf > > [webclient] > url=http://localhost:9000 > verify_ssl=false > > [scheduler] > tenant_config=/etc/zuul/main.yaml > log_config=/etc/zuul/logging.conf > [merger] > git_user_email=git_user(a)example.com > git_user_name=git_user > log_config=/etc/zuul/logging.conf > > [executor] > private_key_file=/home/stack/.ssh/id_rsa > default_username=executor_user > trusted_rw_paths=/srv/static/logs > > [connection gerrit] > driver=gerrit > server=review.opendev.org > user=git_user > sshkey=/ssh/id_rsa And the following is the tenant_config file. > - tenant: > name: myCI > source: > gerrit: > untrusted-projects: > - openstack/cinder Could you please tell me what I need to modify or add in the config file? Thanks and Regards, Inori.

2 2

[kolla] Weird upgrade procudere ?
by Michal Arbet 22 Sep '24

22 Sep '24

Hi Koalas, I am not sure but is this normal ? In rabbitmq.yml is this +++ b/ansible/rabbitmq.yml @@ -0,0 +1,115 @@ +--- +# For RabbitMQ we need to be careful about restarting services, to avoid losing quorum. +- name: Apply role rabbitmq + gather_facts: false + hosts: + - rabbitmq + - '&enable_rabbitmq_True' But I can see during the upgrade restart every node at the same moment and then ther is some try to do it better ... I mean is that restart before OK ? Thanks TASK [rabbitmq : Enable all stable feature flags] ***************************************************************************************************************************************************************** ok: [controller1] ok: [controller0] ok: [controller2] TASK [rabbitmq : Check rabbitmq containers] *********************************************************************************************************************************************************************** changed: [controller0] => (item={'key': 'rabbitmq', 'value': {'container_name': 'rabbitmq', 'group': 'rabbitmq', 'enabled': True, 'image': 'dockerhub.ultimum.io/kolla-dev/debian-rabbitmq:KB-2023.1', 'bootstrap_environment': {'KOLLA_BOOTSTRAP': None, 'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS', 'RABBITMQ_CLUSTER_COOKIE': 'ultimum', 'RABBITMQ_LOG_DIR': '/var/log/kolla/rabbitmq'}, 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS', 'RABBITMQ_CLUSTER_COOKIE': 'ultimum', 'RABBITMQ_LOG_DIR': '/var/log/kolla/rabbitmq'}, 'volumes': ['/etc/kolla/rabbitmq/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'rabbitmq:/var/lib/rabbitmq/', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}, 'healthcheck': {'interval': '30', 'retries': '3', 'start_period': '5', 'test': ['CMD-SHELL', 'healthcheck_rabbitmq'], 'timeout': '30'}, 'haproxy': {'rabbitmq_management': {'enabled': 'yes', 'mode': 'http', 'port': '15672', 'host_group': 'rabbitmq'}, 'rabbitmq_outward_management': {'enabled': False, 'mode': 'http', 'port': '15674', 'host_group': 'outward-rabbitmq'}, 'rabbitmq_outward_external': {'enabled': False, 'mode': 'tcp', 'external': True, 'port': '5674', 'host_group': 'outward-rabbitmq', 'frontend_tcp_extra': ['timeout client 1h'], 'backend_tcp_extra': ['timeout server 1h']}}}}) changed: [controller2] => (item={'key': 'rabbitmq', 'value': {'container_name': 'rabbitmq', 'group': 'rabbitmq', 'enabled': True, 'image': 'dockerhub.ultimum.io/kolla-dev/debian-rabbitmq:KB-2023.1', 'bootstrap_environment': {'KOLLA_BOOTSTRAP': None, 'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS', 'RABBITMQ_CLUSTER_COOKIE': 'ultimum', 'RABBITMQ_LOG_DIR': '/var/log/kolla/rabbitmq'}, 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS', 'RABBITMQ_CLUSTER_COOKIE': 'ultimum', 'RABBITMQ_LOG_DIR': '/var/log/kolla/rabbitmq'}, 'volumes': ['/etc/kolla/rabbitmq/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'rabbitmq:/var/lib/rabbitmq/', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}, 'healthcheck': {'interval': '30', 'retries': '3', 'start_period': '5', 'test': ['CMD-SHELL', 'healthcheck_rabbitmq'], 'timeout': '30'}, 'haproxy': {'rabbitmq_management': {'enabled': 'yes', 'mode': 'http', 'port': '15672', 'host_group': 'rabbitmq'}, 'rabbitmq_outward_management': {'enabled': False, 'mode': 'http', 'port': '15674', 'host_group': 'outward-rabbitmq'}, 'rabbitmq_outward_external': {'enabled': False, 'mode': 'tcp', 'external': True, 'port': '5674', 'host_group': 'outward-rabbitmq', 'frontend_tcp_extra': ['timeout client 1h'], 'backend_tcp_extra': ['timeout server 1h']}}}}) changed: [controller1] => (item={'key': 'rabbitmq', 'value': {'container_name': 'rabbitmq', 'group': 'rabbitmq', 'enabled': True, 'image': 'dockerhub.ultimum.io/kolla-dev/debian-rabbitmq:KB-2023.1', 'bootstrap_environment': {'KOLLA_BOOTSTRAP': None, 'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS', 'RABBITMQ_CLUSTER_COOKIE': 'ultimum', 'RABBITMQ_LOG_DIR': '/var/log/kolla/rabbitmq'}, 'environment': {'KOLLA_CONFIG_STRATEGY': 'COPY_ALWAYS', 'RABBITMQ_CLUSTER_COOKIE': 'ultimum', 'RABBITMQ_LOG_DIR': '/var/log/kolla/rabbitmq'}, 'volumes': ['/etc/kolla/rabbitmq/:/var/lib/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', 'rabbitmq:/var/lib/rabbitmq/', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}, 'healthcheck': {'interval': '30', 'retries': '3', 'start_period': '5', 'test': ['CMD-SHELL', 'healthcheck_rabbitmq'], 'timeout': '30'}, 'haproxy': {'rabbitmq_management': {'enabled': 'yes', 'mode': 'http', 'port': '15672', 'host_group': 'rabbitmq'}, 'rabbitmq_outward_management': {'enabled': False, 'mode': 'http', 'port': '15674', 'host_group': 'outward-rabbitmq'}, 'rabbitmq_outward_external': {'enabled': False, 'mode': 'tcp', 'external': True, 'port': '5674', 'host_group': 'outward-rabbitmq', 'frontend_tcp_extra': ['timeout client 1h'], 'backend_tcp_extra': ['timeout server 1h']}}}}) RUNNING HANDLER [rabbitmq : Restart rabbitmq container] *********************************************************************************************************************************************************** [WARNING]: Failure using method (v2_playbook_on_handler_task_start) in callback plugin (<ansible.plugins.callback.ara_default.CallbackModule object at 0x7f66542e0100>): 'NoneType' object is not subscriptable changed: [controller0] changed: [controller1] changed: [controller2] PLAY [Restart rabbitmq services] ********************************************************************************************************************************************************************************** TASK [rabbitmq : Get info on RabbitMQ container] ****************************************************************************************************************************************************************** ok: [controller0] TASK [rabbitmq : Put RabbitMQ node into maintenance mode] ********************************************************************************************************************************************************* changed: [controller0] TASK [rabbitmq : Restart rabbitmq container] ********************************************************************************************************************************************************************** changed: [controller0] TASK [rabbitmq : Waiting for rabbitmq to start] ******************************************************************************************************************************************************************* changed: [controller0] PLAY [Restart rabbitmq services] ********************************************************************************************************************************************************************************** TASK [rabbitmq : Get info on RabbitMQ container] ****************************************************************************************************************************************************************** ok: [controller1] TASK [rabbitmq : Put RabbitMQ node into maintenance mode] ********************************************************************************************************************************************************* changed: [controller1] TASK [rabbitmq : Restart rabbitmq container] ********************************************************************************************************************************************************************** changed: [controller1] TASK [rabbitmq : Waiting for rabbitmq to start] ******************************************************************************************************************************************************************* changed: [controller1] PLAY [Restart rabbitmq services] ********************************************************************************************************************************************************************************** TASK [rabbitmq : Get info on RabbitMQ container] ****************************************************************************************************************************************************************** ok: [controller2] TASK [rabbitmq : Put RabbitMQ node into maintenance mode] ********************************************************************************************************************************************************* changed: [controller2] TASK [rabbitmq : Restart rabbitmq container] ********************************************************************************************************************************************************************** changed: [controller2] TASK [rabbitmq : Waiting for rabbitmq to start] ******************************************************************************************************************************************************************* changed: [controller2] PLAY [Apply rabbitmq post-configuration] ************************************************************************************************************************************************************************** TASK [Include rabbitmq post-deploy.yml] *************************************************************************************************************************************************************************** TASK [rabbitmq : Enable all stable feature flags] ************************* Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

1 0

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

22 Sep '24

Hello Stackers, We're in the home stretch of the 2024.2 ("Dalmatian") release cycle this week [1]. OpenStack services will be tagging their final release candidates in preparation for the final release next week. Since the release train never stops, I'd direct your attention to the 2025.1 ("Epoxy") release cycle's schedule [2], active feature development has already begun across the board. We concluded elections for four seats on the OpenStack Technical Committee last week [3]. I'm pleased to welcome first-time TC members Doug Goldstein (cardoe) and Sylvain Bauza (bauzas), and welcome back Ghanshyam Mann (gmann) and Dr. Jens Harbott (frickler). I'd also like to extend congratulations to the PTLs of 37 project teams who volunteered to lead their teams. Most of these leaders have served in the past cycle, and on behalf of the TC, I'd like to thank them for their dedication. I also welcome Guillaume Boutry (gboutry), who will be the PTL for the Sunbeam project for the first time. Last week, the TC merged a goal proposal to move all Ubuntu-based testing in the Zuul CI system to the latest LTS release: 24.04 LTS (Noble Numbat). Ghanshyam Mann (gmann) is expected to lead this goal and is asking project teams to help resolve test failures and incompatibilities when transitioning both unit and functional test jobs to this distribution. This goal may be selected for implementation during the 2025.1 ("Epoxy") release cycle. Several minor governance changes were also merged and proposed, as listed below. === Weekly Meeting === The OpenStack TC weekly meeting was held over IRC on 2024-09-17. The IRC meeting logs are available on eavesdrop [4]. We continued to populate topics for the upcoming virtual Project Teams Gathering [5] and began addressing leadership appointments for two projects with volunteers (Swift and Mistral). We're also checking the community's interest in maintaining the "Watcher" project [6], and waiting on the Tacker team to drop its dependency on "kuryr-kubernetes" so that project can be retired. Amy Marrich (spotz) and Sylvain Bauza (bauzas) recapped the OpenInfra Summit in Suwon, noting the packed rooms and commending the organizers for a great job. Feedback from hallway discussions highlighted the need for improved documentation translation, as the lack of translated materials makes it difficult for new users and contributors, especially in non-English-speaking regions. We’ll discuss this further at the PTG in October. bauzas also raised the need for better tracking and communication regarding the etherpads used in the community for various tasks and contributor work. The next OpenStack TC meeting will be held over IRC in OFTC's #openstack-tc channel on 2024-09-24 at 1800 UTC. I hope you'll be able to attend and participate in the discussions. The agenda for the meeting is on the meeting wiki [7]. Please remember that you can always edit the wiki and propose new topics. === Governance Proposals === ==== Merged ==== - Add goal to migrate CI/CD jobs to Ubuntu Noble | https://review.opendev.org/c/openstack/governance/+/928078 - PTI: Project-first wording | https://review.opendev.org/c/openstack/governance/+/929644 - Charms: Retire unmaintained charms | https://review.opendev.org/c/openstack/governance/+/926793 - Add TC/PTL results from the 2025.1 election | https://review.opendev.org/c/openstack/governance/+/929940 ==== Open for Review ==== - Appoint Tim Burke as PTL for Swift | https://review.opendev.org/c/openstack/governance/+/928881 - Add Axel Vanzaghi as PTL for Mistral | https://review.opendev.org/c/openstack/governance/+/927962 - Retire all single charm repositories | https://review.opendev.org/c/openstack/governance/+/903490 - Add gouthamr nomination for 2025.1 TC chair | https://review.opendev.org/c/openstack/governance/+/929971 - Add chair nomination folder for 2025.1 | https://review.opendev.org/c/openstack/governance/+/929970 - Select community-wide goal: Migrate CI/CD jobs to Ubuntu Noble | https://review.opendev.org/c/openstack/governance/+/929703 - Mark kuryr-kubernetes and kuryr-tempest-plugin inactive | https://review.opendev.org/c/openstack/governance/+/929698 === Upcoming Events === - 2024-10-08: OpenInfra Monthly Board Meeting: https://board.openinfra.dev/ - 2024-10-15: OpenInfra Days NA, Indianapolis: https://ittraining.iu.edu/explore-topics/titles/oid-iu/ - 2024-10-21: OpenInfra Project Teams Gathering: https://openinfra.dev/ptg/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] 2024.2 "Dalmatian" Release Schedule: https://releases.openstack.org/dalmatian/schedule.html [2] 2025.1 "Epoxy" Release Schedule: https://releases.openstack.org/epoxy/schedule.html [3] 2025.1 TC and PTL Election Results: [4] TC Meeting IRC Log, 2024-09-17: https://meetings.opendev.org/meetings/tc/2024/tc.2024-09-17-18.00.log.html [5] 2025.1 OpenStack TC/PTG planning etherpad: https://etherpad.opendev.org/p/oct2024-ptg-os-tc [6] Retirement of openstack/watcher: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [7] TC Meeting Agenda, 2024-09-24: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee

1 0

[upgrade][openstack] OpenStack Upgrade Procedure
by Ammar Al-Sayegh 21 Sep '24

21 Sep '24

Hello, I need to upgrade an OpenStack installation for the first time. The system Admin who performed the original installation is no longer available. How can I determine the current OpenStack version, modules installed, type of installation, and networking paradigm from OpenStack Horizon? Once determined, where I can find the appropriate upgrade procedure? Thank you. -ammar

2 1

[networking-mlnx] Project Health
by William Szumski 20 Sep '24

20 Sep '24

Hi all, I've noticed that there hasn't been any stable releases of networking-mlnx since stable/zed and was just wondering if this project still has any active maintainers. I would be interested in helping to keep this project going, so please give me a shout if you require any assistance. Thanks for all your hard work, Will

3 3

[unmaintained][cinder] question about zuul jobs for unmaintained branches
by Brian Rosmaita 20 Sep '24

20 Sep '24

Hello Unmaintained maintenance team, I was reviewing a cinder-tempest-plugin patch (which is in an un-branched repository), and noticed that we have a bunch of Zuul cinder jobs defined for stable branches that no longer exist, for example, stable/wallaby [0]. Where this impacts the unmaintained branches is that, for example, unmaintained/wallaby's .zuul.yaml is configured to run (for example) cinder-tempest-plugin-lvm-lio-barbican in the check [1], but you can see on this review, it's not actually running: https://review.opendev.org/c/openstack/cinder/+/926279?tab=change-view-tab-… So, my question is what to do about these unused jobs: (a) delete them (b) only delete stable/x for x <= ussuri, and update the jobs for stable/x for victoria <= x <= zed to unmaintained/x (c) delete them all, but propose a patch to the appropriate unmaintained branches zuul.yaml files that contain the job definition so that the Unmaintained team can make any changes needed to get them running without having to go through the cinder-tempest-plugin-core team's review/approval process (d) something I haven't thought of Thanks! brian [0] https://opendev.org/openstack/cinder-tempest-plugin/src/branch/master/.zuul… [1] https://opendev.org/openstack/cinder/src/branch/unmaintained/wallaby/.zuul.…

2 1

New to OpenStack. Test environment with 1 control node and 2 compute nodes. Unable to migrate or resize instances
by collinl＠churchofjesuschrist.org 20 Sep '24

20 Sep '24

As the subject says, I am new to OpenStack, and have spun up a test cluster with one control node, and two compute nodes. It seems to work for several tasks (i.e. I can spin up a cirros instance on both of the compute nodes, which seems to work just fine) However, when I attempt to migrate an instance from one compute node to the other, the instance goes in to an error state. (In order to get it running again, I have to set the state to active, then reboot the instance) I am not sure which logs will have the required information to help debug this issue, but I have looked through nova and cinder and keystone logs. Nothing I am seeing is obvious to me as to the cause of the failures. Also taking a snapshot seems to fail as well, with this error: Error: Unable to create snapshot. Details Invalid input received: Invalid volume: Volume e12b3ff8-9870-45f9-b59a-c6fb194ed517 status must be available, in-use, but current status is: attaching. (HTTP 400) (Request-ID: req-499d3bf9-97a0-48b2-8565-254a87287cff) (HTTP 400) (Request-ID: req-d0cd5aed-894e-40b2-8a2f-4b22188ec372) Looking at the volumes in my environment, both volumes show a status of "attaching" (both are for a test cirros instance, both are type nfs, and both instances seem to work just fine (meaning I can connect to them either on the console or via ssh and run commands without errors) Is the reason that each of those tasks is failing because of the "attaching" status of the volumes? I spun up the cluster using packstack and all the nodes are installed on Rocky Linux 9.4. I added an nfs backend after packstack was all done, and that does seem to be working, as the ephemeral volumes used to spin up the test instances does seem to be on the nfs storage, rather than the default lvm storage backend. I have installed openstack using the bobcat release of openstack (from the centos-openstack-bobcat repository). I have been crawling through the standalone install documentation to see if I can find something that explains why the instance migration isn't working, but, again, nothing is jumping out at me. Any guidance on where I should be looking, or advice on what I may be missing would be greatly appreciated.

4 10

upper-constraints (< $latest) considered harmful
by Stephen Finucane 20 Sep '24

20 Sep '24

o/ I'll jump straight into it. For those of you not in the loop we're currently going through a situation where it looks like OSC will be held back due to a bug that the Nova gates are highlighted. The actual details aren't hugely important, but what is important is the fact that this bug was first included in the OSC 7.0.0 release, which was released on August 6th. For those of you who are better at mental calendar maths than I am (or already looked at your calendar), you'll know this was over 6 weeks ago, well before the various feature freeze deadlines . and you might ask why did we only spot this last week? That would be because the upper-constraint (henceforth referred to as u-c) bump failed [1] due a different issue, meaning u-c kept us pinned at <= 6.6.1 which in turn meant every CI job *except* the ones running in the OSC gate itself kept testing the old release instead of the thing we were supposed to be released as part of Dalmatian. That only changed last week when 7.1.0 was released and the u-c bump for *that* merged [2], at which point people started shouting and hollering. Now, there is one other important consideration to factor into this, namely that, due to a flaw in our tooling, we didn't end up cutting a release branch for OSC alongside the rest of the client-library deliverables. Had we done so, we'd have seen 7.1.0 much earlier than we actually did [3]. That 7.1.0 release fixed the initial issue that prevented us releasing 7.0.0. However, this doesn't change the fact that 7.0.0 came out 6 weeks ago and not once did we get to test it outside of OSC's gate, and what's worse, we (the SDK team) were totally oblivious to the fact). Had it been known, we'd have cut a new release as soon as the fix [4] for that issue had merged (August 12th, which for the record is over 5 weeks ago). This is not the first time this has happened to us with one of our own dependencies. We had a very similar issue in Bobcat (2023.2) where we cut an oslo.db 13.0.0 release very early in that cycle, followed by a number of subsequent releases, only to have none of them end up making their way into u-c due to issues with some services. We then got to the end of the cycle, realized this, and had to do a frenzied mega revert to get us back to a pre-13.x state and allow us to release an oslo.db deliverable for Bobcat. It also happened with Castellan, whose 4.2.0 release sat waiting to merge for 4 months [4] before undergoing a similar mass revert. Adding more fuel to this fire, it's not just a problem with our own dependencies either. In fact, the problem is probably worse there. Need I remind people that it took 5 releases or 2 years, 8 months and change to uncap SQLAlchemy 2.x (a contributing factor in the oslo.db issue, fwiw). We had to struggle to get Sphinx uncapped in Bobcat [5] and fight to not revert that cap. You currently can't build docs for many projects on Fedora hosts since we're capping, among many other things, the Pillow library. The list goes on. Which brings me to my main points, of which there are three. Firstly: * There needs to be a clear time limit for how long a u-c bump can remain unmerged and a plan for what happens if affected projects have not resolved their issues within that time. There will always be exceptions - no one could rightly have asked services to switch to SQLAlchemy 2.x in a fortnight, and libraries can have legit bugs that justify a block - but those exceptions should be well-understood and, as with the bumps themselves, time-limited. A project that needs 4 releases to adapt to a crucial new library version is not a healthy project. secondly: * Caps or u-c bump reverts should similarly be clearly time-limited. We should not be defaulting to e.g re-capping Sphinx because your docs build has started to fail and then leaving that cap in place for months. Cap, fix the issue, and remove the cap asap. and, finally: * A failing u-c bump for an openstack deliverable should be treated with the highest priority 🚨🚨🚨 and should be something that the corresponding team should be made aware of immediately so they can start coordinating a resolution. We should not have u-c patches languishing for weeks, let alone months, only for there to be a last minute panic like this. I have ideas on the above (which basically warrant to more stick/[7]) but, perhaps fortunately, this isn't something I can decide on my own. Nor, should I add, is it something I expect the understaffed and oversubscribed release team to be able to do themselves. Instead, I think it's something that the TC and community as a whole need to settle on. So as soon as we get Dalmatian out the door, let's do that. Cheers, Stephen [1] https://review.opendev.org/c/openstack/requirements/+/925763 [2] https://review.opendev.org/c/openstack/requirements/+/928948 [3] https://review.opendev.org/c/openstack/releases/+/928838 [4] https://review.opendev.org/c/openstack/requirements/+/883141 [5] https://review.opendev.org/c/openstack/requirements/+/891694 [6] https://review.opendev.org/c/openstack/requirements/+/927102 [7] https://y.yarn.co/dbdc0d5b-04e6-4c39-9cd3-44c3be3729ab.mp4

8 9

[release] Release countdown for week R-1, Sep 23-27
by Elõd Illés 20 Sep '24

20 Sep '24

Development Focus ----------------- We are on the final mile of the 2024.2 Dalmatian development cycle! Remember that the 2024.2 Dalmatian final release will include the latest release candidate (for cycle-with-rc deliverables) or the latest intermediary release (for cycle-with-intermediary deliverables) available. September 26th, 2024 is the deadline for final 2024.2 Dalmatian release candidates as well as any last cycle-with-intermediary deliverables. We will then enter a quiet period until we tag the final release on October 2nd, 2024. Teams should be prioritizing fixing release-critical bugs, before that deadline. Otherwise it's time to start planning the 2025.1 Epoxy development cycle, including discussing PTG sessions content, in preparation of Project Teams Gathering. Actions ------- Watch for any translation patches coming through on the stable/2024.2 branch and merge them quickly. If you discover a release-critical issue, please make sure to fix it on the master branch first, then backport the bugfix to the stable/2024.2 branch before triggering a new release. Please drop by #openstack-release with any questions or concerns about the upcoming release ! Upcoming Deadlines & Dates -------------------------- Final 2024.2 Dalmatian release: October 2nd, 2024 Project Teams Gathering: October 21-25, 2024 Előd Illés irc: elodilles @ #openstack-release

1 0

[cinder] Retype encrypted cinder volume to non-encrypted volume
by Jan Wasilewski 20 Sep '24

20 Sep '24

Hi, I would like to ask about the procedure to retype a Cinder volume that is in-use (bootable volume, connected to a VM) from an encrypted (LUKS) type to a non-encrypted type (1000 IOPS). I tried to do this via the CLI[1], and while it seemed to work (at least according to the CLI output), the process didn’t complete successfully. Cinder logs[2] indicate that everything looks more or less fine: the volume is created, the volume migration is OK, and the retype is marked as completed. However, in the end, it doesn’t work (final output of [1]). I reviewed the blueprint at https://blueprints.launchpad.net/cinder/+spec/retype-encrypted-volume, which appears to be implemented. Am I doing something wrong, or does this functionality not work as expected? Thanks in advance for your help and guidance. /JW *[1] Retype from CLI: https://paste.openstack.org/show/bVpFT82oURnanXkixreT/ <https://paste.openstack.org/show/bVpFT82oURnanXkixreT/>[2] cinder-logs: https://paste.openstack.org/show/b5rZpWNMqdi6qdpjaDfg/ <https://paste.openstack.org/show/b5rZpWNMqdi6qdpjaDfg/>*

4 6

[glance] Still not working over uwsgi
by Thomas Goirand 20 Sep '24

20 Sep '24

Hi, I've been told in the past in this very list, that Glance would now work over uwsgi. Though that's not the case. Normal image upload works, but doing a "openstack server backup" fails, as well as shelving (it's the same operation...). We get: "Failed to upload image data due to HTTP error: webob.exc.HTTPRequestEntityTooLarge: Image storage media is full: Object PUT failed" even though the Swift user Glance is configured for isn't over quota. Is there any configuration options that we missed? Or should we still consider that Glance over uwsgi is broken? Cheers, Thomas Goirand (zigo)

3 2

[neutron] Drivers meeting canceled today and next Friday, September 27th
by Brian Haley 20 Sep '24

20 Sep '24

Hello Neutrinos: I'm going to cancel today's and next Friday's drivers meeting as there is no agenda and I have conflicts both days/times. We can spend the time making sure 2024.2 RC is in a good place :) Have a nice weekend! -Brian

1 0

[debian] Dalmatian release validated from the Debian point of view
by Thomas Goirand 20 Sep '24

20 Sep '24

Hi, This is probably a breaking record from my side: I've finished packaging even with all project not being tagged for RC1 ! :) Indeed, I have just finished running tempest on a new Dalmatian release today. Result is: no new tempest failure, so hopefully, no regression. Feel free to start consuming the Debian package of OpenStack for Dalmatian the usual way (for example with extrepo on Bookworm): extrepo enable openstack_dalmatian apt-get update I'll be uploading Dalmatian to Unstable in the next following days. This OpenStack release will be the one in Debian 13, aka Trixie. This will run under Python 3.13, so I'm getting ready to fix Python 3.13 bugs as soon as I can, both upstream and in Debian. Cheers, Thomas Goirand (zigo)

3 2

Farewell o/
by Mark Goddard 19 Sep '24

19 Sep '24

Dear OpenStack, Tomorrow will be my final day working at StackHPC before I move to a new role outside of the OpenStack community. My journey with OpenStack began at Cray 10 years ago, trying to coerce a very fresh Ironic project into managing a rack of PCs and resulting in the SNMP power driver [1]. Since then I moved to StackHPC where I've deployed and maintained many OpenStack systems of different sizes, generally with an element of High Performance Computing (HPC). I've been lucky enough to have had the opportunity to get involved in upstream OpenStack development. Over time I grew from contributor to Kolla & Ironic core to Kolla PTL for 5 cycles. I attended several summits and PTGs, and this really helped in working out how to navigate and get more involved in the community. More recently I have been more focussed on downstream than upstream work, but still marvel at the way so many people around the world come together to volunteer their time and effort to build complex software ecosystems. I'd like to thank everyone in this community who has helped me over the years. It really is a special place. To anyone standing on the sidelines wondering how to get more involved - speak up on IRC, join the PTG, triage bugs, review some code. It doesn't need to take up too much of your time. If you're like me you'll feel self-conscious at first, and unsure about the value you're providing. But keep at it, and over time you'll become an important part of the community. All the best, Mark [1] https://review.opendev.org/c/openstack/ironic/+/118404

8 7

[ironic] [neutron] [ptg] DHCP cross-project session?
by Jay Faulkner 19 Sep '24

19 Sep '24

HI all, Myself and CID from the GR-OSS team are planning on, community willing, adding a new, more reliable DHCP backend to both Ironic and Neutron. Right now, that looks like kea, but we are less concerned about the specific project as much as we are about it not being dnsmasq ( https://bugs.launchpad.net/ironic/+bug/2026757 ). Given neither of us are incredibly familiar with the Neutron codebase, we wanted to get buy in and some general implementation advice. As a note; if desired this can happen outside PTG, but this DHCP conversation is a PTG topic for Ironic so I thought this would be a good place to do it. -- Jay Faulkner

5 7

[Glance] Cancelling Weekly Meeting (Sept 19)
by Pranali Deore 18 Sep '24

18 Sep '24

Hi All, Cancelling today's glance meeting since there is nothing much on agenda & I will also not be around as I've Dr. appointment around the same time. Thanks & Regards, Pranali Deore

1 0

[all][elections][tc][ptl] 2025.1 Epoxy: Technical Committee & PTL Election Conclusion & Results
by Ian Y. Choi 18 Sep '24

18 Sep '24

Thank you to the electorate, to all those who supported and to all candidates who put their name forward for Technical Committee (TC) & Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. 1. Please join me in congratulating the 4 newly elected members of the Technical Committee (TC). Ghanshyam Mann (gmann) Jens Harbott (frickler) Sylvain Bauza (bauzas) Doug Goldstein (cardoe) Full results: https://civs1.civs.us/cgi-bin/results.pl?id=E_079cc0f0dda5010c 2. For the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant: Dale Smith (dalees) * Barbican: Grzegorz Grasza (xek) * Blazar: Pierre Riteau (priteau) * Cinder: Jon Bernard () * Cloudkitty: Rafael Weingartner () * Cyborg: alex song (songwenping) * Designate: Michael Johnson (johnsom) * Glance: Pranali Deore (pdeore) * Heat: Takashi Kajinami (tkajinam) * Horizon: Tatiana Ovchinnikova (tmazur) * Ironic: Riccardo Pittau (rpittau) * Keystone: Dave Wilde (d34dh0r53) * Kolla: Michal Nasiadka (mnasiadka) * Magnum: Jake Yip (jakeyip) * Manila: Carlos Silva (carloss) * Masakari: sam sue () * Monasca: Hasan Acar () * Neutron: Brian Haley (haleyb) * Nova: Sylvain Bauza (bauzas) * Octavia: Gregory Thiemonge (gthiemonge) * OpenStack Charms: James Page (jamespage) * OpenStack Helm: Vladimir Kozhukalov (kozhukalov) * OpenStackAnsible: Dmitriy Rabotyagov (noonedeadpunk) * OpenStackSDK: Artem Goncharov (gtema) * Puppet OpenStack: Takashi Kajinami (tkajinam) * Quality Assurance: Martin Kopec (kopecmartin) * Rally: Andrey Kurilin (andreykurilin) * Skyline: Wenxiang Wu (wu_wenxiang) * Storlets: Takashi Kajinami (tkajinam) * Sunbeam: Guillaume Boutry (gboutry) * Tacker: Yasufumi Ogawa (yasufum) * Telemetry: Erno Kuvaja (jokke_) * Trove: wu chunyang (wuchunyang) * Venus: Eric Zhang () * Vitrage: Dmitriy Rabotyagov (noonedeadpunk) * Zaqar: Hao Wang (wanghao) * Zun: Hongbin Lu () PTL Election: no election required. For remaining projects (without PTL candidates), TC will work on the appointment. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. Thank you, /Ian, an election official

2 1

[cinder] No meeting today (9/18)
by Jon Bernard 18 Sep '24

18 Sep '24

Hello all, there will be no meeting today (I have a conflict). If there is something that needs attention feel free to raise it in IRC or reach out directly. Thanks, -- Jon

1 0

[horizon][ironic][swift][qa] cycle-with-intermediary deliverables without recent release
by Elõd Illés 18 Sep '24

18 Sep '24

Hi, Quick reminder that for deliverables following the cycle-with-intermediary model, the release team will use the latest 2024 Dalmatian release available on release week. The following deliverables have done a 2024.2 Dalmatian release, but it was not refreshed in the last two months: * horizon * ironic-inspector * swift * tempest (Note that swift haven't had a release so far in this cycle) You should consider making a new one very soon, so that we don't use an outdated version for the final release. Thanks, Előd Illés irc: elodilles @ #openstack-release

2 1

[keystone] Weekly meeting cancelled 18-Sep-2024
by Dave Wilde 18 Sep '24

18 Sep '24

Hello, I’m on PTO today and will not be conducting the weekly meeting, please reach out on IRC/Matrix should you need anything. Thanks! /Dave

1 0

Volume Detachment issue
by Dipongkor Roy 18 Sep '24

18 Sep '24

Volume not detach from instance fc drive on storage nimble server. Can one help me with this? -- Regards, Dipongkor Roy Cloud Engineer PLEXUS CLOUD Dhaka, Bangladesh

1 0

[openstack][kolla-ansible]Collection ansible.posix does not support Ansible version 2.14.17
by Nguyễn Hữu Khôi 18 Sep '24

18 Sep '24

Hello/ I am deploying openstack 2023.1 with kolla customized images but I get this error: FAILED! => {"changed": false, "msg": "Can not parse the inner module output: b'[WARNING]: Collection ansible.posix does not support Ansible version 2.14.17\\n These images were built from kolla 16.5.1.dev1. Thank you. Nguyen Huu Khoi

4 6

Openstack projects
by engineer2024 18 Sep '24

18 Sep '24

Hi All, Can anyone pont me to some interesting openstack based projects which r not yet implemented and those which need improvement ? Any such websites, information etc.... Thanks elinux

2 1

Opensearch Service Update
by Daniel Pawlik 17 Sep '24

17 Sep '24

Hello, We would like to notify you that the Opensearch service [1] would be updated to a newer version on 17 September 2024 at 12: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

openstack-ansible
by engineer2024 17 Sep '24

17 Sep '24

In the playbook at https://opendev.org/openstack/openstack-ansible/src/branch/stable/2023.1/pl… , after the play "Basic host setup", it is going to the role 'apt_package_pinning' as shown below: --- PLAY [Gather host facts] ************************************************************************************************************************************************* META: ran handlers META: ran handlers META: ran handlers Read vars_file 'defaults/{{ install_method }}_install.yml' Read vars_file 'defaults/{{ install_method }}_install.yml' Read vars_file 'defaults/{{ install_method }}_install.yml' PLAY [Basic host setup] ************************************************************************************************************************************************** Read vars_file 'defaults/{{ install_method }}_install.yml' TASK [Check for a supported Operating System] **************************************************************************************************************************** task path: /opt/openstack-ansible/playbooks/openstack-hosts-setup.yml:54 container_name: "aio1" physical_host: "aio1" ok: [aio1] => { "changed": false, "msg": "All assertions passed" } [aio1] TASK: Check for a supported Operating System (debug)> c Read vars_file 'defaults/{{ install_method }}_install.yml' META: ran handlers Read vars_file 'defaults/{{ install_method }}_install.yml' TASK [apt_package_pinning : Add apt pin preferences] ********************************************************************************************************************* task path: /etc/ansible/roles/apt_package_pinning/tasks/main.yml:16 container_name: "aio1" ---- Why is it going to the apt pinning role, when it is not mentioned in the playbook anywhere ? Please explain.. Thanks elinux

2 2

[publiccloud-sig] Reminder - next meeting September 18th - 0700 UTC
by Felix Kronlage-Dammers 17 Sep '24

17 Sep '24

Hi everyone, This Wednesday (September 18th) the next meeting of the public cloud sig is going to happen. We’ll be meeting at 0700 UTC here: https://meetpad.opendev.org/publiccloud-sig <https://meetpad.opendev.org/publiccloud-sig> See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG <https://wiki.openstack.org/wiki/PublicCloudSIG> See you on Wednesday (-> tomorrow)! felix -- Felix Kronlage-Dammers Sovereign Cloud Stack — standardized, built and operated by many Ein Projekt der Open Source Business Alliance - Bundesverband für digitale Souveränität e.V. Tel.: +49-30-206539-205 | Matrix: @fkronlage:matrix.org | fkr(a)osb-alliance.com

1 0

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

16 Sep '24

Hello Stackers, This week, the community has been actively testing the release candidates from the 2024.2 release cycle [1]; you might notice projects re-spin their RCs if blocking bugs are reported. Our 2025.1 election season will conclude tomorrow, 2024-09-18. If you haven't already voted, please check your emails for a ballot [2]. There haven't been any governance changes made by the OpenStack Technical Committee this week. However, there are several proposals available for the community's review. === Weekly Meeting === Last week's meeting of the OpenStack Technical Committee was held on OFTC's #openstack-tc channel on 2024-09-10. The meeting logs are available on eavesdrop [3]. At this meeting, we started compiling a set of topics for the 2025.2 Project Teams' Gathering in October [4]. Please feel free to suggest any topics that may be of interest to you. Dr. Jens Harbott (frickler) shared a tracker organized by the release management team [5]. The tracker highlighted several projects where PTLs or release management liaisons had not reviewed releases for their projects. The release management team has the authority to tag releases of OpenStack software at any time, but it relies on the release liaisons (and Project Team Leads) to vet any release proposals that they make. If you are a Project Team Lead or a release liaison of an OpenStack deliverable that has releases, please take a look at the tracker and the guide on Liaison Responsibilities [6]. Your timely action will help ensure a smooth delivery process for the software you work on. The next meeting of the OpenStack TC is today, 2024-09-17, at 1800 UTC on OFTC's #openstack-tc channel. Please find the agenda for the meeting on the meeting wiki [7]. === Governance Proposals === ==== Open for review ==== - Add goal to migrate CI/CD jobs to Ubuntu Noble | https://review.opendev.org/c/openstack/governance/+/928078 - charms: retire unmaintained charms | https://review.opendev.org/c/openstack/governance/+/926793 - Appoint Tim Burke as PTL for Swift | https://review.opendev.org/c/openstack/governance/+/928881 - Add Axel Vanzaghi as PTL for Mistral | https://review.opendev.org/c/openstack/governance/+/927962 - Retire all single charm repositories | https://review.opendev.org/c/openstack/governance/+/903490 === Upcoming Events === - 2024-09-18: OpenStack 2025.1 Election Polling Ends - 2024-10-15: OpenInfra Days NA, Indianapolis: https://ittraining.iu.edu/explore-topics/titles/oid-iu/ - 2024-10-21: OpenInfra Project Teams Gathering https://openinfra.dev/ptg/ Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] Release Schedule: https://releases.openstack.org/dalmatian/schedule.html [2] Combined PTL/TC 2025.1 cycle Election Voting Last Days email: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… [3] TC Meeting IRC Log, 2024-09-10: https://meetings.opendev.org/meetings/tc/2024/tc.2024-09-10-18.00.log.html [4] 2025.1 OpenStack TC/PTG planning Etherpad: https://etherpad.opendev.org/p/oct2024-ptg-os-tc [5] Relmgmt Score Card for Project Teams: https://etherpad.opendev.org/p/r.68bf834e08ac22df93204808812cb166#L479 [6] Relmgmt Liaison Responsibilities: https://docs.openstack.org/project-team-guide/release-management.html#liais… [7] TC Meeting Agenda, 2024-09-17: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee

1 0

[tacker] Cancelling IRC meeting
by Yasufumi Ogawa 16 Sep '24

16 Sep '24

Hi tacker team, I'd like to skip IRC meeting this week since I'm out of office today. Thanks, Yasufumi

1 0

[dev][ptl][release] Cycle highlights reminder (2024.2/Dalmatian)
by Jeremy Stanley 16 Sep '24

16 Sep '24

Just a reminder in case anyone missed it: we're technically a week past the deadline for merging 2024.2/Dalmatian release highlights, but if anyone has something they want to mention then now is the time to write, push and approve it! The OpenInfra marketing machine is getting ready to digest what they find at https://releases.openstack.org/dalmatian/highlights.html and put together a press release and package for news outlets. They're interested in whatever you're excited to include, but especially anything related to AI, digital sovereignty, security, or VMware feature parity. Please get your remaining highlights in ASAP!!! -- Jeremy Stanley

1 0

[cloudkitty] Proposing Matt Crees as core reviewer
by Pierre Riteau 16 Sep '24

16 Sep '24

Hello, I would like to nominate Matt Crees as core reviewer for the CloudKitty project. He has been involved for around a year now and has provided valuable contributions, both as reviews and commits. He is also actively participating in our bi-weekly meetings. Cheers, Pierre Riteau (priteau)

2 1

[all][elections][ptl][tc] Combined PTL/TC 2025.1 cycle Election Voting Last Days
by Slawek Kaplonski 16 Sep '24

16 Sep '24

Hi, We are coming down to the last hours for voting in the TC elections. Voting ends Sep 18, 2024 23:45 UTC. Search your Gerrit preferred email address[0] for the messages with subjects like... Poll: OpenStack 2025.1 Cycle Technical Committee Election Poll That is your ballot and links you to the voting application. Please vote. If you have voted, please encourage your colleagues to vote. Candidate statements are linked to the names of all confirmed candidates: https://governance.openstack.org/election/ What to do if you don't see the email and have a commit in at least one of the official project teams' deliverable repositories[1]: * check the trash of your gerrit Preferred Email address[0], in case it went into trash or spam * find the ID of at least one commit merged to an official deliverable repo[1] over the current and previous cycles, confirm you are an OpenStack Foundation Individual Member[2], and then email the election officials[3] or get in touch in the #openstack-elections channel on the OFTC IRC network. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Please vote! Thank you, [0] Sign into review.openstack.org and go to Settings > Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. [1] https://opendev.org/openstack/governance/src/tag/to-be-released/reference/p… [2] https://www.openstack.org/profile/ [3] https://governance.openstack.org/election/#election-officials -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[sdk] possible bug in the openstacksdk/cloud?
by astepanov2007＠gmail.com 16 Sep '24

16 Sep '24

Hello, Recently, I was debugging an issue related to the ansible openstack.cloud.server module while creating an instance with floating ip attached. A part of stack trace goes below: ... File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_compute.py", line 1013, in create_server server = self.wait_for_server( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_compute.py", line 1153, in wait_for_server server = self.get_active_server( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_compute.py", line 1200, in get_active_server return self.add_ips_to_server( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_network_common.py", line 1412, in add_ips_to_server server = self._add_ip_from_pool( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_network_common.py", line 1247, in _add_ip_from_pool f_ip = self.create_floating_ip( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_network_common.py", line 765, in create_floating_ip return self._neutron_create_floating_ip( File "/home/user/venv/lib/python3.11/site-packages/openstack/cloud/_network_common.py", line 824, in _neutron_create_floating_ip network_id = network['id'] ~~~~~~~^^^^^^ TypeError: 'NoneType' object is not subscriptable Tracing this down to openstacksdk python module I have found a suspicious place in the openstacksdk code: if network_name_or_id: try: network = self.network.find_network(network_name_or_id) except exceptions.NotFoundException: raise exceptions.NotFoundException( "unable to find network for floating ips with ID " "{}".format(network_name_or_id) ) network_id = network['id'] https://github.com/openstack/openstacksdk/blob/de07fd02639eb565f10956b612ed… I suppose that this call to self.network.find_network lacks "ignore_missing=True" param. E.g.: network = self.network.find_network(network_name_or_id, ignore_missing=True) This fixed my issue with floating ips, but I'm not sure such patch is suitable for the mainline code of the openstacksdk. Am I correct? Regards, Alexander.

2 2

[neutron] Bug Deputy Report September 9 - 15
by Lucas Alvares Gomes 16 Sep '24

16 Sep '24

Hi, This is the Neutron bug report from September 9th to 15th. *High:* * https://bugs.launchpad.net/neutron/+bug/2080072 - "Failed to delete vpnaas ipsec-site-connections with 502 error, ORM session: SQL execution without transaction in progress" Unassigned * https://bugs.launchpad.net/neutron/+bug/2080199 - "Functional jobs failing with "Too many open files"" Assigned to: Lajos Katona * https://bugs.launchpad.net/neutron/+bug/2080447 - "Update firewall policy interface timeout when it's associated with a large number of rules " Assigned to: dongdong *Medium:* * https://bugs.launchpad.net/neutron/+bug/2080314 - "ML2 plugin: No consumers for q-agent-notifier-port-delete_fanout exchange result in unroutable RabbitMQ messages" Unassigned *Low:* * https://bugs.launchpad.net/neutron/+bug/2079996 - "[OVN] OVN metadata agent check to restart the HAProxy container" Assigned to: Rodolfo Alonso *Needs further triage:* * https://bugs.launchpad.net/neutron/+bug/2080492 - "[OVN] VIP port does not come up when its virtual-parents are trunk sub-ports" Cheers, Lucas

1 0

Re: Migratekit: near-live migrations from VMware to OpenStack
by Oliver Weinmann 13 Sep '24

13 Sep '24

Hi Mohammed, We struggled using virt-v2v directly with OpenStack. Our approach was using ovftool to export the VM as OVA and then create a qcow2 image that we can import in OpenStack. So many manual steps involved. So I tested your tool aganst vsphere 7.x vcenter. But I just can't manage to get it working. It keeps complaining about the path of the source VM. I can use the following just fine with virt-v2v: virt-v2v -v -x --password-file pass.txt -ic vpx:// user123(a)vcenter.somedomain.local /GE%Office%20One/Projects/esx01.somedomain.local?no_verify=1 test-vm-01 Using the same in your tool: docker run -it --rm --privileged \ -v /dev:/dev \ -v /usr/lib64/vmware-vix-disklib/:/usr/lib64/vmware-vix-disklib:ro \ --env-file <(env | grep OS_) registry.atmosphere.dev/library/migratekit:latest migrate \ --vmware-endpoint vcenter.somedomain.local \ --vmware-username user123 \ --vmware-password XXXXXX \ --vmware-path /GE%Office%20One/Projects/esx01.somedomain.local/test-vm-01 Results in: Error: vm '/GE%Office%20One/Projects/ esx01.somedomain.local/test-vm-01 ' not found I tried many different variants of the path none has worked. Is there a way to lookup the path of a VM? I can also use: virsh -c 'vpx:// user123(a)vcenter.somedomain.local /GE%Office%20One/Projects/esx01.somedomain.local?no_verify=1 list --all which shows me all VMs running on that particular ESXi host. Best Regards, Oliver

2 9

neutron
by Saeed 13 Sep '24

13 Sep '24

I run some scenarios with ML2/OVN and ML2/OVS (in all tests security-group has no rule) With the OVN backend, when port security is enabled I can NOT watch the unicast traffic of other instances by tcpdump, but when port security is disabled I can watch other unicast traffic for other instances. I also run the same scenarios when the backend is Openvswitch only (not OVN) I can watch unicast traffic of other instances (enabling or disabling port security has no impact). Is there any link or reference that explicitly explains this issue and the impact of OVN in OpenStack for dropping other traffic? I dump flow rules from openvswitch and compare them, and I'm pretty sure that the OVN adds some rules to drop other unicast traffic. Can I drop the unicast traffic of other instances in Openvswitch when I do not use OVN as the backend? (automatically or by configuration)

1 0

[neutron] OpenStack compute nodes L3 agent reconfiguration `dvr` mode to `dvr_no_external`
by frantisek.reznicek.szn＠gmail.com 13 Sep '24

13 Sep '24

Dear upstream OpenStack colleagues, we recently identified a lot of allocated "network:floatingip_agent_gateway ports" as we were running in pure dvr / dvr_snat modes (compute/network nodes) as also discussed in thread [1]. As we want to reduce amount of "network:floatingip_agent_gateway ports", our approach is to migrate majority of compute nodes from L3 agent `dvr` to `dvr_no_external` mode. Although we have success with empty nodes where we can see the node working as expected so north/south traffic now goes via network nodes on the non-empty compute nodes we struggle. The reconfiguration steps we are taking: 1. our maintenance per each compute node (still in `dvr` mode) 1.1. we first identify all VMs with FIP addresses, keep track of the FIPs and connected ports 1.2. we disconnect each FIP from port 1.3. all VMs on the compute node does not have FIPs 1.4. compute node L3 agent configuration is switched `dvr` -> `dvr_no_external` 1.5 delete `hypervisor network:floatingip_agent_gateway` port 1.6. re-attach all tracked FIPs 1.7. test FIP traffic At the step 1.7. we can see FIPs are not accessible after L3 agent re-configuration. Revert of the L3 agent configuration into `dvr` mode helps to get back the FIP connectivity. Our questions are: 1. Principally, can we get rid of `hypervisor network:floatingip_agent_gateway` ports by switching L3 agent to dvr_no_external mode? Can you think of a better way? 2. Would you recommend other steps how to migrate drom `dvr` to `dvr_no_external`? [2] Is it necesary to restart whole neutron / OVS or reconfigured L3 agent is just enough? Hope for your reply. ;-) Kind Regards, František [1] https://lists.openstack.org/pipermail/openstack-dev/2016-June/096384.html [2] https://opendev.org/openstack/neutron/src/branch/master/releasenotes/notes/…

3 2

[release] Release countdown for week R-2
by Thierry Carrez 13 Sep '24

13 Sep '24

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for all the 2024.2 Dalmatian deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/2024.2 branch creation for all deliverables that have not branched yet, using the latest available 2024.2 Dalmatian release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/2024.2 branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/2024.2 branch before releasing out of the stable/2024.2 branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for 2025.1 Epoxy development, though the focus should still be on finishing up 2024.2 (Dalmatian) until the final release. Opening up the new development cycle is also a good opportunity to teams to revise their zuul jobs and used nodesets and clean up all unnecessary ones. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final 2024.2 Dalmatian release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the 2024.2 Dalmatian version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: September 26th, 2024 (R-1 week) Final 2024.2 Dalmatian release: October 2nd, 2024 2025.1 Epoxy Project Teams Gathering: October 21-25, 2024 -- Thierry Carrez (ttx)

1 0

PTG October 2024 Teams List
by Kendall Nelson 12 Sep '24

12 Sep '24

Hello Everyone! The October 2024 Project Teams List is official! The following teams will be attending our Project Team Gathering, taking place October 21-25, 2024! Projects + Teams - OpenInfra Foundation Teams - - Diversity WG - Kata Containers - StarlingX - OpenStack - - Services - - Blazar - Cinder - CloudKitty - Designate - Glance - Horizon - Ironic - Keystone - Kolla - Manila - Neutron - Nova - Octavia - OpenStack-Ansible - OpenStack-Helm - QA - SDK/CLI - Sunbeam - Tacker - Other OpenStack Teams - OpenStack Security SIG - OpenStack Technical Committee - Public Cloud SIG - Adjacent Open Source Communities - - OceanBase If your team was planning to meet and isn’t in this list, please contact ptg(a)openinfra.dev IMMEDIATELY. Soon I will be contacting moderators to sign up for time via the PTGBot[1] once I have it configured for the teams that are signed up to attend the event. Otherwise, please don't forget to register[2] — its FREE! As usual, feel free to let us know if you have any questions! Thanks! [1] PTGBot Docs: https://github.com/openstack/ptgbot#open-infrastructure-ptg-bot [2] PTG Registration: http://ptg.openinfra.dev/

1 0

On pre-commit, black, ruff, ruff-format and everything else $linter related
by Stephen Finucane 12 Sep '24

12 Sep '24

o/ Seeing as we've been doing quite a bit of experimentation on this topic in the SDK team recently, and it's come up in random discussions a few times over recent days, I thought it might be helpful to share a few tips and tricks on how our linting stored has evolved across SDK deliverables. Hopefully it's helpful to someone. Historically, teams have provided a `pep8` tox target to run their linters. Originally this would have run flake8 or the hacking wrapper, but over the years these targets have expanded to cover other linters like bandit, doc8 and mypy, as well as various flake8 plugins. In recent times, we have been slowly introducing use of the pre-commit tool [1]. Initially this was purely additive, as it's a nice help for users working in a terminal (like me!) and mostly duplicated what was defined in the `pep8` target. This duplication led to issues where pre-commit was doing slightly different things from the `pep8` target, so we have evolved this so that the `pep8` target now simply calls pre-commit. This is pretty easy to do now since most if not all of the linters in common use across OpenStack - flake8, hacking, doc8, bandit, etc. - provides pre-commit hooks. I recommend anyone using pre-commit does the same thing otherwise these thing can drift. For example, your pep8 target can become: [testenv:pep8] description = Run style checks. skip_install = true deps = pre-commit commands = pre-commit run --all-files --show-diff-on-failure We've since evolved this further to start changing the linters we've used in general. We first introduced black [2], the automatic code formatting tool. The rationale behind this was to remove the need to even think about code style and focus on the actual semantic change. We're already overburdened, and going back and forth on style issues is a waste of everyone's time. Contributors (particularly new ones) can simply install pre-commit or use the `pep8` tox target and their code will be automatically restyled in a generally non- offensive manner. Is it perfect? No, but it's close enough that we've decided we don't care. When we have introduced black, we have typically kept the changes introduced by black separate from the changes to e.g. the `.pre-commit- config.yaml` or `tox.ini` file. This allows us to introduce a `.git-blame- ignore-revs` file afterwards which some software forges (like GitHub, though sadly not Gittea (yet!)) can use to ignore these bulk update changes when using `git-blame`. You can also configure git locally to ignore this, and I've made an effort to place comments in the files whenever I've added them. In addition to black, we also added other linters like bandit [3] and pyupgrade [4], including these in pre-commit so that they would run automatically on commit and in CI. However, as anyone reading the orange site or surveying the broader Python landscape might be aware, the ruff [5] linter and formatter has been gaining steam and is pretty mature at this point. In recent weeks, we have been migrating pretty much all our linters and formatters - black, pyupgrade, bandit and (most of) flake8 - to ruff and ruff-format. We have kept hacking but only enable the H (hacking) ruleset plus any custom rules for now, but at some point we will explore getting these few hacking rules into ruff or writing them off. In any case, this migration has resulted in a significantly trimmer pre- commit-config.yaml file (and much faster runtime to boot). You can see the end result on a repo like e.g. osc-lib [6]. All in all, I think I can recommend this approach for anyone interested in pursuing it. Linters are far from the most important aspect of development, but I've found these tools to yield a nice improvement in developer experience. Top tips: * Have your 'pep8' target (and any other linter-related target run 'pre-commit' rather than the linters themselves), and don't forget to remove linters from test-requirements.txt once you do (with the exception of hacking if you have custom hacking rules) * Consider using ruff and ruff-format in place of all non-hacking linters/formatters: it's seriously fast and provides rules to cover most of these. * When applying ruff-format or the UP (pyupgrade) ruff rules, do it separately so you can add the commit ID to a .git-blame-ignore-revs file. You should be able to do this pre-merge since Gerrit/Zuul merge patches rather than rebasing them so the commit ID won't change. Other points: * When we first introduced pre-commit, some people noted that installing from Git rather than PyPI introduced a possible attack vector since tags can be changed. Given we only use a small, curated set of linters from trusted sources, I don't know how much of an issue this is but I'll raise it here. * Difficulty backporting code has been highlighted as an blocker for running a formatter like black or ruff-format. We don't do many backports in SDK, OSC etc. so this hasn't been a huge issue. If it were though, we would simply apply the formatter to the stable branch first before backporting. Hope this helps, Stephen [1] https://pre-commit.com/ [2] https://github.com/psf/black [3] https://github.com/PyCQA/bandit [4] https://github.com/asottile/pyupgrade [5] https://github.com/astral-sh/ruff [6] https://opendev.org/openstack/osc-lib/

3 3

[horizon] Weekly meeting cancelled Sept 18
by Tatiana Ovchinnikova 11 Sep '24

11 Sep '24

Hello team, I'm on PTO next week, so I'm cancelling the weekly meeting on September 18. See you on September 25! Regards, Tatiana

1 0

[kolla] Proposing Sven Kieske as Kolla and Kolla-Ansible core
by Michał Nasiadka 11 Sep '24

11 Sep '24

Hello Koalas, I would like to propose Sven Kieske as a core reviewer for Kolla and Kolla-Ansible Sven has been very active and providing insightful feedback to reviews as well as code contributions. If I won’t receive any negative votes until 11th of September - I’ll add Sven in Gerrit on the Kolla weekly meeting on that day. Thanks! Michał Nasiadka mnasiadka(a)gmail.com

7 7

[API] Gitea API return 404
by tzing0013＠gmail.com 10 Sep '24

10 Sep '24

Hi everyone， I'm testing Gitea API, I visit the web[1], and click "Try is out", no matter what I enter there, it returns 404, and I also test "/contents" [2], that's ok. [1] https://opendev.org/api/swagger#/repository/repoListPullRequests [2] https://opendev.org/api/swagger#/repository/repoGetContentsList

2 4

[openstack-ansible]: Move one control node to different chasis
by Ram Ram 10 Sep '24

10 Sep '24

Hi All We are currently running 3 control nodes with LXC containers deployed using openstack-ansible release ussuri and need to move 1 control node on HP blade from one chasis to another chasis. Is there any recommended way/procedure to do that? can we directly move the HP blade from one chasis to another? or we need to install new control node and decommission the older one? Regards Rambo

3 3

[kolla][vpn-as-a-service] docker container missing
by garcetto 10 Sep '24

10 Sep '24

good afternoon, installed all-in-one ubuntu 22.04 based kolla-ansible version 2024.1, so far so good. tried to enable vpnaas, folllowing the instructions here https://docs.openstack.org/kolla-ansible/2024.1/reference/networking/neutro… but still missing the container "neutron_vpnaas_agent". i checked the ansible playbook but see no evidence of deployment of this container, what am i doing wrong? thank you.

3 2