Chapter 2. Deploying OpenShift Container Storage on Microsoft Azure

Procedure

1. Click Operators → OperatorHub in the left pane of the OpenShift Web Console.

2. Click on OpenShift Container Storage.

   You can use the Filter by keyword text box or the filter list to search for OpenShift Container Storage from the list of operators.

3. On the OpenShift Container Storage operator page, click Install.

4. On the Install Operator page, ensure the following options are selected:

   1. Update Channel as stable-4.4
   2. Installation Mode as A specific namespace on the cluster.
   3. Installed Namespace as Operator recommended namespace PR openshift-storage. If Namespace openshift-storage does not exist, it will be created during the operator installation.

   4. Select Approval Strategy as Automatic or Manual. Approval Strategy is set to Automatic by default.

      • Approval Strategy as Automatic.

        Note

        When you select the Approval Strategy as Automatic, approval is not required either during fresh installation or when updating to the latest version of OpenShift Container Storage.

        1. Click Install
        2. Wait for the install to initiate. This may take up to 20 minutes.
        3. Click Operators → Installed Operators
        4. Ensure the Project is openshift-storage. By default, the Project is openshift-storage.
        5. Wait for the Status of OpenShift Container Storage to change to Succeeded.

      • Approval Strategy as Manual.

        Note

        When you select the Approval Strategy as Manual, approval is required during fresh installation or when updating to the latest version of OpenShift Container Storage.

        1. Click Install
        2. On the Installed Operators page, click ocs-operator.
        3. On the Subscription Details page, click the Install Plan link.
        4. On the InstallPlan Details page, click Preview Install Plan
        5. Review the install plan and click Approve.
        6. Wait for the Status of the Components to change from Unknown to either Created or Present.
        7. Click Operators → Installed Operators
        8. Ensure the Project is openshift-storage. By default, the Project is openshift-storage.
        9. Wait for the Status of OpenShift Container Storage to change to Succeeded.

Procedure

1. Click Operators → Installed Operators from the left pane of the OpenShift Web Console to view the installed operators.
2. On the Installed Operator page, select openshift-storage from the Project drop down list to switch to the openshift-storage project.

3. Click OpenShift Container Storage operator.

   OpenShift Container Storage operator creates a OCSInitialization resource automatically.

4. On the OpenShift Container Storage operator page, scroll right and click the Storage Cluster tab.

   Figure 2.1. OpenShift Container Storage Operator page

   

5. On the OCS Cluster Services page, click Create OCS Cluster Service.

   Figure 2.2. Create New OCS Service page

   

6. On the Create New OCS Service page, perform the following:

   1. Select at least three worker nodes from the available list of nodes for the use of OpenShift Container Storage service. Ensure that the nodes are in different Location.

   2. Storage Class is set by default depending on the platform.

      managed-premium is the default storage for Azure.

   3. Select OCS Service Capacity from the drop down list.

      Note

      Once you select the initial storage capacity here, you can add more capacity only in this increment.

7. Click Create.

   The Create button is enabled only after you select three nodes. A new storage cluster of three volumes will be created with one volume per worker node. The default configuration uses a replication factor of 3.

Before you begin

1. Log in to Azure web console.
2. Create Azure Blob storage account for MCG to store object data as described in Create a BlockBlobStorage account. Make sure to set Account kind as BlobStorage and connectivity method as public endpoint.
3. Locate access keys of the Blob storage account and note down the value for key1 for later use.
4. Create a new Container within the new Blob storage account with public access level set as private.

1. Log in to OpenShift Container Platform web console.
2. Click Operators → Installed Operators from the left pane of the OpenShift Web Console to view the installed operators.
3. Click OpenShift Container Storage Operator.

4. On the OpenShift Container Storage Operator page, scroll right and click the Backing Store tab.

   Figure 2.3. OpenShift Container Storage Operator page with backing store tab

   

5. Click Create Backing Store.

   Figure 2.4. Create Backing Store page

   

6. On the Create New Backing Store page, perform the following:

   1. Enter a name for Backing Store Name.
   2. Select Azure Blob as the Provider.
   3. Click Switch to Credentials.
   4. Enter the Account Name of Azure Blob storage account you created earlier.
   5. Enter the value of key1 of the Azure storage account you noted down earlier.
   6. Enter the name of the container that you created inside the Azure storage account for Target Blob Container. This allows you to create a connection that tells MCG that it can use this container for the system.
7. Click Create Backing Store.
8. In the OpenShift Container Platform web console, click Installed Operators → OpenShift Container Storage → Bucket Class.
9. Edit noobaa-default-bucket-class YAML specification field spec: placementPolicy: tiers: -backingStores: to use the newly created backing store instead of noobaa-default-backing-store.

Verification steps

1. Run the following command by using the MCG command line tool noobaa (from mcg rpm package) to verify that the Azure backing store that you created is in Ready state.

   $ noobaa status -n openshift-storage

2. Verify that the output shows the default bucket class in Ready state and uses the expected backing store.

   .
   .
   .
   ------------------
   - Backing Stores -
   ------------------
   
   NAME                           TYPE            TARGET-BUCKET
   PHASE   AGE
   noobaa-azure-backing-store             azure-blob      noobaabucketcontainer Ready   10m27s
   noobaa-default-backing-store   s3-compatible nb.1595507787728.apps.mbukatov20200723a.azure.qe.rh-ocs.com   Ready 1h58m20s
   
   ------------------
   - Bucket Classes -
   ------------------
   
   NAME                          PLACEMENT
   PHASE   AGE
   noobaa-default-bucket-class   {Tiers:[{Placement: BackingStores:[noobaa-azure-backing-store]}]}   Ready   1h58m21s