Veritas InfoScale™ for Kubernetes Environments 8.0.100 - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.100)
  1. Overview
    1.  
      Introduction
    2.  
      Features of InfoScale in Containerized environment
    3.  
      CSI Introduction
    4.  
      I/O fencing
    5.  
      Disaster Recovery
    6.  
      Licensing
  2. System requirements
    1.  
      Introduction
    2.  
      Supported platforms
    3.  
      Disk space requirements
    4.  
      Hardware requirements
    5.  
      Number of nodes supported
    6.  
      DR support
  3. Preparing to install InfoScale on Containers
    1. Setting up the private network
      1.  
        Guidelines for setting the media speed for LLT interconnects
      2.  
        Guidelines for setting the maximum transmission unit (MTU) for LLT
    2.  
      Synchronizing time settings on cluster nodes
    3.  
      Securing your InfoScale deployment
    4.  
      Configuring kdump
  4. Installing Veritas InfoScale on OpenShift
    1.  
      Introduction
    2.  
      Prerequisites
    3.  
      Additional Prerequisites for Azure RedHat OpenShift (ARO)
    4. Installing InfoScale on a system with Internet connectivity
      1. Installing from OperatorHub by using web console
        1.  
          Adding Nodes to an InfoScale cluster by using OLM
        2.  
          Undeploying and uninstalling InfoScale
      2. Installing from OperatorHub by using Command Line Interface (CLI)
        1.  
          Configuring cluster
        2.  
          Adding nodes to an existing cluster
        3.  
          Undeploying and uninstalling InfoScale by using CLI
      3. Installing by using YAML
        1.  
          Configuring cluster
        2.  
          Adding nodes to an existing cluster
        3.  
          Undeploying and uninstalling InfoScale
    5. Installing InfoScale in an air gapped system
      1.  
        Prerequisites to install by using YAML
      2.  
        Prerequisites to install by using OLM
      3.  
        Installing from OperatorHub by using web console
      4.  
        Installing from OperatorHub by using Command Line Interface (CLI)
      5.  
        Installing by using YAML
  5. Installing Veritas InfoScale on Kubernetes
    1.  
      Introduction
    2. Prerequisites
      1.  
        Installing Node Feature Discovery (NFD) Operator and Cert-Manager on Kubernetes
    3.  
      Installing the Special Resource Operator
    4.  
      Applying licenses
    5. Tagging the InfoScale images on Kubernetes
      1.  
        Downloading side car images
    6. Installing InfoScale on Kubernetes
      1.  
        Configuring cluster
      2.  
        Adding nodes to an existing cluster
    7.  
      Undeploying and uninstalling InfoScale
  6. Tech Preview: Configuring KMS-based Encryption on an OpenShift cluster
    1.  
      Introduction
    2.  
      Adding a custom CA certificate
    3.  
      Configuring InfoScale to enable transfer of keys
  7. Tech Preview: Configuring KMS-based Encryption on a Kubernetes cluster
    1.  
      Introduction
    2.  
      Adding a custom CA certificate
    3.  
      Configuring InfoScale to enable transfer of keys
  8. InfoScale CSI deployment in Container environment
    1.  
      CSI plugin deployment
    2.  
      Static provisioning
    3. Dynamic provisioning
      1.  
        Reclaiming provisioned storage
    4.  
      Resizing Persistent Volumes (CSI volume expansion)
    5. Snapshot provisioning (Creating volume snapshots)
      1.  
        Dynamic provisioning of a snapshot
      2.  
        Static provisioning of an existing snapshot
      3.  
        Using a snapshot
      4.  
        Restoring a snapshot to new PVC
      5.  
        Deleting a volume snapshot
    6. Managing InfoScale volume snapshots with Velero
      1.  
        Setting up Velero with InfoScale CSI
      2.  
        Taking the Velero backup
      3.  
        Creating a schedule for a backup
      4.  
        Restoring from the Velero backup
    7. Volume cloning
      1.  
        Creating volume clones
      2.  
        Deleting a volume clone
    8.  
      Using InfoScale with non-root containers
    9.  
      Using InfoScale in SELinux environments
    10.  
      CSI Drivers
    11.  
      Creating CSI Objects for OpenShift
  9. Installing and configuring InfoScale DR Manager on OpenShift
    1.  
      Introduction
    2.  
      Prerequisites
    3.  
      Creating Persistent Volume for metadata backup
    4.  
      External dependencies
    5. Installing InfoScale DR Manager by using OLM
      1.  
        Installing InfoScale DR Manager by using web console
      2.  
        Configuring InfoScale DR Manager by using web console
      3.  
        Installing from OperatorHub by using Command Line Interface (CLI)
    6. Installing InfoScale DR Manager by using YAML
      1.  
        Configuring Global Cluster Membership (GCM)
      2.  
        Configuring Data Replication
      3.  
        Additional steps for Azure RedHat OpenShift(ARO) environment
      4.  
        Configuring DNS
      5.  
        Configuring Disaster Recovery Plan
  10. Installing and configuring InfoScale DR Manager on Kubernetes
    1.  
      Introduction
    2.  
      Prerequisites
    3.  
      Creating Persistent Volume for metadata backup
    4.  
      External dependencies
    5. Installing InfoScale DR Manager
      1.  
        Configuring Global Cluster Membership (GCM)
      2.  
        Configuring Data Replication
      3.  
        Configuring DNS
      4.  
        Configuring Disaster Recovery Plan
  11. Disaster Recovery scenarios
    1.  
      Migration
    2.  
      Takeover
  12. Configuring InfoScale
    1.  
      Logging mechanism
    2.  
      Configuring Veritas Oracle Data Manager (VRTSodm)
  13. Troubleshooting
    1.  
      Collecting logs by using SORT Data Collector
    2.  
      Known Issues
    3.  
      Limitations

Prerequisites to install by using YAML

  1. Run the following commands to set the environment variable.
    export LOCAL_REGISTRY=<local_registry_host_name>:
                                        <local_registry_host_port>
    export REG_CREDS=${XDG_RUNTIME_DIR}/containers/auth.json
    export ARCHITECTURE='<platform>/<architecture>'
     # Where ARCHITECTURE can be linux/amd64,
     # linux/ppc64le, linux/s390x
    export VTAG=<ocp release> # eg: v4.9, v4.10
    
  2. Perform the following steps on the mirror host node to mirror the Red Hat operator - nfd.
    • Authenticate your local registry and registry.redhat.io.

      podman login registry.redhat.io
      podman login ${LOCAL_REGISTRY}
    • To mirror nfd operator only, run the following command to prune the source index

      opm index prune \
      -f registry.redhat.io/redhat/redhat-operator-index
      :${VTAG} \
      		-p nfd -t ${LOCAL_REGISTRY}/catalog/redhat-operator:${VTAG}
      
    • Run the following command to push the operator index images to your local registry.

      podman push ${LOCAL_REGISTRY}/catalog/redhat-operator:${VTAG}
    • Run the following command to mirror the operators.

      mkdir ~/mirror-operator
      cd ~/mirror-operator
      oc adm catalog mirror --index-filter-by-os=${ARCHITECTURE} \
      		-a ${REG_CREDS} ${LOCAL_REGISTRY}/catalog/redhat-operator:
         ${VTAG} 		${LOCAL_REGISTRY}/operators
      
    • Run the following command to push the operator index images to your local registry.

      	podman push ${LOCAL_REGISTRY}/catalog/redhat-operator:${VTAG}
    • Run the following command to mirror the operators.

      oc adm catalog mirror --index-filter-by-os=${ARCHITECTURE} \
      		-a ${REG_CREDS} ${LOCAL_REGISTRY}/catalog/redhat-operator:${VTAG} \
      		${LOCAL_REGISTRY}/operators
    • Inspect the manifests directory that is generated in your current directory. The manifest directory format is

      manifests-<index_image_name>-<random_number>
    • Run the following command to customize mapping.txt with the local pull secret.

      oc image mirror -f \
      <path to manifest directory>/mapping.txt -a \
                              ${REG_CREDS}
  3. Perform the following steps on the bastion node.
    • Copy manifests directories from mirror host to bastion node.

      scp -r <IP address of the mirror node>:~/mirror ~/ 
    • Disable the sources for the default catalogs by adding disableAllDefaultSources: true to the OperatorHub object.

      	oc patch OperatorHub cluster --type json \
      		-p '[{"op": "add", "path": "/spec/disableAllDefaultSources", 
                                                    "value": true}]'
      
    • Apply imageContentSourcePolicy.yaml.

      cd ~/mirror/
      oc create -f manifests-redhat-operator-*/
                          imageContentSourcePolicy.yaml
      
    • Apply catalogSource.yaml.

      oc create -f manifests-redhat-operator-*/catalogSource.yaml
      
    • Verify whether the following resources are created successfully.

      oc get catalogsource -n openshift-marketplace
      oc get pods -n openshift-marketplace
      oc get packagemanifest -n openshift-marketplace
      	
      # Wait For READY State:
      # Example: operator name:- redhat-operator-catalog
      oc get catsrc <operator name> \
      		-n openshift-marketplace -ojsonpath=
              "{.status.connectionState.lastObservedState}"
      

    Now you can install nfd operator from the web console.

  4. Copy the following images to the local registry.
        ${LOCAL_REGISTRY}/veritas
        OS_VER=<OS Version> # eg: 'rhel8.4'
        KERNEL=<Kernel Version of worker>'# eg: 4.18.0-305.45.1.el8_4.x86_64'

    cert-manager Images

    • quay.io/jetstack/cert-manager-cainjector:v1.7.1

    • quay.io/jetstack/cert-manager-controller:v1.7.1

    • quay.io/jetstack/cert-manager-webhook:v1.7.1

    SRO Images

    • registry.redhat.io/openshift4/ose-kube-rbac-proxy

    • registry.redhat.io/openshift4/special-resource-rhel8-operator:<vTAG> where, vTAG=v4.10.0-202206171549.p0.g034862e.assembly.stream or v4.9.0

    Operator Image

    • registry.connect.redhat.com/veritas-technologies/infoscale-sds-operator:8.0.100-rhel8

    • registry.connect.redhat.com/veritas-technologies/infoscale-licensing-operator:8.0.100-rhel8

    Infoscale Images

    • registry.connect.redhat.com/veritas-technologies/infoscale-sds:8.0.100-$OS_VER-$KERNEL

    • registry.connect.redhat.com/veritas-technologies/infoscale-csi:2.0.100-rhel8 registry.connect.redhat.com/veritas-technologies/infoscale-fencing:2.0.100-rhel8

    CSI IMAGES

    • registry.redhat.io/openshift4/ose-csi-external-provisioner-rhel8:v4.7

    • registry.redhat.io/openshift4/ose-csi-external-attacher:v4.7

    • registry.redhat.io/openshift4/ose-csi-external-resizer-rhel8:v4.7

    • registry.redhat.io/openshift4/ose-csi-external-snapshotter-rhel8:v4.7

    • registry.redhat.io/openshift4/ose-csi-driver-registrar:v4.3

    FENCING IMAGES

    • ghcr.io/kvaps/kube-fencing-controller:v2.3.0

    • ghcr.io/kvaps/kube-fencing-switcher:v2.3.0

    To copy images to ${LOCAL_REGISTRY}

    • If mirror host is connected to internet and ${LOCAL_REGISTRY} both, run the following commands on mirror host

      podman pull <src image>
      podman tag <src image> <tgt image>
      podman push <tgt image>
      
      #If csi images push fail, try push with '--remove-signatures'
    • If mirror host is connected to internet only, run the following commands on the mirror host

      podman pull <src image>
      podman save -o <image_name>.tar <src image> <tgt image>
      -> Copy tar to ${LOCAL_REGISTRY} connected host (bastion node)

      Run the following commands on the bastion node.

      podman load -i <image_name>.tar
      podman tag <src image> <tgt image>
      podman push <tgt image>
  5. Update YAML
    • Download YAML_8.0.100.tar from the Veritas Download Centre.

    • Extract YAML_8.0.100.tar . A folder YAML/OpenShift/air-gapped is created and all files required for installation are available in the folder.

    • Update YAML/OpenShift/air-gapped/*.yaml with your ${LOCAL_REGISTRY}. Run the following commands.

      cd YAML/OpenShift/air-gapped-systems
      sed -i "s/192.168.1.21/${LOCAL_REGISTRY}/g" cert-manager.yaml
      sed -i "s/192.168.1.21/${LOCAL_REGISTRY}/g" iso.yaml
      sed -i "s/192.168.1.21/${LOCAL_REGISTRY}/g" lico.yaml
      sed -i "s/192.168.1.21/${LOCAL_REGISTRY}/g" cr.yaml

    Note:

    Ensure that you change the image path in all yamls to the local registry address.