Installing IBM Spectrum Fusion HCI
Use this information to install IBM Spectrum Fusion HCI.
Before you begin
- A connection to the internet is required to install the software that operates the IBM Spectrum Fusion HCI appliance. If you plan to do an offline installation of IBM Spectrum Fusion, mirror external-operators and OpenShift® Container Platform image repositories to your registry. For the actual steps, see Enterprise registry for IBM Spectrum Fusion HCI installation.
- Important: You need IBM Spectrum Fusion software entitlement to access IBM Spectrum Fusion images. For steps to register your customer number in Entitlement System Support, see Registering customer number in Entitled System Support (ESS).
- Important: IBM Spectrum Fusion HCI requires Red Hat OpenShift Container Platform, which you must purchase. OpenShift is not pre-entitled with the IBM Spectrum Fusion HCI appliance. For more information, see Step 5 of Registering customer number in Entitled System Support (ESS) topic.
- Ensure that IBM Spectrum Fusion HCI is installed in a restricted access location, such that the area is accessible only to skilled and instructed persons with proper authorization.
- Follow the OpenShift Container Platform guidelines to create a
certificate. Consider the following points for the chain of certificates:
- Wildcard certificate must be the first certificate in the file
- Any intermediate certificates must follow the wildcard certificate
- End of the file must have root CA certificate
- Go through the Site-readiness topics and confirm whether your premise satisfies the requirements.
- The following are the high-level steps to set up and configure the hardware appliance:
- You must unpack the appliance and locate it in your data center. For planning and prerequisites, see Planning and prerequisites.
- The Service Support Representative (SSR) assists you in network cabling and power connections by using the details that are provided by your network team.
- The SSR assists you with the Network setup stage of the installation. The network setup includes the configuration of your network, such as high-speed switch and IP configuration. For more information, see Network planning.
- If you plan to use a proxy server for internet access, then do the following steps:
- See Firewall requirements for IBM Spectrum Fusion HCI.
- Contact IBM Support team.
- The Container Network Interface (CNI) network (daemon network) is created for Scale core pods.
By default, IP addresses are assigned for scale daemon network. You can override the default IP
address before you begin the Final installation. For the procedure, see Configuring Scale daemon network IP parameters.Note: You can override the default IP addresses only if you have not started the Final Installation Wizard.
- If you plan to install site 2 in a Metro sync DR setup, ensure that the following prerequisites
are met:
- IBM Spectrum Scale on the site 1 is healthy and all IBM Spectrum Scale core pods are up and running.
- Ensure that the disk count is same on site 1 and site 2.
About this task
The IBM support representative completes the initial verification and physically connects the system to network and power. Then, they conduct the network setup of the appliance, which connects the appliance to the data center network.
This procedure configures all the default nodes (Three controllers and three compute nodes). If you ordered additional nodes, then they get installed as well. Finally, Storage and Backup software get installed on these nodes. For upsize procedure, see Upsizing nodes.
Procedure
What to do next
- After successful installation, follow the instructions:
- If you are using the online installation mode,Edit catalog source named
ibm-operator-catalog
and, ifibm-operator-catalog
source exists, add the following lines to thespec
section:
Example catlogsource yaml:updateStrategy: registryPoll: interval: 45m
apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: ibm-operator-catalog namespace: openshift-marketplace spec: displayName: IBM Operator Catalog publisher: IBM sourceType: grpc image: icr.io/cpopen/ibm-operator-catalog:latest updateStrategy: registryPoll: interval: 45m
- If you are using enterprise registry for installation,
Delete the catalog source named
ibm-operator-catalog
from theopenshift-marketplace
namespace if theibm-operator-catalog
source exists.
- If you are using the online installation mode,
- To verify the installation, see Validating IBM Spectrum Fusion HCI installation.
- Optionally, after the storage is available, configure the OpenShift Container Platform image registry:
- Run the following command to change Removed to
Managed for
managementState
value:oc edit configs.imageregistry.operator.openshift.io cluster
For example:apiVersion: imageregistry.operator.openshift.io/v1 kind: Config metadata: creationTimestamp: "2022-05-12T09:11:56Z" finalizers: - imageregistry.operator.openshift.io/finalizer generation: 1 name: cluster resourceVersion: "3508213" uid: fc6eee2a-5dab-44ca-9b45-b7870dfa046d spec: logLevel: Normal managementState: Removed observedConfig: null operatorLogLevel: Normal proxy: {} replicas: 1 requests: read: maxWaitInQueue: 0s write: maxWaitInQueue: 0s rolloutStrategy: RollingUpdate storage: {} unsupportedConfigOverrides: null
- Run the following command to ensure that you have one of storage class set as default.
oc patch storageclass ibm-spectrum-fusion-mgmt-sc -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}'
Here, replace
ibm-spectrum-fusion-mgmt-sc
with the storage class of your choice. - Do the following steps to add storage to
Spec
section for OpenShift Container Platform image registry:- Run the following command to open
configs.imageregistry.operator.openshift.io
in edit mode:oc edit configs.imageregistry.operator.openshift.io
- Add the following to
Spec
section:storage: pvc: claim:
For example:apiVersion: imageregistry.operator.openshift.io/v1 kind: Config metadata: creationTimestamp: "2022-05-12T09:11:56Z" finalizers: - imageregistry.operator.openshift.io/finalizer generation: 1 name: cluster resourceVersion: "3518342" uid: fc6eee2a-5dab-44ca-9b45-b7870dfa046d spec: logLevel: Normal managementState: Managed storage: pvc: claim: observedConfig: null operatorLogLevel: Normal proxy: {} replicas: 1 requests: read: maxWaitInQueue: 0s write: maxWaitInQueue: 0s rolloutStrategy: RollingUpdate storage: {} unsupportedConfigOverrides: null
- Run the following command to open
- Run the following command to expose the registry outside the cluster:
oc patch configs.imageregistry.operator.openshift.io/cluster --patch ‘{“spec”:{“defaultRoute”:true}}’ --type=merge
Note: For more information about image registry operator configuration parameters, see https://docs.openshift.com/container-platform/4.10/registry/configuring-registry-operator.html.
- Run the following command to change Removed to
Managed for