Chapter 8. Multicloud Object Gateway bucket replication

Procedure

• Apply the following YAML:

  apiVersion: objectbucket.io/v1alpha1
  kind: ObjectBucketClaim
  metadata:
    name: <desired-bucket-claim>
    namespace: <desired-namespace>
  spec:
    generateBucketName: <desired-bucket-name>
    storageClassName: openshift-storage.noobaa.io
    additionalConfig:
      replicationPolicy: {"rules": [{ "rule_id": "", "destination_bucket": "", "filter": {"prefix": ""}}]}

  <desired-bucket-claim>

  Specify the name of the bucket claim.

  <desired-namespace>

  Specify the namespace.

  <desired-bucket-name>

  Specify the prefix of the bucket name.

  "rule_id"

  Specify the ID number of the rule, for example, {"rule_id": "rule-1"}.

  "destination_bucket"

  Specify the name of the destination bucket, for example, {"destination_bucket": "first.bucket"}.

  "prefix"

  Is optional. It is the prefix of the object keys that should be replicated, and you can even leave it empty, for example, {"prefix": ""}.

Additional information

• For more information about OBCs, see Object Bucket Claim.

Procedure

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

  noobaa -n openshift-storage bucketclass create placement-bucketclass <bucketclass-name> --backingstores <backingstores> --replication-policy=/path/to/json-file.json

  <bucketclass-name>

  Specify the name of the bucket class.

  <backingstores>

  Specify the name of a backingstore. You can pass many backingstores separated by commas.

  /path/to/json-file.json

  Is the path to a JSON file which defines the replication policy.

  Example JSON file:

  [{ "rule_id": "rule-1", "destination_bucket": "first.bucket", "filter": {"prefix": "repl"}}]

  "prefix"

  Is optional. The prefix of the object keys gets replicated. You can leave it empty, for example, {"prefix": ""}.

  For example:

  noobaa -n openshift-storage bucketclass create placement-bucketclass bc --backingstores azure-blob-ns --replication-policy=/path/to/json-file.json

  This example creates a placement bucket class with a specific replication policy defined in the JSON file.

Prerequisites

• Ensure that object logging is enabled in AWS. For more information, see the “Using the S3 console” section in Enabling Amazon S3 server access logging.
• Administrator access to OpenShift Web Console.

Procedure

• Edit the YAML of the bucket’s OBC to enable log based bucket replication. Add the following under spec:

  replicationPolicy: '{"rules":[{"rule_id":"<RULE ID>", "destination_bucket":"<DEST>", "filter": {"prefix": "<PREFIX>"}}], "log_replication_info": {"logs_location": {"logs_bucket": "<LOGS_BUCKET>"}}}'

Prerequisites

• Refer to Microsoft Azure documentation and ensure that you have completed the following tasks in the Microsoft Azure portal:

  1. Ensure that have created a new application and noted down the name, application (client) ID, and directory (tenant) ID.

     For information, see Register an application.

  2. Ensure that a new a new client secret is created and the application secret is noted down.

  3. Ensure that a new Log Analytics workspace is created and its name and workspace ID is noted down.

     For information, see Create a Log Analytics workspace.

  4. Ensure that the Reader role is assigned under Access control and members are selected and the name of the application that you registered in the previous step is provided.

     For more information, see Assign Azure roles using the Azure portal.

  5. Ensure that a new storage account is created and the Access keys are noted down.

  6. In the Monitoring section of the storage account created, select a blob and in the Diagnostic settings screen, select only StorageWrite and StorageDelete, and in the destination details add the Log Analytics workspace that you created earlier. Ensure that a blob is selected in the Diagnostic settings screen of the Monitoring section of the storage account created. Also, ensure that only StorageWrite and StorageDelete is selected and in the destination details, the Log Analytics workspace that you created earlier is added.

     For more information, see Diagnostic settings in Azure Monitor.

  7. Ensure that two new containers for object source and object destination are created.
• Administrator access to OpenShift Web Console.

Prerequisites

• Administrator access to OpenShift Web Console.
• AWS Server Access Logging configured for the desired bucket.