InfoScale™ 9.0 Support for Containers - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Linux
  1. Overview
    1.  
      Introduction
    2.  
      Features of InfoScale in Containerized environment
    3.  
      CSI Introduction
    4.  
      I/O fencing
    5.  
      Disaster Recovery
  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 Arctera InfoScale™ on OpenShift
    1.  
      Introduction
    2.  
      Prerequisites
    3. Installing InfoScale on a system with Internet connectivity
      1. Using web console of OperatorHub
        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.tar
        1.  
          Configuring cluster
        2.  
          Adding nodes to an existing cluster
        3.  
          Undeploying and uninstalling InfoScale
    4. Installing InfoScale in an air gapped system
      1.  
        Configuring cluster
      2.  
        Adding nodes to an existing cluster
      3.  
        Undeploying and uninstalling InfoScale
  5. Installing Arctera 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. Tagging the InfoScale images on Kubernetes
      1.  
        Downloading side car images
    5. Installing InfoScale on Kubernetes
      1.  
        Configuring cluster
      2.  
        Adding nodes to an existing cluster
    6.  
      Undeploying and uninstalling InfoScale
  6. 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
  7. Installing InfoScale DR on OpenShift
    1.  
      Introduction
    2.  
      Prerequisites
    3.  
      External dependencies
    4. Installing InfoScale DR
      1.  
        Configuring DR Operator
      2.  
        Configuring Global Cluster Membership (GCM)
      3.  
        Configuring Data Replication
      4.  
        Configuring DNS
      5.  
        Configuring Disaster Recovery Plan
  8. Installing InfoScale DR on Kubernetes
    1.  
      Introduction
    2.  
      Prerequisites
    3.  
      External dependencies
    4. Installing InfoScale DR
      1.  
        Configuring DR Operator
      2.  
        Configuring Global Cluster Membership (GCM)
      3.  
        Configuring Data Replication
      4.  
        Configuring DNS
      5.  
        Configuring Disaster Recovery Plan
  9. TECHNOLOGY PREVIEW: Disaster Recovery scenarios
    1.  
      Migration
  10. Configuring InfoScale
    1.  
      Logging mechanism
    2.  
      Configuring Arctera Oracle Data Manager (VRTSodm)
  11. Troubleshooting
    1.  
      Known Issues
    2.  
      Limitations

Resizing Persistent Volumes (CSI volume expansion)

Using the persistent volume expansion feature, you can easily expand the storage capacity of a persistent volume by just updating the Persistent Volume Claim storage specification. However, to use this feature, you must set the allowVolumeExpansion attribute to true in their StorageClass object. Only the PVCs created by using such Storage Class allow volume expansion. When the storage attribute of such a PVC object is updated, Container Orchestrator interprets it as a change request and triggers automatic volume resizing.

The following sample Storage Class yaml shows the allowVolumeExpansion attribute definition.

---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: csi-infoscale-sc
annotations:
storageclass.kubernetes.io/is-default-class: "false"
provisioner: org.veritas.infoscale
reclaimPolicy: Delete
allowVolumeExpansion: true
parameters:
fstype: vxfs

While performing the volume expansion operation, you must note the following:

  • Ensure that the PVC is in use by some application pod while performing resize operation. InfoScale supports dynamic volume expansion in 'Online' mode.

  • Do not perform the volume expansion operation from InfoScale driver-container pods. In such case, OpenShift is not aware of these changes and updated volume size is not reflected in the PV and PVC objects.

  • InfoScale does not support the shrinking of persistent volume as OpenShift does not support it.

  • When a volume is used in any InfoScale configuration, make sure that you use only InfoScale commands to resize it. Do not use any other methods - like OS-specific commands - to resize such volumes. Doing so may disrupt the functioning of your InfoScale configuration.

After the volume is provisioned, create the container application pod, run the application, and access the volume. If the volume is full and must be resized, use one of the following ways:

  • Edit the Persistent Volume Claim

  • Use the oc patch pvc command

Note:

Resize operation on volume is not supported when it is provisioned in ReadOnlyMany mode.

Resizing a Persistent Volume by editing the Persistent Volume Claim

  1. Find the Persistent Volume Claim to resize. 
    oc get pvc

    Output similar to this is displayed: 

    NAME              STATUS  VOLUME   CAPACITY 
csi-infoscale-pvc Bound   pvc-<id> 5Gi
    ACCESS MODES STORAGECLASS     AGE
RWX          csi-infoscale-sc 32m
  2. To resize the storage capacity, edit the PVC.
    oc edit pvc csi-infoscale-pvc
  3. From your text editor, change the storage capacity to the required larger value. For example, from 5Gi to 10Gi .
  4. Check the status of the Persistent Volume Claim and Persistent Volume to verify if the size is updated. 
    oc get pvc

    Output similar to this is displayed: 

    NAME               STATUS VOLUME
csi-infoscale-pvc  Bound  pvc-<id>
    CAPACITY ACCESS MODES STORAGECLASS     AGE  
10Gi     RWX          csi-infoscale-sc 32m

Resizing a Persistent Volume using the 'patch pvc' command

  1. Find the Persistent Volume Claim to resize. 
    oc get pvc

    Output similar to this is displayed: 

    NAME              STATUS VOLUME   CAPACITY
csi-infoscale-pvc Bound  pvc-<id> 5Gi
    ACCESS MODES STORAGECLASS     AGE
RWX          csi-infoscale-sc 32m
  2. To resize the storage capacity to the required larger value, for example, from 5Gi to 10Gi, run the following command. 
     oc patch pvc csi-infoscale-pvc --patch 
'{"spec": {"resources": {"requests": {"storage": "10Gi"}}}}'
  3. Check the status of the Persistent Volume Claim and Persistent Volume to verify if the size is updated. 
     oc get pvc

    Output similar to this is displayed: 

    NAME                 STATUS   VOLUME
csi-infoscale-pvc    Bound    pvc-<id>
    CAPACITY   ACCESS MODES STORAGECLASS     AGE
10Gi       RWX          csi-infoscale-sc 32m