Identifying computers as running on public clouds (Ansible® scenario)

9.2.23 Available from 9.2.23.

Computers that run on public clouds must additionally be identified as such. It ensures that proper subcapacity counting rules are applied by License Metric Tool. You can identify a computer as running on a public cloud from the License Metric Tool user interface or by specifying the lmt_scanner_public_cloud_type parameter in the inventory file.

Before you begin

You can choose the method that is suitable for your needs. Specifying the parameter is better during the environment setup as it ensures proper subcapacity counting rules are applied from the very beginning. Identifying computers from the user interface is better in the following scenarios:
  • Closed appliances that do not allow for specifying the parameter.
  • When you did not identify an x86 computer as running on the public cloud from the very beginning as it applies the proper counting rules for the past. In case of other architectures, the computer is considered as running on a public cloud from the day when it was marked as such.

About this task

  • License Metric Tool supports selected operating systems that run on selected public clouds. For more information, see: Licensing on public clouds.
  • Computers that are not identified as public clouds can have the No VM Manager Data or No Scan Data status on the Capacity Scan Health widget on the Dashboard.
  • Marking computers from the License Metric Tool user interface overrides values that you specify in the lmt_scanner_public_cloud_type parameter.

9.2.31 Identifying computers from the user interface

You can identify the computer as running on a public cloud from the Hardware Inventory report in License Metric Tool. The disconnected scanner must be in version 9.2.28 or later for this method to work.

Procedure

For detailed instructions, see: Identifying computers as running on public cloud.

Identifying computers by using the parameter

You can identify the computer as running on a public cloud by setting the value of the lmt_scanner_public_cloud_type parameter.

Procedure

  1. Open the inventory file.
  2. Add the lmt_scanner_public_cloud_type parameter to each computer that runs on a public cloud, and set its value. For the list of available values, see: Parameters used in playbooks.
    Note: Ensure the name of the public cloud is enclosed in quotation marks.

Results

A computer that runs on a public cloud is assigned the number of PVUs that is specified in the IBM Eligible Public Cloud BYOSL policy.

What to do next

For the changes to take effect, run the import of data. To view what public cloud is defined for a particular computer, see the Public Cloud Type column on the Hardware Inventory report.