Overriding the default backing store

Follow this procedure to override the default NooBaa backing store.

Before you begin

Download the Multicloud Object Gateway (MCG) command-line interface. 
subscription-manager repos --enable=rh-odf-4-for-rhel-8-x86_64-rpms
 yum install mcg
Note: Specify the appropriate architecture for enabling the repositories using the subscription manager.
  • For IBM Power, use the following command: 
    subscription-manager repos --enable=rh-odf-4-for-rhel-8-ppc64le-rpms
  • For IBM Z infrastructure, use the following command: 
    subscription-manager repos --enable=rh-odf-4-for-rhel-8-s390x-rpms

About this task

You can use the manualDefaultBackingStoreflag to override the default NooBaa backing store and remove it if you do not want to use the default backing store configuration. This provides flexibility to customize your backing store configuration and tailor it to your specific needs. By leveraging this feature, you can further optimize your system and enhance its performance.

Procedure

  1. Check if noobaa-default-backing-store is present:

    $ oc get backingstore
NAME TYPE PHASE AGE
noobaa-default-backing-store pv-pool Creating 102s

  2. Patch the NooBaa CR to enable manualDefaultBackingStore:

    $ oc patch noobaa/noobaa --type json --patch='[{"op":"add","path":"/spec/manualDefaultBackingStore","value":true}]'
    Important: Use the Multicloud Object Gateway CLI to create a new backing store and update accounts.

  3. Create a new default backing store to override the default backing store. For example:

    $ noobaa backingstore create pv-pool _NEW-DEFAULT-BACKING-STORE_ --num-volumes 1 --pv-size-gb 16

    1. Replace NEW-DEFAULT-BACKING-STORE with the name you want for your new default backing store.

  4. Update the admin account to use the new default backing store as its default resource:

    $ noobaa account update admin@noobaa.io --new_default_resource=_NEW-DEFAULT-BACKING-STORE_

    1. Replace NEW-DEFAULT-BACKING-STORE with the name of the backing store from the previous step.

      Updating the default resource for admin accounts ensures that the new configuration is used throughout your system.

  5. Configure the default-bucketclass to use the new default backingstore:

    $ oc patch Bucketclass noobaa-default-bucket-class -n openshift-storage --type=json --patch='[{"op": "replace", "path": "/spec/placementPolicy/tiers/0/backingStores/0", "value": "NEW-DEFAULT-BACKING-STORE"}]'

  6. Optional: Delete the noobaa-default-backing-store.

    1. Delete all instances of and buckets associated with noobaa-default-backing-store and update the accounts using it as resource.

    2. Delete the noobaa-default-backing-store:

      $ oc delete backingstore noobaa-default-backing-store -n openshift-storage | oc patch -n openshift-storage backingstore/noobaa-default-backing-store --type json --patch='[ { "op": "remove", "path": "/metadata/finalizers" } ]'

      You must enable the manualDefaultBackingStore flag before proceeding. Additionally, it is crucial to update all accounts that use the default resource and delete all instances of and buckets associated with the default backing store to ensure a smooth transition.