File and Object Storage

$ chmod 770 /ibm/fs1/afm-cache /ibm/fs2/afm-target/
$ chown 1602:1996 /ibm/fs1/afm-cache /ibm/fs2/afm-target/
$ chcon system_u:object_r:container_file_t:s0:c111,c234 /ibm/fs1/afm-cache /ibm/fs2/afm-target/

$ mmdas account create project1 --uid 1602 --gid 1996
Account is created successfully. The secret and access keys are as follows.
Secret Key                               Access Key
----------                               -----------
czAjbq8/CzyMHJfKWvGi50nTRrS4/Id3DA/P3Hau P71YOPyNAYCdfmIjIuv4

$ alias s3p1='AWS_ACCESS_KEY_ID=P71YOPyNAYCdfmIjIuv4 AWS_SECRET_ACCESS_KEY=czAjbq8/CzyMHJfKWvGi50nTRrS4/Id3DA/P3Hau aws --endpoint https://192.0.2.12 --no-verify-ssl s3'

Create a S3 bucket based on AFM cache fileset
From a node configured to work with the OCP cluster, create an S3 export by making the AFM cache fileset accessible as an S3 bucket. For example if IBM Storage Scale file system with path "/ibm/fs1" is mounted at path "/mnt/remote-sample" in CNSA setup then a sample command would be as follows:

$ mmdas export create project1-bucket --filesystemPath /mnt/remote-sample/afm-cache/afm-s3-dir
Export is successfully created

Now AFM fileset is ready to be used as a bucket. Try writing data to the bucket by following step 3 in section "Using S3 buckets and S3 objects" at https://www.ibm.com/docs/en/ssdas?topic=installing-example-configuration-spectrum-scale-das#task_z1t_kzy_frb__title__2 

Use Case 1: Read and update the data at S3 bucket (based on the AFM cache fileset)

Below commands use the 's3p1' alias which was created in previous steps when 'project1' account was created.

$ s3p1 cp s3://project1-bucket/sample sample-copy # Read the sample file as an object
copy: s3://project1-bucket/sample to sample-copy

$ cat sample-copy
This line was written at AFM cache fileset at filesystem fs1 on Storage Scale cluster.

# Append a line to sample-copy
$ echo "This line was added at S3 bucket." >> sample-copy
$ cat sample-copy
This line was written at AFM cache fileset at filesystem fs1 on Storage Scale cluster.
This line was added at S3 bucket.

$ s3p1 cp sample-copy s3://project1-bucket/sample # Update the sample file
upload: sample-copy to s3://project1-bucket/sample

Create a new S3 object

$ echo "This line was written to a new object created inside a S3 bucket." > new-object
$ cat new-object
This line was written to a new object created inside a S3 bucket.

$ s3p1 cp new-object s3://project1-bucket # Upload the new object
upload: new-object to s3://project1-bucket/new-object

Use Case 2: Read and update the data at AFM cache fileset (mapped to S3 bucket) 

Follow below steps at the IBM Storage cluster:

$ ls /ibm/fs1/afm-cache/afm-s3-dir #shows the new-obj created at the S3 bucket
new-obj sample

$ ls /ibm/fs1/afm-target/afm-s3-dir
new-obj sample

$ cat /ibm/fs1/afm-cache/afm-s3-dir/sample
This line was written at AFM cache fileset at filesystem fs1 on Storage Scale cluster.
This line was added at S3 bucket.
$ cat /ibm/fs2/afm-target/afm-s3-dir/sample
This line was written at AFM cache fileset at filesystem fs1 on Storage Scale cluster.
This line was added at S3 bucket.

$ cat /ibm/fs1/afm-cache/afm-s3-dir/new-object
This line was written to a new object created inside a S3 bucket.
$ cat /ibm/fs1/afm-cache/afm-s3-dir/new-object
This line was written to a new object created inside a S3 bucket.

$ echo "This line was added at AFM cache fileset on Storage Scale cluster." >> /ibm/fs1/afm-cache/afm-s3-dir/new-object
$ cat /ibm/fs1/afm-cache/afm-s3-dir/new-object
This line was written to a new object created inside a S3 bucket.
This line was added at AFM cache fileset on Storage Scale cluster.

Now verify by reading the updated object at S3 bucket (mapped to AFM cache fileset) at S3 client

$ s3p1 cp s3://project1-bucket/new-obj new-obj-copy # Read the new-obj file as an object
copy: s3://project1-bucket/new-obj to new-obj-copy

$ cat new-obj-copy
This line was written to a new object created inside a S3 bucket.
This line was added at AFM cache fileset on Storage Scale cluster.

Conclusion:

The above use cases show the data at IBM Storage Scale AFM cache and target filesets could be read and updated as S3 object. Similarly, new S3 objects could be read and updated at AFM cache and target filesets on the IBM Storage Scale cluster.

Note: At the time of writing this blog, performance measurement of IBM Storage Scale Data Access Services (DAS) along with AFM was not carried out.

References:

1. IBM Storage Scale Data Access Services Documentation https://www.ibm.com/docs/en/ssdas?topic=spectrum-scale-data-access-services-517
2. IBM Storage Scale AFM Documentation https://www.ibm.com/docs/en/storage-scale/5.1.7?topic=reference-active-file-management-afm
3. IBM Storage Scale Container Native Documentation https://www.ibm.com/docs/en/scalecontainernative?topic=spectrum-scale-container-native-storage-access-517