You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Make sure to set the correct {rhos_acro} project namespace in which to run commands.
24
-
ifeval::["{build_variant}" == "ospdo"]
25
-
* In director Operator adoption, the source {rhos_prev_long} {rhos_prev_ver} namespace is `openstack`. In order to successfully adopt the {OpenStackShort} {rhos_prev_ver} environment, the destination {rhos_acro} {rhos_curr_ver} namespace must be different, for example, `rhoso`.
26
-
endif::[]
27
-
+
28
-
[source, shell]
29
-
----
30
-
ifeval::["{build_variant}" == "ospdo"]
31
-
$ oc project rhoso
32
-
endif::[]
33
-
ifeval::["{build_variant}" != "ospdo"]
34
-
$ oc project openstack
35
-
endif::[]
36
-
----
37
23
* Familiarize yourself with mapping RHOSO versions to OpenStack Operators and OpenStackVersion custom resources (CRs). For more information, see the Red Hat Knowledgebase article link:https://access.redhat.com/articles/7125383[How RHOSO versions map to OpenStack Operators and OpenStackVersion CRs].
38
24
39
25
Back-up information::
@@ -47,21 +33,33 @@ Back-up information::
47
33
Compute::
48
34
+
49
35
* Upgrade your Compute nodes to Red Hat Enterprise Linux {rhel_prev_ver}. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html-single/framework_for_upgrades_16.2_to_17.1/index#upgrading-compute-nodes_upgrading-the-compute-node-operating-system[Upgrading all Compute nodes to RHEL 9.2] in _Framework for upgrades (16.2 to 17.1)_.
50
-
* Perform a minor update to the latest {OpenStackShort} version. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/performing_a_minor_update_of_red_hat_openstack_platform/index[Performing a minor update of Red Hat OpenStack Platform].
51
-
* Install the `systemd-container` package on your Compute hosts. For more information, see xref:installing-the-systemd-container-package-on-compute-hosts_{context}[Installing the `systemd-container` package on Compute hosts].
36
+
* On your Compute hosts, the `systemd-container` package must be installed and the `systemd-machined` service must be running. For more information about how to verify that the package is installed and that the service is running, see xref:installing-the-systemd-container-package-on-compute-hosts_{context}[Installing the `systemd-container` package on Compute hosts].
52
37
53
38
ML2/OVS::
54
39
+
55
40
* If you use the Modular Layer 2 plug-in with Open vSwitch mechanism driver (ML2/OVS), migrate it to the Modular Layer 2 plug-in with Open Virtual Networking (ML2/OVN) mechanism driver. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/migrating_to_the_ovn_mechanism_driver/index[Migrating to the OVN mechanism driver].
56
41
57
42
Tools::
58
43
+
59
-
* Install the `oc` command line tool on your workstation.
60
-
* Install the `podman` command line tool on your workstation.
44
+
* The oc and podman command line tools are installed on your workstation.
45
+
* Make sure to set the correct {rhos_acro} project namespace in which to run commands.
46
+
ifeval::["{build_variant}" == "ospdo"]
47
+
* In director Operator adoption, the source {rhos_prev_long} {rhos_prev_ver} namespace is `openstack`. In order to successfully adopt the {OpenStackShort} {rhos_prev_ver} environment, the destination {rhos_acro} {rhos_curr_ver} namespace must be different, for example, `rhoso`.
48
+
endif::[]
49
+
+
50
+
[source, shell]
51
+
----
52
+
ifeval::["{build_variant}" == "ospdo"]
53
+
$ oc project rhoso
54
+
endif::[]
55
+
ifeval::["{build_variant}" != "ospdo"]
56
+
$ oc project openstack
57
+
endif::[]
58
+
----
61
59
62
60
{OpenStackShort} {rhos_prev_ver} release::
63
61
+
64
-
* The {OpenStackShort} {rhos_prev_ver} cloud is updated to the latest minor version of the {rhos_prev_ver} release.
62
+
* The {OpenStackShort} {rhos_prev_ver} cloud is updated to the 17.1.4 release or later. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/performing_a_minor_update_of_red_hat_openstack_platform/index[Performing a minor update of Red Hat OpenStack Platform].
Copy file name to clipboardExpand all lines: docs_user/modules/con_identity-service-authentication.adoc
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,15 @@
4
4
= {identity_service} authentication
5
5
6
6
[role="_abstract"]
7
-
If you have custom policies enabled, contact Red Hat Support before adopting a {OpenStackPreviousInstaller} OpenStack deployment. You must complete the following steps for adoption:
7
+
If you have custom policies enabled, complete the following steps for adoption:
8
8
9
9
. Remove custom policies.
10
10
. Run the adoption.
11
11
. Re-add custom policies by using the new SRBAC syntax.
12
12
13
+
[IMPORTANT]
14
+
Red Hat does not support customized roles or policies. Syntax errors or misapplied authorization can negatively impact security or usability. If you need customized roles or policies in your production environment, contact Red Hat support for a support exception before you begin the adoption.
15
+
13
16
After you adopt a {OpenStackPreviousInstaller}-based OpenStack deployment to a {rhos_long_noacro} deployment, the {identity_service} performs user authentication and authorization by using Secure RBAC (SRBAC). If SRBAC is already enabled, then there is no change to how you perform operations. If SRBAC is disabled, then adopting a {OpenStackPreviousInstaller}-based OpenStack deployment might change how you perform operations due to changes in API access policies.
14
17
15
18
For more information on SRBAC, see link:{defaultURL}/performing_security_operations/assembly_srbac-in-rhoso_performing-security-services#assembly_srbac-in-rhoso_performing-security-services[Secure role based access control in Red Hat OpenStack Services on OpenShift] in _Performing security operations_.
Copy file name to clipboardExpand all lines: docs_user/modules/proc_adopting-the-block-storage-service.adoc
+57-3Lines changed: 57 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,9 +168,8 @@ Ensure that you use the same configuration group name for the driver that you us
168
168
====
169
169
+
170
170
. Configure the NetApp NFS Block Storage volume service:
171
-
.. Create secrets that include sensitive information such as hostnames, passwords, and usernames to access the third-party NetApp NFS storage. You can find the credentials in the `cinder.conf` file that was generated from the {OpenStackPreviousInstaller} deployment.
171
+
.. Create a secret that includes sensitive information such as hostnames, passwords, and usernames to access the third-party NetApp NFS storage. You can find the credentials in the `cinder.conf` file that was generated from the {OpenStackPreviousInstaller} deployment:
* The following example shows a `cinder_netappNFS.patch` file that configures a NetApp NFS Block Storage volume service:
200
+
* Replace `<cinder_netappNFS.patch>` with the name of the patch file for your NetApp NFS Block Storage volume back end.
201
+
+
202
+
The following example shows a `cinder_netappNFS.patch` file that configures a NetApp NFS Block Storage volume service:
202
203
+
203
204
[source,yaml]
204
205
----
@@ -224,6 +225,59 @@ spec:
224
225
customServiceConfigSecrets:
225
226
- cinder-volume-ontap-secrets
226
227
----
228
+
+
229
+
. Configure the NetApp iSCSI Block Storage volume service:
230
+
.. Create a secret that includes sensitive information such as hostnames, passwords, and usernames to access the third-party NetApp iSCSI storage. You can find the credentials in the `cinder.conf` file that was generated from the {OpenStackPreviousInstaller} deployment:
Copy file name to clipboardExpand all lines: docs_user/modules/proc_installing-the-systemd-container-package-on-compute-hosts.adoc
+52-3Lines changed: 52 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,11 +4,60 @@
4
4
= Installing the `systemd-container` package on Compute hosts
5
5
6
6
[role="_abstract"]
7
-
Before you adopt the {rhos_long} data plane, you must install the `systemd-container` package on all the hypervisors on your Compute hosts. This procedure must be performed on one Compute host at a time.
7
+
Before you adopt the {rhos_long} data plane, you must verify that the `systemd-container` package is installed and that `systemd-machined` is running on all the Compute hosts. You must install the `systemd-container` package on each Compute host that does not have this package.
8
8
9
9
.Procedure
10
10
11
-
. If your Compute host is running a virtual machine, live migrate the virtual machine from the host. For more information about live migration, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/performing_a_minor_update_of_red_hat_openstack_platform/assembly_rebooting-the-overcloud_keeping-updated#proc_rebooting-compute-nodes_rebooting-the-overcloud[Rebooting Compute nodes] in _Performing a minor update of Red Hat OpenStack Platform_.
11
+
. Log in to the Compute node host as a user with the appropriate permissions.
12
+
13
+
. List the instances that are running on the host:
14
+
+
15
+
----
16
+
$ sudo machinectl list
17
+
----
18
+
+
19
+
Sample output::
20
+
+
21
+
----
22
+
MACHINE CLASS SERVICE OS VERSION ADDRESSES
23
+
qemu-1-instance-000000b9 vm libvirt-qemu - - -
24
+
qemu-2-instance-000000c2 vm libvirt-qemu - - -
25
+
26
+
2 machines listed.
27
+
----
28
+
29
+
. Verify that the `systemd-machined` service is running:
30
+
+
31
+
----
32
+
$ sudo systemctl status systemd-machined.service
33
+
----
34
+
+
35
+
Sample output::
36
+
+
37
+
----
38
+
systemd-machined.service - Virtual Machine and Container Registration Service
Active: active (running) since Mon 2025-06-16 11:42:07 EDT; 2min 48s ago
41
+
Docs: man:systemd-machined.service(8)
42
+
man:org.freedesktop.machine1(5)
43
+
Main PID: 136614 (systemd-machine)
44
+
Status: "Processing requests..."
45
+
Tasks: 1 (limit: 838860)
46
+
Memory: 1.4M
47
+
CPU: 33ms
48
+
CGroup: /system.slice/systemd-machined.service
49
+
└─136614 /usr/lib/systemd/systemd-machined
50
+
51
+
Jun 16 11:42:07 computehost001 systemd[1]: Starting Virtual Machine and Container Registration Service...
52
+
Jun 16 11:42:07 computehost001 systemd[1]: Started Virtual Machine and Container Registration Service.
53
+
Jun 16 11:43:44 computehost001 systemd-machined[136614]: New machine qemu-1-instance-000000b9.
54
+
Jun 16 11:43:51 computehost001 systemd-machined[136614]: New machine qemu-2-instance-000000c2.
55
+
----
56
+
+
57
+
[IMPORTANT]
58
+
If the `systemd-machined` service is running, skip the rest of this procedure. Ensure that you verify that the `systemd-machined` service is running each Compute node host in the cluster.
59
+
60
+
. If the `systemd-machined` service is not running, before you can install the `systemd-container` package, live migrate all virtual machines from the host. For more information about live migration, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/performing_a_minor_update_of_red_hat_openstack_platform/assembly_rebooting-the-overcloud_keeping-updated#proc_rebooting-compute-nodes_rebooting-the-overcloud[Rebooting Compute nodes] in _Performing a minor update of Red Hat OpenStack Platform_.
12
61
13
62
. Install the `systemd-container` on the host:
14
63
** If you upgraded your environment from an earlier version of {rhos_prev_long}, reboot the Compute host to automatically install the `systemd-container`.
0 commit comments