Designating the Cloud services nodes

This topic describes how to designate a node as Cloud services node in the IBM Storage Scale cluster.

Before you begin, ensure that you install the server package RPMs on all nodes that you want to designate as Cloud services nodes. These nodes must have GPFS server licenses enabled.

Also, ensure that a user-defined node class is created and properly configured for Cloud services. For more information, see Creating a user-defined node class for Transparent cloud tiering or Cloud data sharing.

To start working with Cloud services, the administrator first needs to designate a node as Cloud services node in the IBM Storage Scale cluster. Data migration to or data recall from a Cloud Object Storage that occurs in this node.

You can designate a maximum combination of four CES or NSD nodes as Cloud services nodes in each node class (with a maximum of four node class for 16 nodes total) in the IBM Storage Scale cluster.

If you use multiple node classes for Cloud services, then you can designate at least one node in each node class as Cloud services server nodes.

By default and by way of recommendation, Cloud services use the node IP addresses, not the CES IPs.

Note: You need to perform this procedure only on a single node where the server package is installed.

To designate the nodes as Cloud services nodes, issue a command according to this syntax: mmchnode change-options -N {Node[,Node...] | NodeFile | NodeClass} [--cloud-gateway-nodeclass CloudGatewayNodeClass].
You can either choose to designate all nodes or only some selected nodes in a node class as Cloud services nodes.
To designate all nodes in the node class, TCTNodeClass1, as Cloud services server nodes, issue this command:
```
mmchnode --cloud-gateway-enable -N TCTNodeClass1
```
To designate only a few nodes (node1 and node2) in the node class, TCTNodeClass1, as Cloud services server nodes, issue this command:
```
mmchnode --cloud-gateway-enable -N node1,node2 --cloud-gateway-nodeclass TCTNodeClass1
```
It designates only node1 and node2 as Cloud services server nodes from the node class, TCTNodeClass1. Administrators can continue to use the node class for other purposes.
Note: The Cloud services node must have connectivity to the object storage service that the Cloud services uses.
To designate nodes from multiple node classes as Cloud services server nodes, issue the following commands:
- ```
mmchnode --cloud-gateway-enable -N TCTNodeClass1
```
- ```
mmchnode --cloud-gateway-enable -N TCTNodeClass2
```
Note: These nodes cannot be combined into a single Cloud services across node classes because Cloud services for nodes in different node classes are always different or separate.
To list the designated Transparent cloud tiering nodes, issue this command: mmcloudgateway node list.

Note: For more information, see mmcloudgateway command.
To disable two nodes, node1 and node2, from the node class, TCTNodeClass1, issue this command:
```
mmchnode --cloud-gateway-disable -N nod1,node2 --cloud-gateway-nodeclass TCTNodeClass1
```

You can add a node to the node class at any time. For example, issue the following commands to add the node, 10.11.12.13, to the node class, TCTNodeClass1:

mmchnodeclass TCTNodeClass1 add -N 10.11.12.13
mmchnode --cloud-gateway-enable -N 10.11.12.13 --cloud-gateway-nodeclass TCTNodeClass1

Next step: Starting up the Cloud services software