NooBaa System creation
When a NooBaa system is created, the mcg-operator reconciles the following:
Default BackingStore
Depending on the platform that OpenShift Container Platform and Fusion Data Foundation are deployed on, a default backing store resource is created so that buckets can use it for their placement policy. The different options are as follows:
| Amazon Web Services (AWS) deployment | The mcg-operator uses the
CloudCredentialsOperator (CCO) to mint credentials in order to create a new AWS::S3
bucket and creates a BackingStore on top of that bucket. |
| Microsoft Azure deployment | The mcg-operator uses the CCO to mint credentials in
order to create a new Azure Blob and creates a BackingStore on top of that
bucket. |
| Google Cloud Platform (GCP) deployment | The mcg-operator uses the CCO to mint credentials in
order to create a new GCP bucket and will create a BackingStore on top of that bucket. |
| On-prem deployment | If RGW exists, the mcg-operator creates a new
CephUser and a new bucket on top of RGW and create a BackingStore
on top of that bucket. |
| None of the previously mentioned deployments are applicable | The mcg-operator creates a pv-pool
based on the default storage class and creates a BackingStore on top of that
bucket. |
Default BucketClass
A BucketClass with a placement policy to the default
BackingStore is created.
NooBaa pods
The following NooBaa pods are created and started:
| Database (DB) | This is a Postgres DB holding metadata, statistics, events, and so on. However, it does not hold the actual data being stored. |
| Core | This is the pod that handles configuration, background processes, metadata management, statistics, and so on. |
| Endpoints | These pods perform the actual I/O-related work such as deduplication
and compression, communicating with different services to write and read data, and so on. The
endpoints are integrated with the HorizonalPodAutoscaler and their number increases
and decreases according to the CPU usage observed on the existing endpoint pods. |
Route
A Route for the NooBaa S3 interface is created for applications that uses S3.
Service
A Service for the NooBaa S3 interface is created for applications that uses S3.