Creating a Fusion Data Foundation cluster on managed clusters

About this task

In order to configure storage replication between the two OpenShift Container Platform clusters, create an Fusion Data Foundation storage system after you install the Fusion Data Foundation operator.

Note: Refer to Fusion Data Foundation deployment guides and instructions that are specific to your infrastructure (AWS, VMware, BM, Azure, etc.).

Procedure

Install and configure the latest Fusion Data Foundation cluster on each of the managed clusters.

For information about the Fusion Data Foundation deployment, refer to your infrastructure specific deployment guides (for example, AWS, VMware, Bare metal, Azure).
Validate the successful deployment of Fusion Data Foundation on each managed cluster with the following command:
```
oc get storagecluster -n openshift-storage ocs-storagecluster -o jsonpath='{.status.phase}{"\n"}'
```
For the Multicloud Gateway (MCG):
```
oc get noobaa -n openshift-storage noobaa -o jsonpath='{.status.phase}{"\n"}'
```
If the status result is Ready for both queries on the Primary managed cluster and the Secondary-managed cluster, then continue with the next step.
In the OpenShift Web Console, navigate to Installed Operators > > Storage System > ocs-storagecluster-storagesystem > Resources and verify that Status of StorageCluster is Ready and has a green tick mark next to it.
Optional: If Globalnet was enabled when Submariner was installed, then edit the StorageCluster after the OpenShift Data Foundation install finishes.
For Globalnet networks, manually edit the StorageCluster YAML file to add the clusterID and set enabled to true. Replace <clustername> with your RHACM imported or newly created managed cluster name. Edit the StorageCluster on both the Primary managed cluster and the Secondary managed cluster.
Warning: Do not make this change in the StorageCluster unless you enabled Globalnet when Submariner was installed.
```
oc edit storagecluster -o yaml -n openshift-storage
```
```
spec:
  network:
    multiClusterService:
      clusterID: <clustername>
      enabled: true
```
After the above changes are made,
1. Wait for the OSD pods to restart and OSD services to be created.
2. Wait for all MONS to failover.
3. Ensure that the MONS and OSD services are exported.
```
oc get serviceexport -n openshift-storage
```
```
NAME              AGE
rook-ceph-mon-d   4d14h
rook-ceph-mon-e   4d14h
rook-ceph-mon-f   4d14h
rook-ceph-osd-0   4d14h
rook-ceph-osd-1   4d14h
rook-ceph-osd-2   4d14h
```
4. Ensure that cluster is in a Ready state and cluster health has a green tick indicating Health ok. Verify using step 3.