releases/deliverables/xena/nova.yaml
Előd Illés 30697d66f4 [nova] Transition Xena to EM
This transition the stable/xena branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch after the transition.

Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.

The transition deadline is April 20th, 2023.

Change-Id: I25980e149389fd7650d77dcda835007a387d29c6
2023-04-13 13:27:49 +02:00

68 lines
2.7 KiB
YAML

---
launchpad: nova
release-model: cycle-with-rc
team: nova
type: service
repository-settings:
openstack/nova: {}
cycle-highlights:
- |
Nova now supports `Cyborg managed SmartNICs
<https://docs.openstack.org/api-guide/compute/accelerator-support.html#using-sriov-with-cyborg>`_
represented by Neutron ports and attached as SRIOV devices to the Nova servers.
- |
Nova's libvirt virt driver now supports any PCI devices, not just virtual GPUs, that are using
the ``VFIO-mdev`` virtualization framework like network adapters or compute accelerators.
`See more in the spec <https://specs.openstack.org/openstack/nova-specs/specs/xena/approved/generic-mdevs.html>`_
- |
Nova stores the cinder volume connection_info in its database. Over time this information can
become stale if changes are made in the environment, the most common example of which being the
changing of MON IP addresses when using Ceph as the backing store for the Cinder volume service.
Previously operators have had to query the database directly for an understanding of the current
state of the connection_info and could only migrate or shelve the instance to force a refresh
of this. Now Nova provides a set of ``nova-manage``
`CLI commands <https://docs.openstack.org/nova/latest/cli/nova-manage.html#volume-attachment-commands>`_
to read and refresh the stale information.
- |
`API microversion 2.90 <https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-xena>`_
allows users to configure the hostname that will be exposed via the nova metadata service when
creating or rebuilding their instance.
releases:
- version: 24.0.0.0rc1
projects:
- repo: openstack/nova
hash: 1c502ebaec29615f08d4af7dc6680f3141d70e67
- version: 24.0.0.0rc2
projects:
- repo: openstack/nova
hash: 928d3feffd674a842d4bb4348d2f0e0d7e93a8a5
- version: 24.0.0
projects:
- repo: openstack/nova
hash: 928d3feffd674a842d4bb4348d2f0e0d7e93a8a5
diff-start: 23.0.0.0rc1
- version: 24.1.0
projects:
- repo: openstack/nova
hash: 6f81db2dd65060135ac093aa3b1c8bd08ac0af0c
- version: 24.1.1
projects:
- repo: openstack/nova
hash: 3872647092353229302919d305758f3fc777277f
- version: 24.2.0
projects:
- repo: openstack/nova
hash: ac3728e1239fe2aeffc2a06bbeab6a24eff28ae9
- version: 24.2.1
projects:
- repo: openstack/nova
hash: 706ee6010a3720b9d9faf72d6782665b6eb083a7
- version: xena-em
projects:
- repo: openstack/nova
hash: 706ee6010a3720b9d9faf72d6782665b6eb083a7
branches:
- name: stable/xena
location: 24.0.0.0rc1
release-notes: https://docs.openstack.org/releasenotes/nova/xena.html