Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 1. New and enhanced features

Review features that have been added to or significantly enhanced in Red Hat OpenStack Services on OpenShift (RHOSO).

RHOSO improves substantially over previous versions of Red Hat OpenStack Platform (RHOSP). The RHOSO control plane is natively hosted on the Red Hat OpenShift Container Platform (RHOCP) and the external RHEL-based data plane and workloads are managed with Ansible. This shift in architecture aligns with Red Hat’s platform infrastructure strategy. You can future proof your existing investments by using RHOCP as a hosting platform for all of your infrastructure services.

For information about mapping RHOSO versions to OpenStack Operators and OpenStackVersion Custom Resources (CRs), see the Red Hat knowledge base article at https://access.redhat.com/articles/7125383.

RHOSP 17.1 is the last version of the product to use the director-based OpenStack on OpenStack form-factor for the control plane.

1.1. New and enhanced in 18.0.10 (FR3)
Copy link

Review features that have been added to or significantly enhanced in Red Hat OpenStack Services on OpenShift.

1.1.1. Bare Metal Provisioning
Copy link

Layer 2 network configuration using Networking Generic Switch in the Bare Metal Provisioning service (Technology Preview)
RHOSO 18.0.10 (Feature Release 3) introduces support for the configuration of L2 networks on non-provisioning NIC interfaces when using Baremetal as a Service (BMaaS) through the Bare Metal Provisioning service (ironic). This feature allows network configuration on switches by leveraging the networking-generic-switch Modular Layer 2 Neutron Mechanism driver.

1.1.2. Compute
Copy link

PCI device tracking in the Placement service is now generally available
Previously, this feature was available as Technology Preview. You can use the Placement service to observe the PCI resource availability and usage across the whole cloud through the Placement API. The administrator can also reserve PCI devices for maintenance through the Placement API.
Configuration of notifications to the Telemetry service
Starting with RHOSO 18.0.10 (Feature Release 3), you can configure the Compute service (nova) to provide notifications to Telemetry services in your RHOSO environment.
Setting the maximum number of vGPUs that an SR-IOV NVIDIA GPU can create
Starting with RHOSO 18.0.10 (Feature Release 3), you can define the maximum number of vGPUs that a SR-IOV NVIDIA GPU can create.
Reserving One Time Use devices
Starting with RHOSO 18.0.10 (Feature Release 3), you can tag PCI devices as One Time Use (OTU) to reserve them for a single use by a single instance.

1.1.3. Control plane
Copy link

Multiple RHOSO deployments on a single RHOCP cluster by using namespace separation
Starting with RHOSO 18.0.10 (Feature Release 3), you can deploy multiple RHOSO environments on a single RHOCP cluster by using namespace (project) isolation.
Note

Do not deploy multiple RHOSO environments on a single cluster with namespace separation in production. Multiple deployments are suitable only for development, staging, and testing environments.

Documentation: Guidance for deploying Red Hat OpenStack Services on OpenShift in a disconnected environment
RHOSO 18.0.10 (Feature Release 3) introduces documentation support for deploying Red Hat OpenStack Services on OpenShift (RHOSO) in a disconnected environment. For more information, see Deploying Red Hat OpenStack Services on OpenShift in a disconnected environment.

1.1.4. Dashboard
Copy link

The horizon-operator creates an additional sidecar container for logging
Starting with RHOSO 18.0.10 (Feature Release 3), the Dashboard service horizon-operator implements a separate sidecar container to ensure the availability of logs for debugging. If you use a custom container image, you might need to rebuild your custom image when updating.

1.1.5. Networking
Copy link

DNS service (designate) (Technology Preview)
With this technology preview, you can test the management of DNS records, names, and zones using the DNS service (designate). For more information, see Configuring DNS as a service.
Vertical scaling for load-balancing service (Octavia) instances (amphorae)
Starting with RHOSO 18.0.10 (Feature Release 3), RHOSO supports vertical scaling for load-balancing service instances. Users can scale-up their load balancers, increasing the CPU and RAM of the load-balancing instance, to improve performance and capacity. Vertically scaling increases the volume of network traffic processed. To scale-up a load balancer, use the appropriate load-balancing flavor when you create a load balancer. RHOSO ships with amphora-4vcpus, which creates an instance that contains 4 vCPUs, 4GB RAM, and 3GB of disk space. Your RHOSO administrator can create other custom load-balancing flavors that meet the load-balancing needs of your particular environment. For more information, see Creating Load-balancing service flavors in Configuring load balancing as a service.
Load-balancing service (Octavia) support for DCN deployments (Technology Preview)
With this technology preview, you can create load balancers in a distributed compute node (DCN) environment to increase traffic throughput and reduce latency. for more information, see Creating availability zones for load balancing of network traffic at the edge in Configuring load balancing as a service.
Load-balancing service (Octavia) TLS client authentication
Starting with RHOSO 18.0.10 (Feature Release 3), you can secure your web client communication with a load balancer by using two-way TLS authentication. For more information, see Creating a TLS-terminated HTTPS load balancer with client authentication in Configuring load balancing as a service.
BGP-EVPN support for provider network workloads without FDP support (Developer Preview)
Starting with RHOSO 18.0.10 (Feature Release 3), you can test a developer preview of BGP-EVPN support for provider network workloads without FDP support. Openstack provides a mature infrastructure platform for virtualized workload focussing on on-prem environments. With most of the Telco 4G workloads running on virtualized platforms and the expanding landscape of multiple sites and clusters, there is an imperative need for connectivity across the clusters that enables tenant workload deployment across multiple clusters. In addition to providing control plane and data plane isolation in a shared environment, there is a need for multi-tenancy extending to the compute nodes. RHOSO 18 FR3 adds support for BGP-EVPN enabling multi-tenant, multi-VRF support with overlapping IP addresses for provider network workloads. The feature is available as developer preview in RHOSO 18 FR3 and is suitable for functional operation and testing in lab environments only.
Prometheus Exporter for OVN logical routers and logical switches
Starting with RHOSO 18.0.10 (Feature Release 3), you can use Prometheus Exporter for OVN logical routers and logical switches. RHOSO deployments use . Network observability requires metrics and KPIs to be available at the OVN layer, exposing packet statistics within the networking infrastructure orchestrated by OVN. RHOSO 18 FR3 adds support for monitoring metrics at the OVN layer (logical routers and switches) via prometheus exporter, allowing correlation between the top-level content management system (CMS), logical OVN, and physical representations of networking elements.
New OVN database synchronization tool to fix OVN load balancers
RHOSO 18.0.10 (Feature Release 3) introduces an OVN database synchronization tool to fix OVN load balancers that experience problems. The new tool, octavia-ovn-db-sync-util, is run on the command-line to synchronize the state of Load-balancing service (octavia) resources, with the OVN databases. For more information, see https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/configuring_load_balancing_as_a_service/troubleshoot-maintain-lb-service_rhoso-lbaas#synch-lbs-ovn-provider_trbls-lbs

1.1.6. NFV
Copy link

OVS-DPDK is now supported for all workloads
RHOSO 18.0.10 (Feature Release 3) introduces support for OVS-DPDK for all workloads. Previously, OVS-DPDK was only supported in NFV workloads.
TCP segmentation offloading (TSO) for OVS-DPDK is now generally available
Previously, TSO for OVS-DPDK was available as a technology preview. Now it is generally available. TSO offloads segmentation to NICs, freeing up host CPU resources and improving overall performance.
OVS-DPDK on networker nodes for acceleration of gateway traffic
RHOSO 18.0.10 (Feature Release 3) introduces support of DPDK-accelerated Open vSwitch (OVS-DPDK) on Networker nodes. The DPDK datapath provides lower latency and higher performance than the standard kernel OVS datapath. OVS-DPDK is a high-performance, user-space solution that bundles Open vSwitch with the Data Plane Development Kit (DPDK). This technology is designed to process packets quickly by running mostly in the user-space, allowing applications to directly handle packet processing to or from the Network Interface Card (NIC).

1.1.7. Observability
Copy link

Database and Compute metrics available to Prometheus for telemetry data collection and storage
Starting with RHOSO 18.0.10 (Feature Release 3), the Telemetry service collects both database and Compute metrics and makes them available to Prometheus, enabling database telemetry and Compute node telemetry to be stored in the telemetry storage system.

1.1.8. Security
Copy link

LDAP Support
RHOSO 18.0.10 (Feature Release 3) introduces support for connecting the Identity service (keystone) to LDAP for authentication.
Proteccio HSM support
In RHOSO 18.0.10 (Feature Release 3), the Key Manager service (barbican) supports the Proteccio HSM as a back end to store secrets.

1.1.9. Storage
Copy link

Distributed zones with third-party storage
RHOSO 18.0.10 (Feature Release 3) introduces support for using certified third-party storage with distributed zones.
Adopting the Image service (glance) with an NFS storage back end
RHOSO 18.0.10 (Feature Release 3) introduces support for adopting the Image service from Red Hat OpenStack Platform (RHOSP) 17.1 with an NFS back end.
Improved parallel image upload performance with load distribution
Starting with RHOSO 18.0.10 (Feature Release 3), you can improve parallel image upload performance by using the mod_wsgi package to distribute the load across workers.
Image service (glance) notifications for events in image lifecycle
Starting with RHOSO 18.0.10 (Feature Release 3), you can enable notifications in the Image service by using the notificationBusInstance parameter, allowing integration with either the existing RabbitMQ instance or a dedicated one.
Adopting the Block Storage service (cinder) with an NFS storage back end
RHOSO 18.0.10 (Feature Release 3) introduces support for adopting the Block Storage service from Red Hat OpenStack Platform (RHOSP) 17.1 with an NFS back end.
Remote ring storage supports larger deployments of the Object Storage service (Technical Preview)
Starting with RHOSO 18.0.10 (Feature Release 3), you can use remotely stored rings to manage larger deployments of the Object storage service (swift).
CephFS file name added to CephFS share metadata
Starting with RHOSO 18.0.10 (Feature Release 3), you can check a CephFS file name when mounting a native CephFS share by viewing the mount_options metadata of the share. Starting with RHOSO 18.0.10 (Feature Release 3), you can check a CephFS file name when mounting a native CephFS share by viewing the mount_options metadata of the share.
Adopting the Shared File Systems service (manila) with a third-party back end
RHOSO 18.0.10 (Feature Release 3) introduces support for adopting the Shared File Systems service from Red Hat OpenStack Platform (RHOSP) 17.1 with a third-party back end, for example, NetApp or Dell.

1.1.10. Upgrades and updates
Copy link

Granular package update workflow for RHOSO Compute nodes during the RHOSO update process (Technology Preview)
RHOSO 18.0.10 (Feature Release 3) introduces a mechanism to break down the update process for RHOSO Compute nodes running RHEL 9.4 into two distinct phases: updating OpenStack-related RPM packages and updating system-related RPM packages. By enabling this separation, operators gain finer control over the update process, reducing risks and simplifying troubleshooting in the event of issues.

1.1.11. Resource optimization
Copy link

Optimize service (watcher) strategies for resource optimization (Technology Preview)
RHOSO 18.0.10 (Feature Release 3) introduces support for three new supported strategies in the Optimize service: host maintenance, zone migration for instances, and workload balance. For more information about supported strategies to achieve resource optimization goals, see Sample Optimize service workflows in Optimizing infrastructure resource utilization.

1.2. New and enhanced in 18.0.6 (FR2)
Copy link

Review features that have been added to or significantly enhanced in Red Hat OpenStack Services on OpenShift.

1.2.1. Bare Metal Provisioning
Copy link

RHOSO environment with a routed spine-leaf network topology
RHOSO 18.0.6 (Feature Release 2) introduces support for deploying a RHOSO environment with a routed spine-leaf network topology. For more information, see Deploying a RHOSO environment with a routed spine-leaf network topology.

1.2.2. Control plane
Copy link

Streamlined RHOSO service Operators installation and initialization
RHOSO 18.0.6 (Feature Release 2) introduces a new initialization resource that streamlines the management of the RHOSO service Operators under a single Operator Lifecycle Manager (OLM) bundle. After you install the OpenStack Operator and before creating the control plane, you now create the new OpenStack initialization resource, which installs all the RHOSO service Operators.
Distributed zones
RHOSO 18.0.6 (Feature Release 2) introduces support for deploying a distributed control plane across multiple RHOCP cluster nodes that are located in distributed low latency L3 connected data centers.
Custom environment variables for the OpenStackClient pod
Starting with RHOSO 18.0.6 (Feature Release 2), you can customize the OpenStackClient pod environment variables to set the API version to use when connecting to the service API endpoints with the openstackclient CLI.
Multiple RHOSO deployments on a single RHOCP cluster using namespace separation (Technology Preview)
Starting with RHOSO 18.0.6 (Feature Release 2), you can test a technology preview of using namespace separation to deploy multiple RHOSO environments on a single RHOCP cluster. To deploy each RHOSO environment, create multiple isolated namespaces, then use the procedures in Deploying Red Hat OpenStack Services on OpenShift.
Note

Ensure that the NMState Operator on each host worker node provides for the multiple VLANs that are required to enable network isolation for each namespace.

1.2.3. High availability
Copy link

Instance high availability
Starting with RHOSO 18.0.6 (Feature Release 2), you can use instance high availability (instance HA) to automatically evacuate and re-create instances on a different Compute node if a Compute node fails.

1.2.4. Networking
Copy link

DNS service (Technology Preview)
Starting with RHOSO 18.0.6 (Feature Release 2), you can test a technology preview of the RHOSO DNS service (designate), a multi-tenant service that enables you to manage DNS records, names, and zones.
OVS-DPDK on networker nodes for OVN gateway acceleration
Starting with RHOSO 18.0.6 (Feature Release 2), you can enable OVS-DPDK on networker nodes for improved forwarding performance.
Support for nmstate provider in new greenfield deployments
Starting with RHOSO 18.0.6 (Feature Release 2), the nmstate provider is supported for new RHOSO deployments. The default os-net-config provider for new (greenfield) RHOSO deployments is ifcfg. For limitations and other details, see https://issues.redhat.com/browse/OSPRH-11309.
TCP segmentation offload for RHOSO environments with OVS-DPDK (Technology Preview)
Starting with RHOSO 18.0.6 (Feature Release 2), you can test a technology preview of TCP segmentation offload (TSO) for RHOSO environments with OVS-DPDK. For details, see OVS-DPDK with TCP segmentation offload (Technology Preview).

1.2.5. Observability
Copy link

Power consumption monitoring
Starting with RHOSO 18.0.6 (Feature Release 2), the visualization of IPMI power metrics is available in the dashboard. For more information, see https://issues.redhat.com/browse/OSPRH-10808.
Enhanced OpenStack Observability
Starting with RHOSO 18.0.6 (Feature Release 2), you can use the openstack-network-exporter to expose metrics from OVS or OVS-DPDK, OVN, and DPDK (PMD), and a dashboard has been added for these metrics.
Container health check

Starting with RHOSO 18.0.6 (Feature Release 2), you can use new metrics for monitoring the health of RHOSO services, including the following:

  • kube_pod_status_phase
  • kube_pod_status_ready
  • node_systemd_unit_state
  • podman_container_state

  • podman_container_health

    You can use kube_pod_status_phase and kube_pod_status_ready to monitor control plane services. For more information, see https://issues.redhat.com/browse/OSPRH-1052.

1.2.6. Security
Copy link

Key Manager (barbican) support for Luna
Starting with RHOSO 18.0.6 (Feature Release 2), when you install RHOSO, you have the option of using it with a Luna hardware security module (HSM). Using a hardware security module provides hardened protection for storing keys.
Identity service (keystone) support for Federation
RHOSO 18.0.6 (Feature Release 2) introduces Red Hat support for Red Hat Single Sign-On (RH-SSO) or Active Directory Federation Services (ADFS) as identity providers for RHOSO.

1.2.7. Storage
Copy link

Integration with external Red Hat Ceph Storage (RHCS) clusters
Starting with RHOSO 18.0.6 (Feature Release 2), you can integrate RHOSO with external Red Hat Ceph Storage 8 clusters (as well as Red Hat Ceph Storage 7 clusters) to include Red Hat Ceph Storage capabilities with your deployment. Due to known issues, not all Red Hat Ceph Storage 8 functionality is supported. For more information about these issues, see the Known Issues section.
Image service (glance) support for S3 back end
Starting with RHOSO 18.0.6 (Feature Release 2), you can configure the Image service with an S3 back end.

1.2.8. Upgrades and updates
Copy link

Important

OpenStack Operator 18.0.6 now requires you to install a new initialization resource called OpenStack. You must create this resource when you update your RHOSO deployment from a version older than 18.0.6, or when you perform a new installation of 18.0.6. Also, if you deployed RHOSO 18.0.4 or earlier on RHOCP 4.16, you must create the OpenStack initialization resource before upgrading your RHOCP cluster to RHOCP 4.18.

RHOSO environments installed earlier than 18.0.6 have individual Operators, such as horizon-operator, nova-operator, and so on, in the openstack-operators namespace. Creation of the OpenStack resource automatically cleans up these unnecessary resources in the OpenShift environment. For more information about creating the OpenStack resource, see Installing the OpenStack Operator in Deploying Red Hat OpenStack Services on OpenShift.

Baremetal as a service (ironic) adoption from RHOSP 17.1 to RHOSO 18.0 (Technology Preview)
RHOSO 18.0.6 (Feature Release 2) introduces a technology preview of the ability to adopt Baremetal as a service (ironic) from RHOSP 17.1 to RHOSO 18.0. For details, see Adopting the Bare Metal Provisioning service in Adopting a Red Hat OpenStack Platform 17.1 deployment.
IPv6 stack adoption from RHOSP 17.1 to RHOSO 18.0 (Technology Preview)
Starting with RHOSO 18.0.6 (Feature Release 2), you can test a technology preview of configuring IPv6 networking for adoption. For more information, see Adopting a Red Hat OpenStack Platform 17.1 deployment.
Kernel live patching for RHOSO environments (Technology Preview)
Starting with RHOSO 18.0.6 (Feature Release 2), you can test a technology preview of kernel live patching support for RHOSO environments. With this feature, you can apply critical security updates and bug fixes to the kernel without requiring a system reboot. You cannot use this feature to apply custom live patches or third-party live patching solutions.

1.3. New and enhanced in 18.0.3 (FR1)
Copy link

Review features that have been added to or significantly enhanced in Red Hat OpenStack Services on OpenShift.

1.3.1. Distributed Compute nodes (DCN)
Copy link

DCN with Red Hat Ceph storage
RHOSO 18.0.3 (Feature Release 1) introduces support for Distributed Compute Nodes (DCN) with persistent storage backed by Red Hat Ceph Storage.

1.3.2. Networking
Copy link

Dynamic routing on data plane with FRR and BGP

RHOSO 18.0.3 (Feature Release 1) introduces support of Free Range Routing (FRR) border gateway protocol (BGP) to provide dynamic routing capabilities on the RHOSO data plane.

Limitations:

  • If you use dynamic routing, you must also use distributed virtual routing (DVR).
  • If you use dynamic routing, you also use dedicated networker nodes.
  • You can not use dynamic routing in an IPv6 deployment or a deployment that uses the Load-balancing service (octavia).
Custom ML2 mechanism driver and SDN backend (Technology Preview)
RHOSO 18.0.3 (Feature Release 1) allows you to test integration of the Networking service (neutron) with a custom ML2 mechanism driver and software defined networking (SDN) back end components, instead of the default OVN mechanism driver and back end components. Do not use this feature in a production environment.
IPv6 metadata
RHOSO 18.0.3 (Feature Release 1) introduces support of the IPv6 metadata service.
NMstate provider for os-net-config (Development Preview)
RHOSO 18.0.3 (Feature Release 1) allows you to test a Development Preview of the NMstate provider for os-net-config. To test the NMstate provider, set edpm_network_config_nmstate: true. Do NOT use this Development Preview setting in a production environment.
Forwarding database (FDB) learning and aging controls

RHOSO 18.0.3 (Feature Release 1) introduces FDB learning and related FDB aging parameters.

You can use FDB learning to prevent traffic flooding on ports that have port security disabled. Set localnet_learn_fdb to true.

Use the fdb_age_threshold parameter to set the maximum time (seconds) that the learned MACs stay in the FDB table. Use the fdb_removal_limit parameter to prevent OVN from removing a large number of FDB table entries at the same time.

Example configuration

apiVersion: core.openstack.org/v1beta1
kind: OpenStackControlPlane
metadata:
    name: unused
spec:
    neutron:
        template:
            customServiceConfig: |
               [ovn]
               localnet_learn_fdb = true
               fdb_age_threshold = 300
               fdb_removal_limit = 50
Copy to Clipboard Toggle word wrap

1.3.3. Observability
Copy link

Power consumption monitoring (Technology Preview)

RHOSO 18.0.3 (Feature Release 1) introduces technology previews of power consumption monitoring capability for VM instances and virtual networking functions (VNFs).

See Jira Issue OSPRH-10006: Kepler Power Monitoring Metrics Visualization in RHOSO (Tech Preview) and Jira Issue OSPRH-46549: As a service provider I need a comprehensive dashboard that provides a power consumption matrix per VNF(Tech Preview).

RabbitMQ metrics dashboard
Starting in RHOSO 18.0.3 (Feature Release 1), RabbitMQ metrics are collected and stored in Prometheus. A new dashboard for displaying these metrics was added.

1.3.4. Upgrades and updates
Copy link

Adoption from RHOSP 17.1
RHOSO 18.0.3 (Feature Release 1) introduces the ability to use the adoption mechanism to upgrade from RHOSP 17.1 to RHOSO 18.0 while minimizing impacts to your workloads.

1.4. New and enhanced in 18.0 (GA)
Copy link

Review features that have been added to or significantly enhanced in Red Hat OpenStack Services on OpenShift.

1.4.1. Control plane
Copy link

Control plane deployed on Red Hat OpenShift Container Platform (RHOCP)

In RHOSO 18.0 (GA), the director-based undercloud is replaced by a control plane that is natively hosted on an RHOCP cluster and managed with the OpenStack Operator. The Red Hat OpenStack Services on OpenShift (RHOSO) control plane features include:

  • Deployed in pods and governed by Kubernetes Operators.
  • Deploys in minutes, consuming only a fraction of the CPU and RAM footprint required by earlier RHOSP releases.
  • Takes advantage of native Kubernetes mechanisms for high availability.
  • Features built-in monitoring based on RHOCP Observability.

1.4.2. Dashboard
Copy link

Pinned CPUs
Starting with RHOSO 18.0 (GA), the OpenStack Dashboard service (horizon) shows how many pinned CPUs (pCPUs) are used and available to use in your environment.

1.4.3. Data plane
Copy link

Ansible-managed data plane

In RHOSO 18.0 (GA), the director-deployed overcloud is replaced by a data plane driven by the OpenStack Operator and executed by Ansible. RHOSO data plane features include:

  • The OpenStackDataPlaneNodeSet custom resource definition (CRD), which provides a highly parallel deployment model.
  • Micro failure domains based on the OpenStackDataPlaneNodeSet CRD. If one or more node sets fail, the other node sets run to completion because there is no interdependency between node sets.
  • Faster deployment times compared to previous RHOSP versions.
  • Highly configurable data plane setup based on the OpenStackDataPlaneNodeSet and OpenStackDataPlaneService CRDs.

1.4.4. Documentation
Copy link

In RHOSO 18.0 (GA), the documentation library has been restructured to align with the user lifecycle of RHOSO. Each guide incorporates content from one or more product areas that work together to cover end-to-end tasks. The titles are organized in categories for each stage in the user lifecycle of RHOSO.

The following categories are published with RHOSO 18.0:

Plan

Information about the release, requirements, and how to get started before deployment. This category includes the following guides:

  • Release notes
  • Planning your deployment
  • Integrating partner content
Prepare, deploy, configure, test

Procedures for deploying an initial RHOSO environment, customizing the control plane and data plane, configuring validated architectures, storage, and testing the deployed environment. This category includes the following guides:

  • Deploying Red Hat OpenStack Services on OpenShift
  • Customizing the Red Hat OpenStack Services on OpenShift deployment
  • Deploying a Network Functions Virtualization environment
  • Deploying a hyper-converged infrastructure environment
  • Configuring persistent storage
  • Validating and troubleshooting the deployed cloud
Adopt and update

Information about performing minor updates to the latest maintenance release of RHOSO, and procedures for adopting a Red Hat OpenStack Platform 17.1 cloud. This category includes the following guides:

  • Adopting a Red Hat OpenStack Platform 17.1 overcloud to a Red Hat OpenStack Services on OpenShift 18.0 data plane
  • Updating your environment to the latest maintenance release
Customize and scale

Procedures for configuring and customizing specific components of the deployed environment. These procedures must be done before you start to operate the deployment. This category includes the following guides:

  • Configuring the Compute service for instance creation
  • Configuring data plane networking
  • Configuring load balancing as a service
  • Customizing persistent storage
  • Configuring security services
  • Auto-scaling for instances
Manage resources and maintain the cloud

Procedures that you can perform during ongoing operation of the RHOSO environment. This category includes the following guides:

  • Maintaining the Red Hat OpenStack Services on OpenShift deployment
  • Creating and managing instances
  • Performing storage operations
  • Performing security operations
  • Managing networking resources
  • Managing cloud resources with the Dashboard
  • Monitoring high availability services

1.4.4.1. Documentation in progress
Copy link

In RHOSO 18.0 (GA), the following titles are being reviewed and will be published asynchronously:

  • Configuring the Bare Metal Provisioning service
  • Configuring load balancing as a service (Technology Preview)

1.4.4.2. RHOCP feature documentation
Copy link

Starting with RHOSO 18.0 (GA), features that are supported and managed natively in RHOCP are documented in the RHOCP documentation library. The RHOSO documentation includes links to relevant RHOCP documentation where needed.

1.4.4.3. Earlier documentation versions
Copy link

The RHOSO documentation page shows documentation for version 18.0 and later. For earlier supported versions of RHOSP, see Product Documentation for Red Hat OpenStack Platform 17.1.

1.4.5. High availability
Copy link

High availability managed natively in RHOCP
Starting with RHOSO 18.0 (GA), RHOSO high availability (HA) uses RHOCP primitives instead of RHOSP services to manage failover and recovery deployment.

1.4.6. Networking
Copy link

Egress QoS support at NIC level using DCB (Technology Preview)

Starting with RHOSO 18.0 (GA), egress quality of service (QoS) at the network interface controller (NIC) level uses the Data Center Bridging Capability Exchange (DCBX) protocol to configure egress QoS at the NIC level in the host. It triggers the configuration and provides the information directly from the top of rack (ToR) switch that peers with the host NIC. This capability, combined with egress QoS for OVS/OVN, enables end-to-end egress QoS.

This is a Technology Preview feature. A Technology Preview feature might not be fully implemented and tested. Some features might be absent, incomplete, or not work as expected.

For more information on this feature, see Feature Integration document - DCB for E2E QoS.

Configuring and deploying networking with Kubernetes NMState Operator and the RHEL NetworkManager service (Technology preview)
Starting with RHOSO 18.0 (GA), the RHOSO bare-metal network deployment uses os-net-config with a Kubernetes NMState Operator and NetworkManager back end. Therefore, administrators can use the Kubernetes NMState Operator, nmstate, and the RHEL NetworkManager CLI tool nmcli to configure and deploy networks on the data plane, instead of legacy ifcfg files and network-init-scripts.

1.4.7. NFV
Copy link

Power optimization enhancements
RHOSO 18.0 (GA) features a Tuned power saving profile, cpu-partitioning-powersave. You can use this profile to improve CPU power consumption by shutting down idle CPU cores or associated sub-systems. Additionally, support for adaptive nano sleep enables power saving for low packet rates.

1.4.8. Observability
Copy link

Enhanced Openstack Observability
  • In RHOSO 18.0 (GA), enhanced dashboards provide unified observability with visualizations that are natively integrated into the RHOCP Observability UI. These include the node_exporter agent that exposes metrics to the Prometheus monitoring system.
  • In RHOSO 18.0 (GA), the node_exporter agent replaces the collectd daemon, and Prometheus replaces the Time series database (Gnocchi).
Logging
In RHOSO 18.0 (GA), the OpenStack logging capability is significantly enhanced. You can now collect logs from the control plane and Compute nodes, and use RHOCP Logging to store them in-cluster via Loki log store or forward them off-cluster to an external log store. Logs that are stored in-cluster with Loki can be visualized in the RHOCP Observability UI console.
Service Telemetry Framework deprecation
The Observability product for previous versions of RHOSP is Service Telemetry Framework (STF). With the release of RHOSO 18.0 (GA), STF is deprecated and in maintenance mode. There are no feature enhancements for STF after STF 1.5.4, and STF status reaches end of life at the end of the RHOSP 17.1 lifecycle. Maintenance versions of STF will be released on new EUS versions of RHOCP until the end of the RHOSP 17.1 lifecycle.

1.4.9. Security
Copy link

FIPS enabled by default
  • Starting with RHOSO 18.0 (GA), Federal Information Processing Standard (FIPS) is enabled by default when RHOSO is installed on a FIPS enabled RHOCP cluster in new deployments.
  • You do not enable or disable FIPS in your RHOSO configuration. You control the FIPS state in the underlying RHOCP cluster.
TLS-everywhere enabled by default
In RHOSO 18.0 (GA), after deployment, you can configure public services with your own certificates. You can deploy without TLS-everywhere and enable it later. You cannot disable TLS-everywhere after you enable it.
Secure RBAC enabled by default
The Secure Role-Based Access Control (RBAC) policy framework is enabled by default in RHOSO 18.0 (GA) deployments.
Key Manager (barbican) enabled by default
The Key Manager is enabled by default in RHOSO 18.0 (GA) deployments.

1.4.10. Storage
Copy link

Integration with external Red Hat Ceph Storage (RHCS) 7 clusters
You can integrate RHOSO 18.0 (GA) with external RHCS 7 clusters to include RHCS capabilities with your deployment.
Distributed image import
RHOSO 18.0 (GA) introduces distributed image import for the Image service (glance). With this feature, you do not need to configure a shared staging area for different API workers to access images that are imported to the Image service. Now the API worker that owns the image data is the same API worker that performs the image import.
Block Storage service (cinder) backup and restore for thin volumes
Starting with RHOSO 18.0 (GA), the backup service for the Block Storage service service preserves sparseness when restoring a backup to a new volume. This feature ensures that restored volumes use the same amount of storage as the backed up volume. It does not apply to RBD backups, which use a different mechanism to preserve sparseness.
Support for RHCS RBD deferred deletion
RHOSO 18.0 (GA) introduces Block Storage service and Image service RBD deferred deletion, which improves flexibility in the way RBD snapshot dependencies are managed. With deferred deletion, you can delete a resource such as an image, volume, or snapshot even if there are active dependencies.
Shared File Systems service (manila) CephFS NFS driver with Ganesha Active/Active
In RHOSO 18.0 (GA), the CephFS-NFS driver for the Shared File Systems service consumes an active/active Ganesha cluster by default, improving both the scalability and high availability of the Ceph NFS service.
Unified OpenStack client parity with native Shared File Systems service client
Starting with RHOSO 18.0 (GA), the Shared File Systems service fully supports the openstack client command line interface.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat