releases/deliverables/xena/nova.yaml
Előd Illés f62d97fb1e [nova] Transition EM branches to Unmaintained
With the new TC resolution the community replaces Extended Maintenance
with Unmaintained status [1].

So this patch transitions victoria, wallaby, and xena EM branches to
Unmaintained as follows:
- tip of the given branch will be tagged with <series>-eom tag
- unmaintained/<series> branch will be cut from <series>-eom tag
- stable/<series> branch will be deleted

Some further notes:
- stable policy still applies
- backports can be pushed against unmaintained/<series> branch
- openstack-unmaintained-core group have the rights to merge patches

For further details please read the resolution [1] & review and +1 this
patch if this is correct as soon as possible.

[1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html

Change-Id: I212b8e818b075dcfcd9de810e22c2cbdc14ae21e
2024-02-27 19:51:06 +01:00

74 lines
2.9 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
- version: xena-eom
projects:
- repo: openstack/nova
hash: ac1c6a8c7d85502babdf617bc49b5bb2301c2053
branches:
- name: stable/xena
location: 24.0.0.0rc1
- name: unmaintained/xena
location: xena-eom
release-notes: https://docs.openstack.org/releasenotes/nova/xena.html