Installing Fusion Data Foundation
Install Fusion Data Foundation in local, dynamic, external, client, or provider modes.
Before you begin
-
Important: If you install Fusion Data Foundation 4.21 or later and the Global Data Platform remote mount service is installed and configured, the service is automatically migrated to version 6.0.1.0. Review the supported migration scenarios before installation.
-
- Existing storage installations
-
If you already have an installation of Fusion Data Foundation cluster or Red Hat® OpenShift® Data Foundation cluster, the IBM Fusion UI automatically discovers it.
- In the Data Foundation page, you can only view the Usable capacity, Health, and information about the storage nodes.
- If it is Red Hat OpenShift Data Foundation, migrate it to Fusion Data Foundation by following the instructions in Upgrading Red Hat OpenShift Data Foundation to IBM Storage Fusion Data Foundation.
- If you have a Rook-Ceph operator, contact IBM Support for guidance on expected behavior.
-
- Storage device and node requirements
-
- Use a maximum of nine storage devices per node to ensure optimal recovery time and stay within cloud provider dynamic storage device attachment limits. Using more storage devices increases recovery time if a node is lost.
- Add nodes in multiples of three, with each node in a different failure domain.
- For deployments with three failure domains, scale up storage by adding disks in multiples of three, with the same number of disks from nodes in each failure domain.
-
- Clean installation verification
-
Before enabling the Fusion Data Foundation service, verify that there is no previously installed Fusion Data Foundation, Red Hat OpenShift Data Foundation, OpenShift Container Storage, or Rook-Ceph in this OpenShift cluster:
- Verify that the namespace
openshift-storagedoes not exist. - Run the following command to confirm that no storage resources exist:
oc get storagecluster -A; oc get cephcluster -A - Run the following command to confirm that no nodes have storage labels:
oc get node -l cluster.ocs.openshift.io/openshift-storage=
- Verify that the namespace
-
- Infrastructure nodes
- Ensure that the following prerequisites are met:
- For infrastructure requirements, see Infrastructure requirements.
- For Fusion Data Foundation resource requirements, see ODF sizer tool. For common Fusion Data Foundation components per instance requirements of CPU and Memory, see Resource requirements.
- If you want to deploy Fusion Data Foundation in an
Infra node, make sure the worker node label
exists.
oc get node -l "node-role.kubernetes.io/worker=" - Ensure that there are no taints in the infra or compute nodes that are used as storage nodes.
For more information about the limitations and considerations of using OVE as an alternative to OpenShift Container Platform platform, see OVE considerations.
About this task
-
Both Data Foundation service and Global Data Platform service can coexist during the following scenarios:
- Deploy Data Foundation service without
dedicatedmode. - Deploy Data Foundation in
dedicatedmode first, and then deploy Global Data Platform service.
- Deploy Data Foundation service without
- For Red Hat OpenShift Data Foundation deployed outside of IBM Fusion, you cannot add nodes or capacity from IBM Fusion. See Scaling storage in Red Hat OpenShift Data Foundation documentation.
- For client cluster with Fusion Data Foundation, you do not install IBM Fusion spoke cluster or Fusion Data Foundation from the user interface. These installations are automatically run from the IBM Fusion HCI hub cluster.
-
Data Foundation service supports five storage types: local, dynamic, external, client, and provider. Only one device type can be used for Data Foundation service in an OpenShift Container Platform. For more information about the different deployment modes, see Storage cluster deployment approaches.
The following table shows supported platforms and which device types are supported in each platform.Platform Support VMware Local, dynamic, client, and external device Bare Metal Local, external device, client, provider mode Linux on IBM Z Local, dynamic, client, and external device IBM Power Systems Local, client, and external device ROKS on IBM Cloud (ROKS on VPC and Classic Bare Metal) Cloud-managed Fusion Data Foundation service. For the procedure to install, see Understanding Fusion Data Foundation. Self managed OpenShift Container Platform on Microsoft Azure Dynamic and client Self managed OpenShift Container Platform on Amazon Web Services Dynamic and client Amazon Web Services ROSA and Amazon Web Services ROSA HCP Dynamic and client Self managed OpenShift Container Platform on Google Cloud Dynamic and client - For IBM Fusion services and platform support matrix, see IBM Fusion services and platform support matrix.
Procedure
What to do next
Configure the Fusion Data Foundation storage service by following the instructions mentioned in Configuring Fusion Data Foundation.
Optionally, you can also setup encryption to use an external Key Management System. For the procedure to set up encryption, see Preparing to connect to an external KMS server in Fusion Data Foundation.