Search
SupportConsoleDevelopersStart a trialContact

Chapter 2. Scaling up storage capacity

download PDF

Depending on the type of your deployment, you can choose one of the following procedures to scale up storage capacity.

If you want to scale using a storage class other than the one provisioned during deployment, you must also define an additional storage class before you scale. See Creating a storage class for details.

Note

OpenShift Container Storage does not support heterogeneous OSD sizes.

2.1. Creating a Storage Class

You can define a new storage class to dynamically provision storage from an existing provider.

Prerequisites

  • Administrator access to OpenShift web console.

Procedure

  1. Log in to OpenShift Web Console.
  2. Click Storage Storage Classes.
  3. Click Create Storage Class.
  4. Enter the storage class Name and Description.
  5. Select the required Reclaim Policy and Provisioner.
  6. Click Create to create the Storage Class.

Verification steps

  • Click Storage Storage Classes and verify that you can see the new storage class.

2.2. Scaling up storage by adding capacity to your OpenShift Container Storage nodes

Use this procedure to add storage capacity and performance to your configured Red Hat OpenShift Container Storage worker nodes on the following infrastructures:

  • AWS
  • VMware vSphere
  • Red Hat Virtualization
  • Microsoft Azure

Prerequisites

  • A running OpenShift Container Storage Platform.
  • Administrative privileges on the OpenShift Web Console.
  • To scale using a storage class other than the one provisioned during deployment, first define an additional storage class. See Creating a storage class for details.

Procedure

  1. Log in to the OpenShift Web Console.
  2. Click on Operators Installed Operators.
  3. Click OpenShift Container Storage Operator.
  4. Click Storage Cluster tab.
  5. The visible list should have only one item. Click (⋮) on the far right to extend the options menu.
  6. Select Add Capacity from the options menu.

  7. Select the Storage Class.

    Set the storage class to gp2 on AWS, thin on VMware, ovirt-csi-sc on Red Hat Virtualization or managed_premium on Microsoft Azure if you are using the default storage class generated during deployment. If you have created other storage classes, select whichever is appropriate.

    Important

    Using storage classes other than the default for your provider is a Technology Preview feature.

    Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

    For more information, see Technology Preview Features Support Scope.

    The Raw Capacity field shows the size set during storage class creation. The total amount of storage consumed is three times this amount, because OpenShift Container Storage uses a replica count of 3.

  8. Click Add and wait for the cluster state to change to Ready.

Verification steps

  • Navigate to Overview Block and File tab, then check the Raw Capacity breakdown card.

    Note that the capacity increases based on your selections.

    Note

    The raw capacity does not take replication into account and shows the full capacity.

  • Verify that the new OSDs and their corresponding new PVCs are created.

    • To view the state of the newly created OSDs:

      1. Click Workloads Pods from the OpenShift Web Console.
      2. Select openshift-storage from the Project drop-down list.

    • To view the state of the PVCs:

      1. Click Storage Persistent Volume Claims from the OpenShift Web Console.
      2. Select openshift-storage from the Project drop-down list.

  • (Optional) If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

    1. Identify the node(s) where the new OSD pod(s) are running. 

      $ oc get -o=custom-columns=NODE:.spec.nodeName pod/<OSD pod name>

      For example: 

      oc get -o=custom-columns=NODE:.spec.nodeName pod/rook-ceph-osd-0-544db49d7f-qrgqm

    2. For each of the nodes identified in previous step, do the following:

      1. Create a debug pod and open a chroot environment for the selected host(s). 

        $ oc debug node/<node name>
$ chroot /host

      2. Run “lsblk” and check for the “crypt” keyword beside the ocs-deviceset name(s) 

        $ lsblk
Important

Cluster reduction is supported only with the Red Hat Support Team’s assistance.

2.3. Scaling up storage by adding capacity to your OpenShift Container Storage nodes using local storage devices

Use this procedure to add storage capacity (additional storage devices) to your configured local storage based OpenShift Container Storage worker nodes on the following infrastructures:

  • Bare metal
  • VMware
  • Red Hat Virtualization

Prerequisites

Procedure

To add capacity, you can either use a storage class that you provisioned during the deployment or any other storage class that matches the filter.

  1. On the OpenShift web console, click on Operators Installed Operators.
  2. Click OpenShift Container Storage Operator.
  3. Click Storage Cluster tab.
  4. The visible list should have only one item. Click (⋮) on the far right to extend the options menu.
  5. Select Add Capacity from the options menu.
  6. Select the Storage Class for which you added disks or the new storage class depending on your requirement. Available Capacity displayed is based on the local disks available in storage class.

  7. Click Add.

    You might need to wait a couple of minutes for the storage cluster to reach Ready state.

Verification steps

  • Navigate to Overview Block and File tab, then check the Raw Capacity breakdown card.

    Note that the capacity increases based on your selections.

    Note

    The raw capacity does not take replication into account and shows the full capacity.

  • Verify that the new OSDs and their corresponding new PVCs are created.

    • To view the state of the newly created OSDs:

      1. Click Workloads Pods from the OpenShift Web Console.
      2. Select openshift-storage from the Project drop-down list.

    • To view the state of the PVCs:

      1. Click Storage Persistent Volume Claims from the OpenShift Web Console.
      2. Select openshift-storage from the Project drop-down list.

  • (Optional) If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

    1. Identify the node(s) where the new OSD pod(s) are running. 

      $ oc get -o=custom-columns=NODE:.spec.nodeName pod/<OSD pod name>

      For example: 

      oc get -o=custom-columns=NODE:.spec.nodeName pod/rook-ceph-osd-0-544db49d7f-qrgqm

    2. For each of the nodes identified in previous step, do the following:

      1. Create a debug pod and open a chroot environment for the selected host(s). 

        $ oc debug node/<node name>
$ chroot /host

      2. Run “lsblk” and check for the “crypt” keyword beside the ocs-deviceset name(s) 

        $ lsblk
Important

Cluster reduction is supported only with the Red Hat Support Team’s assistance.

2.4. Scaling up storage by adding capacity to your OpenShift Container Storage nodes on IBM Z or LinuxONE infrastructure

Use this procedure to add storage capacity and performance to your configured Red Hat OpenShift Container Storage worker nodes.

Prerequisites

  • A running OpenShift Container Storage Platform.
  • Administrative privileges on the OpenShift Web Console.
  • To scale using a storage class other than the one provisioned during deployment, first define an additional storage class. See Creating a storage class for details.

Procedure

  1. Add additional hardware resources with zFCP disks

    1. List all the disks with the following command. 

      $ lszdev

      Example output: 

      TYPE         ID                                              ON   PERS  NAMES
zfcp-host    0.0.8204                                        yes  yes
zfcp-lun     0.0.8204:0x102107630b1b5060:0x4001402900000000  yes  no    sda sg0
zfcp-lun     0.0.8204:0x500407630c0b50a4:0x3002b03000000000  yes  yes   sdb sg1
qeth         0.0.bdd0:0.0.bdd1:0.0.bdd2                      yes  no    encbdd0
generic-ccw  0.0.0009                                        yes  no

      A SCSI disk is represented as a zfcp-lun with the structure <device-id>:<wwpn>:<lun-id> in the ID section. The first disk is used for the operating system. The device id for the new disk can be the same.

    2. Append a new SCSI disk with the following command. 

      $ chzdev -e 0.0.8204:0x400506630b1b50a4:0x3001301a00000000
      Note

      The device ID for the new disk must be the same as the disk to be replaced. The new disk is identified with its WWPN and LUN ID.

    3. List all the FCP devices to verify the new disk is configured. 

      $ lszdev zfcp-lun
TYPE         ID                                              ON   PERS  NAMES
zfcp-lun     0.0.8204:0x102107630b1b5060:0x4001402900000000 yes  no    sda sg0
zfcp-lun     0.0.8204:0x500507630b1b50a4:0x4001302a00000000  yes  yes   sdb sg1
zfcp-lun     0.0.8204:0x400506630b1b50a4:0x3001301a00000000  yes  yes   sdc sg2
  2. Navigate to the OpenShift Web Console.
  3. Click Operators on the left navigation bar.
  4. Select Installed Operators.
  5. In the window, click OpenShift Container Storage Operator:
  6. In the top navigation bar, scroll right and click Storage Cluster tab.
  7. Click (⋮) next to the visible list to extend the options menu.

  8. Select Add Capacity from the options menu.

    The Raw Capacity field shows the size set during storage class creation. The total amount of storage consumed is three times this amount, because OpenShift Container Storage uses a replica count of 3.

  9. Click Add and wait for the cluster state to change to Ready.

Verification steps

  1. Navigate to Overview Block and File tab, then check the Capacity breakdown card.

    Note that the capacity increases based on your selections.

    Note

    The raw capacity does not take replication into account and shows the full capacity.

Important

Cluster reduction is supported only with the Red Hat Support Team’s assistance.

2.5. Scaling up storage by adding capacity to your OpenShift Container Storage nodes on IBM Power Systems infrastructure using local storage devices

Use this procedure to add storage capacity (additional storage devices) to your configured local storage based OpenShift Container Storage worker nodes on IBM Power Systems infrastructures.

Prerequisites

  • You must be logged into OpenShift Container Platform (RHOCP) cluster.

  • You must have installed local storage operator. Use the following procedures, see

  • If you upgraded to OpenShift Container Storage 4.8 from a previous version and have not already created the LocalVolumeDiscovery object, do so now by following the procedure described in Post-update configuration changes for clusters backed by local storage.
  • You must have three OpenShift Container Platform worker nodes with the same storage type and size attached to each node (for example, 0.5TB SSD) as the original OpenShift Container Storage StorageCluster was created with.

Procedure

  1. To add storage capacity to OpenShift Container Platform nodes with OpenShift Container Storage installed, you need to

    1. Find the available devices that you want to add, that is, a minimum of one device per worker node. You can follow the procedure for finding available storage devices in the respective deployment guide.

      Note

      Make sure you perform this process for all the existing nodes (minimum of 3) for which you want to add storage.

    2. Add the additional disks to the LocalVolume custom resource (CR). 

      $ oc edit -n openshift-local-storage localvolume localblock

      Example output: 

      spec:
  logLevel: Normal
  managementState: Managed
  nodeSelector:
    nodeSelectorTerms:
      - matchExpressions:
          - key: kubernetes.io/hostname
            operator: In
            values:
              - worker-0
              - worker-1
              - worker-2
  storageClassDevices:
    - devicePaths:
        - /dev/sda
        - /dev/sdx    # newly added device
      storageClassName: localblock
      volumeMode: Block

      Make sure to save the changes after editing the CR.

      Example output: 

      localvolume.local.storage.openshift.io/localblock edited

      You can see in this CR that new devices have been added.

      • sdx

  2. Display the newly created PVs with storageclass name used in localVolume CR. 

    $ oc get pv | grep localblock | grep Available

    Example output: 

    local-pv-a04ffd8       500Gi      RWO      Delete       Available      localblock       24s
local-pv-a0ca996b      500Gi      RWO      Delete       Available      localblock       23s
local-pv-c171754a      500Gi      RWO      Delete       Available      localblock       23s
  3. Navigate to the OpenShift Web Console.
  4. Click on Operators on the left navigation bar.
  5. Select Installed Operators.
  6. In the window, click OpenShift Container Storage Operator:
  7. In the top navigation bar, scroll right and click Storage Cluster tab.
  8. The visible list should have only one item. Click (⋮) on the far right to extend the options menu.

  9. Select Add Capacity from the options menu.

    From this dialog box, set the Storage Class name to the name used in the localVolume CR. Available Capacity displayed is based on the local disks available in storage class.

  10. Once you are done with your setting, click Add.

    You might need to wait a couple of minutes for the storage cluster to reach Ready state.

Verification steps

  • Navigate to Overview Block and File tab, then check the Raw Capacity breakdown card.

    Note that the capacity increases based on your selections.

    Note

    The raw capacity does not take replication into account and shows the full capacity.

  • Verify that the new OSDs and their corresponding new PVCs are created.

    • To view the state of the newly created OSDs:

      1. Click Workloads Pods from the OpenShift Web Console.
      2. Select openshift-storage from the Project drop-down list.

    • To view the state of the PVCs:

      1. Click Storage Persistent Volume Claims from the OpenShift Web Console.
      2. Select openshift-storage from the Project drop-down list.

  • (Optional) If cluster-wide encryption is enabled on the cluster, verify that the new OSD devices are encrypted.

    1. Identify the node(s) where the new OSD pod(s) are running. 

      $ oc get -o=custom-columns=NODE:.spec.nodeName pod/<OSD pod name>

      For example: 

      oc get -o=custom-columns=NODE:.spec.nodeName pod/rook-ceph-osd-0-544db49d7f-qrgqm

    2. For each of the nodes identified in previous step, do the following:

      1. Create a debug pod and open a chroot environment for the selected host(s). 

        $ oc debug node/<node name>
$ chroot /host

      2. Run “lsblk” and check for the “crypt” keyword beside the ocs-deviceset name(s) 

        $ lsblk
Important

Cluster reduction is supported only with the Red Hat Support Team’s assistance.

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.