Veritas InfoScale™ 8.0 Support for Containers - Linux
- Overview
- System requirements
- Preparing to install InfoScale on Containers
- Installing Veritas InfoScale on OpenShift
- Installing Veritas InfoScale on Kubernetes
- InfoScale CSI deployment in Container environment
- Dynamic provisioning
- Snapshot provisioning (Creating volume snapshots)
- Managing InfoScale volume snapshots with Velero
- Volume cloning
- Installing InfoScale DR on OpenShift
- Installing InfoScale DR on Kubernetes
- TECHNOLOGY PREVIEW: Disaster Recovery scenarios
- Configuring InfoScale
- Troubleshooting
Configuring cluster
After successfully installing InfoScale operator, you can create a cluster.
Edit clusterInfo section of the sample
/YAML/OpenShift/OLM/cr.yaml
for InfoScale specifications as under -Note:
You can specify up to 16 worker nodes in
cr.yaml
. Although cluster configuration is allowed even with one Network Interface Card, Veritas recommends a minimum of two physical links for performance and High Availability (HA). Number of links for each network link must be same on all nodes. Optionally, you can enter node level IP addresses. If IP addresses are not provided, IP addresses of OpenShift cluster nodes are used.clusterInfo: - nodeName: <Name of the first node> ip: - <Optional - First IP address of the first node > - <Optional - Second IP address of the first node> excludeDevice: - <Optional - Device path of the disk on the node that you want to exclude from Infoscale disk group.> - nodeName: <Name of the second node> ip: - <Optional - First IP address of the second node > - <Optional - Second IP address of the second node> excludeDevice: - <Optional - Device path of the disk on the node that you want to exclude from Infoscale disk group.> - nodeName: <Name of the third node> ip: - <Optional - First IP address of the third node > - <Optional - Second IP address of the third node> excludeDevice: - <Optional - Device path of the disk on the node that you want to exclude from Infoscale disk group.> . . . YOU CAN ADD UP TO 16 NODES.
Note:
Do not enclose parameter values in angle brackets (<>). For example, Primarynode is the name of the first node; for nodeName : <Name of the first node> , enter nodeName : Primarynode. InfoScale on OpenShift is a keyless deployment.
Run the following command on the bastion node.
oc create -f /YAML/OpenShift/OLM/cr.yaml
Run the following command on the bastion node to know the name and namespace of the cluster.
oc get infoscalecluster
Use the namespace from the output similar to the following.
NAME NAMESPACE VERSION STATE AGE infoscalecluster-dev infoscale-vtas 8.0.0.0000 Running 1m15s
Run the following command on the bastion node to verify whether the pods are created successfully.
oc get pods -n infoscale-vtas
An output similar to the following indicates a successful creation of nodes
NAME READY STATUS RESTARTS AGE infoscale-vtas-csi-driver-node-5tnct 2/2 Running 0 2m27s infoscale-vtas-csi-driver-node-6w2q7 2/2 Running 0 2m27s infoscale-vtas-csi-driver-node-lj4xz 2/2 Running 0 2m27s infoscale-vtas-csi-driver-node-vzq7s 2/2 Running 0 2m27s infoscale-vtas-driver-container-rhel8-7zcrk 1/1 Running 0 10m infoscale-vtas-driver-container-rhel8-f7h4f 1/1 Running 0 10m infoscale-vtas-driver-container-rhel8-qqjkv 1/1 Running 0 10m infoscale-vtas-driver-container-rhel8-ww8md 1/1 Running 0 10m infoscale-vtas-fencing-controller-5dd876748d-rbbgn 1/1 Running 0 2m39s infoscale-vtas-fencing-switcher-7tqwg 1/1 Running 0 2m49s infoscale-vtas-fencing-switcher-chllt 1/1 Running 0 2m49s infoscale-vtas-fencing-switcher-m5hp4 1/1 Running 0 2m49s infoscale-vtas-fencing-switcher-wdcqw 1/1 Running 0 2m49s infoscale-vtas-licensing-controller-7b749fb8d-xdwjn 1/1 Running 0 11m infoscale-operator-75667df67b-vjm5p 1/1 Running 0 14m
After a successful InfoScale deployment, a disk group is automatically created. You can now create Persistent Volumes/ Persistent Volume Claims (PV / PVC) by using the corresponding Storage class.