IBM License Metric Tool (ILMT)

 View Only
Expand all | Collapse all

How to report sub-cap for DB2 env running in AWS EC2 Instance

  • 1.  How to report sub-cap for DB2 env running in AWS EC2 Instance

    Posted Mon September 16, 2024 02:27 PM

    Hi

    Is sub-cap supported for  DB2 env running in AWS EC2 Instance?  And if so how would that be configured as I'm assuming you have no VM-Manager.

    How does ILMT know that we have reduced number of vCPU cores via kernel or by launching instance with less cores than EC2 comes with?

    Regards 

    Ray



    ------------------------------
    Ray Mahon
    Tivoli Client Technical Professional
    IBM Ireland
    353-(0)86 4128743
    ------------------------------


  • 2.  RE: How to report sub-cap for DB2 env running in AWS EC2 Instance

    Posted Tue September 17, 2024 05:27 AM

    Hello,

    It is.
    In such case it only has access to information about the number of vCPUs that each VM is assigned to (Collected by HW scan placed directly on VM).
    So, ILMT will count number of vCPUs as seen by the operating system installed on the VM.


    By 'Reduced number of vCPU cores via kernel' you mean 'processor affinity' or 'Optimize CPUs for Amazon EC2 instances' feature ?
    As a quick reminder, the affinity is not PVU eligible technology and it cannot be used to limit the number of processor cores according to PVU license agreement.



    ------------------------------
    Thank you,
    Oktawian

    Oktawian Powązka, L3 Support
    IBM License Metric Tool
    ------------------------------

    Original Message


  • 3.  RE: How to report sub-cap for DB2 env running in AWS EC2 Instance

    Posted Wed September 18, 2024 01:41 AM

    Hi Ray,

    from an IBM Licensing point of view, when a Customer deploys Db2 on a VM instance of AWS EC2, the IBM BYOSL licensing policy applies.
    This is the official IBM BYOSL page:
    https://www.ibm.com/software/passportadvantage/eligible_public_cloud_BYOSL_policy.html

    Assuming that we are dealing with a deployment of IBM Db2 within an AWS EC2 compute VM instance, the IBM BYOSL licensing policy that applies is described under the relevant Note 1: In all instances: 1 vCPU = 1 Core = 1 VPC = 70 PVUs.
    The PVU rate is therefore a flat 70 PVUs per vCPU allocated to the AWS EC2 VM instance.
    The ILMT Virtual Manager component does not need to be configured and connected to the HyperVisor, but, You only need to classify the VM instance as being hosted on AWS EC2. This is done in ILMT Hardware Inventory report via ILMT Web UI as documented:
    https://www.ibm.com/docs/en/license-metric-tool?topic=computers-identifying-as-running-public-cloud

    The ILMT Scanner running within the OS of the AWS EC2 VM instance will meter the allocated vCPUs.
    AWS EC2 VM instance profiles are always provisioned with the default and maximum number of vCPUs they can have, and the number of vCPUs officially documented.
    For a selected set of EC2 VM instance profiles, AWS allows to start the EC2 VM instance with an allowed combination of number of Cores and Threads per Core, in order to reduce the allocated capacity of vCPUs of the VM instance versus the related default and maximum capacity.
    In such a case, IBM will recognise the reduction of capacity only if reported via ILMT. otherwise the default and maximum available capacity will be used.

    Antonio Gallotti
    WW Technical SW License Manager - IBM Licensing. 



    ------------------------------
    Antonio Gallotti
    Program Director
    IBM Licensing
    ------------------------------

    Original Message