Core-pair
Catalog row in Vendor License Metrics · Cited
- Unit
- Core
- Aliases
- core-pair; 2 cores or 4 vCPUs
- Definition
- One of the bases for self-managed OpenShift subscriptions. It is defined as 2 physical cores or as 4 virtual central processing units (vCPUs). On a bare-metal machine, it always refers to the physical core, regardless of any hyperthreading or symmetric multithreading technology. If hyperthreading is turned on, then 2 physical cores that present as 4 vCPU are still counted as a single core-pair. For hyperscaler deployments, e.g. AWS, Azure, and GCP, 4 vCPU are always considered a single core-pair.
- Counting rules
- Count the aggregate number of physical cores or vCPUs across all OpenShift compute nodes running across all OpenShift clusters you want to entitle using core-pair subscriptions. Core-pair subscriptions are counted at the cluster level and can span multiple cloud instances, VMs, and physical servers. Bare metal: always physical cores regardless of hyperthreading; 2 physical cores that present as 4 vCPU are still one core-pair. Hyperscaler (AWS, Azure, GCP): 4 vCPU are always considered a single core-pair.
- Floors / minimums
- Core-pair (2 cores or 4 vCPUs). Control plane and infrastructure nodes do not need to be counted unless application instances run on them (exceptions named in the OpenShift subscription guide). There is no conversion from Core-pair to Socket-pair.
- Applies to products (more)
- Red Hat OpenShift AI
- Red Hat OpenShift Container Platform
- Red Hat OpenShift Kubernetes Engine
- Red Hat OpenShift Platform Plus
- Red Hat OpenShift Platform Plus (without OpenShift Container Platform)
- Red Hat OpenShift Platform Plus with OpenShift Data Foundation Advanced
- Applies to editions
- Premium (for Windows)
- Virtual Node / Core-pair
- Product category