Yoga Release Highlights

Yoga Release Highlights


These are significant changes reported directly from the project teams and have not been processed in any way. Some highlights may be more significant than others. Please do not take this list as a definitive set of highlights for the release until the Open Infrastructure Foundation marketing staff have had a chance to compile a more accurate message out of these changes.



  • A host availability calendar is now available in the Blazar dashboard.

  • Implemented initial support for running preemptible instances on unreserved hosts.

  • Added a new API to query for resource properties of hosts, allowing them to be used in creating leases more effectively.



  • Block Storage API microversion 3.68 adds the ability for users to request that a volume be re-imaged. It has always been possible in Block Storage API version 3 to create a bootable volume by requesting that image data from the Image service be written to the volume when the volume was created; now it’s possible to do this to an existing volume.

  • The Block Storage API no longer requires that request URLs contain a project ID. This makes the API more consistent with other OpenStack APIs. For backward compatibility, legacy URLs containing a project ID continue to be recognized.

  • New backend drivers were added: Lightbits LightOS for NVMe/TCP, a TOYOU NetStor Fibre Channel driver, and NEC V Series Storage drivers (FC and iSCSI).

  • Current backend storage drivers have added support for features exceeding the required driver functions, for example, Active/Active replication.



  • Added nova-cyborg interaction manual, updated Cyborg organizational structure diagram, and refactoring API guidelines to improve user experience.

  • Proposes a spec of adding a new OWNER_NOVA trait and pre-filter the trait for every Nova request group that is generated from the flavor, to better improve Cyborg’s vGPU support.

  • Device profile API microversion 2.2 supports getting device profile by name, now users can get device profile by name and uuid.



  • The Designate community has focused on stability for Yoga. Increased test coverage and great feedback from the community has helped us identify and fix numerous race conditions and bugs.

  • Designate now supports TXT records over 255 characters in length.



  • Added support to get quota usage information.

  • Added new APIs for cache related operations.

  • Added support to append new metadef tags rather than overwriting the existing tags.

  • Added support to fetch additional information about RBD store.



  • Horizon added experimental support of System Scope. There is a new entry System Scope added in context switcher menu which allows users to switch to a system scope token so operations that require this kind of token can be performed. It is disabled by default in the Yoga release.

  • Users can now perform Qos Rules CRUD operations to the Network QoS Policy using horizon.



  • The default deployment boot mode changed from Legacy BIOS to UEFI.

  • Booting final instances via network (as opposed to via a local bootloader) is now deprecated, except for the cases of booting from volume or the ramdisk deploy interface.

  • New parameter image_type in instance_info field, used to distinguish between partition and whole disk images instead of kernel/ramdisk pair.



  • Binary images are deprecated and any support for them will be removed in the next release. Users are requested to migrate to source based images.

  • Created an openstack.kolla Ansible collection to improve code reuse between Kolla projects.

  • Added support for deploying Prometheus Libvirt exporter.

  • Kayobe now supports building multiple overcloud disk images through direct use of diskimage-builder.

  • Added support for Horizon custom themes.

  • Zun deployment now supports using Cinder Ceph volumes.



  • Enhanced debugging capabalities by including Kubernetes events to resources managed by Kuryr.

  • Improved Neutron resources management to reduce the workload Kuryr puts on Neutron.



  • The usage of oslo.rootwrap is being deprecated in favor of oslo.privsep in places where manila’s micro services need elevated privileges to execute actions on the host. The LVM share back end driver now uses privsep dropping the need for a number of rootwrap entries.

  • Shares can now be soft-deleted into a recycle bin where they can stay for a configurable amount of time before being purged. While they’re in the recycle bin, they can be viewed and restored on demand.

  • Cloud administrators can now direct provisioning of shares and replicas to specific hosts via scheduler hints

  • Users may now specify more than one subnet on their share networks across any availability zone. This allows scaling the networks on the NAS servers that export their shared file systems.



  • Local IP - a virtual IP which can be shared across multiple ports or VMs is now available. Local IP is guaranteed to only be reachable within the same physical server or node boundaries.

  • Add support for VNIC type remote-managed to support port binding to SmartNIC DPUs. SmartNIC DPU portbinding requires OVN version 21.12 or above, compiled with OVN VIF version 21.12 or above.

  • Support for minimum packet processing based scheduling. With this feature, Nova instances can be scheduled to compute hosts that will honor the minimum pps requirements of the instance as defined by QoS policies of its ports.



  • Nova provides work-in-progress support for Keystone’s unified limits in order to allow operators to test this feature in non-production systems so we can collect early feedback about performance.

  • Nova now implements the scope concept and default system and project roles provided by Keystone. This feature isn’t yet enabled by default but operators are encouraged to start using it before we switch from the legacy roles in a next release.

  • Support is added for network backends that leverage SmartNICs to offload the controlplane from the host server. This enables increased security by removing the control plane from the host server and reduced overhead by leveraging the cpu and ram resources on modern SmartNIC DPUs.

  • Nova now provides AArch64, PPC64LE, MIPs, and s390x emulated architecture support independent of the host architecture. Please note this feature isn’t fully tested in our upstream CI so support should be considered experimental.



  • Octavia load balancers now support deep observability by adding PROMETHEUS listeners that expose a Prometheus exporter endpoint. The Octavia amphora provider exposes over 150 unique metrics.

  • The Octavia controllers and amphora instances can now be run with Federal Information Processing Standard (FIPS) 140-2 enforcement enabled.



  • Ansible-core version upgraded to 2.12

  • Added support for CentOS 9 Stream and Rocky linux 8

  • Experimental support of Ubuntu 22.04

  • Lsyncd on repo containers replaced with GlusterFS by default

  • SSH key-based authentication replaced with certificate-based



  • Add the latest v2 APIs for ETSI NFV life-cycle management.

  • Introduce several container supports such as using Docker private registry images in a Kubernetes Cluster environment, adding interfaces for Kubernetes VIM to handle Helm chart or so.

  • Support multi-tenant policy for isolating resources from each other such as Virtualized Infrastructure Managers(VIMs), Virtualized Network Function Packages (VNF packages), and Virtualized Network Function Lifecycle Management Interface (VNF LCM) related to ETSI NFV-SOL based VNF management concerning tenants. Only allows VNF instantiation by VIM of the same tenant.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.