2.2. コントロールプレーン上の OVN サービスの更新

+
* Replace  `<openstack_version>` with the target version you want to install, for example, `1.0.1`.
* Replace `<custom_image>` with the location of the latest custom image for the service. You must update the image location for any custom images and the target version at the same time to ensure that the correct custom image is used after the minor update is complete.

. Patch the `OpenStackVersion` CR:
+

+
* Replace `<openstack_version_CR_name>` with the name of your `OpenStackVersion` resource, for example, `openstack-control-plane`.

. Verify that the OVN services are updated on the control plane:
+

+
The following example output shows that the OVN services are updated:
+

:leveloffset: 1

:leveloffset: +1

:_mod-docs-content-type: PROCEDURE
[id="proc_updating-ovn-on-the-data-plane_{context}"]

= Updating OVN services on the data plane

[role="_abstract"]
Update the OVN services on the data plane.

.Prerequisites

* Create the `openstack-edpm-update-ovn.yaml` file. For more information, see xref:proc_creating-files-for-data-plane-update_preparing-minor-update[Creating the files for the data plane update].

.Procedure

. To update OVN services on the data plane, create an `OpenStackDataPlaneDeployment` custom resource (CR) with the `openstack-edpm-update-ovn.yaml` file:
+

. Verify that the data plane update deployment succeeded:
+

+

+
* Replace `<openstack_version_CR_name>` with the name of your `OpenStackVersion` resource, for example, `openstackversion/openstack`.
+
If the deployment fails, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/deploying_red_hat_openstack_services_on_openshift/assembly_creating-the-data-plane#assembly_troubleshooting-data-plane-creation-and-deployment[Troubleshooting data plane creation and deployment] in the _Deploying Red Hat OpenStack Services on OpenShift_ guide.

[IMPORTANT]
====
If the update fails, you can re-run the procedure. Before you re-run the procedure, you must edit the `name:` parameter in the  `openstack-edpm-update-ovn.yaml` file to avoid conflicts in the CR name. For example:

* Replace `<ovn-update-new-name>` with a unique name for the CR.
====

:leveloffset: 2

:leveloffset: +1

:_mod-docs-content-type: PROCEDURE
[id="proc_verifying-the-control-plane-services-update_{context}"]

= Verifying the control plane services update

[role="_abstract"]
Verify that the automatic update of the control plane services is complete before you begin updating the remaining services on the data plane.

.Procedure

* Wait until all control plane services are updated:
+

+
** Replace `<openstack_version_CR_name>` with the name of the `OpenStackVersion` resource, for example, `openstackversion/openstack`.
+
The command returns the following output when all the control plane services are updated:
+

:leveloffset: 2

:leveloffset: +1

:_mod-docs-content-type: PROCEDURE
[id="proc_updating-services-on-the-data-plane_{context}"]

= Updating the remaining services on the data plane

[role="_abstract"]
When the OVN service is updated on the control plane and data plane, and the OpenStack Operator has completed the automatic update of the remaining control plane packages, services, and container images, you must update the remaining services on the data plane.

.Prerequisites

* Create the `openstack-edpm-update-services.yaml` file. For more information, see xref:proc_creating-files-for-data-plane-update_preparing-minor-update[Creating the files for the data plane update].
* The OVN service is updated on the control plane. For more information, see xref:proc_updating-ovn-on-the-control-plane_perform-update[Updating OVN services on the control plane].
* The OVN service is updated on the data plane. For more information, see xref:proc_updating-ovn-on-the-data-plane_perform-update[Updating OVN services on the data plane].

.Procedure

. Create an `OpenStackDataPlaneDeployment` custom resource (CR) with the `openstack-edpm-update-services.yaml` file:
+

. Verify that the data plane update deployment succeeded:
+

+

+
If the deployment fails, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/deploying_red_hat_openstack_services_on_openshift/assembly_creating-the-data-plane#assembly_troubleshooting-data-plane-creation-and-deployment[Troubleshooting data plane creation and deployment] in the _{deploying-rhoso-t}_ guide.

.Troubleshooting

If the update fails, you can re-run the procedure. Before you re-run the procedure, you must edit the `name:` parameter in the  `openstack-edpm-update-services.yaml` file to avoid conflicts in the CR name. For example:

* Replace `<services-update-new-name>` with a unique name for the CR.

:leveloffset: 2

:leveloffset!:

:leveloffset: +1

:_mod-docs-content-type: ASSEMBLY
[id="assembly_updating-the-operating-system_{context}"]

= Updating the operating system

:context: update-operating-system

[role="_abstract"]

Update your operating system to access the full feature set from the latest release and to improve support.

You can update your operating system by choosing one of the following options:

* Update to the latest release within your current EUS stream: Provides the latest packages and bug fixes.
* Switch to a new EUS stream: Provides additional hardware enablement, full feature compatibility, and extends support for new RHEL minor releases.


:leveloffset: +1

:_mod-docs-content-type: PROCEDURE
[id="proc_updating-the-RHEL-version-current-stream_{context}"]

= Updating the RHEL version within the current EUS stream

[role="_abstract"]
Update Compute nodes to use the full feature set from the latest release within your current EUS stream and to align with the maximum support lifecycle. Update RHEL 9.2 or 9.4 to RHEL 9.6 any time after updating control plane and data plane services.

.Prerequisites

* All of the control plane and data plane services have finished updating.

.Procedure

. Create a file named `openstack-edpm-update-system.yaml` on your workstation and include the following content:
+

. To update the operating system on the data plane, create an `OpenStackDataPlaneDeployment` custom resource (CR) with the `openstack-edpm-update-system.yaml` file:
+

. Wait for the system update to finish:
+

+
The command returns the following output when all the control plane services are updated:
+

. Verify that the system update succeeded:
+

:leveloffset: 2

:leveloffset: +1

:_mod-docs-content-type: PROCEDURE
[id="proc_updating-the-rhel-eus-stream-on-data-plane-nodes_{context}"]

= Updating the RHEL EUS stream on data plane nodes

[role="_abstract"]

Update your {rhos_long} data plane nodes to the latest Red Hat Enterprise Linux (RHEL) Extended Update Support (EUS) stream for additional hardware enablement, full feature compatibility, and improved support. For more information about RHEL EUS streams, see link:https://access.redhat.com/support/policy/updates/errata#Extended_Update_Support[Red Hat Enterprise Linux Life Cycle].

* You can update the RHEL EUS stream in a separate maintenance window after you adopt the RHOSO data plane.
* You can update the RHEL EUS stream on different node sets in different maintenance windows. For example, you can update one node set from RHEL 9.2 to RHEL 9.4 or 9.6 in one maintenance window, and then update a different node set in another maintenance window later.

.Prerequisites

* Your nodes are registered to Red Hat Content Delivery Network (CDN) or Red Hat Satellite 6.13.
** If your environment includes pre-provisioned nodes, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/deploying_red_hat_openstack_services_on_openshift/assembly_creating-the-data-plane#proc_creating-an-OpenStackDataPlaneNodeSet-CR-with-preprovisioned-nodes_dataplane[Creating an OpenStackDataPlaneNodeSet CR with pre-provisioned nodes] in _Deploying Red Hat OpenStack Services on OpenShift_.
** If your environment includes unprovisioned nodes, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/deploying_red_hat_openstack_services_on_openshift/assembly_creating-the-data-plane#proc_creating-an-OpenStackDataPlaneNodeSet-CR-with-unprovisioned-nodes_dataplane[Creating an OpenStackDataPlaneNodeSet CR with unprovisioned nodes] in _Deploying Red Hat OpenStack Services on OpenShift_.

:_mod-docs-content-type: SNIPPET

//If you need to call out a specific feature, add the following sentence as the first sentence in the tech preview note:
//"<feature_name> is a Technology Preview feature only."
//Replace "<feature_name>" with the name of the feature.

[IMPORTANT]
====
Technology Preview features are not supported with Red{nbsp}Hat production service level agreements (SLAs) and might not be functionally complete. Red{nbsp}Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red{nbsp}Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
====

.Procedure

. Optional: Live migrate the instances from the Compute nodes that you plan to update. For more information about your options for live migration, see the following documentation:
+
* link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/configuring_the_compute_service_for_instance_creation/assembly_migrating-virtual-machine-instances-between-compute-nodes_migrating-instances[Migrating virtual machine instances between Compute nodes] in _Configuring the Compute service for instance creation_.
* link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/optimizing_infrastructure_resource_utilization/sample-optimize-workflows_rhoso-optmz#prepare-compute-nodes-plan-maint_wrkfl-optmz[Preparing Compute nodes for planned maintenance] in _Optimizing infrastructure resource utilization_.

. Log in to a Compute node and confirm the current release. For example:
+

+