Creating a local Persistent Volume-backed backingstore

Create a local Persistent Volume-backed backing store using the MCG command-line interface or a YAML file to add storage resources.

Before you begin, ensure the following:

Fusion Data Foundation Platform is running.
Download the MCG command-line interface for easier management.
```
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
```
Alternatively, you can install the MCG package from the RPMs found at Download Red Hat OpenShift Data Foundation page.

Note: Choose the correct Product Variant according to your architecture.

Create a local Persistent Volume-backed backingstore using MCG command-line interface

From the MCG command-line interface, run the following command:

Note: This command must be run from within the openshift-storage namespace.

noobaa -n openshift-storage backingstore create pv-pool <backingstore_name> --num-volumes <NUMBER OF VOLUMES>  --pv-size-gb <VOLUME SIZE> --request-cpu <CPU REQUEST> --request-memory <MEMORY REQUEST> --limit-cpu <CPU LIMIT> --limit-memory <MEMORY LIMIT> --storage-class <LOCAL STORAGE CLASS>

backingstore_name: The name of the backingstore.
NUMBER OF VOLUMES: The number of volumes you would like to create. Note that increasing the number of volumes scales up the storage.
VOLUME SIZE: Required size in GB of each volume.
CPU REQUEST: Guaranteed amount of CPU requested in CPU unit m.
MEMORY REQUEST: Guaranteed amount of memory requested.
CPU LIMIT: Maximum amount of CPU that can be consumed in CPU unit m.
MEMORY LIMIT: Maximum amount of memory that can be consumed.
LOCAL STORAGE CLASS: The local storage class name, recommended to use ocs-storagecluster-ceph-rbd.

Create a local Persistent Volume-backed backingstore using a YAML file

Apply the following YAML for a specific backing store:

apiVersion: noobaa.io/v1alpha1
kind: BackingStore
metadata:
  finalizers:
  - noobaa.io/finalizer
  labels:
    app: noobaa
  name: <backingstore_name>
  namespace: openshift-storage
spec:
   pvPool:
    numVolumes: <NUMBER OF VOLUMES>
    resources:
      requests:
        storage: <VOLUME SIZE>
        cpu: <CPU REQUEST>
        memory: <MEMORY REQUEST>
      limits:
        cpu: <CPU LIMIT>
        memory: <MEMORY LIMIT>
    storageClass: <LOCAL STORAGE CLASS>
  type: pv-pool

backingstore_name: The name of the backingstore.
NUMBER OF VOLUMES: The number of volumes you would like to create. Note that increasing the number of volumes scales up the storage.
VOLUME SIZE: Required size in GB of each volume.
CPU REQUEST: Guaranteed amount of CPU requested in CPU unit m.
MEMORY REQUEST: Guaranteed amount of memory requested.
CPU LIMIT: Maximum amount of CPU that can be consumed in CPU unit m.
MEMORY LIMIT: Maximum amount of memory that can be consumed.
LOCAL STORAGE CLASS: The local storage class name, recommended to use ocs-storagecluster-ceph-rbd.

Example output:

INFO[0001] ✅ Exists: NooBaa "noobaa"
INFO[0002] ✅ Exists: BackingStore "local-mcg-storage"