Chapter 3. What does the subscriptions service track?
The subscriptions service currently tracks and reports usage information for Red Hat Enterprise Linux, some Red Hat OpenShift products, and some Red Hat Cloud Services services.
3.1. Red Hat Enterprise Linux
The subscriptions service tracks RHEL on physical systems, virtual systems, and public cloud. If your RHEL installations predate certificate-based subscription management, the subscriptions service will not track that inventory.
- Tracks physical RHEL usage in CPU sockets, organized by architecture and variants for x86.
- Tracks virtualized RHEL by installed socket count for standard guest subscriptions and by socket count of the hypervisor host node for virtual data center (VDC) subscriptions and similar virtualized environments.
- Tracks public cloud RHEL usage in sockets, where one instance equals one socket.
3.2. Red Hat OpenShift
Generally, the subscriptions service tracks Red Hat OpenShift usage as cluster size on physical and virtual systems. The cluster size is the sum of all subscribed nodes. A subscribed node is a compute or worker node that runs workloads, as opposed to a control plane or infrastructure node that manages the cluster.
However, beyond this general rule, tracking is dependent on several factors:
- The Red Hat OpenShift product
- The type of subscription that was purchased for that product
- The version of that product
- The unit of measurement for the product, as defined by the subscription terms, that determines how cluster size and overall usage is calculated
3.2.1. Red Hat OpenShift Container Platform with a traditional Annual subscription
The subscriptions service tracks Red Hat OpenShift Container Platform usage in CPU cores or sockets for clusters and aggregates this data into an account view, as refined by the following version support:
- RHOCP 4.1 and later with Red Hat Enterprise Linux CoreOS based nodes or a mixed environment of Red Hat Enterprise Linux CoreOS and RHEL based nodes
- RHOCP 3.11
For RHOCP subscription usage, there was a change in reporting models between the major 3 and 4 versions. Version 3 usage is considered at the node level and version 4 usage is considered at the cluster level.
The difference in reporting models for the RHOCP major versions also results in some differences in how the subscriptions service and the associated services in the Cloud Services platform calculate usage. For RHOCP version 4, the subscriptions service recognizes and ignores the parts of the cluster that perform overhead tasks. These parts of the cluster are commonly called infrastructure nodes, and can include master, router, registry, metrics, logging, etcd, and similar nodes. The subscriptions service recognizes and tracks only the parts of the cluster that contain compute nodes, also commonly called worker nodes.
However, for RHOCP version 3.11, the version 3 era reporting model cannot distinguish and ignore the infrastructure nodes. Therefore, for RHOCP version 3.11, you can assume that approximately 15% of the subscription data reported by the subscriptions service is overhead for infrastructure nodes. This percentage is based on analysis of cluster overhead in RHOCP version 3 installations. In this particular case, usage results that show up to 15% over capacity are likely to still be in compliance.
3.2.2. Red Hat OpenShift Container Platform or Red Hat OpenShift Dedicated with a pay-as-you-go On-Demand subscription
- RHOCP or OpenShift Dedicated 4.7 and later
The subscriptions service tracks RHOCP or OpenShift Dedicated 4.7 and later usage from a pay-as-you-go On-Demand subscription in core hours, a measurement of cluster size in CPU cores over a range of time. For OpenShift Dedicated On-Demand subscription, consumption of control plane resources by the availability of the service instance is tracked in instance hours. The subscriptions service ultimately aggregates all cluster core hour and instance hour data in the account into a monthly total, the unit of time that is used by the billing service for Red Hat Marketplace.
As described in the information about RHOCP 4.1 and later, The subscriptions service recognizes and tracks only the parts of the cluster that contain compute nodes, also commonly called worker nodes.
3.3. Red Hat Cloud Services
Because the services in the Red Hat Cloud Services portfolio consume different types of resources while handling different types of workloads, the subscriptions service tracks usage of these services in different ways.
3.3.1. Red Hat OpenShift Streams for Apache Kafka with a pay-as-you-go On-Demand subscription
The subscriptions service tracks Red Hat OpenShift Streams for Apache Kafka usage by the resources that are consumed by the instances of the service, including by the incoming and outgoing network traffic, as data transfer; by the volume of stored data, as data storage; and by the availability of service instances for workloads, as instance hours. The subscriptions service aggregates this data into monthly totals that are then consumed by the billing service of Red Hat Marketplace.