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 OLM

A few operators are needed to install InfoScale by using OLM. As air gapped/restricted networks are disconnected from the internet, operators must be mirrored to local registry. For mirroring, it requires a host having internet as well as local registry connection, named mirror-host.

Note:

In the following steps, ${LOCAL_REGISTRY}:5000 is on the same network. LOCAL_REGISTRY is a system connected to Internet and has a registry setup. 5000 is an indicative port number.

Perform the following steps on the mirror host node

  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
  2. Authenticate your local registry and registry.redhat.io .
    podman login registry.redhat.io
    podman login ${LOCAL_REGISTRY}
  3. Run the following command to create manifests directories.
    mkdir ~/mirror-operator
    cd ~/mirror-operator
  4. The following steps are about mirroring the Red Hat operators - nfd, sro and cert-manager.
    • If the OCP version is 4.10. x

      export VTAG='v4.10'
      opm index prune \
      -f registry.redhat.io/redhat/redhat-operator-index:${VTAG}\
       -p nfd,openshift-special-resource-operator \     
       -t ${LOCAL_REGISTRY}/catalog/redhat-operators:${VTAG}
    • If the OCP version is 4.9. x

      export VTAG='v4.9'
      opm index prune \
      -f registry.redhat.io/redhat/redhat-operator-index:${VTAG} \
       -p openshift-cert-manager-
                operator,nfd,openshift-special-resource-operator \
       -t ${LOCAL_REGISTRY}/catalog/redhat-operators:${VTAG}
      # As openshift-cert-manager-operator is available in v4.10 only. 
       #  Let's use it for now.
      opm index prune \
       -f registry.redhat.io/redhat/redhat-operator-index:v4.10 \
       -p openshift-cert-manager-operator \         
       -t ${LOCAL_REGISTRY}/catalog/redhat-operators:v4.10

      Note:

      Repeat steps 5 to 9 for local index : ${LOCAL_REGISTRY}/catalog/redhat-operators:v4.10.

  5. Run the following command to push the operator index images to your local registry.
    podman push ${LOCAL_REGISTRY}/catalog/redhat-operators:${VTAG}
  6. Run the following command to mirror the operators.
    oc adm catalog mirror \
     --index-filter-by-os=${ARCHITECTURE} \
     -a ${REG_CREDS} ${LOCAL_REGISTRY}/catalog/redhat-
        operators:${VTAG} \
     ${LOCAL_REGISTRY}/operators
  7. Verify the manifests directory that is generated.
    manifests-<index_image_name>-<random_number>
    
    # It contains:
    manifests-redhat-operator-index-1654068262
    ├── catalogSource.yaml
    ├── imageContentSourcePolicy.yaml
    └── mapping.txt
  8. Run the following command to customize the mapping.txt file with the local pull secret.
    oc image mirror \
    -f <path to manifest directory>/mapping.txt -a ${REG_CREDS}
                        
  9. Optionally, you can append the following content to catalogSource.yaml.
    displayName: Redhat Operator Catalog
     publisher: Red Hat Enterprise
     updateStrategy:
     registryPoll:
     interval: 30m

    You have successfully mirrored - nfd, sro and cert-manager.

  10. Prune the certified operators index for InfoScale-operator and InfoScale-licensing-operator, if you want to install by using OLM.
    opm index prune \
     -f registry.redhat.io/redhat/certified-operators:${VTAG}\
     -p infoscale-sds-operator,infoscale-licensing-operator \
     -t ${LOCAL_REGISTRY}/catalog/certified-operators:${VTAG}
  11. Run the following command to push the operator index images to your local registry.
    podman push ${LOCAL_REGISTRY}/catalog/certified-operators:${VTAG}
  12. Run the following command to mirror the operators.
     oc adm catalog mirror\
     --index-filter-by-os=${ARCHITECTURE} -a ${REG_CREDS}\
     ${LOCAL_REGISTRY}/catalog/certified-operators:${VTAG}\
     ${LOCAL_REGISTRY}/operators
  13. Verify the manifests directory that is generated. The format must be as under
    manifests-<index_image_name>-<random_number>
    ├── catalogSource.yaml
    ├── imageContentSourcePolicy.yaml
    └── mapping.txt
  14. Run the following command to customize the mapping.txt file with the local pull secret.
    oc image mirror -f \
    <path to manifest directory>/mapping.txt -a ${REG_CREDS}
                       
  15. Optionally, append the following to catalogSource.yaml.
     displayName: Certified Operator Catalog
     publisher: Red Hat Enterprise
     updateStrategy:
     registryPoll:
     interval: 30m
  16. On the mirror host - Download and untar tools_8.0.100.tar from Veritas Download Center.

    When you untar tools/setup_vtas_registry.sh is automatically created.

  17. Run the following commands on the mirror node.
    cd tools
    OS_VER=<OS Version> # eg: 'rhel8.4'
    KERNEL=<Kernel Version of worker>' # eg: 4.18.0-305.45.1.el8_4.x86_64'
    ./setup_vtas_registry.sh --airgap -o $OS_VER -k $KERNEL

    A folder infoscale_operand_images.tar is automatically created.

Run the following commands on the bastion node

  1. Copy downloaded images and files from mirror host. Run the following commands.

    scp -r <IP address of the mirror node>:~/mirror ~/

    cd ~/mirror

  2. Load infoscale images onto local registry
    OS_VER=<OS Version> # eg: 'rhel8.4'
    KERNEL=<Kernel Version of worker>' # eg: 4.18.0-305.45.1.el8_4.x86_64'
    podman login ${LOCAL_REGISTRY}
    ./setup_vtas_registry.sh --airgap -o $OS_VER -k $KERNEL \ 
                                      -c ${LOCAL_REGISTRY}/veritas -t
    
    infoscale_operand_images.tar
  3. To disable the sources for default catalogs

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

  4. Apply imageContentSourcePolicy.yaml for each operator-index mirrored. Run the following commands.
    # imageContentSourcePolicy for redhat operator index
    oc create -f manifests-redhat-operators-*/imageContentSourcePolicy.yaml
    # imageContentSourcePolicy for certified operator index
    oc create -f manifests-certified-operators-*/imageContentSourcePolicy.yaml
  5. For each operator index mirrored, apply catalogSource.yaml.Run the following commands.
    # catalogSource for redhat operator index
    oc create -f manifests-redhat-operators-*/catalogSource.yaml
    # catalogSource for certified operator index
    oc create -f manifests-certified-operator-*/catalogSource.yaml
  6. For each catalogsource created, 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: opertaor name:- redhat-operator-catalog
    oc get catsrc <operator name> \
    -n openshift-marketplace -ojsonpath=
        "{.status.connectionState.lastObservedState}"
  7. Login to the OpenShift web console and check whether the mirrored operators are displayed inOperators > OperatorHub as under: