Files
releases/deliverables/caracal/nova.yaml
Előd Illés 88dda930f5 [nova] Transition 2024.1 Caracal to Unmaintained
This branch reached the end of its official stable maintained period,
hence this patch transition stable/2024.1 branch to Unmaintained. (For
details about Unmaintained state please see: [1][2])

The transitions is as follows:
- tip of the stable/2024.1 branch is tagged with 2024.1-eom tag
- unmaintained/2024.1 branch will be cut from 2024.1-eom tag
- stable/2024.1 branch will be deleted

Note:
- there will no longer be official releases off of 2024.1 branch after
  this transition
- backports can be pushed to unmaintained/2024.1 branch
- openstack-unmaintained-core (or <project>-unmaintained-core groups if
  such exists) have the rights to merge patches

Important: please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final 2024.1 Caracal stable release
with backports currently in flight that we should wait for. For the
latter case, please propose a final 2024.1 Caracal stable release
patch, and rebase this patch on top of that, with the latest commit
hash of stable/2024.1.

The planned transition deadline is October 24th, 2025 [3] last week,
so please approve this patch as soon as possible if the project is
ready for the transition.

[1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained
[2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html
[3] https://releases.openstack.org

Change-Id: Ifc8b39450fb06e3d097709c185700579aaa0c857
Signed-off-by: Előd Illés <elod.illes@est.tech>
Generated-By: openstack/releases:tools/bulk_review.sh
2025-10-31 09:57:41 +01:00

112 lines
4.6 KiB
YAML

---
launchpad: nova
release-model: cycle-with-rc
team: nova
type: service
repository-settings:
openstack/nova: {}
cycle-highlights:
- |
The Ironic driver ``[ironic]/peer_list`` configuration option has been
deprecated. The Ironic driver now more closely models other Nova drivers by
having a single compute have exclusive control over assigned nodes. If high
availability of a single compute service is required, operators should use
active/passive failover. Now, Ironic nova-compute services can target a
specific shard of ironic nodes by setting the ``[ironic]/shard``
configuration option and a new ``nova-manage db ironic_compute_node_move``
command can help the operators when upgrading their computes and telling
which shard they could use.
- |
Instances using `vGPUs can now be correctly live-migrated
<https://docs.openstack.org/nova/latest/admin/virtual-gpu.html#caveats>`_
if both of the compute nodes support libvirt-8.6.0 and QEMU-8.1.0, as the
source mediated device will migrate the GPU memory to another target
mediated device automatically. In order to do this,
``[libvirt/live_migration_downtime`` config option needs to be modified
according to the aforementioned documentation.
- |
As of the new 2.96 microversion, when asking the API for a server show or a
server list, it returns a new parameter called ``pinned_availability_zone``
that indicates whether the instance is confined to a specific AZ or if it
can be migrated to another one.
- |
Instances using virtio-net will see an increase in performance between 10%
and 20% if their image uses a new ``hw:virtio_packed_ring=true`` property
or their flavor contains ``hw_virtio_packed_ring=true`` extra spec,
provided libvirt version is >= 6.3 and QEMU >= 4.2.
- |
As a security mechanism, a new ``[consoleauth]/enforce_session_timeout``
configuration option provides the ability to automatically close a server
console session when the token expires.
- |
Users can `boot instances with large RAM
<https://specs.openstack.org/openstack/nova-specs/specs/2023.1/approved/libvirt-maxphysaddr-support.html#flavor-extra-specs>`_
by specifying either through flavor extra specs
``hw:maxphysaddr_mode=emulate`` and ``hw:maxphysaddr_bits`` or by image
properties ``hw_maxphysaddr_mode`` and ``hw_maxphysaddr_bits``.
- |
The Hyper-V virt driver has been removed. It was deprecated in the Nova
27.2.0 (Antelope) release. This driver was untested and has no maintainers.
In addition, it had a dependency on the OpenStack Winstacker project that
also has been retired.
- |
A couple of other improvements target reducing the number of bugs we have :
one automatically detecting the maximum number of instances with memory
encryption which can run concurrently, another one allowing to specific an
IP address or hostname for incoming move operations (by setting
``[libvirt]/migration_inbound_addr``) and yet another one defining aliases
for libvirt disks as a defined identifier to look at.
releases:
- version: 29.0.0.0rc1
projects:
- repo: openstack/nova
hash: 77de002d61c4bf591f43c879a07dcdd3598c0954
- version: 29.0.0
projects:
- repo: openstack/nova
hash: 77de002d61c4bf591f43c879a07dcdd3598c0954
diff-start: 28.0.0
- version: 29.0.1
projects:
- repo: openstack/nova
hash: 77de002d61c4bf591f43c879a07dcdd3598c0954
- version: 29.0.2
projects:
- repo: openstack/nova
hash: e05b2a0ea32d86a24759c9421b4c000262ad9417
- version: 29.1.0
projects:
- repo: openstack/nova
hash: 11301e7e3f0d81a3368632f90608e30d9c647111
- version: 29.2.0
projects:
- repo: openstack/nova
hash: da9e56c9af5de97c031334d1a6b72a79fc8adb4a
- version: 29.2.1
projects:
- repo: openstack/nova
hash: 1aeeb96ffa646f4b4ebd2af8336e9f6eba4e974a
- version: 29.2.2
projects:
- repo: openstack/nova
hash: ad1bd175ae57e45dbfa8014f945cbc42d62ad8ce
- version: 29.3.0
projects:
- repo: openstack/nova
hash: 5a92bb594fd5513158044653ddd6919ae8f0ffb2
- version: 29.4.0
projects:
- repo: openstack/nova
hash: 41ae5b7f70481ad1a63eb1cbdba1e890be850ec5
- version: 2024.1-eom
projects:
- repo: openstack/nova
hash: 41ae5b7f70481ad1a63eb1cbdba1e890be850ec5
branches:
- name: stable/2024.1
location: 29.0.0.0rc1
- name: unmaintained/2024.1
location: 2024.1-eom
release-notes:
https://docs.openstack.org/releasenotes/nova/2024.1.html