April 2025 - Release-announce - lists.openstack.org

placement 11.0.1 (caracal)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We are glad to announce the release of: placement 11.0.1 This release is part of the caracal release series. The source is available from: https://opendev.org/openstack/placement Download the package from: https://pypi.org/project/placement Please report issues through: https://storyboard.openstack.org/#!/project/openstack/placement For more details, please see below. 11.0.1 ^^^^^^ Bug Fixes * In a deployment with wide and symmetric provider trees, i.e. where there are multiple children providers under the same root having inventory from the same resource class (e.g. in case of nova's mdev GPU or PCI in Placement features) if the allocation candidate request asks for resources from those children RPs in multiple request groups the number of possible allocation candidates grows rapidly. E.g.: * 1 root, 8 child RPs with 1 unit of resource each a_c requests 6 groups with 1 unit of resource each => 8*7*6*5*4*3=20160 possible candidates * 1 root, 8 child RPs with 6 unit of resources each a_c requests 6 groups with 6 unit of resources each => 8^6=262144 possible candidates Placement generates these candidates fully before applying the limit parameter provided in the allocation candidate query to be able do a random sampling if "[placement]randomize_allocation_candidates" is True. Placement takes excessive time and memory to generate this amount of allocation candidates and the client might time out waiting for the response or the Placement API service run out of memory and crash. To avoid request timeout or out of memory events a new "[placement]max_allocation_candidates" config option is implemented. This limit is applied not after the request limit but *during* the candidate generation process. So this new option can be used to limit the runtime and memory consumption of the Placement API service. The new config option is defaulted to "-1", meaning no limit, to keep the legacy behavior. We suggest to tune this config in the affected deployments based on the memory available for the Placement service and the timeout setting of the clients. A good initial value could be around "100000". If the number of generated allocation candidates is limited by the "[placement]max_allocation_candidates" config option then it is possible to get candidates from a limited set of root providers (e.g. compute nodes) as placement uses a depth-first strategy, i.e. generating all candidates from the first root before considering the next one. To avoid this issue a new config option "[placement]allocation_candidates_generation_strategy" is introduced with two possible values: * "depth-first", generates all candidates from the first viable root provider before moving to the next. This is the default and this triggers the old behavior * "breadth-first", generates candidates from viable roots in a round-robin fashion, creating one candidate from each viable root before creating the second candidate from the first root. This is the possible behavior. In a deployment where "[placement]max_allocation_candidates" is configured to a positive number we recommend to set "[placement]allocation_candidates_generation_strategy" to "breadth- first". (https://bugs.launchpad.net/nova/+bug/2070257) Changes in placement 11.0.0..11.0.1 ----------------------------------- b798523e Add round-robin candidate generation strategy dc4ffdc4 Factor out allocation candidate generation strategy 47ee16bd Add a global limit on the number of allocation candidates af00c864 Update TOX_CONSTRAINTS_FILE for stable/2024.1 f2452734 Update .gitreview for stable/2024.1 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + placement/conf/placement.py | 67 +++++++- placement/objects/allocation_candidate.py | 142 +++++++++------ placement/objects/research_context.py | 4 + .../unit/objects/test_allocation_candidate.py | 57 +++++++ placement/util.py | 13 ++ ...n-limit-and-strategy.yaml-e73796898163fb55.yaml | 63 +++++++ tox.ini | 2 +- 10 files changed, 506 insertions(+), 61 deletions(-)

1 0

octavia 14.0.1 (caracal)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We are glad to announce the release of: octavia 14.0.1 This release is part of the caracal release series. The source is available from: https://opendev.org/openstack/octavia Download the package from: https://pypi.org/project/octavia Please report issues through: https://storyboard.openstack.org/#!/project/908 For more details, please see below. 14.0.1 ^^^^^^ Bug Fixes * Fixed an issue updating listeners when using SR-IOV VIP ports. * Fixed a bug in the VIP SR-IOV implementation that would cause load balancer memebers that use the SR-IOV VIP interface to not receive traffic. * Fixed error on update UDP Health Monitor with empty "delay" parameter * Fixed an issue when failing over load balancers using SR-IOV VIP ports. * Fixed an issue when a failover reverts, a neutron port may get abandoned. The issue was logged with "Failed to delete port", "Resources may still be in use for a port intended for amphora", and "Search for a port named octavia-lb-vrrp-<uuid>". * Fix the issue, when "limit" parameter in request less or equal 0. Now it returns resources according pagination_max_limit as expected, instead of error. * Remove record in amphora_health table on revert. It's necessary, because record in amphora table for corresponding amphora also deleted. It allows to avoid false positive react of failover threshold due to orphan records in amphora_health table. * Fixed potential AttributeError during listener update when security group rule had no protocol defined (ie. it was null). * Added a validation step in the batch member API request that checks if a member is included multiple times in the list of updated members, this additional check prevents the load balancer from being stuck in PENDING_UPDATE. Duplicate members in the batch member flow triggered an exception in Taskflow. The API now returns 400 (ValidationException) if a member is already present in the body of the request. * Fixed an issue when filtering resources with a boolean attribute in the GET calls in the Octavia API. * Fixed a bug when creating a load balancer and a listener with "allowed_cidrs" with the fully-populated load balancer API, the call was rejected because Octavia could not validate that the IP addresses of the "allowed_cidrs" have the same family as the VIP address. * Fixed an issue with SINGLE topology load balancer with UDP listeners, the Amphora now sends a Gratuitous ARP packet when a UDP pool is added, it makes the VIP address more quickly reachable after a failover or when reusing a previously allocated IP address. * Fix load balancer stuck in PENDING_DELETE if TLS storage unavailable or returns error * Fix verification of certificates signed by a private CA when using Neutron endpoints. * Fix error on revert PlugVIPAmphora task, when db_lb is not defined and get_subnet raises NotFound error. It could happen when Amphora creation failed by timeout and before it VIP network was removed. As result revert failed with exception. * Fixed a bug with the *nopreempt* option in keepalived. The option didn't work properly because the default role of the *MASTER* amphora was set. Removing the default roles from the configuration files fixed that issue. Now after a failover, the newly created amphora doesn't preempt the *MASTER* role from the other amphora. Changes in octavia 14.0.0..14.0.1 --------------------------------- 2c2f0d328 Fix incorrect filtering when using bool attrs 6e1b00a8e Fix test_prometheus_proxy.test_main 9c33604ae Fixed VRRP nopreempt option 1338f29d2 Fix port abandonment on failover flow revert e5e462c6e Update stable/2024.1 to use 2024.1 tests 6edc3f274 Fix verification of certificates signed by a private CA 11515cdd4 Fix missing GARP with UDP listeners on SINGLE LB a97dcca94 curl-minimal conflicts with already installed curl 1e1301ff8 Don't install firewalld in the amphora 2e4a03e5c Remove amphora_health record on revert CreateAmphoraInDB efe3ee865 Handle undefined protocol field in security group rules correctly 5a039fcd9 Do not fail on revert PlugVIPAmphora due undefined db_lb 87f5d0a4c Fix amphora image builds to use DIB bindep e5a9a9538 Fix SR-IOV when VIP interface is used for members 2733a6766 Fix failover when using SRIOV VIP 3af5401b8 Fix loadbalancer stuck in cascade delete b61c340b0 Add check for duplicate members in batch update c704267c5 Fix listener update when using SRIOV VIP b370e46c1 Pin pylint on 2024.1 32df43144 Removing tips jobs on stable/2024.1 8d1998299 Fix fully-populated API with allowed_cidrs 1945df32d Fix negative or 0 limit parameter in pagination 8b4e9e731 Handle empty delay on update healthmonitor 6b11062d3 Update TOX_CONSTRAINTS_FILE for stable/2024.1 894023ec9 Update .gitreview for stable/2024.1 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + elements/amphora-agent/package-installs.yaml | 4 + elements/amphora-agent/pkg-map | 1 - .../amphora-agent/source-repository-amphora-agent | 4 +- .../static/usr/local/bin/lvs-masquerade.sh | 62 +++++++++------ elements/octavia-lib/source-repository-octavia-lib | 2 +- .../backends/agent/api_server/keepalivedlvs.py | 9 +++ .../amphorae/backends/agent/api_server/osutils.py | 6 +- octavia/amphorae/backends/agent/api_server/plug.py | 9 ++- .../amphorae/backends/agent/api_server/server.py | 5 +- octavia/amphorae/backends/agent/api_server/util.py | 37 ++++++++- octavia/amphorae/backends/utils/interface.py | 39 +--------- octavia/amphorae/backends/utils/interface_file.py | 33 +++++--- octavia/amphorae/backends/utils/nftable_utils.py | 44 ++++++++--- .../amphorae/drivers/keepalived/jinja/jinja_cfg.py | 1 - .../jinja/templates/keepalived_base.template | 1 - octavia/api/common/pagination.py | 2 +- octavia/api/v2/controllers/health_monitor.py | 4 +- octavia/api/v2/controllers/load_balancer.py | 7 ++ octavia/api/v2/controllers/member.py | 14 +++- octavia/common/clients.py | 8 +- octavia/common/constants.py | 6 +- octavia/controller/worker/v2/controller_worker.py | 4 +- .../controller/worker/v2/flows/amphora_flows.py | 17 +++- octavia/controller/worker/v2/flows/flow_utils.py | 10 ++- .../controller/worker/v2/flows/listener_flows.py | 22 ++++-- .../controller/worker/v2/tasks/database_tasks.py | 16 ++-- .../controller/worker/v2/tasks/network_tasks.py | 25 +++--- octavia/db/base_models.py | 20 ++++- .../drivers/neutron/allowed_address_pairs.py | 5 +- .../backend/agent/api_server/test_server.py | 2 +- .../backends/agent/api_server/test_osutils.py | 2 +- .../backends/agent/api_server/test_plug.py | 7 +- .../backends/agent/api_server/test_util.py | 90 ++++++++++++++++++++- .../unit/amphorae/backends/utils/test_interface.py | 67 +--------------- .../amphorae/backends/utils/test_nftable_utils.py | 50 ++++++------ .../drivers/keepalived/jinja/test_jinja_cfg.py | 4 - .../worker/v2/flows/test_listener_flows.py | 25 +++--- .../worker/v2/flows/test_load_balancer_flows.py | 10 +-- .../worker/v2/tasks/test_database_tasks.py | 34 ++++++-- .../worker/v2/tasks/test_network_tasks.py | 59 +++++++++++++- .../controller/worker/v2/test_controller_worker.py | 57 +++++++++++++- .../drivers/neutron/test_allowed_address_pairs.py | 3 +- playbooks/image-build/run.yaml | 52 ++----------- ...ner-Update-for-SRIOV-VIPs-8348b7fe0c02b9c4.yaml | 4 + ...rface-is-used-for-members-adb150ece454ecff.yaml | 5 ++ ...itor-update-without-delay-c56240e59e15483f.yaml | 4 + ...x-failover-for-SRIOV-VIPs-e2ab193c0de5eb1d.yaml | 4 + ...failover-revert-port-leak-d9879523506c6ff3.yaml | 7 ++ ...nation-less-or-equal-zero-93a33f1318ea34e5.yaml | 6 ++ ...lth_row_on_amphora_revert-082f94459ecacaa2.yaml | 7 ++ ...up-rule-has-protocol-none-9b7217c5477d01b6.yaml | 5 ++ ...e-members-in-batch-update-610ffbbf949927d0.yaml | 10 +++ ...g-with-boolean-attributes-15df51820753a900.yaml | 5 ++ ...ulated-with-allowed-cidrs-ad04ccf02bf9cbbc.yaml | 7 ++ ...ix-garp-for-udp-listeners-6bf2ec8d491d1e1b.yaml | 7 ++ ...dbalancer-stuck-on-delete-da5950cf87fc8507.yaml | 5 ++ ...te-ca-signed-certificates-b9386a0d92627b03.yaml | 5 ++ ..._db_lb_on_plug_vip_revert-5c24af124498b246.yaml | 7 ++ ...ault-role-from-keepalived-c879bad3a42a6b4a.yaml | 8 ++ test-requirements.txt | 2 +- tox.ini | 8 +- zuul.d/jobs.yaml | 91 ++++++++++++++++++++-- zuul.d/projects.yaml | 38 +++++---- 68 files changed, 902 insertions(+), 351 deletions(-) Requirements updates -------------------- diff --git a/test-requirements.txt b/test-requirements.txt index fa31c123f..6f9f2cb36 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -11 +11 @@ oslotest>=3.2.0 # Apache-2.0 -pylint>=2.5.3 # GPLv2 +pylint>=2.5.3,<3.2.0 # GPLv2

1 0

python-cloudkittyclient 4.8.1 (bobcat)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We eagerly announce the release of: python-cloudkittyclient 4.8.1 This release is part of the bobcat release series. The source is available from: https://opendev.org/openstack/python-cloudkittyclient Download the package from: https://pypi.org/project/python-cloudkittyclient Please report issues through: https://storyboard.openstack.org/#!/project/openstack/python- cloudkittyclient For more details, please see below. 4.8.1 ^^^^^ Bug Fixes * Fixed a bug where creating a reprocessing task would fail due to sending a POST request to the wrong endpoint. Changes in python-cloudkittyclient 4.8.0..4.8.1 ----------------------------------------------- c151d6b Fix reprocessing POST request 61d7fce Update TOX_CONSTRAINTS_FILE for stable/2023.2 f34ec5a Update .gitreview for stable/2023.2 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + cloudkittyclient/v2/reprocessing.py | 4 +--- .../notes/fix-reprocessing-post-request-95512686754ee271.yaml | 5 +++++ tox.ini | 4 ++-- 4 files changed, 9 insertions(+), 5 deletions(-)

1 0

placement 12.0.1 (dalmatian)
by no-reply＠openstack.org 17 Apr '25

17 Apr '25

We exuberantly announce the release of: placement 12.0.1 This release is part of the dalmatian release series. The source is available from: https://opendev.org/openstack/placement Download the package from: https://pypi.org/project/placement Please report issues through: https://storyboard.openstack.org/#!/project/openstack/placement For more details, please see below. 12.0.1 ^^^^^^ Bug Fixes * In a deployment with wide and symmetric provider trees, i.e. where there are multiple children providers under the same root having inventory from the same resource class (e.g. in case of nova's mdev GPU or PCI in Placement features) if the allocation candidate request asks for resources from those children RPs in multiple request groups the number of possible allocation candidates grows rapidly. E.g.: * 1 root, 8 child RPs with 1 unit of resource each a_c requests 6 groups with 1 unit of resource each => 8*7*6*5*4*3=20160 possible candidates * 1 root, 8 child RPs with 6 unit of resources each a_c requests 6 groups with 6 unit of resources each => 8^6=262144 possible candidates Placement generates these candidates fully before applying the limit parameter provided in the allocation candidate query to be able do a random sampling if "[placement]randomize_allocation_candidates" is True. Placement takes excessive time and memory to generate this amount of allocation candidates and the client might time out waiting for the response or the Placement API service run out of memory and crash. To avoid request timeout or out of memory events a new "[placement]max_allocation_candidates" config option is implemented. This limit is applied not after the request limit but *during* the candidate generation process. So this new option can be used to limit the runtime and memory consumption of the Placement API service. The new config option is defaulted to "-1", meaning no limit, to keep the legacy behavior. We suggest to tune this config in the affected deployments based on the memory available for the Placement service and the timeout setting of the clients. A good initial value could be around "100000". If the number of generated allocation candidates is limited by the "[placement]max_allocation_candidates" config option then it is possible to get candidates from a limited set of root providers (e.g. compute nodes) as placement uses a depth-first strategy, i.e. generating all candidates from the first root before considering the next one. To avoid this issue a new config option "[placement]allocation_candidates_generation_strategy" is introduced with two possible values: * "depth-first", generates all candidates from the first viable root provider before moving to the next. This is the default and this triggers the old behavior * "breadth-first", generates candidates from viable roots in a round-robin fashion, creating one candidate from each viable root before creating the second candidate from the first root. This is the possible behavior. In a deployment where "[placement]max_allocation_candidates" is configured to a positive number we recommend to set "[placement]allocation_candidates_generation_strategy" to "breadth- first". (https://bugs.launchpad.net/nova/+bug/2070257) Changes in placement 12.0.0..12.0.1 ----------------------------------- 828b2559 Add round-robin candidate generation strategy 1b0a9272 Factor out allocation candidate generation strategy f276fc23 Add a global limit on the number of allocation candidates 901dc827 Update TOX_CONSTRAINTS_FILE for stable/2024.2 0ede4513 Update .gitreview for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- .gitreview | 1 + placement/conf/placement.py | 67 +++++++- placement/objects/allocation_candidate.py | 142 +++++++++------ placement/objects/research_context.py | 4 + .../unit/objects/test_allocation_candidate.py | 57 +++++++ placement/util.py | 13 ++ ...n-limit-and-strategy.yaml-e73796898163fb55.yaml | 63 +++++++ tox.ini | 2 +- 10 files changed, 506 insertions(+), 61 deletions(-)

1 0

puppet-designate 26.0.0 (epoxy)
by no-reply＠openstack.org 16 Apr '25

16 Apr '25

We are amped to announce the release of: puppet-designate 26.0.0 This release is part of the epoxy release series. The source is available from: https://opendev.org/openstack/puppet-designate Download the package from: https://tarballs.openstack.org/puppet-designate/ Please report issues through: https://bugs.launchpad.net/puppet-designate/+bugs For more details, please see below. Changes in puppet-designate 25.0.0..26.0.0 ------------------------------------------ 262a358 Fix version number for epoxy release 0fa0fd4 Bump Ubuntu version 010e2e9 Prepare 2025.1 release a0c795c Add a rabbit_transient_queues_ttl and amqp_auto_delete params 093c129 Fix new lint errors 56e9ea9 Fix assertion of heartbeat_in_pthread parameter 661288b Deprecate support for [oslo_messaging_rabbit] heartbeat_in_pthread 5b3bfe0 Stop using absolute names for defined resource types 2f464e9 Mark puppet 8 supported b80aa36 bind9: Make rndc options optional aff99fc reno: Update master for unmaintained/2023.1 7d5d39f mdns: Add support for [service:mdns] tcp_keepidle 2aea380 Expose configure_service 879a0a0 Update master for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- example/all-in-one-noauth.pp | 2 +- manifests/backend/bind9.pp | 10 +++--- manifests/db/mysql.pp | 2 +- manifests/db/postgresql.pp | 2 +- manifests/init.pp | 41 ++++++++++++++++------ manifests/keystone/auth.pp | 6 ++++ manifests/keystone/authtoken.pp | 2 +- manifests/mdns.pp | 6 ++++ manifests/producer.pp | 2 +- manifests/wsgi/apache.pp | 2 +- metadata.json | 12 +++---- .../notes/amqp_auto_delete-b5c8adf45591c917.yaml | 5 +++ .../notes/configure_service-42a7bc042a86a946.yaml | 5 +++ ...bbit_heartbeat_in_pthread-efd1ff77b7816503.yaml | 5 +++ .../notes/mdns-tcp_keepidle-d358daa4768b3ed3.yaml | 4 +++ releasenotes/notes/puppet-8-c37cfff2cbe4294a.yaml | 4 +++ ...bbit_transient_queues_ttl-60aa2aed9724e5ba.yaml | 6 ++++ .../notes/rndc-optional-303e6561b611d0d1.yaml | 8 +++++ .../notes/ubuntu-noble-6bfcfc2c716003b8.yaml | 8 +++++ releasenotes/source/2023.1.rst | 2 +- releasenotes/source/2024.2.rst | 6 ++++ releasenotes/source/index.rst | 1 + spec/classes/designate_init_spec.rb | 6 +++- spec/classes/designate_keystone_auth_spec.rb | 3 ++ spec/classes/designate_mdns_spec.rb | 3 ++ templates/bind9-pools.yaml.erb | 6 ++++ 26 files changed, 129 insertions(+), 30 deletions(-)

1 0

puppet-horizon 26.0.0 (epoxy)
by no-reply＠openstack.org 16 Apr '25

16 Apr '25

We are jazzed to announce the release of: puppet-horizon 26.0.0 This release is part of the epoxy release series. The source is available from: https://opendev.org/openstack/puppet-horizon Download the package from: https://tarballs.openstack.org/puppet-horizon/ Please report issues through: https://bugs.launchpad.net/puppet-horizon/+bugs For more details, please see below. 26.0.0 ^^^^^^ New Features ************ * Ubuntu 24.04 is now formally supported. Upgrade Notes ************* * Ubuntu 22.04 is no longer supported. Changes in puppet-horizon 25.0.0..26.0.0 ---------------------------------------- d231d1c Bump Ubuntu version 8102e13 Prepare 2025.1 release 258b1c8 Use common implementation in litmus tests 43e815d Validate redirect_type using data type f6a8b2a Replace remaining use of legacy fact 013f80f Mark puppet 8 supported addf49f reno: Update master for unmaintained/2023.1 4ffebe8 Remove support for MemcachedCache backend ce86df8 Require absolutepath for cache cert/key file dfce4a9 Accept an array for cache_tls_allowed_ciphers cd5216f Pass custom_wsgi_process_options to horizon::wsgi::apache 507e4b2 Update master for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- manifests/init.pp | 281 ++++++++++----------- manifests/params.pp | 2 - manifests/wsgi/apache.pp | 58 ++--- metadata.json | 8 +- ...stom_wsgi_process_options-e11e7d92a9d631b1.yaml | 5 + releasenotes/notes/puppet-8-2654c8e29011ca99.yaml | 4 + .../remove-memcached-backend-e429c4f280d4b02b.yaml | 6 + .../notes/ubuntu-noble-7072fa6f20dc8b5e.yaml | 8 + releasenotes/source/2023.1.rst | 2 +- releasenotes/source/2024.2.rst | 6 + releasenotes/source/index.rst | 1 + spec/acceptance/horizon_with_apache_spec.rb | 29 +-- spec/classes/horizon_init_spec.rb | 76 ++---- templates/local_settings.py.erb | 4 + 14 files changed, 230 insertions(+), 260 deletions(-)

1 0

puppet-octavia 26.0.0 (epoxy)
by no-reply＠openstack.org 16 Apr '25

16 Apr '25

We are excited to announce the release of: puppet-octavia 26.0.0 This release is part of the epoxy release series. The source is available from: https://opendev.org/openstack/puppet-octavia Download the package from: https://tarballs.openstack.org/puppet-octavia/ Please report issues through: https://bugs.launchpad.net/puppet-octavia/+bugs For more details, please see below. 26.0.0 ^^^^^^ New Features ************ * Ubuntu 24.04 is now formally supported. Upgrade Notes ************* * Ubuntu 22.04 is no longer supported. Changes in puppet-octavia 25.0.0..26.0.0 ---------------------------------------- 0c4ef85 Bump Ubuntu version 116f94a Prepare 2025.1 release 4504420 Add a rabbit_transient_queues_ttl and amqp_auto_delete params f1363fc Fix new lint errors 5d8b820 Fix assertion of heartbeat_in_pthread parameter 52928b4 Deprecate support for [oslo_messaging_rabbit] heartbeat_in_pthread 5694a8f Stop using absolute names for defined resource types 5bf714a Mark puppet 8 supported e5e9a77 Make password in octavia::neutron class required 4598e03 task_flow: Hard-code default jobboard_backend_driver a92c5f5 Add support for jobboard etcd backend b98f8ad reno: Update master for unmaintained/2023.1 51b49ea Add support for [task_flow] jobboard_redis_backend_db 57f3352 Expose configure_service 90a68de Update master for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- manifests/db/mysql.pp | 4 +- manifests/db/postgresql.pp | 4 +- manifests/init.pp | 41 +++++++--- manifests/keystone/auth.pp | 6 ++ manifests/keystone/authtoken.pp | 2 +- manifests/neutron.pp | 13 +-- manifests/params.pp | 2 + manifests/task_flow.pp | 94 ++++++++++++++-------- manifests/wsgi/apache.pp | 2 +- metadata.json | 14 ++-- .../notes/amqp_auto_delete-2a8027b3f6ca4bc6.yaml | 5 ++ .../notes/configure_service-6b3c1d06ebc42afa.yaml | 5 ++ ...bbit_heartbeat_in_pthread-d18828a91f93d95f.yaml | 5 ++ .../jobboard-etcd-backend-484c6173cd698fa4.yaml | 5 ++ ...jobboard_redis_backend_db-f80010244e87b2c9.yaml | 5 ++ .../octavia-neutron-class-a4fd7a5c86dab7d5.yaml | 6 ++ releasenotes/notes/puppet-8-e44e6614e05cedd1.yaml | 4 + ...bbit_transient_queues_ttl-e128789222dee23c.yaml | 6 ++ .../notes/ubuntu-noble-dd7ea4362dce0d2d.yaml | 8 ++ releasenotes/source/2023.1.rst | 2 +- releasenotes/source/2024.2.rst | 6 ++ releasenotes/source/index.rst | 1 + spec/classes/octavia_init_spec.rb | 8 +- spec/classes/octavia_keystone_auth_spec.rb | 3 + spec/classes/octavia_neutron_spec.rb | 20 +++-- spec/classes/octavia_task_flow_spec.rb | 63 +++++++++++++-- spec/type_aliases/jobboardbackenddriver_spec.rb | 32 ++++++++ types/jobboardbackenddriver.pp | 5 ++ 28 files changed, 292 insertions(+), 79 deletions(-)

1 0

puppet-tempest 26.0.0 (epoxy)
by no-reply＠openstack.org 16 Apr '25

16 Apr '25

We are pumped to announce the release of: puppet-tempest 26.0.0 This release is part of the epoxy release series. The source is available from: https://opendev.org/openstack/puppet-tempest Download the package from: https://tarballs.openstack.org/puppet-tempest/ Please report issues through: https://bugs.launchpad.net/puppet-tempest/+bugs For more details, please see below. 26.0.0 ^^^^^^ New Features ************ * Ubuntu 24.04 is now formally supported. Upgrade Notes ************* * Ubuntu 22.04 is no longer supported. Changes in puppet-tempest 25.0.0..26.0.0 ---------------------------------------- e44d14d Bump Ubuntu version 12af196 Prepare 2025.1 release f2ff866 Bump upper version of puppet-vcsrepo ecd0879 Mark puppet 8 supported 1655760 reno: Update master for unmaintained/2023.1 44b2551 magnum: Update default image name 22ddf9f magnum: Drop outdated default value of image_source cd93bdc Drop unnecessary patch package 65a19e1 Fix undesired multi line message 3d6b63f Drop redundant package name checks ab92176 Support [compute-feature-enabled] vnc_console f41a63e Switch to built-in venv f50ee3c Support [baremetal_introspection] catalog_type cd8e8ce Add support for [baremetal] enabld_drivers dbc9a01 Accept array for barmetal_enabled_hardware_type 91419e0 Move descriptions of *_catalog_type options cd44577 Support customizing catalog_type options be7fdbf Update master for stable/2024.2 8ebd4cf Use native package resource to install tox Diffstat (except docs and test files) ------------------------------------- manifests/init.pp | 129 ++++++++++++++------- manifests/magnum.pp | 51 ++++---- manifests/params.pp | 10 +- metadata.json | 12 +- .../baremetal_enabld_drivers-57da34f4503603ae.yaml | 4 + .../notes/catalog_type-0911aa0e76ec8d9c.yaml | 4 + releasenotes/notes/puppet-8-dc41e4a2b00e6528.yaml | 4 + .../notes/ubuntu-noble-9679481ce22c84b3.yaml | 8 ++ .../notes/vnc_console-b2023cc4002b276a.yaml | 4 + releasenotes/source/2023.1.rst | 2 +- releasenotes/source/2024.2.rst | 6 + releasenotes/source/index.rst | 1 + spec/classes/tempest_init_spec.rb | 39 +++---- spec/classes/tempest_magnum_spec.rb | 24 ++-- 14 files changed, 196 insertions(+), 102 deletions(-)

1 0

puppet-mistral 26.0.0 (epoxy)
by no-reply＠openstack.org 16 Apr '25

16 Apr '25

We are overjoyed to announce the release of: puppet-mistral 26.0.0 This release is part of the epoxy release series. The source is available from: https://opendev.org/openstack/puppet-mistral Download the package from: https://tarballs.openstack.org/puppet-mistral/ Please report issues through: https://bugs.launchpad.net/puppet-mistral/+bugs For more details, please see below. Changes in puppet-mistral 25.0.0..26.0.0 ---------------------------------------- fdea641 Bump Ubuntu version bf11260 Deprecate coordination support 21eda38 Prepare 2025.1 release b7e6266 Add a rabbit_transient_queues_ttl and amqp_auto_delete params 1327eff Drop cleanup of old option e959539 Fix new lint errors 4c91491 Fix assertion of heartbeat_in_pthread parameter 4d1d570 Deprecate support for [oslo_messaging_rabbit] heartbeat_in_pthread d96d48c Stop using absolute names for defined resource types 1b0bc35 Mark puppet 8 supported 6bbc28e reno: Update master for unmaintained/2023.1 f2a9cd1 Fix ignored configure_service debde5b Update master for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- manifests/coordination.pp | 4 +- manifests/db/mysql.pp | 2 +- manifests/db/postgresql.pp | 2 +- manifests/init.pp | 57 ++++++++++++++-------- manifests/keystone/auth.pp | 19 ++++---- manifests/keystone/authtoken.pp | 2 +- manifests/wsgi/apache.pp | 2 +- metadata.json | 12 ++--- .../notes/amqp_auto_delete-8552b7085fdbb335.yaml | 5 ++ .../deprecate-coordination-aa2bbdc971b9a850.yaml | 5 ++ ...bbit_heartbeat_in_pthread-644ca905479767d6.yaml | 5 ++ releasenotes/notes/puppet-8-819db188ea16cbf3.yaml | 4 ++ ...bbit_transient_queues_ttl-c4243834920ec44d.yaml | 6 +++ .../notes/ubuntu-noble-8754d488ab4b6acc.yaml | 8 +++ releasenotes/source/2023.1.rst | 2 +- releasenotes/source/2024.2.rst | 6 +++ releasenotes/source/index.rst | 1 + spec/classes/mistral_init_spec.rb | 4 +- spec/classes/mistral_keystone_auth_spec.rb | 3 ++ 19 files changed, 106 insertions(+), 43 deletions(-)

1 0

puppet-oslo 26.0.0 (epoxy)
by no-reply＠openstack.org 16 Apr '25

16 Apr '25

We are pumped to announce the release of: puppet-oslo 26.0.0 This release is part of the epoxy release series. The source is available from: https://opendev.org/openstack/puppet-oslo Download the package from: https://tarballs.openstack.org/puppet-oslo/ Please report issues through: https://bugs.launchpad.net/puppet-oslo/+bugs For more details, please see below. 26.0.0 ^^^^^^ New Features ************ * Ubuntu 24.04 is now formally supported. Upgrade Notes ************* * Ubuntu 22.04 is no longer supported. Changes in puppet-oslo 25.0.0..26.0.0 ------------------------------------- 67447d0 Bump Ubuntu version 5dff215 Prepare 2025.1 release 408d76a Use bold instead of italic 94b1039 Add an amqp_auto_delete param 06a9b12 Deprecate heartbeat_in_pthread parameter 86a5814 Mark puppet 8 supported abb4fc3 reno: Update master for unmaintained/2023.1 c866d86 Add support for [cache] backend_expiration_time da9434e limit: Support new options to query endpoint 6da1029 Accept list value for ciphers ebdef74 ssl: Reject if only one of cert_file and key_file is set b6b0589 Update master for stable/2024.2 Diffstat (except docs and test files) ------------------------------------- manifests/cache.pp | 7 + manifests/limit.pp | 96 +++++++++----- manifests/messaging/rabbit.pp | 37 ++++-- manifests/service/ssl.pp | 6 +- metadata.json | 8 +- .../notes/amqp_auto_delete-e2734589468a98a2.yaml | 5 + ...e-backend-expiration-time-78bd3c1ebb3ab7c5.yaml | 4 + ...cate-heartbeat_in_pthread-7f8afe949faaac23.yaml | 5 + ...it-query-endpoint-options-c85c4542bc678217.yaml | 10 ++ releasenotes/notes/puppet-8-fb094942670c2b58.yaml | 4 + .../notes/ubuntu-noble-8854795cecbe1e62.yaml | 8 ++ releasenotes/source/2023.1.rst | 2 +- releasenotes/source/2024.2.rst | 6 + releasenotes/source/index.rst | 1 + spec/defines/oslo_cache_spec.rb | 7 +- spec/defines/oslo_limit_spec.rb | 142 ++++++++++++++------- spec/defines/oslo_messaging_rabbit_spec.rb | 1 + spec/defines/oslo_service_ssl_spec.rb | 35 +++++ 18 files changed, 284 insertions(+), 100 deletions(-)

1 0