Adding cloud hosts to different resource groups

Cloud hosts that join the cluster are, by default, added to the ComputeHosts resource group. To add cloud hosts to different resource groups, add resource attribute tags to cloud hosts and create resource groups to which they can be dynamically added. Segregating cloud hosts to different resource groups ensures that the provisioned cloud hosts are used only by authorized applications.

1. Add the cloudprovider resource attribute tag to uniquely identify cloud hosts with the egoconfig addresourceattr command (see egoconfig):

   egoconfig addresourceattr "[resourcemap value*cloudprovider]"

   where value is any string that uniquely identifies your group of hosts (for example, ibmcloud to identify IBM® Cloud hosts).

   Ensure that you use the egoconfig addresourceattr command to tag cloud hosts before the cloud host joins a cluster for the first time, either during image creation or during post-provisioning (recommended). If you are running the command from a post-provisioning script on Windows, include the -f option to suppress confirmation.

   Fast path: The egoconfig addresourceattr configuration is included in the sample post-provisioning scripts that are bundled with IBM Spectrum Symphony. If you use the sample scripts corresponding to each cloud provider, you don't need to use this command separately.

   Note: If a cloud host joined the cluster previously, without this attribute assigned, or to update this attribute, you must remove it from the cluster:

   egosh resource close -reclaim host_name
   egosh resource remove host_name

2. Create a resource group (for example, SymACloudHosts) based on resource requirement and specify your resource attribute tag as a select string:
   • Create a slot-based resource group either from the cluster management console (see Creating a resource group by resource requirement) or from the egosh resourcegroup add command (see resourcegroup).
   • Create a multidimensional resource group either from the cluster management console (see Creating multidimensional resource groups) or from the egosh resourcegroup -MDS add command (see resourcegroup).
   For example, to specify that hosts from the IBM Cloud, AWS, and Azure cloud must be dynamically added to the resource group that you are creating, use the following select string:

   select(cloudprovider == 'ibmcloud' || cloudprovider == 'aws' || cloudprovider == 'azure')

3. Associate your cloud-enabled applications with the new resource group.
   For example, to associate the Symping application with the new SymACloudHosts resource group, complete these steps:
   1. From the cluster management console, go to Resources > Consumers.
   2. In the consumer tree on the left, locate the application's parent consumer. For example, navigate to SymTesting, which includes Symping732 as a leaf consumer.
   3. Click the Consumer Properties tab.
   4. Scroll down to the resource group section and select SymACloudHosts to make the resource group available for all leaf consumers.
   5. Click Apply.
   6. On the Consumers tab, click Symping732.
   7. Select SymACloudHosts as a resource group for the application.
   8. Click Apply, then Close.
4. Update the requestor configuration for the new resource group. For example, to update the symA requestor configuration, update the symAreq_config.json file as follows:
   1. Edit the symAreq_config.json file at:
      • %HF_TOP%\%HF_VERSION%\requestors\symA\conf\ on Windows.
      • $HF_TOP/$HF_VERSION/requestors/symA/conf/ on Linux®.
   2. Update the resource_groups parameter. In the case of multidimensional resource groups, update the resource_plans parameter.
      For example, if Symping must get hosts from both ComputeHosts (the default resource group defined in the Symping consumer) and SymACloudHosts, enter:

      "resource_groups":["ComputeHosts", "SymACloudHosts"],  

   3. Optional: Rank the resource groups in order of preference; otherwise, slots are taken from each resource group without any preference. For more information, see Configuring resource group preference.