Converting an AFM to cloud object storage fileset supporting Azure Blob storage by using a MinIO gateway to native Azure Blob storage

In earlier releases of IBM Storage Scale 5.1.9, the AFM to cloud object storage for Azure Blob is executed by using a MinIO gateway. From IBM Storage Scale 5.1.9, an AFM to cloud object storage fileset can connect to Azure Blob natively without any intermediate gateway or application

To change the AFM to cloud object storage filesets to support Azure Blob naively, complete the following steps:

After the storage accounts and keys are set up from an Azure Blob storage, copy the endpoint URL that you want to add as a target and failover to it by using the following command:
```
# mmafmctl fs1 failover --target-only
```
A sample output is as follows:
```
https://afmtest.blob.core.windows.net/container1
```
where:

afmtest

Is a storage account.

container1

Is the name of a container.
Stop the IOs on the fileset and change the afmObjectAZ fileset parameter to yes.
```
# mmchfileset fs1 test -p afmObjectAZ=yes
```
A sample output is as follows:
```
Fileset test changed.
```

Change the target.

# mmafmctl fs1 failover -j test --new-target https://afmtest.blob.core.windows.net/container1 --target-only

A sample output is as follows:

mmafmctl: Performing failover to https://afmtest.blob.core.windows.net/container1

Fileset test changed.

Create some data and check whether the queue is active and data is synchronized to the Azure Blob storage.

echo 12345 >> /gpfs/fs1/test/ffffff

c7f2n02 01Nov10:40:47 2] getstate

A sample output is as follows:

Fileset Name Fileset Target Cache State Gateway Node Queue Length Queue numExec

------------ -------------- ------------- ------------ ------------ -------------

test https://afmtest.blob.core.windows.net:443/container1 Active c7f2n02 0 4