Subscriptions Guide

Subscription Allocation Back to top

The Subscription Allocation feature has the goal to give users an overview of their subscription usage and offer guidance to solve related issues.

To get an overview of the subscription usage, we are analyzing the system asset of a given organization in SCC and their subscriptions. If the organization has more registered systems than subscriptions for a given product, it is considered to be overusing its subscriptions. If the organization has fewer registered systems than subscriptions, it is not overusing their subscriptions and can register more systems.

In case of a subscription overuse, we provide recommendations to quickly solve the most obvious issues. For example, an organization can deregister inactive systems to free subscription capacities.

The purpose of this feature is not to provide statements about an organization's compliance status and, therefore, it does not replace audits. The goal, instead, is to give an overview based on the data present in SCC and to offer help and guidance to customers.

Currently we only support a subset of products and subscriptions. Over time we want to add more products, architectures and subscription types to offer a more complete overview.

Supported Products Back to top

The current supported products are:

  • SUSE Linux Enterprise Server (x86_64)
  • SLES for SAP (x86_64)

Subscriptions Back to top

Systems running a specific product are covered by specific subscriptions. We currently support only a subset of subscription types.

1-2 Socket w/ Unlimited VMs (High-Density Subscriptions)

These subscriptions are for high-density environments. High-density environments are clusters connecting one or more virtualization hosts, each hosting many virtual systems. Typically, High-Density Subscriptions cover one virtualization host and all virtual systems running on this host. To calculate the required number of subscriptions for a virtualization host, SCC checks the number of socket pairs it has. For each socket pair, the virtualization host requires one subscription of this type.

1-2 VMs or 1-2 Sockets (Low-Density Subscriptions)

The subscriptions are used mainly for systems that run in a public cloud environment, such as Google or AWS, or in low-density scenarios on premises. This can be a physical or a virtual system. One Low-Density Subscription covers one socket pair or 1-2 virtual systems.

1-2 VMS (VM-Only Subscriptions)

VM-Only Subscriptions are used for virtual systems that are not part of a cluster or running in the public cloud. These subscriptions can also be used for virtual systems running on non-SUSE virtualization hosts in low-density environments (the host must have more than two virtual systems per socket pair).

1-2 Sockets (Physical-Only Subscriptions)

Physical-Only Subscriptions are used for physical systems, which are not part of a cluster or running in the public cloud. One subscription can cover one socket pair.

Systems Back to top

To calculate an overuse of subscriptions, SCC uses information about the systems of an organization. Currently, we differentiate between three environments.

Clusters

Clusters are represented by Virtualization Hosts and the Virtual Machines running on them. A Virtualization Host can be of various types. KVM and Xen hosts automatically qualify for High-Density Subscriptions. If they are of other types, it depends on the host's socket pairs and the number of guests running on the host. If there are two or more guests per socket pair, it is recommended to use High-Density Subscriptions.

Public Cloud

Physical or virtual systems that are running in a Public Cloud (e.g. AWS). Those systems should be covered by 1-2 VM or 1-2 Socket (Low-Density) subscriptions.

Private Cloud

Physical or virtual systems that are not running in a Public Cloud. Physical systems should be covered by 1-2 Socket (physical-only) subscriptions. Virtual systems should be covered by 1-2 VM (virtual-only) systems. Both (physical and virtual) can also fall back to low-density subscriptions, in case there are not enough VM-only or physical-only subscriptions.

Disclaimer

IMPORTANT: The subscription allocation tool is made available in the SUSE Customer Center (“SCC”) 'as is' and for convenience only to assist you in reconciling SUSE subscriptions with your deployment information. Subscription information may be incomplete, depending on the method of purchase and the information you have registered in the SCC. Deployment information is based solely on the data you have registered and maintained in the SCC. SUSE does not guarantee the completeness or accuracy of the information provided by the subscription allocation tool and is not responsible for any discrepancies or results derived from its use. This tool is not intended to replace appropriate software asset management practices. You remain responsible for ensuring that you comply with the terms of use of SUSE products and subscription offerings applicable to you. SUSE reserves the right to verify your compliance with such terms as set out therein. By using this tool, you accept this disclaimer.