releases/deliverables/xena/nova.yaml
Hervé Beraud 92c38ef599 Xena final releases for cycle-with-rc projects
This tags the final release for all cycle-with-rc projects for Xena.
While not required, having PTLs ack this patch would be nice to include
that record in the merged metadata.

Release activity should now be frozen until this is processed on Oct 6.
Any bugfixes merged to stable/xena can be queued up and ready to go
as a follow on stable release after the coordinated release date.

There are different diff-start values for each project. This is used
when generating release notes to denote the point where the
stable/wallaby branch started to diverge from what is included on
stable/xena. For some, this will be the final Wallaby major version,
but if multiple RCs were done, this may show the initial RC1 release
version. This is normal.

This patch will be merged on Oct 6.

Change-Id: Ic315f2d0b9377975a9cf72fe284f71cb090ace5c
2021-10-05 09:11:40 +02:00

48 lines
2.2 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
branches:
- name: stable/xena
location: 24.0.0.0rc1
release-notes: https://docs.openstack.org/releasenotes/nova/xena.html