diff --git a/docs_user/assemblies/assembly_adopting-the-bare-metal-provisioning-service.adoc b/docs_user/assemblies/assembly_adopting-the-bare-metal-provisioning-service.adoc index 43c724af3..37e9d9d2b 100644 --- a/docs_user/assemblies/assembly_adopting-the-bare-metal-provisioning-service.adoc +++ b/docs_user/assemblies/assembly_adopting-the-bare-metal-provisioning-service.adoc @@ -8,4 +8,4 @@ Review information about your {bare_metal_first_ref} configuration and then adop include::../modules/con_bare-metal-provisioning-service-configurations.adoc[leveloffset=+1] -include::../modules/deploying-the-bare-metal-provisioning-service.adoc[leveloffset=+1] +include::../modules/proc_deploying-the-bare-metal-provisioning-service.adoc[leveloffset=+1] diff --git a/docs_user/modules/con_changes-to-cephFS-via-NFS.adoc b/docs_user/modules/con_changes-to-cephFS-via-NFS.adoc index 5832788f1..e814dfaef 100644 --- a/docs_user/modules/con_changes-to-cephFS-via-NFS.adoc +++ b/docs_user/modules/con_changes-to-cephFS-via-NFS.adoc @@ -1,8 +1,8 @@ -[id="changes-to-cephFS-via-NFS_{context}"] +[id="changes-to-cephFS-through-NFS_{context}"] -= Changes to CephFS via NFS += Changes to CephFS through NFS -If the {rhos_prev_long} ({OpenStackShort}) {rhos_prev_ver} deployment uses CephFS via NFS as a backend for {rhos_component_storage_file_first_ref}, there's a `ceph-nfs` service on the {OpenStackShort} controller nodes deployed and managed by {OpenStackPreviousInstaller}. This service cannot be directly imported into {rhos_long} {rhos_curr_ver}. On {rhos_acro} {rhos_curr_ver}, the {rhos_component_storage_file} only supports using a "clustered" NFS service that is directly managed on the Ceph cluster. So, adoption with this service will involve a data path disruption to existing NFS clients. The timing of this disruption can be controlled by the deployer independent of this adoption procedure. +If the {rhos_prev_long} ({OpenStackShort}) {rhos_prev_ver} deployment uses CephFS through NFS as a backend for {rhos_component_storage_file_first_ref}, there's a `ceph-nfs` service on the {OpenStackShort} controller nodes deployed and managed by {OpenStackPreviousInstaller}. This service cannot be directly imported into {rhos_long} {rhos_curr_ver}. On {rhos_acro} {rhos_curr_ver}, the {rhos_component_storage_file} only supports using a "clustered" NFS service that is directly managed on the Ceph cluster. So, adoption with this service will involve a data path disruption to existing NFS clients. The timing of this disruption can be controlled by the deployer independent of this adoption procedure. On {OpenStackShort} {rhos_prev_ver}, pacemaker controls the high availability of the `ceph-nfs` service. This service is assigned a Virtual IP (VIP) address that is also managed by pacemaker. The VIP is typically created on an isolated `StorageNFS` network. There are ordering and collocation constraints established between this VIP, `ceph-nfs` and the Shared File Systems service's share manager service on the controller nodes. Prior to adopting {rhos_component_storage_file}, pacemaker's ordering and collocation constraints must be adjusted to separate the share manager service. This establishes `ceph-nfs` with its VIP as an isolated, standalone NFS service that can be decommissioned at will after completing the {OpenStackShort} adoption. diff --git a/docs_user/modules/proc_decommissioning-rhosp-standalone-ceph-NFS-service.adoc b/docs_user/modules/proc_decommissioning-rhosp-standalone-ceph-NFS-service.adoc index b76d92617..a057d93d9 100644 --- a/docs_user/modules/proc_decommissioning-rhosp-standalone-ceph-NFS-service.adoc +++ b/docs_user/modules/proc_decommissioning-rhosp-standalone-ceph-NFS-service.adoc @@ -2,7 +2,7 @@ = Decommissioning the {rhos_prev_long} standalone Ceph NFS service -If the deployment uses CephFS via NFS, you must inform your {rhos_prev_long}({OpenStackShort}) users +If the deployment uses CephFS through NFS, you must inform your {rhos_prev_long}({OpenStackShort}) users that the old, standalone NFS service will be decommissioned. Users can discover the new export locations for their pre-existing shares by querying the {rhos_component_storage_file} API. To stop using the old NFS server, they need to unmount and remount their diff --git a/docs_user/modules/proc_deploying-file-systems-service-control-plane.adoc b/docs_user/modules/proc_deploying-file-systems-service-control-plane.adoc index f3db438d7..a217c6f80 100644 --- a/docs_user/modules/proc_deploying-file-systems-service-control-plane.adoc +++ b/docs_user/modules/proc_deploying-file-systems-service-control-plane.adoc @@ -8,7 +8,7 @@ Copy the {rhos_component_storage_file_first_ref} configuration from the {rhos_pr * Ensure that {rhos_component_storage_file} systemd services (`api`, `cron`, `scheduler`) are stopped. For more information, see xref:stopping-openstack-services_migrating-databases[Stopping {rhos_prev_long} services]. -* If the deployment uses CephFS via NFS as a storage backend, ensure that +* If the deployment uses CephFS through NFS as a storage backend, ensure that pacemaker ordering and collocation constraints are adjusted. For more information, see xref:stopping-openstack-services_migrating-databases[Stopping {rhos_prev_long} services]. * Ensure that the {rhos_component_storage_file} pacemaker service (`openstack-manila-share`) is @@ -16,7 +16,7 @@ stopped. For more information, see xref:stopping-openstack-services_migrating-da * Ensure that the database migration has completed. For more information, see xref:migrating-databases-to-mariadb-instances_migrating-databases[Migrating databases to MariaDB instances]. * Ensure that {OpenShift} nodes where `manila-share` service will be deployed can reach the management network that the storage system is in. -* If the deployment uses CephFS via NFS as a storage backend, ensure that +* If the deployment uses CephFS through NFS as a storage backend, ensure that a new clustered Ceph NFS service is deployed on the Ceph cluster with the help of Ceph orchestrator. For more information, see xref:creating-a-ceph-nfs-cluster_migrating-databases[Creating a Ceph NFS cluster]. @@ -206,7 +206,7 @@ count of the `manilaShares` service/s to 1. * Ensure that the appropriate storage management network is specified in the `manilaShares` section. The example below connects the `manilaShares` instance with the CephFS backend driver to the `storage` network. -* Prior to adopting the `manilaShares` service for CephFS via NFS, ensure that +* Prior to adopting the `manilaShares` service for CephFS through NFS, ensure that you have a clustered Ceph NFS service created. You will need to provide the name of the service as ``cephfs_nfs_cluster_id``. @@ -263,7 +263,7 @@ spec: __EOF__ ---- + -Below is an example that uses CephFS via NFS. In this example: +Below is an example that uses CephFS through NFS. In this example: * The `cephfs_ganesha_server_ip` option is preserved from the configuration on the old {OpenStackShort} {rhos_prev_ver} environment. diff --git a/docs_user/modules/deploying-the-bare-metal-provisioning-service.adoc b/docs_user/modules/proc_deploying-the-bare-metal-provisioning-service.adoc similarity index 100% rename from docs_user/modules/deploying-the-bare-metal-provisioning-service.adoc rename to docs_user/modules/proc_deploying-the-bare-metal-provisioning-service.adoc diff --git a/docs_user/modules/proc_stopping-openstack-services.adoc b/docs_user/modules/proc_stopping-openstack-services.adoc index 6b213bfa0..054d6bbe6 100644 --- a/docs_user/modules/proc_stopping-openstack-services.adoc +++ b/docs_user/modules/proc_stopping-openstack-services.adoc @@ -69,7 +69,7 @@ services. The cinder-backup service on {OpenStackShort} {rhos_prev_ver} could be running as Active-Passive under pacemaker or as Active-Active, so you must check how it is running and stop it. -If the deployment enables CephFS via NFS as a backend for {rhos_component_storage_file_first_ref}, there are pacemaker ordering and co-location +If the deployment enables CephFS through NFS as a backend for {rhos_component_storage_file_first_ref}, there are pacemaker ordering and co-location constraints that govern the Virtual IP address assigned to the `ceph-nfs` service, the `ceph-nfs` service itself and `manila-share` service. These constraints must be removed: