releases/deliverables/caracal/nova.yaml
Előd Illés e25c580ad6 nova: Release 2024.1 Caracal 29.2.0
MINOR version bump is to highlight CVE related fixes.

$ git log --oneline --no-merges 29.1.0..da9e56c9af
602e68364c [tools] Backport validator: handle unmaintained
92b781f96e [tools] Ignore bot generated patches
9146e90566 Refactor vf profile for PCI device
c782f0e6a0 Fix test_vmdk_bad_descriptor_mem_limit and test_vmdk_bad_descriptor_mem_limit_stream_optimized
8c5929ff51 Remove AMI snapshot format special case
8ef5ec9716 Change force_format strategy to catch mismatches
cf721336d4 cpu: Only check governor type on online cores
a8783a7675 Stabilize iso format unit tests
ae10fde55b fix qemu-img version dependent tests
81e3b0850c Stop using split UEC image (mostly)
eeda7c333c Add iso file format inspector
3a6d9a038f Reproduce iso regression with deep format inspection
66205be426 port format inspector tests from glance
1581f6695f retry write_sys call on device busy
f1c46802b1 add functional repoducer for bug 2065927

Change-Id: Idee1d4d00d821d7124e72e8b6b133ccd02d62ac9
2024-08-01 16:44:20 +02:00

89 lines
3.9 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
branches:
- name: stable/2024.1
location: 29.0.0.0rc1
release-notes: https://docs.openstack.org/releasenotes/nova/2024.1.html