Configure Fusion Data Foundation in Multicloud
Object Gateway (MCG)-only mode to provide scalable object storage without block or file
services.
Before you begin
- Fusion Data Foundation is installed in dynamic mode, as
instructed in Installing Fusion Data Foundation.
- You are logged in to the Red Hat® OpenShift® Container Platform web
console as an administrator.
- Project is set to
openshift-storage.
About this task
Fusion Data Foundation can be deployed in MCG-only
mode, where only the MCG service is installed. In this mode, the system provides object storage
exclusively and does not support block or file storage.
Procedure
-
Go to to view all the installed operators.
- Select the IBM Storage Fusion Data Foundation
operator.
- On the Details tab, click Create
StorageSystem.
- On the Backing storage page, select the following options:
- Deployment type: Select Multicloud Object
Gateway.
- Backing storage type: Select Use an existing
StorageClass.
- Click Next.
- On the Security page, keep the default selection and click
Next.
- On the Review and create page, review the configuration details
and click Create StorageSystem.
Tip: To modify any configuration details, click Back.
- Do the following verification steps:
- Verify that the StorageSystem resource is created.
Command
example:
oc get StorageSystem -n openshift-storage
Example
output:
NAME STORAGE-SYSTEM-KIND STORAGE-SYSTEM-NAME
ocs-storagecluster-storagesystem storagecluster.ocs.openshift.io/v1 ocs-storagecluster
- Verify that the PersistentVolumeClaim (PVC) is created as the backing
storage.
Command
example:
oc get pvc -n openshift-storage
Example
output:
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE
db-noobaa-db-pg-0 Bound pvc-24fb7c6d-2964-4609-859e-5468d6f20461 50Gi RWO fusion-gdp-sc-cp-sc <unset> 116s
- Verify that the StorageCluster is in the
Ready
phase. Command
example:
oc get StorageCluster -n openshift-storage
Example
output:
NAME AGE PHASE EXTERNAL CREATED AT VERSION
ocs-storagecluster 2m59s Ready 2025-08-08T19:18:46Z 4.17.9
- Verify that the noobaa Pods are in
Running
status. Command
example:
oc get pod -n openshift-storage
Example
output:
NAME READY STATUS RESTARTS AGE
ceph-csi-controller-manager-6b45485f4f-hlv7j 2/2 Running 0 3h58m
csi-addons-controller-manager-867f5596fd-ftfzk 2/2 Running 0 3h58m
noobaa-core-0 2/2 Running 0 3m27s
noobaa-db-pg-0 1/1 Running 0 3m28s
noobaa-default-backing-store-noobaa-pod-5a57efda 1/1 Running 0 79s
noobaa-endpoint-d7f495757-9v5vp 1/1 Running 0 104s
noobaa-operator-6b88f87cf6-phcgx 1/1 Running 0 3h58m
ocs-metrics-exporter-649f675dd9-vksg5 1/1 Running 0 3m27s
ocs-operator-554858f998-pkp4t 1/1 Running 0 3h57m
odf-console-656656598-djnz7 1/1 Running 0 3h58m
odf-operator-controller-manager-77ff48499c-nptnh 2/2 Running 0 3h58m
rook-ceph-operator-66ccffcc44-skbrf 1/1 Running 0 3h57m
ux-backend-server-6b4d8fb86f-r97qn 2/2 Running 0 3h57m
- Verify that the noobaa resources are in the
Ready
phase. Command
example:
oc get -n openshift-storage noobaas.noobaa.io,bucketclasses.noobaa.io,noobaas.noobaa.io
Example
output:
NAME S3-ENDPOINTS STS-ENDPOINTS SYSLOG-ENDPOINTS IMAGE PHASE AGE
noobaa.noobaa.io/noobaa ["https://9.11.110.227:31135"] ["https://9.11.110.227:30345"] registry.redhat.io/odf4/mcg-core-rhel9@sha256:0176d3ecd09d375ccfce03657b47b0d597131991ebd16f903171248fee383a6c Ready 11m
NAME TYPE PHASE AGE
backingstore.noobaa.io/noobaa-default-backing-store s3-compatible Ready 9m17s
NAME PLACEMENT NAMESPACEPOLICY QUOTA PHASE AGE
bucketclass.noobaa.io/noobaa-default-bucket-class {"tiers":[{"backingStores":["noobaa-default-backing-store"]}]} Ready 9m17s
- In the Red Hat OpenShift Container Platform web console, go
to
and check that the storage system is healthy.
- In the IBM Fusion web console, go to
and
check that the Multi-cloud Gateway mode is detected.
Results
Fusion Data Foundation is configured and running in
MCG-only mode.