Deploying IBM Cloud Satellite hosts
Steps to set up, configure, and deploy IBM Cloud® Satellite hosts.
Before you begin
- Install Red Hat®OpenShift® Virtualization Operator.Note:
- For the installation steps, see About OpenShift Virtualization.
- To know the supported Guest Operating System, see https://access.redhat.com/articles/973163.
- Supports only Red Hat Enterprise Linux server 8.x.
- Download the latest KVM image of Red Hat Enterprise Linux Server release 8.8 or higher. It is available at https://access.redhat.com/downloads/content/479/ver=/rhel---8/8.8/x86_64/product-software.
- If an image does not exist, do the following steps to create an image.
Rephrase leading sentence.
:- IBM Cloud Satellite operator assumes the availability of
a registry, where the virtual machine image can be stored. Red Hat Enterprise Linux (RHEL) 8.X
images are available in qcow2 format. The qcow2 images must be uploaded and available for the
registry. Use the following docker file to create an image:
FROM scratch ADD ./rhel-8.8-x86_64-kvm.qcow2 /disk/
- Use the following script to create and push the image to the docker
registry.
#!/bin/sh docker build -t qcow2-image:latest docker image tag qcow2-image:latest <docker-repo>/qcow2-image:latest docker image push hub.docker.com/repository/docker/satelliteimage/qcow2-image:latest
Note: Before you run the docker build command, make sure that you use only the external OpenShift registry for these images and therhel-server-8.8-x86_64-kvm.qcow2
on the path where you have the Dockerfile.
- IBM Cloud Satellite operator assumes the availability of
a registry, where the virtual machine image can be stored. Red Hat Enterprise Linux (RHEL) 8.X
images are available in qcow2 format. The qcow2 images must be uploaded and available for the
registry. Use the following docker file to create an image:
- Create a VLAN of type IBM Cloud Satellite and add the created VLAN to Link. For more information about VLAN, see Adding VLANs. For more information about Link, see Adding links.
- Verify IBM Cloud Satellite operator installation:
Verify whether the IBM Cloud Satellite is installed, and the corresponding pod is in Running state in the
ibm-spectrum-fusion-ns
project. Do these steps:- Log in to IBM Storage Fusion.
- From the menu, click OpenShift console to go to the OpenShift web management console.
- Go to .
- Verify whether the
isf-ics-operator-controller-manager
is in Running state.
- Verify whether the following secrets and
Configmaps
are available:Note:- If they are not available, then use the OC command to create the secrets and the sample YAML
file to create the
Configmap
. - After
isf-operator
upgrade, theisf-ui-operator-ics-config
configmap gets reset to default. Before you deploy any new satellite locations, update configmap parameters with proper values.
- Secret
<Secret> isf-ics-pull-secret
Here,oc create secret docker-registry isf-ics-pull-secret --docker-server=<docker-server> --docker-username=<username> --docker-password=<password> --docker-email=<email ID> -n ibm-spectrum-fusion-ns
docker-server
,username
andpassword
are for the docker registry where the qcow2 image is mirrored.<Secret> isf-ics-rhsubscription
You must have access to all the Red Hat repositories. This secret stores Red Hat subscription details.oc create secret generic isf-ics-rhsubscription --from-literal=rhsuser=<Redhat Subscription Username> --from-literal=rhspassword=<Redhat Subscription Password> -n ibm-spectrum-fusion-ns
- Configmap
The
isf-ui-operator-ics-config
configmap has two parameters, namely storageclass and isfregistryurl. Before you deploy Satellite Locations, update these parameters with proper values.The sample value for storageclass is
ibm-spectrum-fusion
and format for isfregistryurl sample value isdocker-registry/<path to file>/qcow2-image:latest
.
- If they are not available, then use the OC command to create the secrets and the sample YAML
file to create the
- Review and follow the host network requirements that relate to the network setup and inbound connectivity requirements of host machines. For more information, see Host network and Inbound connectivity requirements.
- Review and follow the outbound connectivity requirements for hosts in all regions. For the required outbound connectivity for hosts in all regions, see Required outbound connectivity for hosts in all regions.