The Eligible Public Cloud Bring Your Own Software License (BYOSL) policy allows you to deploy any IBM software licensed to you directly or through an authorized IBM reseller under the terms and conditions described here.

Eligible IBM Software

The Eligible Public Cloud Bring Your Own Software License (BYOSL) policy allows you to deploy and execute on an Eligible Public Cloud (EPC) any IBM software licensed to you directly or through an authorized IBM reseller under IBM license terms, subject to the use authorizations and restrictions stated in the applicable governing license agreements and transaction documents for such software including the IBM International Passport Advantage (IPAA) and IBM International Program License Agreement (IPLA) and the License Information documents applicable to the software.

This policy does not apply to IBM zSeries software or to any IBM software sublicensed to you by a third party. This policy also does not apply if you are an IBM Business Partner authorized to deploy your solution on a hosted environment – such situations are handled under a separate arrangement.

Eligible Public Clouds

The Eligible Public Clouds (EPCs) subject to this policy are defined below.

Provider Offering PVUs per vCPU or Core For more details
go to:
Required IBM Licensing Tools
IBM IBM Cloud Virtual Servers See Note 1 below https://www.ibm.com/cloud

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

IBM Cloud Containers See Note 1 below https://www.ibm.com/cloud
IBM Power Virtual Server See Considerations for IBM Power Systems Virtual Servers in the note sections below. https://www.ibm.com/cloud/power-virtual-server
IBM Cloud Bare Metal Servers See Note 2 below

www.softlayer.com

https://www.ibm.com/cloud

IBM Kubernetes Service (IKS) See Note 1 below www.ibm.com/cloud/container-service/

IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Red Hat OpenShift on IBM Cloud4 See Note 1 below https://www.ibm.com/cloud/openshift
Alibaba Alibaba Cloud (Elastic Compute Service) See Note 1 below https://www.alibabacloud.com/

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Amazon EC2 Instances & Dedicated Instances See Note 1 below aws.amazon.com/ec2/instance-types

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Elastic Kubernetes Service (EKS) See Note 1 below aws.amazon.com/eks/

IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Red Hat OpenShift Service on AWS (ROSA)4 See Note 1 below https://aws.amazon.com/rosa/
Fujitsu Fujitsu Cloud IaaS Instance (FJcloud-V) See Note 1 below https://jp.fujitsu.com/solutions/cloud/fjcloud/-v/

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Fujitsu Cloud IaaS Instance (FJcloud-O) See Note 1 below https://jp.fujitsu.com/solutions/cloud/fjcloud/-o/
NIFCLOUD See Note 1 below https://pfs.nifcloud.com
Google Google Compute Engine See Note 1 below cloud.google.com/compute/docs/machine-types

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Google Kubernetes Engine (GKE) See Note 1 below cloud.google.com/kubernetes-engine/

IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Red Hat OpenShift Container Platform4 See Note 1 below https://cloud.google.com/architecture/partners/openshift-on-gcp
Microsoft Azure Virtual Machines See Note 1 below

azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/


azure.microsoft.com/en-us/pricing/details/virtual-machines/windows/

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Azure Kubernetes See Note 1 below azure.microsoft.com/en-us/services/kubernetes-service/

IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Azure Red Hat OpenShift (ARO)4 See Note 1 below https://azure.microsoft.com/en-us/services/openshift/
NEC Cloud Infrastructure Service (NEC Cloud IaaS) See Note 1 below https://www.nec.com/en/global/solutions/cloud/index.html

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

NTT Communications ECL 1.0 See Note 1 below https://ecl.ntt.com/

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Smart Data Platform Cloud / Server (ECL 2.0) See Note 1 below https://sdpf.ntt.com/
Oracle Cloud Compute Instances See Note 3 below https://cloud.oracle.com/compute

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Tencent Tencent Cloud Server Instance See Note 1 below https://intl.cloud.tencent.com/product/cvm

Traditional Deployments: IBM License Metric Tool

Red Hat OpenShift Deployments: IBM License Service

Amended PA terms for Container Licensing (via Addendum)

Notes:

  1. In all instances: 1 vCPU = 1 Core = 1 VPC = 70 PVUs
    • For containers with Hyperthreading enabled:  2 vCPUs = 1 Core = 1 VPC = 70 PVUs  (See Container Licensing page for more information).
  2. See the Processor Value Unit tables for requirements based on system configuration.
  3. An Oracle Compute Unit (OCPU) corresponds to two hardware execution threads, known as vCPUs.  PVU licensing requires 1 OCPU = 2 vCPU = 140 PVU
  4. Metering and reporting requirements are to be managed by client in Managed Kubernetes environments (such as OpenShift managed by Red Hat).

Considerations for IBM Power Systems Virtual Servers

The provisions in this section below apply solely to VPC-based or PVU-based Programs deployed on IBM Power Systems Virtual Servers. For sub-capacity licensing, cores may be allocated in a minimum of 0.25 core increments for shared processors (i.e. physical processors whose processing capacity is shared among multiple logical partitions) and 1.0 core for dedicated processors (i.e. whole physical processors that are assigned to a single logical partition). Fractional cores will be aggregated and rounded to the next full integer, it being clarified that all logical partitions running on the same machine type are counted as a single pool rather than by server. For purposes of illustration and not limitation, see the following examples:

  • 3 logical partitions are deployed on separate S922 servers @ 0.25 cores each. The calculation will be as follows: 0.25 x 3 = 0.75 cores, which is rounded up to 1.0 cores.
  • 3 logical partitions are deployed on 2 S922 servers and 1 E980 server @ 0.25 cores each. The calculation will be as follows: (0.25 x 2 = 0.5, which is rounded up to 1.0 cores) + (0.25 x 1 = 0.25, which is rounded up to 1.0 cores) = 2.0 cores.

Client is required to install and configure ILMT v9.2.22 or later and comply with the Sub-Capacity Licensing and reporting requirements in accordance with Sections 1.13 and 1.14 of the IPAA.

In accordance with the reporting terms outlined in IPAA Section 1.14, clients will collect deployment data and complete the manual calculation of virtualization capacity report once per quarter for the IBM Software using the command-line interface (CLI) (see link) to determine core usage. For Google Cloud, pcloud CLI commands are to be used. Such core usage shall be in accordance with the IBM Eligible Public Cloud BYOSL policy.

PVU per Core values are determined based on the Power System in use as outlined on the PVU Table per Core (section 1 of 2 - RISC and System z) table on the Processor Value Unit webpage

Licensing requirements and conditions

The Eligible Public Cloud BYOSL policy does not modify or supersede any obligations in the applicable governing license agreements, including requirements for licensed software use in a virtualized environment as  defined in the sub-capacity and container licensing policies.

The verification terms in such license agreements apply to you when you upload, install, or use eligible IBM software in an EPC and you agree to collect any required usage data for your licensed software in that EPC. You will not provide the cloud provider with any unauthorized use or access to the eligible IBM software.

You must use install and configure reporting tools designated by IBM (as noted above) for reporting usage and provide such reports to IBM upon request in accordance with IBM’s guidelines.

When you use a license entitlement according to this policy, you may not use such entitlements for any other purpose or in any other place at the same time.

Unless it is noted above,  the Eligible Public Cloud BYOSL policy DOES NOT apply to engagements with vendors where those vendors are accessing the software and/or running or managing some or all of your computing environment under the control of their own employees, either on your premises or on theirs (e.g. Strategic Outsourcing, Web Hosting, managed service providers, etc.) –such engagements require separate arrangements.