Red Hat License Calculator

Red Hat License Calculator Formula and Explanation

The calculation for Red Hat licenses is not a single, universal formula but rather a set of rules applied based on the deployment type and chosen licensing model. Our Red Hat License Calculator employs simplified versions of these rules to provide a practical estimate.

Physical Server Licensing Logic

For physical servers, the calculation depends on your selected model:

• Per Socket Pair: If selected, each pair of physical CPU sockets on a server typically requires one RHEL subscription. For example, a server with 2 sockets needs 1 subscription, while a server with 4 sockets needs 2 subscriptions. This model often implies a certain limit on physical cores per socket, but for simplicity, we focus on socket count.
• Per Core Pair: If selected, every two physical cores on a server require one RHEL subscription. For example, a server with 16 physical cores would need 8 subscriptions (16 cores / 2 cores per unit). This model is common for high-density, multi-core processors.

The calculator aggregates these requirements across all your physical servers.

Virtual Machine Licensing Logic

For virtual machines, two primary models are considered:

• Per Virtual Machine (up to 4 vCPUs): Each individual RHEL virtual machine requires one subscription, provided it does not exceed a certain number of virtual CPUs (commonly 4 vCPUs per VM). If a VM has more than 4 vCPUs, it might require additional subscriptions or a higher-tier license. For simplicity, our calculator assumes VMs are within this vCPU limit for a single subscription.
• Per Host (Unlimited RHEL Guests): This is a powerful model where a single, higher-tier RHEL subscription (e.g., RHEL for Virtual Datacenters) applied to a physical host covers an unlimited number of RHEL virtual machines running on that specific host. This is highly efficient for dense virtualization. If this option is chosen and the host is marked as "dedicated," the calculator counts the number of physical hosts rather than individual VMs.

Add-on Subscriptions

• Red Hat Satellite: This management platform is typically licensed based on the number of managed systems. Our calculator estimates 1 Satellite subscription for every 25 RHEL systems (physical or virtual).
• Ansible Automation Platform: Often licensed per managed node. We estimate 1 Ansible Automation Platform subscription for every 50 RHEL systems.

Total Subscriptions = Physical Server Subscriptions + Virtual Machine Subscriptions + Satellite Subscriptions + Ansible Automation Platform Subscriptions

Practical Examples Using the Red Hat License Calculator

Example 1: Small Physical Deployment with Management

Let's say you have a small data center with 3 physical servers, each with 2 sockets and 12 physical cores per socket. You plan to license them using the "Per Socket Pair" model and also want to include Red Hat Satellite for management.

• Inputs:
  • Number of Physical Servers: 3
  • Sockets per Physical Server: 2
  • Cores per Socket (Physical): 12
  • Physical Server Licensing Model: Per Socket Pair
  • Number of Red Hat Virtual Machines: 0
  • Include Red Hat Satellite Subscriptions: Yes
  • Include Ansible Automation Platform Subscriptions: No
• Calculation:
  • Physical Server Subscriptions: 3 servers * (2 sockets / 2 sockets per unit) = 3 subscriptions
  • Total RHEL Systems (for Satellite): 3 physical servers
  • Red Hat Satellite Subscriptions: ceil(3 / 25) = 1 subscription
• Results:
  • Total RHEL Subscriptions: 3
  • Physical Server Subscriptions: 3
  • Virtual Machine Subscriptions: 0
  • Red Hat Satellite Subscriptions: 1
  • Ansible Automation Platform Subscriptions: 0

This scenario shows how the "Per Socket Pair" model works for physical hosts and how management add-ons are estimated based on the total number of managed RHEL instances.

Example 2: Large Virtualized Environment

Consider a large virtualization cluster with 10 physical hosts, each with 4 sockets and 16 physical cores per socket. You plan to run 150 RHEL virtual machines, each with 4 vCPUs. You want to use the "Per Host (Unlimited RHEL Guests)" model for your VMs and include Ansible Automation Platform. Your physical hosts are dedicated to RHEL VMs.

• Inputs:
  • Number of Physical Servers: 10
  • Sockets per Physical Server: 4
  • Cores per Socket (Physical): 16
  • Physical Server Licensing Model: Per Core Pair (Note: This model might be more expensive but is shown for example. For unlimited guests, the VM licensing model often takes precedence for the host.)
  • Number of Red Hat Virtual Machines: 150
  • Virtual Cores (vCPUs) per VM: 4
  • Virtual Machine Licensing Model: Per Host (Unlimited RHEL Guests)
  • Are the physical hosts exclusively dedicated to running RHEL VMs?: Yes
  • Include Red Hat Satellite Subscriptions: No
  • Include Ansible Automation Platform Subscriptions: Yes
• Calculation:
  • Physical Server Subscriptions (if not dedicated to VMs, but here VM model applies to host): 0 (because "Per Host Unlimited" covers the host for VMs)
  • Virtual Machine Subscriptions: 10 physical hosts (since "Per Host Unlimited" is selected and hosts are dedicated) = 10 subscriptions
  • Total RHEL Systems (for Ansible): 150 virtual machines
  • Ansible Automation Platform Subscriptions: ceil(150 / 50) = 3 subscriptions
• Results:
  • Total RHEL Subscriptions: 13
  • Physical Server Subscriptions: 0
  • Virtual Machine Subscriptions: 10
  • Red Hat Satellite Subscriptions: 0
  • Ansible Automation Platform Subscriptions: 3

This example highlights the efficiency of the "Per Host (Unlimited RHEL Guests)" model, where a few high-tier subscriptions can cover many VMs, especially when hosts are dedicated. It also demonstrates how add-on licensing scales with the number of managed RHEL instances.

How to Use This Red Hat License Calculator

Our Red Hat License Calculator is designed for ease of use, providing quick and reliable estimates. Follow these steps for accurate results:

1. Input Physical Server Details:
   • Enter the "Number of Physical Servers" you have or plan to deploy RHEL on.
   • Specify the "Sockets per Physical Server" (e.g., 1, 2, 4) and "Cores per Socket (Physical)" (e.g., 8, 16, 32).
   • Choose your "Physical Server Licensing Model":
     • Per Socket Pair: Generally for servers with fewer sockets and/or lower core counts.
     • Per Core Pair: Common for servers with many physical cores, where every two cores constitute a license unit.
2. Input Virtual Machine Details:
   • Enter the "Number of Red Hat Virtual Machines (VMs)" you intend to run.
   • Specify the "Virtual Cores (vCPUs) per VM".
   • Select your "Virtual Machine Licensing Model":
     • Per Virtual Machine (up to 4 vCPUs): Each VM is individually licensed.
     • Per Host (Unlimited RHEL Guests): A single, higher-tier license on the physical host covers all RHEL VMs on that host. This is often cost-effective for dense virtualization.
   • If you chose "Per Host (Unlimited RHEL Guests)," check the box if your physical hosts are "exclusively dedicated to running RHEL VMs". This impacts how the physical hosts themselves are counted for the VM licensing model.
3. Select Add-on Subscriptions:
   • Check the box if you want to "Include Red Hat Satellite Subscriptions".
   • Check the box if you want to "Include Ansible Automation Platform Subscriptions".
4. Calculate and Interpret Results:
   • The calculator will automatically update as you change inputs. You'll see a "Total RHEL Subscriptions" as the primary result.
   • View the breakdown into "Physical Server Subscriptions," "Virtual Machine Subscriptions," "Red Hat Satellite Subscriptions," and "Ansible Automation Platform Subscriptions".
   • The chart below the calculator visually represents this breakdown.
   • Use the "Copy Results" button to quickly save the estimated figures.
   • Remember that these are estimates. For official quotes, always consult Red Hat.

Key Factors That Affect Red Hat License Calculator Results

Understanding the nuances of Red Hat licensing is critical for accurate budgeting and compliance. Several factors significantly influence the number of subscriptions required:

1. Physical vs. Virtual Deployment: This is the most fundamental distinction. Licensing models for physical servers (per socket, per core) differ greatly from those for virtual machines (per VM, per host unlimited guests). A mixed environment requires careful calculation for both.
2. Number of Sockets and Physical Cores: For physical servers, the count of CPU sockets and the number of physical cores within those sockets directly determine the subscription count under core-based or socket-based models. More cores/sockets generally mean more subscriptions, especially with per-core licensing.
3. Number of Virtual Machines and vCPUs: If licensing per VM, the total count of RHEL VMs is key. If licensing per-VM with a vCPU limit, exceeding that limit (e.g., 4 vCPUs) can necessitate additional subscriptions for that specific VM, though our calculator simplifies this assumption.
4. Virtualization Strategy (Dense vs. Sparse): For highly virtualized environments, a "Per Host (Unlimited RHEL Guests)" subscription can be far more cost-effective than licensing each individual VM. This strategy significantly reduces the total subscription count if you're running many RHEL VMs on a few dedicated hosts.
5. Subscription Tiers (Standard, Premium, Datacenter): While our calculator focuses on the *count* of subscriptions, the *type* of subscription (e.g., Standard, Premium, RHEL for Virtual Datacenters) impacts the features, support level, and ultimately the cost per subscription. Higher tiers often come with more inclusive licensing models (like unlimited guests).
6. Add-on Products (Satellite, Ansible, OpenShift): Integrating Red Hat management tools or container platforms like OpenShift adds to the licensing requirements. These are often licensed separately based on the number of managed nodes or other metrics, as estimated by our calculator for Satellite and Ansible Automation Platform.
7. Cloud Deployments: Licensing RHEL in public cloud environments (AWS, Azure, Google Cloud) often involves different models, such as "Cloud Access" or pay-as-you-go options. Our calculator primarily focuses on on-premise or self-managed cloud instances. For specific cloud scenarios, Red Hat's cloud pricing models apply.
8. Core Factor / Hyper-threading: Red Hat's licensing typically counts *physical* cores. Hyper-threading (logical cores) does not usually increase the subscription count. Some specific processors might have a "core factor" applied by vendors, but this is less common for RHEL base licensing and beyond the scope of a simplified calculator.

Understanding these factors is crucial for making informed decisions and utilizing a Red Hat cost estimator effectively.

Red Hat License Calculator FAQ