Deploying IBM Fusion using CLI
Use the instructions to deploy the IBM Fusion using the command-line interface (CLI).
Procedure
- Log in to the OpenShift® terminal
using the following command.
oc login --token=${TOKEN_VALUE} --server=${SERVER_NAME}
- Create the YAML to deploy the IBM Fusion.
cat << EOF > deployfusion.yaml apiVersion: v1 kind: Namespace metadata: name: ibm-spectrum-fusion-ns --- apiVersion: operators.coreos.com/v1 kind: OperatorGroup metadata: name: isf-og namespace: ibm-spectrum-fusion-ns spec: targetNamespaces: - ibm-spectrum-fusion-ns upgradeStrategy: Default --- apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: ibm-operator-catalog namespace: openshift-marketplace spec: sourceType: grpc image: icr.io/cpopen/ibm-operator-catalog:latest displayName: IBM Operator Catalog publisher: IBM updateStrategy: registryPoll: interval: 45m --- apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: isf-operator namespace: ibm-spectrum-fusion-ns spec: channel: v2.0 name: isf-operator sourceNamespace: openshift-marketplace source: ibm-operator-catalog installPlanApproval: Automatic EOF
- Run the following command to apply the YAML created in the previous
step.
Sample output:oc apply -f deployfusion.yaml
namespace/ibm-spectrum-fusion-ns created operatorgroup.operators.coreos.com/isf-og created catalogsource.operators.coreos.com/ibm-operator-catalog created subscription.operators.coreos.com/isf-operator created
- Run the following command to verify whether the IBM Fusion is
deployed.
Sample output:oc get pods -n ibm-spectrum-fusion-ns
NAME READY STATUS RESTARTS AGE fusion-console-8fcc98dd7-slp8g 1/1 Running 0 3m36s isf-application-operator-controller-manager-5796c55576-9p76j 2/2 Running 0 3m50s isf-cns-operator-controller-manager-6f6c5ff5b7-kfx87 2/2 Running 0 3m54s isf-data-protection-operator-controller-manager-7fbd4489f-vqn9j 2/2 Running 0 3m58s isf-prereq-operator-controller-manager-76b8547ff5-hj9zw 2/2 Running 0 4m2s isf-proxy-6bb976f5cf-9n7fn 1/1 Running 0 3m36s isf-proxy-6bb976f5cf-xt25d 1/1 Running 0 3m36s isf-serviceability-operator-controller-manager-7dc8bbc7fb-zkdt8 2/2 Running 0 3m37s isf-ui-dep-85688bb65f-g8zhg 1/1 Running 0 3m36s isf-ui-dep-85688bb65f-hhd8k 1/1 Running 0 3m36s isf-ui-operator-controller-manager-6b78f885c4-2jcmh 2/2 Running 0 3m41s isf-update-operator-controller-manager-76b89b777f-lbdvp 2/2 Running 0 3m45s
- After the IBM Fusion installation,
create the YAML to accept the license. Note: For Global Data Platform installation, ensure the
Enable
filed is set to true.cat << EOF > accept_license.yaml apiVersion: prereq.isf.ibm.com/v1 kind: SpectrumFusion metadata: name: spectrumfusion namespace: ibm-spectrum-fusion-ns spec: GlobalDataPlatform: Enable: true license: accept: true EOF
- Run the following command to apply the YAML created in the previous step to accept the
license.
Sample output:oc apply -f accept_license.yaml
spectrumfusion.prereq.isf.ibm.com/spectrumfusion created
- Run the following command to check whether the CR is created
successfully.
Sample output:oc get SpectrumFusion -n ibm-spectrum-fusion-ns
NAME AGE spectrumfusion 4m53s
- Run the following command to check the IBM Fusion service
instances.
Sample output:oc get FusionServiceDefinitions -n ibm-spectrum-fusion-ns
NAME AGE data-cataloging-service-definition 18m data-foundation-service 18m ibm-backup-restore-agent-service 18m ibm-backup-restore-service 18m
- Run the following command to check the Global Data Platform installation
status.
Sample output:oc get spectrumfusion -n ibm-spectrum-fusion-ns -o json
"status": { "GlobalDataPlatformStatus": { "ServiceEnabled": true, "health": "Healthy", "installStatus": "Completed", "installStatusMessage": "IBM Storage Scale installation is succeeded", "installStatusMessageCode": "BMYSS0003", "isCRCRendered": false, "isDeployable": true, "isMachineConfigRendered": false, "isSupported": true, "isUpgradeFailed": false, "isUpgradeInProgress": false, "maxAvailableVersion": "5.2.1.1", "progressPercentage": 100, "upgradeAvailable": false, "version": "5.2.1.1" }