Chapter 10. Object Bucket Claim

Procedure

1. Add the following lines to your application YAML:

   apiVersion: objectbucket.io/v1alpha1
   kind: ObjectBucketClaim
   metadata:
     name: <obc-name>
   spec:
     generateBucketName: <obc-bucket-name>
     storageClassName: openshift-storage.noobaa.io

   Copy to Clipboard Toggle word wrap

   These lines are the OBC itself.

   1. Replace <obc-name> with the a unique OBC name.
   2. Replace <obc-bucket-name> with a unique bucket name for your OBC.

2. You can add more lines to the YAML file to automate the use of the OBC. The example below is the mapping between the bucket claim result, which is a configuration map with data and a secret with the credentials. This specific job claims the Object Bucket from NooBaa, which creates a bucket and an account.

   apiVersion: batch/v1
   kind: Job
   metadata:
     name: testjob
   spec:
     template:
       spec:
         restartPolicy: OnFailure
         containers:
           - image: <your application image>
             name: test
             env:
               - name: BUCKET_NAME
                 valueFrom:
                   configMapKeyRef:
                     name: <obc-name>
                     key: BUCKET_NAME
               - name: BUCKET_HOST
                 valueFrom:
                   configMapKeyRef:
                     name: <obc-name>
                     key: BUCKET_HOST
               - name: BUCKET_PORT
                 valueFrom:
                   configMapKeyRef:
                     name: <obc-name>
                     key: BUCKET_PORT
               - name: AWS_ACCESS_KEY_ID
                 valueFrom:
                   secretKeyRef:
                     name: <obc-name>
                     key: AWS_ACCESS_KEY_ID
               - name: AWS_SECRET_ACCESS_KEY
                 valueFrom:
                   secretKeyRef:
                     name: <obc-name>
                     key: AWS_SECRET_ACCESS_KEY

   Copy to Clipboard Toggle word wrap
   1. Replace all instances of <obc-name> with your OBC name.
   2. Replace <your application image> with your application image.

3. Apply the updated YAML file:

   # oc apply -f <yaml.file>

   Copy to Clipboard Toggle word wrap

   Replace <yaml.file> with the name of your YAML file.

4. To view the new configuration map, run the following:

   # oc get cm <obc-name> -o yaml

   Copy to Clipboard Toggle word wrap

   Replace obc-name with the name of your OBC.

   You can expect the following environment variables in the output:

   • BUCKET_HOST - Endpoint to use in the application.

   • BUCKET_PORT - The port available for the application.

     • The port is related to the BUCKET_HOST. For example, if the BUCKET_HOST is https://my.example.com, and the BUCKET_PORT is 443, the endpoint for the object service would be https://my.example.com:443.
   • BUCKET_NAME - Requested or generated bucket name.
   • AWS_ACCESS_KEY_ID - Access key that is part of the credentials.
   • AWS_SECRET_ACCESS_KEY - Secret access key that is part of the credentials.

Procedure

1. Use the command-line interface to generate the details of a new bucket and credentials. Run the following command:

   # noobaa obc create <obc-name> -n openshift-storage

   Copy to Clipboard Toggle word wrap

   Replace <obc-name> with a unique OBC name, for example, myappobc.

   Additionally, you can use the --app-namespace option to specify the namespace where the OBC configuration map and secret will be created, for example, myapp-namespace.

   Example output:

   INFO[0001] ✅ Created: ObjectBucketClaim "test21obc"

   Copy to Clipboard Toggle word wrap

   The MCG command-line-interface has created the necessary configuration and has informed OpenShift about the new OBC.

2. Run the following command to view the OBC:

   # oc get obc -n openshift-storage

   Copy to Clipboard Toggle word wrap

   Example output:

   NAME        STORAGE-CLASS                 PHASE   AGE
   test21obc   openshift-storage.noobaa.io   Bound   38s

   Copy to Clipboard Toggle word wrap

3. Run the following command to view the YAML file for the new OBC:

   # oc get obc test21obc -o yaml -n openshift-storage

   Copy to Clipboard Toggle word wrap

   Example output:

   apiVersion: objectbucket.io/v1alpha1
   kind: ObjectBucketClaim
   metadata:
     creationTimestamp: "2019-10-24T13:30:07Z"
     finalizers:
     - objectbucket.io/finalizer
     generation: 2
     labels:
       app: noobaa
       bucket-provisioner: openshift-storage.noobaa.io-obc
       noobaa-domain: openshift-storage.noobaa.io
     name: test21obc
     namespace: openshift-storage
     resourceVersion: "40756"
     selfLink: /apis/objectbucket.io/v1alpha1/namespaces/openshift-storage/objectbucketclaims/test21obc
     uid: 64f04cba-f662-11e9-bc3c-0295250841af
   spec:
     ObjectBucketName: obc-openshift-storage-test21obc
     bucketName: test21obc-933348a6-e267-4f82-82f1-e59bf4fe3bb4
     generateBucketName: test21obc
     storageClassName: openshift-storage.noobaa.io
   status:
     phase: Bound

   Copy to Clipboard Toggle word wrap

4. Inside of your openshift-storage namespace, you can find the configuration map and the secret to use this OBC. The CM and the secret have the same name as the OBC. Run the following command to view the secret:

   # oc get -n openshift-storage secret test21obc -o yaml

   Copy to Clipboard Toggle word wrap

   Example output:

   Example output:
   apiVersion: v1
   data:
     AWS_ACCESS_KEY_ID: c0M0R2xVanF3ODR3bHBkVW94cmY=
     AWS_SECRET_ACCESS_KEY: Wi9kcFluSWxHRzlWaFlzNk1hc0xma2JXcjM1MVhqa051SlBleXpmOQ==
   kind: Secret
   metadata:
     creationTimestamp: "2019-10-24T13:30:07Z"
     finalizers:
     - objectbucket.io/finalizer
     labels:
       app: noobaa
       bucket-provisioner: openshift-storage.noobaa.io-obc
       noobaa-domain: openshift-storage.noobaa.io
     name: test21obc
     namespace: openshift-storage
     ownerReferences:
     - apiVersion: objectbucket.io/v1alpha1
       blockOwnerDeletion: true
       controller: true
       kind: ObjectBucketClaim
       name: test21obc
       uid: 64f04cba-f662-11e9-bc3c-0295250841af
     resourceVersion: "40751"
     selfLink: /api/v1/namespaces/openshift-storage/secrets/test21obc
     uid: 65117c1c-f662-11e9-9094-0a5305de57bb
   type: Opaque

   Copy to Clipboard Toggle word wrap

   The secret gives you the S3 access credentials.

5. Run the following command to view the configuration map:

   # oc get -n openshift-storage cm test21obc -o yaml

   Copy to Clipboard Toggle word wrap

   Example output:

   apiVersion: v1
   data:
     BUCKET_HOST: 10.0.171.35
     BUCKET_NAME: test21obc-933348a6-e267-4f82-82f1-e59bf4fe3bb4
     BUCKET_PORT: "31242"
     BUCKET_REGION: ""
     BUCKET_SUBREGION: ""
   kind: ConfigMap
   metadata:
     creationTimestamp: "2019-10-24T13:30:07Z"
     finalizers:
     - objectbucket.io/finalizer
     labels:
       app: noobaa
       bucket-provisioner: openshift-storage.noobaa.io-obc
       noobaa-domain: openshift-storage.noobaa.io
     name: test21obc
     namespace: openshift-storage
     ownerReferences:
     - apiVersion: objectbucket.io/v1alpha1
       blockOwnerDeletion: true
       controller: true
       kind: ObjectBucketClaim
       name: test21obc
       uid: 64f04cba-f662-11e9-bc3c-0295250841af
     resourceVersion: "40752"
     selfLink: /api/v1/namespaces/openshift-storage/configmaps/test21obc
     uid: 651c6501-f662-11e9-9094-0a5305de57bb

   Copy to Clipboard Toggle word wrap

   The configuration map contains the S3 endpoint information for your application.

Procedure

1. Log into the OpenShift Web Console.

2. On the left navigation bar, click Storage Object Bucket Claims Create Object Bucket Claim.

   1. Enter a name for your object bucket claim and select the appropriate storage class based on your deployment, internal or external, from the dropdown menu:

      Internal mode

      

      View larger image

      

      The following storage classes, which were created after deployment, are available for use:

      • ocs-storagecluster-ceph-rgw uses the Ceph Object Gateway (RGW)
      • openshift-storage.noobaa.io uses the Multicloud Object Gateway (MCG)

      External mode

      

      View larger image

      

      The following storage classes, which were created after deployment, are available for use:

      • ocs-external-storagecluster-ceph-rgw uses the RGW

      • openshift-storage.noobaa.io uses the MCG

        Note

        The RGW OBC storage class is only available with fresh installations of OpenShift Data Foundation version 4.5. It does not apply to clusters upgraded from previous OpenShift Data Foundation releases.

   2. Click Create.

      Once you create the OBC, you are redirected to its detail page:

      

      View larger image

      

Procedure

1. On the left navigation bar, click Storage Object Bucket Claims.

2. Click the Action menu (⋮) next to the OBC you created.

   1. From the drop-down menu, select Attach to Deployment.

      

      View larger image

      

   2. Select the desired deployment from the Deployment Name list, then click Attach.

      

      View larger image

      

Procedure

1. Log into the OpenShift Web Console.

2. On the left navigation bar, click Storage Object Buckets.

   

   View larger image

   

   Alternatively, you can also navigate to the details page of a specific OBC and click the Resource link to view the object buckets for that OBC.

3. Select the object bucket you want to see details for. You are navigated to the Object Bucket Details page.

Procedure

1. On the left navigation bar, click Storage Object Bucket Claims.

2. Click the Action menu (⋮) next to the Object Bucket Claim (OBC) you want to delete.

   

   View larger image

   
   1. Select Delete Object Bucket Claim.
   2. Click Delete.