February 2025 - openstack-discuss

[nova] Wondering about dynamic overcommit scheduling
by Jacquet, Pierre 10 Feb '25

10 Feb '25

Hello, I am exploring the potential for resource consolidation from the initial placement perspective, specifically within the filter scheduler. From my research, I understand that OpenStack Watcher can addresses consolidation in a dynamic manner (monitoring resource usage and using live migration), while consolidation in nova seems to rely on a static overcommitment ratio, without accounting for real resource usage. Has dynamic overcommitment been considered for the initial placement phase? If not, I would like to propose implementing such a feature and would greatly appreciate any feedback or guidance from the community on this idea. Specifically, a custom filter could be interfaced with a monitoring stack to deploy servers as long as some thresholds are not exceeded Thank you for your time and input. Best regards, Pierre

3 2

[kolla-ansible] stuck at Discover nova hosts
by Satish Patel 08 Feb '25

08 Feb '25

Folks, I am deploying kolla-ansible 2024.1 but somehow it has been stuck here for the last 2 hours not giving me any kind of clue or error even when I run in -vvvv mode. Any idea what it's trying to discover and why there is no timeout for this task? TASK [nova-cell : Fail if cell settings not found] ************************************************************************************************************************ task path: /usr/local/share/kolla-ansible/ansible/roles/nova-cell/tasks/discover_computes.yml:7 skipping: [os-chn-gen-comp-001] => { "changed": false, "false_condition": "not nova_cell_settings", "skip_reason": "Conditional result was False" } TASK [nova-cell : Discover nova hosts] ************************************************************************************************************************************ task path: /usr/local/share/kolla-ansible/ansible/roles/nova-cell/tasks/discover_computes.yml:14 Using module file /usr/local/lib/python3.10/dist-packages/ansible/modules/command.py Pipelining is enabled. <os-chn-ctrl01> ESTABLISH SSH CONNECTION FOR USER: None <os-chn-ctrl01> SSH: EXEC ssh -C -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o 'ControlPath="/root/.ansible/cp/eaac57fe12"' os-chn-ctrl01 '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-pnxqbtjwqxuxexfjfrnpukckzrfbkegh ; /usr/bin/python3'"'"'"'"'"'"'"'"' && sleep 0'"'"'' Escalation succeeded

2 1

[release] Release countdown for week R-7
by Thierry Carrez 07 Feb '25

07 Feb '25

Development Focus ----------------- We are entering the last weeks of the 2025.1 Epoxy development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-AC freeze, in preparation for elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Contributor and allowed to vote. This is done by adding extra-acs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-AC freeze on February 13th. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * Oslo libraries are entering feature freeze next week, February 13th. * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (February 20th). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 27th) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, February 27th. Any feature addition beyond that date should be discussed on the mailing list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (March 14th) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (March 28th) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to one week after Feature freeze (March 6th). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… jeremy [at] openstack.org/fungi on IRC is available if you need help selecting or writing your highlights. Upcoming Deadlines & Dates -------------------------- Extra-AC freeze: February 13th (R-7 week) Oslo feature freeze: February 13th (R-7 week) Non-client library freeze: February 20th (R-6 week) Client library freeze: February 27th (R-5 week) epoxy-3 milestone: February 27th (R-5 week) Cycle highlights deadline: March 6th (R-4 week) -- Thierry Carrez (ttx)

1 0

[openstack-ansible][masakari][yoga]pcs cluster not getting started
by Danish Khan 07 Feb '25

07 Feb '25

Dear All, I have upgraded my openstack cluster from wallaby to Yoga. And I am facing issue with masakari services. pacemaker service is running fine on all nodes but pacemaker_remote.service is not getting started on any of the nodes. And Masakari containers doesn't have any idea of it monitor nodes. I purged the masakari cluster and tried to deploy it again. Playbook is running successfully again and again but it is not setting up the cluster. Playbook is not installing corosync service on masakari containers and now pacemaker server is also not getting installed on masakari api containers. I idea to run masakari in a way that it can create the cluster and install required services on its own? I tried with below but that did not work:

1 2

[Monasca][Masakari][Requirements] Migrate of of oslosphinx
by Tony Breeds 07 Feb '25

07 Feb '25

Hello all, This is a heads up to let you know that the requirements team have approved 940215: Drop oslosphinx | https://review.opendev.org/c/openstack/requirements/+/940215 which will mean any changes to Monasca or Masakari that touch a requirements file will fail. The solution is to remove your dependency on oslosphinx, as many projects have done this I expect there is plenty of knowledge in git epos for what needs to be done. In the short term if your gate is blocked you can land a change that switches check-requirements to non-voting -- Yours Tony.

1 0

[neutron] Drivers meeting canceled Friday, February 7th
by Brian Haley 07 Feb '25

07 Feb '25

Hello Neutrinos: I'm going to cancel tomorrow's drivers meeting as there is no agenda. Just a reminder there are still open specs that need review, list is at [0]. Have a nice weekend! -Brian [0] https://review.opendev.org/q/status:open+project:openstack/neutron-specs

1 0

Having troubles with Mistral.
by Alvin Starr 07 Feb '25

07 Feb '25

I am trying to use Mistral to create a VM and I cannot seem to find the appropriate parameters. Here is part of my workflow. tasks: create_instance: action: nova.servers_create input: name: <% $.vm_name %> image: <% $.image %> flavor: <% $.flavor %> nics: - net-id: <% $.network %> key_name: <% $.keypair %> disk_config: AUTO availability_zone: nova meta: status: "pending" # Initial metadata value publish: instance_id: <% task(create_instance).result.id %> on-success: - get_vm_details I seem to keep getting a no suitable hypervisor found error. I have checked and i am sure I am not running into any resource constraints. any help or pointers would be greatly appreciated. -- Alvin Starr || land: (647)478-6285 Netvel Inc. || home: (905)513-7688 alvin(a)netvel.net ||

2 2

[nova][elections][ptl] Leaving my seat
by Sylvain Bauza 07 Feb '25

07 Feb '25

Hey Nova-ers That's a bit bittersweet but after running as a Nova PTL for 7 cycles, I preferred to leave this seat as I no longer have a lot of time for this. I'll continue to be around and I'll help our next PTL for sure :-) Thanks and see you at the PTG anyway :-) -Sylvain

2 1

[deployment] Is there a ranked list of automated deployment technologies (based on production usage)?
by Jordan Olin (OLINSolutions) 06 Feb '25

06 Feb '25

Hello, I’m trying to narrow my deployment focus on the most commonly used OpenStack automated deployment technologies/approaches. Does a ranked list or previous recent survey exist of currently available deployment automation solutions? If not, what is the correct approach for me to take to collect something like this? Thank you, Jordan. =========================== Jordan Olin, TOGAF EA President and Chief Solutioneer OLINSolutions, Inc. e: jordan(a)olinsolutions.com p: +1 508-982-4872 w: olinsolutions.com This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. This communication may contain material protected by government legislation. If you are not the intended recipient or the person responsible for delivering this email to the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender by replying to this email and then delete the email from your computer.

2 1

[openstack-ansible] Relocate ceph-mons to new hosts and decouple Ceph from openstack-ansible
by Jan Marquardt 06 Feb '25

06 Feb '25

Hi, We run a cluster with ~15 compute hosts and ~25 Ceph nodes. Everything was initially deployed with openstack-ansible. For some reasons we would like to decouple Ceph from openstack-ansbile and therefore move the ceph-mon containers to dedicated hosts. - Moving the containers seems straightforward, but how do we tell openstack-ansible that the containers are gone and that it can’t use the ip addresses anymore for other purposes? - How do we tell openstack-ansible which keyrings it has to deploy on compute hosts? Any recommendations? Has anyone done this before? Can you think of anything else that should be considered? Thanks in advance and best regards Jan

2 1