mkcloudserver

The mkcloudserver command creates a configuration entry for a cloud.

Note: The storage system supports up to eight clouds. The first cloud created on the system will be automatically activated. All the clouds created after the first cloud will have to be manually activated using managecloudserver command.

Notes:

¹ The nossl parameter is required when the -type is swift.
² The parameters tenant, username, pw, endpoint, rootcaloc, intermcaloc, and syscaloc cannot be used when the cloud -type is TS7700.
³ The primary7700IPs parameter is required with -type TS7700.
⁴ The secondary7700IPs parameter is required with -type TS7700.

Parameters

(Required) Displays the type of cloud. The following options are supported:

swift: Specifies that the storage system uses OpenStack Swift cloud computing system to encrypt authentication credentials and connect to a cloud storage target.
swift-keystone: Specifies that the storage system uses Swift-Keystone to encrypt authentication credentials and connect to a cloud storage target. Authentication is done using root or system certificates with Transport Layer Security (TLS).
TS7700: Specifies that the storage system authenticates and stores data directly on the IBM® TS7700 system. Authentication credentials such as a user name, password, or certificate are not required. Instead, the system uses primary and alternate IP addresses to authenticate and verify connection to the IBM TS7700 system.
aws-s3: Specifies that Amazon Simple Storage Service (Amazon S3) is to allow the storage system to authenticate and connect to S3 storage.
ibmcos: Specifies IBM Cloud® Object Storage (COS) for data protection through backup and recovery.
s3: Specifies that s3 allows the storage system to authenticate and store data on any other s3 compatible cloud storage target.

-nossl

(Optional) Specifies that communication between the storage system and the specified cloud does not require the SSL protocol.

For -type TS7700, the -nossl parameter will prevent data in flight encryption for data that is sent from the storage system to the IBM TS7700 object store.

Note: The -nossl parameter is required when you specify -type swift.

-notest

(Optional) Specifies that the default cloud connectivity test is not performed. The cloud connectivity test verifies the connection between the storage system and the cloud.

-tenant tenant_name

(Optional) The tenant name that you use to connect with the cloud.

-username user_name

(Optional) The user name that you use to connect with the cloud.

Note: The -username parameter cannot be used with -type TS7700.

The -username parameter is required when you specify the -type parameter with the swift, swift-keystone, aws-s3, s3, or ibmcos option.

-pw password

(Optional) The password that you use to connect with the cloud.

Note: The -pw parameter cannot be used with -type TS7700.

The -pw parameter is required when you specify the -type parameter with the swift, swift-keystone, aws-s3, s3, or ibmcos option.

-endpoint endpoint

(Optional) The location, or URL, of the cloud.

Note: The -endpoint parameter cannot be used with -type TS7700.

The -endpoint parameter is required when you specify the -type parameter with the swift, swift-keystone, aws-s3, ibmcos, or s3 option.

-loc location

(Optional) The detailed location or vault template of the cloud depending on the -type parameter.

Note: The -loc parameter is valid with type ibmcos or aws-s3, only.

ibmcos: The location parameter specifies the name of the user generated vault template created on the IBM Cloud Object Storage Manager.
aws-s3: The location parameter specifies the AWS Region as defined by the endpoint of the Amazon S3 service.

-primary7700IPs primary_ip_address

On this parameter (first Hydra), you can indicate a maximum of two primary IP addresses and up to two alternate IP addresses. Each IP address should be separated with a comma. For example:

primaryl_ip_address (mandatory), primary2_ip_address (optional), alternatel_ip_address (optional), alternate2_ip_address (optional)

-secondary7700IPs alternate_ip_address

If your configuration includes a second Hydra, you can indicate a maximum of two primary IP addresses and up to two alternate IP addresses on this parameter as well. Each IP address should be separated with a comma. For example:

primaryl_ip_address (mandatory), primary2_ip_address (optional), alternatel_ip_address (optional), alternate2_ip_address (optional)

-rootcaloc root_ca_location

(Optional) The path of the root certification file on your computer. The certificate determines which protocol (TLS) is used to communicate with the cloud.

Multiple clouds can share the root certificate if a root certificate exists that is defined to the system. (Root and intermediate certificates are currently the same.) If a root certificate does not exist in the storage system, the -rootcaloc parameter is required.

-intermcaloc interm_ca_location

(Optional) The path of the intermediate certification file on your computer.

-syscaloc sys_ca_location

(Optional) The path of the system certification file on your computer.

The certificate determines which protocol (TLS) to use to communicate with the cloud. Multiple clouds can share root certificate. Each cloud has a respective system certificate.

cloud_name

(Required) The name of the cloud.

Note: Each cloud must have a unique name. Multiple clouds with the same name are not supported.

-keygrp key_group_ID

(Optional) Specifies a key group that is configured for encryption of transparent cloud tiering, which ensures that data is encrypted while it is transferred to cloud storage.

Example

dscli> mkcloudserver 
-type swift -tenant mytest04 -username mrproduct 
-pw ProdUct02-endpoint "https://hostname:port/”  
-rootcaloc "/tmp/ssl_cacert.pem" 
-syscaloc "/tmp/ssl_cert.pem" ibmcloud

Note: For the first cloud that is created on the system, Output 1 is displayed. For clouds that are created after the first cloud, Output 2 is displayed.

Output 1

CMUC00505I The cloud ibmcloud was successfully created and activated on node 0.

CMUC00505I The cloud ibmcloud was successfully created and activated on node 1.

Output 2

CMUC00602W The cloud ibmcloud was successfully created on node 0.
           To activate the cloud, run managecloudserver -action applypndgconfig command.

CMUC00602W The cloud ibmcloud was successfully created on node 1.
           To activate the cloud, run managecloudserver -action applypndgconfig command.