Subscription Terms

By accessing or using the benefits of a Subscription Offering (including by accessing the Customer Center), you (“You”) accept the Agreement (as defined in Section 2 below) with Rancher Federal, Inc. DBA Rancher Government Solutions (RGS). If You have previously accepted a different version of the Agreement, this Agreement supersedes that agreement.

2. Structure

The “Agreement” means the following components, each as defined in the Glossary: (a) the applicable Order Form, (b) the Enterprise Agreement (EA) (including exhibits and addenda attached thereto) (c) the RGS Software Terms; (d) the RG S Support and Maintenance Terms of Service set forth at https://ranchergovernment.com/terms-and-conditions ; and (e) this document, being the Subscription Terms, including any terms on hyperlinks included in these terms. To the extent of any conflict or ambiguity between the terms of the above documents, the documents shall apply in the following order of precedence: (i) the applicable Order Form; (ii) these Subscription Terms; (iii) the EA; (iv) the RGS Software Terms; and (v) the RGS Support and Maintenance Terms. Each time You renew a Subscription Offering, the then-current version of these Subscription Terms shall apply to that renewal, unless the most recent version of the Subscription Terms no longer refers to Your Subscription Offering, in which case the most recent version of the Subscription Terms referring to Your particular Subscription Offering shall govern Your use of that Subscription Offering.

3. Agreement Effective Date

If you have signed a Partner Agreement with or without accompanying Schedules, the Agreement is effective as of the date of final signature of that Partner Agreement. If you have not signed a Partner Agreement with RGS, the Agreement becomes effective on the first date you submit an order for Products, directly or indirectly.

4. Evaluation Proof of Concept or Beta Offerings

RGS may offer limited Subscription Offerings for proof of concept purposes (“Evaluation Offering”). These Subscription Offerings are for a limited and governed by the terms found here: https://ranchergovernment.com/terms-and-conditions 

5. Subscription Offering

5.1 Benefit of RGS Subscription Offerings. For each Subscription Offering, subject to registration, You are entitled to receive the materials and services, including technical support services as applicable, identified in these Subscription Terms and on the below URLs (“Subscription Benefits”):

1. 1. RGS Support. Each Subscription Offering entitles you to web and telephone support set forth in the Terms of Support and Maintenance found here https://ranchergovernment.com/terms-and-conditions. In order to receive technical support for a Product, all of Your installations for that Product must be covered by a Subscription Offering.
   2. Product Support Lifecycle and Application of Current Software. RGS Product support lifecycle provides support availability guidelines for RGS Offerings as described in the Support and Maintenance Terms of Service found here: https://ranchergovernment.com/terms-and-conditions. Subscription Offering benefits may be conditioned on You having applied the most current maintenance software available; for example, once a new Service Pack becomes available, support may be conditioned on You having applied that Service Pack. Similarly, support for Modules may be conditioned on You having updated to the most recent Module version made available.
   3. Software Updates and Upgrades. If RGS commercially releases any Upgrades and/or Updates during the period covered by Your Subscription Offering, RGS will make such Upgrades and/or Updates available to You within a reasonable period of time after they become commercially available. You will be entitled (and may be required) to install and use such Upgrades and/or Updates up to the number of installations for which You have purchased a Subscription Offering. Use of Upgrades is subject to the restrictions of the RGS Software Terms provided with the Upgrade.
   4. Third party products. RGS shall not be liable to You, and shall not be in breach of any of its obligations under the Agreement, to the extent that any errors or defects in the operation of any RGS Product are caused by a third party product with which that RGS Product interacts or interfaces.
   5. Professional Services. RGS offers optional professional services including training, consultancy and implementation services, which are as described in a statement of work entered into between You and RGS or described in standard service descriptions available in the Support and Maintenance Terms of Service found here: https://ranchergovernment.com/terms-and-conditions , the terms of which are incorporated into the Agreement, and referenced in an order placed by You,. 
   6. RGS AI. Your use of the RGS AI Suite is also governed by the RGS AI Supplemental Terms set out at https://ranchergovernment.com/terms-and-conditions from time to time, the terms of which are incorporated into the Agreement.

5.2 Unit of Measure. The unit of measure for a Subscription Offering is the metric specified in Exhibit A (“Unit”). You agree to comply with all restrictions set out in the Metrics Appendices with respect to your access and use of the Subscription Offerings.

5.3 No Mixing of Subscription Offerings. Subscription Offerings may only be applied to the exact RGS Product for which the Subscription Offering was acquired. By way of example and not limitation, You cannot apply Subscription Offering benefits for the x86 platform version of SUSE® Linux Enterprise Server (SLES) to the z System platform version of SLES, nor may you apply Subscription Offerings benefits for SLES to SLES for SAP Applications. You may not mix 1-2 Virtual Machine Subscription Offerings with Unlimited Virtual Machine Subscription Offerings on the same Physical Server. All Subscription Offerings must be of the same type on a Physical Server.

6. Bring Your Own Subscription (“BYOS”)

6.1 Transferring or deploying Subscription Offerings to a Public Cloud. RGS operates a ‘Bring Your Own Subscription’ (BYOS) policy that allows You, subject to compliance with the remainder of this Section 6 to use RGS Products in Eligible Public Clouds (“RGS Cloud Products”) and to ‘transfer’ existing Subscription Offerings in respect of ‘on premise’ deployments to those RGS Cloud Products.

6.2 Removal of Public Cloud Vendor from Eligibility. RGS may remove a particular Public Cloud vendor with sixty (60) days’ notice. You may continue to use such Subscription Offerings that have already been validly transferred to that Public Cloud vendor under Section 6.1 hereto during this sixty day notice period or for the remainder of the term of the Subscription Offering, whichever is shorter. You may, subject to Section 6.1, also transfer Your Subscription Offering to another eligible Public Cloud vendor or (back) to your premises

Exhibit A – Matrix of RGS Products

RGS has updated the product names of certain Products and, accordingly, the names of the corresponding RGS Offerings. This name change does not affect Your entitlement to support under the Agreement for the RGS Products pursuant to purchased RGS Offerings of the previous name. All previous names for RGS Products (in brackets) and RGS Offerings will now correspond to the new names as listed below:

Appendix A – SUSE Linux Enterprise Server and SUSE Linux Enterprise Server for SAP Applications

SUSE Linux Enterprise Server Subscription Offerings and Units of Measure

Operating Environments and Unit of Measure

Each Physical Server, Virtualization Host or Virtualization Environment on which SUSE Linux Enterprise Server is deployed, installed, used or executed must have a Subscription Offering. Except for our Arm AArch64 processor Subscription offerings, Units of Measure do not differentiate between single core, multi-core or simultaneous multi-threading capable Processors.

For Virtualization Environments, if the Unit of Measure chosen is per number of Sockets with Unlimited Virtual Machines per Physical Server, only Physical Servers for which the appropriate Subscription Offering has been acquired may be used to deploy such Virtualization Environment, irrespective of whether such Physical Server is actually used or for how long such Physical Server is used.

A SUSE Linux Enterprise Server Subscription Offering must not be used as Subscription Offering for SUSE Linux Enterprise Server for SAP Applications. SUSE Linux Enterprise Server for SAP with 1-2 Sockets or 1-2 VMs allows you to use any combination of SUSE Linux Enterprise Server for SAP, SUSE Linux Enterprise Server, or SUSE Linux Enterprise Server together with SUSE Linux Enterprise High Availability Extension on a Physical Server or as guest VM.

To change the deployment type of a Product during the Subscription Offering period, You must choose the highest valued Subscription Offering matching Your different deployment types for this Product. For example, if You deploy the higher valued SUSE Linux Enterprise Server Subscription Offering for '1-2 Sockets with Unlimited Virtual Machines' during the Subscription Offering period for a deployment scenario matching a lower valued (when compared to the 1-2 Sockets with Unlimited Virtual Machines Subscription Offering) '1-2 Sockets or 1-2 Virtual Machines', You may continue to use the higher valued Subscription Offering for the remaining subscription period. However, You may not deploy the lower valued SUSE Linux Enterprise Server Subscription Offering for '1-2 Sockets or 1-2 Virtual Machines' during the Subscription Offering period for a deployment type matching the higher valued '1-2 Sockets with Unlimited Virtual Machines' Subscription Offering.

x86 and x86-64 Architectures

For x86 and x86-64 Architectures, the following Subscription Offerings are available:

1. Subscription Offerings for 1-2 Sockets or 1-2 Virtual Machines
   These Subscription Offerings are to be used for flexible deployments on either Physical Servers or low-density Virtualization Environments or cloud virtualization.
2. Subscription Offerings for Physical only, 1-2 Sockets
   These Subscription Offerings are to be used for flexible deployments on Physical Servers and are not eligible for BYOS and cannot be transferred to SUSE Cloud Products.
3. Subscription Offerings for 1 Virtual Machine
   These Subscription Offerings are to be used for flexible deployments on low-density Virtualization Environments and are not eligible for BYOS and cannot be transferred to SUSE Cloud Products.
4. Subscription Offerings for 1-2 Sockets with Unlimited Virtual Machines
   These Subscription Offerings are to be used for flexible deployments on high-density Virtualization Environments.

Deployment on Physical Servers

The number of Subscription Offerings needed for a Physical Server is determined by the number of Sockets in the Physical Server.

Physical Servers with 1 - 2 Sockets need either 1 Subscription Offering for "1-2 Sockets or 1-2 Virtual Machines" or 1 Subscription Offering for “Physical-only, 1-2 Sockets”.

For Physical Servers with more than 2 Sockets, Subscription Offerings are Stackable to match or exceed the number of Sockets. For example, a Physical Server with 4 Sockets needs 2 Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines” or alternatively 2 Subscription Offerings for “Physical only, 1-2 Sockets”. A Subscription Offering for “1-2 Sockets or 1-2 Virtual Machines” or for “Physical only, 1-2 Sockets” can only be deployed on the same Physical Server (i.e. these Subscription Offerings cannot be used for 1 Socket on one Physical Server and 1 Socket on another Physical Server).

Subscription Offerings can be transferred to new and/or different Physical Servers. For example, when 10 Physical Servers with 2 Sockets each are replaced by 4 Physical Servers with 4 Sockets each, the 10 “1-2 Sockets or 1-2 Virtual Machines” Subscription Offerings can be transferred to the new Physical Servers. In this example, a total of 8 Subscription Offerings (2 per Physical Server with 4 Sockets) are transferred to the new Physical Servers. You can use the remaining 2 Subscription Offerings for later deployments.

Subscription Offerings for “Physical only, 1-2 Sockets” are not eligible for BYOS and cannot be transferred to SUSE Cloud Products.

Low-Density Virtualization Environments or Cloud Deployments

For low-density Virtualization Environments, the following Subscription Offerings are available:

1. Up to 2 Virtual Machines running on the same Virtualization Host or Virtualization Environment or within the same Private Cloud account or Public Cloud zone can be deployed with one “1-2 Sockets or 1-2 Virtual Machines” Subscription Offering. Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines” can also be repurposed as Virtual Machines on any Virtualization Host, Virtualization Environment or with any SUSE certified Cloud Services Provider (CSP).
   
   At any point in time, a Subscription Offering for “1-2 Sockets or 1-2 Virtual Machines” can only be deployed either on a Physical Server or as Virtual Machines. For clarity, a Subscription Offering for “1-2 Sockets or 1-2 Virtual Machines” cannot be used for 1 Socket on a Physical Server and 1 Virtual Machine.
   
   Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines” may not be used as a Virtualization Host. Virtualization Host capability is provided pursuant to the Subscriptions for 1-2 Sockets with Unlimited Virtual Machine defined below for high-density Virtualization Environments.
2. Up to 1 Virtual Machine in a Virtualization Environment can be deployed with one “1 Virtual Machine” Subscription Offering.
   
   Subscription Offerings for “1 Virtual Machine” are not eligible BYOS and cannot be transferred to SUSE Cloud Products. Subscription Offerings for “1 Virtual Machine” cannot be used for the deployment of SAP workloads or for Sub-Capacity for ppc64le Power server deployments, as defined below.

High-Density Virtualization Deployments

For high-density Virtualized Deployments a Subscription Offering for “1-2 Sockets with Unlimited Virtual Machines” is available. This Subscription Offering entitles You to deploy an unlimited number of Virtual Machines per 1-2 Sockets on a Virtualization Host. For Virtualization Hosts with more than 2 Sockets, Subscription Offerings are Stackable to match or exceed the number of Sockets. This Subscription Offering can be used on any third- party Virtualization Host and also includes the entitlement to run SUSE Linux Enterprise for x86-64 Xen or KVM as the Virtualization Host.

Subscription Offerings for “1-2 Sockets with Unlimited Virtual Machines” may be deployed either (1) on an any Virtualization Host or (2) with any Cloud Services provider which is authorized by SUSE (Bring Your Own Subscription or “BYOS”), in each case only as 1 or 2 Virtual Machines and not with unlimited Virtual Machines. Subscription offerings for 1-2 Sockets with Unlimited Virtual Machines must be acquired for each Virtualization Host capable of deploying RGS Products within a Virtualization Environment.

SUSE Linux Enterprise Server for SAP with Unlimited Virtual Machines Subscription Offering allows you to run SUSE Linux Enterprise Server for SAP, SUSE Linux Enterprise Server, SUSE Linux Enterprise Server with SUSE Linux Enterprise High Availability Extension or SUSE Linux Micro as the host OS or use a third party VM host. It also allows you to use any combination of SUSE Linux Enterprise Server for SAP, SUSE Linux Enterprise Server, SUSE Linux Enterprise Server together with SUSE Linux Enterprise High Availability Extension or SUSE Linux Micro as guest VM.

SUSE Linux Enterprise Server with Unlimited Virtual Machines Subscription Offering allows you to run SUSE Linux Enterprise Server or SUSE Linux Micro as the host OS or use a third party VM host. It also allows you to use any combination of SUSE Linux Enterprise Server or SUSE Linux Micro as guest VM.

SUSE Linux Enterprise Server for x86-64 and Power and for SUSE Linux Enterprise Server for SAP Applications for x86-64 and Power

Starting July 1st 2021, the x86-64 and Power Subscription Offerings for SUSE Linux Enterprise Server for SAP Applications with Live Patching, 1-2 Sockets with Unlimited Virtual Machines and SUSE Linux Enterprise Server with Live Patching, 1-2 Sockets with Unlimited Virtual Machines will respectively replace the existing Subscription Offerings for SUSE Linux Enterprise Server for SAP Applications, 1-2 Sockets with Unlimited Virtual Machines and SUSE Linux Enterprise Server, 1-2 Sockets with Unlimited Virtual Machines. This has no effect on Subscription Offerings for these products acquired before this date.

Both Standard and Priority Subscription Offerings for SUSE Linux Enterprise Server for SAP Applications with Live Patching, 1-2 Sockets with Unlimited Virtual Machines and SUSE Linux Enterprise Server with Live Patching, 1-2 Sockets with Unlimited Virtual Machines will include SUSE Linux Enterprise Live Patching. SUSE Linux Enterprise Live Patching must be purchased separately for SUSE Linux Enterprise Server and SUSE Linux Enterprise Server for SAP Applications Subscription Offerings for 1-2 Sockets or 1-2 Virtual Machines.

z Systems (“s390x”)

For a Physical Server with IBM z Systems Processors (s390x), the number of required Subscription Offerings for Your environment must match or exceed the number of Integrated Facility for Linux (IFLs) on which SUSE Linux Enterprise Server is deployed, installed, used or executed. You can use an unlimited number of SUSE Linux Enterprise Server Instances per IFL. Subscription Offerings are available for EC (Enterprise Class), BC (Business Class) type IBM z Systems models, and IBM LinuxONE type systems. The Unit of Measure for these Subscription Offerings is per IFL. If a single IFL on a specific Physical Server is used as an IFLe, then only IFLe use is permitted on that specific Physical Server. SUSE Linux Enterprise High Availability Extension (SLE HA) Subscription Offerings are included in SUSE Linux Enterprise Server for z Systems Subscription Offering.

Subscription Offerings for “LinuxOne” can only be deployed on a “LinuxOne” system and may not be used for deployment on any other system, including without limitation, deployment on EC (Enterprise Class), BC (Business Class) type IBM z Systems models.

Sub-Capacity for ppc64le Power servers

Physical Servers with PowerVM virtualization provide a hardware platform designed for workload consolidation with high scalability (192 cores + 64 TB memory) of servers combined with efficient virtualized resource management. SUSE Subscription Offerings for Power servers may be purchased for a subset of the Sockets on the Physical Server. This is known as Sub-Capacity pricing.

Sub-Capacity pricing is available for RGS Subscription Offerings running on Power servers with four or more physical Sockets and PowerVM virtualization. Sub-capacity pricing can be used for all SUSE Subscription Offerings that are based on a 1-2 Socket charge metric including but not limited to SUSE Linux Enterprise Server for Power, SUSE Linux Enterprise Server for SAP Applications for Power, SUSE Linux Enterprise High Availability Extension for Power, SUSE Linux Enterprise Live Patching, SUSE Multi-Linux Manager, and SUSE Multi-Linux Manager Lifecycle Management.

For example, if a Power 980 server with 16 Sockets of total capacity is configured to only provide 8 Sockets of Processor capacity to SUSE Linux Enterprise Server for Power, then You only have to purchase four 1-2 Socket Subscription Offerings for SUSE Linux Enterprise Server for Power. This is useful for customers that consolidate multiple SUSE and non-SUSE workloads on a single Physical Server.

Prerequisites for Sub-Capacity pricing on Power servers include:

• Must be server based on POWER8 or later generation Processors
• The Physical Server must have four or more physical Sockets
• PowerVM virtualization must be used to limit that amount of Processor capacity available to run the SUSE Subscription Offerings using PowerVM methodologies such as Dedicated processor partitions (Dedicated LPAR), Dynamic LPAR, Single or Multiple Shared Processor Pools

Note: Integrated Facility for Linux (IFL) on Power does not automatically limit RGS Subscription Offerings to only run on IFL Processors.

Calculating Socket Pair Equivalent for ppc64le Power servers: IBM PowerVM virtualization assigns Processor capacity to an LPAR/VM in 1/20th increments of a Processor Core. Since SUSE Subscription Offerings for IBM Power are sold by Socket Pairs, it is necessary to calculate the “Socket Pair Equivalent” of Processor capacity assigned to a SUSE Subscription Offering when using Sub-Capacity. IBM Power servers vary the number of physical Processor Cores per physical Socket from 8 to 12 Cores. Due to this variability, it is necessary to calculate the Socket Pair Equivalent for each individual Physical Server because the Cores/Socket can vary between Physical Servers.

To calculate the Socket Pair Equivalent, the number of whole Processor Cores available to run the RGS Subscription Offering are divided by the number of Cores for each physical Socket Pair in the Physical Server for which Subscription Offerings are being acquired.

For example, an eight Socket Power Physical Server with ten Cores per physical Socket and 40 Processor Cores assigned to SUSE Linux for SAP Applications for Power, the calculation is 40 Cores divided by 20 Cores (the Cores per Socket Pair on this Physical Server) = 2 Socket Pair Equivalent. You would need to purchase two SUSE Linux Enterprise Server for SAP Applications on Power Subscription Offerings. You must calculate the Socket Pair Equivalent calculation for each RGS Subscription Offering running on that Physical Server.

When calculating the Socket Pair Equivalent, any fractional Cores or fractional Socket Pairs must be rounded up to the next highest integer. For example, if the number of Cores of capacity available to the RGS Subscription Offering was “40.4”, you would round the number of Cores to “41”. Similarly, if the number of Sockets in the Socket Pair Equivalent is “2.1”, the Socket Pair Equivalent is rounded up to “3”.

Should You increase the Processor capacity you must correspondingly increase the number of RGS Subscription Offerings. Note that changes to Processor pools or LPAR/VM configuration may require the acquisition of additional SUSE Subscription Offerings.

Subscription Offerings for “1 Virtual Machine” are not eligible for Sub-Capacity for ppc64le Power server deployments.

Arm AArch64 Processors (“AArch64”), Subscription Offerings for 1-2 Sockets or 1-2 Virtual Machines

These Subscription Offerings are intended for flexible deployments on Physical Servers and low-density or cloud virtualization.

The number of Subscription Offerings needed for a Physical Server is determined by the number of Cores or Sockets in the Physical Server.

For Physical Servers with 16 or more Cores, the Subscription Offering is based on 1-2 Sockets. For example, a Physical Arm server with 16 Cores would require a single 1-2 Socket Subscription Offering.

For Physical Servers with more than 2 Sockets, Subscription Offerings are Stackable to match or exceed the number of Sockets. For example, a Physical Server with 4 Sockets needs 2 Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines.” The maximum number of Cores per Socket Pair is limited to 144. One Subscription Offering cannot be used to entitle more than one Physical Server.

Each Physical Server on which SUSE Linux Enterprise Server is deployed, installed, used or executed must have a Subscription. Subscription Offerings can be transferred to new and/or different Physical Servers. For example, when 10 Physical Servers with 2 Sockets each are replaced by 4 Physical Servers with 4 Sockets each, the 10 “1-2 Sockets or 1-2 Virtual Machines” Subscription Offerings can be transferred to the new Physical Servers. In this example, a total of 8 Subscription Offerings (2 per Physical Server with 4 Sockets) are transferred to the new Physical Servers. You can use the remaining 2 Subscription Offerings for later deployments.

Up to 2 Virtual Machines running on the same Virtualization Host or Virtualization Environment or within the same Private Cloud account or Public Cloud zone can be deployed with one “1-2 Sockets or 1-2 Virtual Machines” Subscription Offering.

Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines” can also be repurposed as Virtual Machines on any Virtualization Host or with any SUSE certified Cloud Services Provider (CSP).

At any point in time, a Subscription Offering for “1-2 Sockets or 1-2 Virtual Machines” can only be deployed either on a Physical Server or as Virtual Machines. For clarity, a Subscription Offering for “1-2 Sockets or 1-2 Virtual Machines” cannot be used for 1 Socket on a Physical Server and 1 Virtual Machine.

Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines” may not be used as a Virtualization Host. Virtualization Host capability is provided pursuant to the Subscriptions for 1-2 Sockets with Unlimited Virtual Machine defined below.

Arm AArch64 Processors (“AArch64), Subscription Offerings for 1-2 Sockets with Unlimited Virtual Machines

For a Physical Server with 64-bit Arm AArch64 Processors, “Unlimited Virtual” Subscription Offerings are available for Virtualized Deployments of SUSE Linux Enterprise Server for use as Virtual Guest and/or Virtualization Host.

For Physical Servers with 16 or more Cores, the Unlimited Virtual Machine Subscription Offering is based on 1-2 Sockets. For example, an Arm Physical Server with 16 Cores would require a single 1-2 Socket Unlimited Virtual Machine Subscription Offering.

This Subscription Offering entitles You to deploy an unlimited number of Virtual Machines per Subscription Offering on a Virtualization Host. For Virtualization Hosts with more than 2 Sockets, Subscription Offerings are Stackable to match or exceed the number of Sockets. This Subscription Offering can be used on any third-party Virtualization Host and also includes the entitlement to run SUSE Linux Enterprise Xen or KVM as the Virtualization Host One Subscription Offering cannot be used to entitle more than one Physical Server.

Each Physical Server on which SUSE Linux Enterprise Server is deployed, installed, used or executed must have a Subscription.

Arm AArch64 Processors (“AArch64”), 1-2 Virtual Machines per 4 Cores

For Physical Servers with less than 16 physical Arm Cores, the Subscription Offerings are based on groups of 4 Cores. These Subscription Offerings are stackable up to a total of 15 Cores per Physical Server. For example, an Arm Physical Server such as a Raspberry Pi with a total of 4 Cores would need a single, 4-Core group Subscription Offering. An Arm Physical Server with 12 Cores would require three 4-Core group Subscription Offerings. An Arm Physical Server with 15 Cores would require four 4-Core group Subscription Offerings.

For a Physical Server with 64-bit Arm AArch64 Processors, the number of required Subscription Offerings must match or exceed the number of Cores in the Physical Server divided by four (4) and if necessary rounded to the next integer. Subscription Offerings are available for each group of 4 Cores. One Subscription Offering cannot be used to entitle more than one Physical Server.

Each Physical Server on which SUSE Linux Enterprise Server is deployed, installed, used or executed must have a Subscription.

Virtualized Deployment of SUSE Linux Enterprise Server is not permitted with these Subscription Offerings (see “Virtualized Deployment” below).

Arm AArch64 Processors (“AArch64”), Unlimited Virtual Machines per 4 Cores

For a Physical Server with 64-bit Arm AArch64 Processors, “Unlimited Virtual Machines” Subscription Offerings are available for Virtualized Deployments of SUSE Linux Enterprise Server for use as Virtual Guest and/or Virtualization Host.

For Arm Physical Servers with less than 16 Cores, the Subscription Offerings are based on groups of 4 Cores. These Subscription Offerings are stackable up to a total of 15 Cores per Physical Server. For example, an Arm Physical Server with a total of 4 Cores would need a single, 4-Core group Unlimited Virtual Machine Subscription Offering. An Arm Physical Server with 12 Cores would require three 4-Core group Unlimited Virtual Machine Subscription Offerings.

This Subscription Offering entitles You to deploy an unlimited number of Virtual Machines per 4 Cores on a Virtualization Host. For Virtualization Hosts with more than 4 Cores, Subscription Offerings are Stackable to match or exceed the number of Cores. This Subscription Offering can be used on any third-party Virtualization Host and also includes the entitlement to run SUSE Linux Enterprise Xen or KVM as the Virtualization Host

The number of required “Unlimited Virtual Machines” Subscription Offerings for Your Physical Server must match or exceed the number of Cores in the Physical Server divided by four (4) and if necessary rounded to the next integer for each Core on which SUSE Linux Enterprise Server is deployed, installed, used or executed.

Each Physical Server on which SUSE Linux Enterprise Server is deployed, installed, used or executed must have a Subscription Offering.

SUSE Linux Enterprise Server with Expanded Support Subscription Offerings and Units of Measure

When You acquire SUSE Linux Enterprise Server with Expanded Support, You are actually acquiring a Subscription Offering for SUSE Linux Enterprise Server, but with the added entitlement for Expanded Support. As such, the Units of Measure for SUSE Linux Enterprise Server with Expanded Support are the same as for the corresponding SUSE Linux Enterprise Server Subscription Offering (e.g. with Unlimited Virtual Machines).

SUSE Multi-Linux Support (formerly SUSE Liberty Linux) Subscription Offerings and Units of Measure

Except for Promotional Subscriptions that are subject to Promotional Conditions, when You acquire a Subscription Offering for SUSE Multi-Linux Support, it includes an entitlement to SUSE Linux Enterprise Server. The Units of Measure for SUSE Multi-Linux Support are the same as for the corresponding SUSE Linux Enterprise Server Subscription Offering (e.g. with Unlimited Virtual Machines). However, if You use Your Subscription Offering in respect of a SUSE Multi-Linux Support deployment, You cannot, contemporaneously, use that same Subscription Offering for SUSE Linux Enterprise Server. You may use a Subscription Offering for SUSE Multi-Linux Support for a deployment of SUSE Linux Enterprise Server, only if: (i) that deployment of SUSE Linux Enterprise Server was formerly a deployment non-SUSE Linux distribution; or (ii) You have otherwise ceased using that Subscription Offering in relation to a deployment of a non-SUSE Linux distribution.

For CentOS deployments, Subscription Offerings may be used only for specific hardware and/or software versions of CentOS as specified: (a) in an Order Form; or (b) on https://ranchergovernment.com/ at the time an Order Form is entered into (such conditions or restrictions being “Promotional CentOS Conditions”). If Your Subscription Offering includes Promotional CentOS Conditions, You may use that Subscription Offering only in accordance with the Promotional CentOS Conditions.

Appendix B – SUSE Linux Enterprise Extensions

SUSE Linux Enterprise High Availability Extension

SUSE Linux Enterprise High Availability Extension is a RGS Product based on open-source technology to implement highly available Linux clusters. It is supported on all Physical and Virtual Deployments where SUSE Linux Enterprise Server (x86, x86-64, ppc64, s390x) is supported.

Unit of Measure is the same as the Unit of Measure for SUSE Linux Enterprise Server Subscription Offerings for x86, AMD64 & Intel64, and POWER (see Appendix A).

Organizations with a Current SUSE Linux Enterprise Server Subscription Offering z Systems (s390x) are entitled to receive Subscription Offering benefits for SUSE Linux Enterprise High Availability Extension for the respective Hardware Architecture. Organizations with a SUSE Linux Enterprise Server Subscription Offering for POWER (ppc64) purchased before April 1st 2016, are entitled to receive Subscription Offering benefits for SUSE Linux Enterprise High Availability Extension.

SUSE Linux Enterprise High Availability Extension Subscription Offering benefits are determined by and inherited from the underlying SUSE Linux Enterprise Server Subscription Offering benefits.

Geo Clustering for SUSE Linux Enterprise High Availability Extension

To receive Subscription Offering benefits for Geographically Clustered Linux Servers, separate Geo Clustering for SUSE Linux Enterprise High Availability Extension Subscription Offerings are required, in addition to Current SUSE Linux Enterprise Server and SUSE Linux Enterprise High Availability Extension Subscription Offerings.

Unit of Measure for Geo SLE HA is the same as the Unit of Measure for SUSE Linux Enterprise Server for x86, AMD64 & Intel64 (x86 / x86-64), and z Systems (s390x) Subscription Offerings in Appendix A. Subscription Offering benefits for Geo Clustering for SUSE Linux Enterprise High Availability Extension are determined by and inherited from the Subscription Offering benefit of the underlying SUSE Linux Enterprise Server Subscription Offerings.

SUSE Linux Enterprise Server Real Time Extension

To receive Subscription Offering benefits for SUSE Linux Enterprise Server Real Time Extension (“SLE RT”), a separate SLE RT Extension Subscription Offering is required in addition to a Current SUSE Linux Enterprise Server Subscription Offering (see Appendix A) either for Physical Deployment or Unlimited Virtual Machines.

Unit of Measure for SLE RT is per Physical Server. Subscription Offering benefits for SLE RT are determined by and inherited from the underlying SUSE Linux Enterprise Server Subscription Offering.

SUSE Linux Enterprise Virtual Machine Driver Pack Extension

To receive Subscription Offering benefits for SUSE Linux Enterprise Virtual Machine Driver Pack Extension (“SLE VMDP”), a Current SUSE Linux Enterprise Server Subscription Offering is required (see Appendix A). Purchasing SLE VMDP Subscription Offerings without a Current SUSE Linux Enterprise Server Subscription Offering does not entitle You to receive Subscription Offering benefits for SLE VMDP.

Unit of Measure for SLE VMDP is either 1 to 4 Virtual Instances per Physical Server or unlimited number of Virtual Instances per Physical Server. Subscription Offering benefits for SLE VMDP are determined by the Subscription Offering benefit of the underlying SUSE Linux Enterprise Server Subscription Offering.

SUSE Linux Enterprise Workstation Extension Units of Measure

Units of Measure do not differentiate between single core or multi-core, or simultaneous multi-threading capable Processors. SUSE Linux Enterprise Workstation Extension (“SLE WE”) requires one Current SLES Subscription Offering per Physical Server in addition to the respective SLE WE Instances.

SUSE Linux Enterprise Workstation Extension for Intel or AMD Processors (“x86-64”), Physical Deployment

For Physical Servers with 64-bit Processors, the number of Subscription Offerings must match or exceed the number of Physical Servers or Devices, where SLE WE is deployed, installed, used or executed. Subscription Offering benefits for SLE WE are determined by and inherited from the Subscription Offering benefits of the underlying SUSE Linux Enterprise Server Subscription Offering. Virtualized Deployment of SUSE Linux Enterprise Workstation Extension is not permitted with this Subscription Offering. (See Virtualized Deployment below.) One Subscription Offering cannot be used to entitle more than one Physical Server.

SUSE Linux Enterprise Workstation Extension for Intel or AMD Processors (“x86-64”), Virtualized Deployment

For Physical Servers with 64-bit Processors, the number of Subscription Offerings must match or exceed the number of Instances of SUSE Linux Enterprise Workstation Extension for use as Virtual Instance. You can use an unlimited number of SUSE Linux Enterprise Workstation Instances per Physical Server. One Subscription Offering cannot be used to entitle more than one Virtual Instance. Each Virtual Instance on a Virtualization Host on which SUSE Linux Enterprise Workstation Extension is deployed, installed, used or executed must have a Subscription Offering. Subscription Offering benefits for SLE WE are determined by and inherited from the Subscription Offering benefits of the underlying SUSE Linux Enterprise Server Subscription Offering.

SUSE Linux Enterprise High Availability Extension with Expanded Support

When You acquire SUSE Linux Enterprise High Availability Extension with Expanded Support, You are actually acquiring a Subscription Offering for SUSE Linux Enterprise High Availability Extension, but with the added entitlement for Expanded Support. As such, the Units of Measure for SUSE Linux Enterprise High Availability Extension with Expanded Support are the same as for the corresponding SUSE Linux Enterprise High Availability Subscription Offering.

SUSE Multi-Linux Support (formerly SUSE Liberty Linux) High Availability Extension

When You acquire SUSE Multi-Linux Support High Availability Extension, You are actually acquiring a Subscription Offering for SUSE Linux Enterprise High Availability Extension, but with the added entitlement for SUSE Multi-Linux Support. As such, the Units of Measure for SUSE Multi-Linux Support High Availability Extension are the same as for the corresponding SUSE Linux Enterprise High Availability Subscription Offering.

SUSE Linux Enterprise Live Patching

SUSE Linux Enterprise Live Patching is a RGS Product based on open source technology to implement code updates during operation of the system. It is supported on all Physical and Virtual Deployments starting with SUSE Linux Enterprise Server 12 on x86-64 and POWER (ppc64le) and IBM z Systems (s390x).

Unit of Measure for SUSE Linux Enterprise Live Patching is the same as SUSE Linux Enterprise Server Subscription Offerings for x86-64 and POWER (ppc64le), and IBM z Systems (s390x) respectively (see Appendix A).

SUSE Linux Enterprise Live Patching Subscription Offering requires an underlying Current SUSE Linux Enterprise Server Priority Subscription Offering (except for SUSE Linux Enterprise Server x86-64 and Power and SUSE Linux Enterprise Server for SAP x86-64 and Power as described below). Subscription Offering benefits are available for the kernel versions listed on https://www.suse.com/products/live-patching/. The list is subject to change at RGS’s discretion and your entitlement to receive Subscription Offering benefits may be conditioned on Your deployment of a current version from this list.

The x86-64 and Power Subscription Offerings for SUSE Linux Enterprise Server for SAP Applications with Live Patching, 1-2 Sockets with Unlimited Virtual Machines and SUSE Linux Enterprise Server with Live Patching, 1-2 Sockets with Unlimited Virtual Machines will respectively replace the existing Subscription Offerings for SUSE Linux Enterprise Server for SAP Applications, 1-2 Sockets with Unlimited Virtual Machines and SUSE Linux Enterprise Server, 1-2 Sockets with Unlimited Virtual Machines. This has no effect on Subscription Offerings for these products acquired before this date.

Both Standard and Priority Subscription Offerings for SUSE Linux Enterprise Server for SAP Applications with Live Patching, 1-2 Sockets with Unlimited Virtual Machines and SUSE Linux Enterprise Server with Live Patching, 1-2 Sockets with Unlimited Virtual Machines will include SUSE Linux Enterprise Live Patching.

SUSE Linux Enterprise Live Patching must be purchased separately for SUSE Linux Enterprise Server and SUSE Linux Enterprise Server for SAP Applications Subscription Offerings for 1-2 Sockets or 1-2 Virtual Machines. SUSE Linux Enterprise Live Patching must be purchased separately for server Subscription Offerings for IBM z Systems.

Appendix C – SUSE Linux Enterprise Point of Service

SUSE Linux Enterprise Point of Service (“SLE POS”) Subscription Offerings and Units of Measure

Subscription Offerings for SUSE Linux Enterprise Point of Service (SLE POS) include access to SUSE Linux Enterprise Server and maintenance updates. Subscription Offering benefits are limited to the use of those components in a SLE POS solution as outlined below. In order for any individual Device to be eligible for Subscription Offering benefits, all Physical Servers, Instances, and Client Devices used as part of a SLE POS solution must have a Current Subscription Offering.

SLE POS Client

All point of service Client Devices that are running a SUSE Linux Enterprise operating system, either deployed by the SUSE Multi-Linux Manager for Retail solution or otherwise installed or deployed, must have a “SUSE Linux Enterprise Point of Service Client” Subscription Offering.

Client Devices are entitled to be used for running typical point of service applications or for supporting client applications (for example, a web browser). If the point of service application needs certain SUSE Linux Enterprise Server services to run, for example a local database, this is also covered by the SLE POS Client Subscription Offering.

Point of service Devices that are used as a combined point of service terminal and as a branch server, or point of service hardware used in any other server role, must have at least a SUSE Multi-Linux Manager for Retail Branch Server Subscription Offering.

SLE POS Client Subscription Offerings must not be employed for any general purpose desktop or server use.

SLE POS Hardware Architectures

SLE POS Client operating systems may only be built for the x86 Hardware Architecture.

SLE POS Virtualization

Provided that the restrictions mentioned above are complied with and all Instances belong to the same Point of Service solution, more than one virtual SUSE Linux Enterprise Point of Service Instance may be run on a single Physical Server that has a Current SUSE Multi-Linux Manager Branch Server Subscription Offering. For example, an operating system build server may be run as a Virtual Instance on the SUSE Multi-Linux Manager Branch Server or it can be run as a Virtual Instance on a combined point of service and SUSE Multi-Linux Manager Branch Server Device. SLE POS Subscription Offerings must not be used as general purpose servers or Client Device virtualization.

Appendix D – SUSE Multi-Linux Manager

SUSE Multi-Linux Manager (formerly SUSE Manager) Lifecycle Management+ Subscription Offerings

SUSE Multi-Linux Manager (formerly SUSE Manager) Subscription Offerings and Units of Measure

SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offering is an infrastructure management offering for SUSE Linux Enterprise Server, SUSE Linux (Enterprise) Micro and other selected non-SUSE operating systems and consists of entitlements for the SUSE Multi-Linux Manager Server and SUSE Multi-Linux Manager Proxy. SUSE Multi-Linux Manager Server and SUSE Multi-Linux Manager Proxy, along with their support entitlement will now be included with the new SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offerings subject to the terms below when the requirement of a minimum of 10 Subscription Offerings is met or a SUSE Multi-Linux Manager Lifecycle Management+ Starter Pack (10) Subscription Offering is purchased.

SUSE Multi-Linux Manager Server is available for installation on a Physical Server or as a Virtual Instance.

A quantity of 1 Current SUSE Multi-Linux Manager Lifecycle Management+, 1-2 Sockets Unlimited Virtual Machines Subscription Offerings, or 10 Current SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offerings, 1-2 Sockets or 1-2 Virtual Machines is required to receive support.

In order to fulfill this requirement, You can purchase a SUSE Multi-Linux Manager Lifecycle Management+ Starter Pack (10) Subscription Offering for 1-2 Sockets or 1-2 Virtual Machines. Optionally, You may purchase a minimum of 10 single SUSE Multi-Linux Manager Lifecycle Management+, 1-2 Sockets or 1-2 Virtual Machines, or 1 SUSE Multi-Linux Manager Lifecycle Management+, 1-2 Sockets Unlimited Virtual Machines Subscription Offering.

Promotional Conditions can override this minimum subscription requirement.

Each Managed Instance requires a SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offering.

Each SUSE Multi-Linux Manager Proxy is considered to be a Managed Instance and requires a SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offering. No additional workloads may be deployed on the Instance that is running SUSE Multi-Linux Manager Server or SUSE Multi-Linux Manager Proxy, but monitoring functionality can be added for each Managed Instance or the SUSE Multi-Linux Manager Server with a SUSE Multi-Linux Manager Monitoring Subscription Offering.

SUSE Multi-Linux Manager (formerly SUSE Manager) for Retail

At least one Retail Branch Server Subscription Offering is required for a deployment of SUSE Multi-Linux Manager for Retail Server. Managed Instances connected to the SUSE Multi-Linux Manager Server via the SUSE Multi-Linux Manager for Retail Branch Server or the SUSE Multi-Linux Manager for Retail Branch Server All-in-one, including the branch server and the point of service related workloads running on the branch server, do not require the SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offering. Every Subscription Offering for a deployment of SUSE Multi-Linux Manager for Retail Branch Server or SUSE Multi-Linux Manager for Retail Branch Server All-in-one includes a free Subscription Offering for SUSE Linux Micro. No additional workloads may be deployed on the same Physical Server or Virtual Instance, except: (a) workloads that are solely used to serve data and applications to Point of Service client devices, which can be deployed on the same Physical Server; and (b) monitoring functionality, which can be added to SUSE Multi-Linux Manager for Retail Branch Server with a SUSE Multi-Linux Manager Monitoring Subscription Offering and that is also contained in the SUSE Multi-Linux Manager for Retail Branch Server All-in-one Subscription Offering.

Each Managed Instance connected directly to the SUSE Multi-Linux Manager Server requires a SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offering.

You may only deploy POS Client Device Managed Instances running SLE POS or SUSE Linux (Enterprise) Micro with current Subscription Offerings in your SUSE Multi-Linux Manager for Retail environment.

SUSE Multi-Linux Manager (formerly SUSE Manager) Server

SUSE Multi-Linux Manager Server is available for installation on a Physical Server with SUSE Multi-Linux Manager Serveror SUSE Multi-Linux Manager Proxy. Every Subscription Offering for a deployment of SUSE Multi-Linux Manager Server includes a free Subscription Offering for SUSE Linux Micro. You may not run any workloads besides SUSE Multi-Linux Manager Server on these instances of SUSE Linux Micro. Monitoring functionality can be added to SUSE Linux Micro with a SUSE Multi-Linux Manager Monitoring Subscription Offering.

No additional workloads are permitted to be deployed on the same Instance that is running the SUSE Multi-Linux Manager Server. Monitoring functionality can be added to SUSE Multi-Linux Manager Server with a SUSE Multi-Linux Manager Monitoring Subscription Offering.

The SUSE Multi-Linux Manager Server can be used with an unlimited number of Sockets per Physical Server or per Virtual Machine.

SUSE Multi-Linux Manager (formerly SUSE Manager) Proxy

SUSE Multi-Linux Manager Proxy is available for installation on a Physical Server or Virtual Instance or as a Container. Regardless of the deployment option chosen, the minimum of ten SUSE Multi-Linux Manager Lifecycle Management+ Subscriptions Offerings has to be met to receive support. The SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offering can only be used with SUSE Multi-Linux Manager Server or SUSE Multi-Linux Manager Proxy. Every Subscription Offering for a deployment of SUSE Multi-Linux Manager Proxy includes a free Subscription Offering for SUSE Linux Micro. You may not run any workloads besides SUSE Multi-Linux Manager Proxy on these instances of SUSE Linux Micro. Monitoring functionality can be added to SUSE Linux Micro with a SUSE Multi-Linux Manager Monitoring Subscription Offering.

Every installation of SUSE Multi-Linux Manager Proxy comes with a free subscription to SUSE Linux Micro to run on. You may not run any workloads besides SUSE Multi-Linux Manager Proxy on these instances of SUSE Linux Micro, but monitoring functionality can be added for SUSE Multi-Linux Manager Proxy with a SUSE Multi-Linux Manager Monitoring Subscription Offering. Unless used in the SUSE Multi-Linux Manager for Retail environment, each SUSE Multi-Linux Manager Proxy is considered a Managed Instance and requires a SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offering.

When deployed as part of the SUSE Multi-Linux Manager for Retail environment, each Instance of SUSE Multi-Linux Manager Proxy requires a SUSE Multi-Linux Manager for Retail Branch Server Subscription Offering or a SUSE Multi-Linux Manager for Retail Branch Server All-in-one Subscription Offering. The SUSE Multi-Linux Manager for Retail Branch Server Subscription Offering and the SUSE Multi-Linux Manager for Retail Branch Server All-in-one Subscription Offering can only be used when the SUSE Multi-Linux Manager Proxy is deployed as part of the SUSE Multi-Linux Manager for Retail architecture, in a typical point of service environments. No additional workloads may be deployed on the same Physical Server or Virtual Instance. However, where SUSE Multi-Linux Manager Proxy is deployed with the SUSE Multi-Linux Manager for Retail Branch Server Subscription Offering, workloads that are solely used to serve data and applications to Point of Service client devices can be deployed on the same Physical Server.

RGS only provides support for SUSE Multi-Linux Manager Proxy when deployed with SUSE Multi-Linux Manager.

SUSE Multi-Linux Manager (formerly SUSE Manager)High Availability Servers

SUSE Multi-Linux Manager Server and SUSE Multi-Linux Manager Proxy can be set up as a cluster of 2 Instances using the SUSE Linux Enterprise High Availability Extension. Terms and conditions are available on request.

Rules for Applying Subscription Offerings to Managed Instances

Physical Servers (except Arm AArch64)

SUSE Multi-Linux Manager Lifecycle Management+, SUSE Multi-Linux Manager Virtualization Management and SUSE Multi-Linux Manager Monitoring Subscription Offerings need to be applied on Physical Servers based on the number of Sockets per Physical Server. Subscription Offerings for 1 to 2 Sockets can be aggregated to provide Current Subscription Offerings for Physical Servers with more than 2 Sockets. For example, a 6 Socket Physical Server must have 3 “SUSE Multi-Linux Manager Lifecycle Management+ up to 2 Sockets or 2 Virtual Machines” Subscription Offerings.

SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offerings for the Managed Instances are not required with the purchase of SUSE Multi-Linux Manager for Retail Branch Server Subscription Offerings or SUSE Multi-Linux Manager for Retail Branch Server All-in-One Subscription Offerings.

SUSE Multi-Linux Manager Lifecycle Management+ Subscription Offerings for the Managed Instances in a branch, are not required when the SUSE Multi-Linux Manager for Retail Branch Server or the SUSE Multi-Linux Manager for Retail Branch Server All-in-One Subscription Offerings have been rightfully acquired for that branch.

Physical Servers based on Arm AArch64 processors.

Subscription Offerings for SUSE Multi-Linux Manager Lifecycle Management for Arm need to be applied on Physical Servers based on the number of Sockets per Physical Server.

For Physical Servers with 16 or more Cores, the SUSE Multi-Linux Manager Lifecycle Management+ for Arm Subscription Offering is based on 1-2 Sockets. For example, an Arm Physical Server with 16 Cores would require a single 1-2 Socket Unlimited Virtual Machine Subscription Offering.

Virtual Instances

SUSE Multi-Linux Manager Lifecycle Management+, SUSE Multi-Linux Manager Lifecycle Management+ Starter Pack (10), and SUSE Multi-Linux Manager Monitoring each have two Subscription Offering options for Virtual Instances: You may choose a Subscription Offering either per 2 Virtual Instances or Unlimited Virtual Machines per Physical Server (as per preceding paragraph).

Per 2 Virtual Instances

The “SUSE Multi-Linux Manager Lifecycle Management+ up to 2 Sockets or 2 Virtual Instances” Subscription Offerings and “SUSE Multi-Linux Manager Monitoring up to 2 Sockets or 2 Virtual Machines” Subscription Offerings can be used to entitle 1 to 2 Virtual Machines.

Unlimited Virtual Machines

SUSE Multi-Linux Manager Lifecycle Management+ 1-2 Sockets with Unlimited Virtual Machines Subscription Offering include lifecycle management of the Virtualization Hosts and all Virtual Guest Operating Systems. SUSE Multi-Linux Manager Monitoring 1-2 Sockets with Unlimited Virtual Machines Subscription Offering include monitoring of the Virtualization Hosts and all Virtual Guest Operating Systems.

Cloud Deployments for SUSE Multi-Linux Manager Lifecycle Management+ and SUSE Multi-Linux Manager Monitoring

Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines” allows You to manage 1 Virtual Machine on any SUSE certified Cloud Services Provider authorized by SUSE (Bring Your Own Subscription or “BYOS”).

Subscription Offerings for “1-2 Sockets with Unlimited Virtual Machines” allows You to manage 3 Virtual Machines on any certified Cloud Services Provider authorized by SUSE (Bring Your Own Subscription or “BYOS”).

Appendix E – SUSE Linux Enterprise Desktop

Operating Environments and Units of Measure for SUSE Linux Enterprise Desktop

Units of Measure do not differentiate between single core or multi-core or simultaneous multi-threading capable Processors.

SUSE Linux Enterprise Desktop for Intel or AMD Processors (“x86” or “x86-64”), Physical Deployment

For a Device with 32-bit or 64-bit Processors, the number of required Subscription Offerings must match or exceed the number of Devices, where SUSE Linux Enterprise Desktop is deployed, installed, used or executed. The Subscription Offering must be either Basic or a mix of Standard or Priority. Virtualized Deployment of SUSE Linux Enterprise Desktop is not permitted with this Subscription Offering. One Subscription Offering cannot be used to entitle more than one Device.

Appendix F – RGS Edge Suite

RGS Edge Suite Offering, Operating Environment and Unit of Measure

The Unit of Measure for the RGS Edge Suite Subscription Offering is per socket. Each Edge Cluster may contain up to 1 socket, up to 32 cores. Each Edge socket must have an associated RGS Edge Suite Subscription Offering.

For edge deployments with more than 1 Sockets or more than 32 Cores, Subscription Offerings are Stackable to match or exceed the number of Sockets and/or Cores

Subscription Offerings for RGS Edge Suite are designed for use cases that move the data processing away from centralized processing in a Data Center or cloud environment over to Decentralized Computing at the data collecting device (edge). RGS Edge Suite Subscription Offerings must not be used in a Data Center or Public Cloud environment.

RGS Edge Suite Subscription Offering

Each RGS Edge Suite Subscription Offering includes support entitlements for RGS Suite (appendix J), SUSE Multi-Linux Manager and on up to 1 Sockets or 32 Cores in the same edge deployment.

The component entitlements that make up this Offering can only be used together in or to manage, Edge deployments that are part of the same RGS Edge Suite and may not be split across Physical Machines. Any use of any of the component entitlements included in a RGS Edge Suite Subscription Offering outside of this scope requires a separate and additional Subscription Offering for that component.

Appendix G – Long Term Service Pack Support

Long Term Service Pack Support Subscription Offerings and Units of Measure

Long Term Service Pack Support (“LTSS”) Subscription Offering extends the support period of a SLES (x86, x86-64, s390x, ppc64, ppc64le) Service Pack and/or SLES for SAP Applications (x86-64) Service Pack as defined at https://ranchergovernment.com/product-lifecycle-dates.

LTSS Subscription Offering is available as an additional offering for SLES (x86, x86-64, s390x, ppc64, ppc64le).

For SLES for SAP Application (x86-64, ppc64le), LTSS Subscription Offering is available to extend the Subscription Offering benefit period after expiration of Extended Service Pack Overlap Support (ESPOS).

SLES for High Performance Computing Long Term Service Pack Support (SLE HPC LTSS) (x86-64, AArch64) Subscription Offering is available to extend the Subscription Offering benefit period after expiration of Extended Service Pack Overlap Support (SLE HPC ESPOS), or to extend the SLE HPC Subscription Offering benefit period.

All LTSS Subscription Offerings require a matching and underlying (i) Current SUSE Linux Enterprise Server Subscription Offering or (ii) Current SLES for SAP Application (x86-64) Subscription Offering or (iii) SLE HPC (x86-64, Aarch64) Subscription Offering, as applicable. Your LTSS Subscription Offering must be registered at RGS Customer Center (RGSCC), and you may be required to install the latest LTSS updates.

LTSS “Extreme Core” for x86-64 architecture, SUSE Linux Enterprise 11, Service Pack 4

A Subscription Offering for Long Term Service Pack Support Extreme Core ("LTSS Extreme Core") is also available as an additional offering for deployments of SUSE Linux Enterprise 11, Service Pack 4 (“SLES 11 SP4”) on x86-64 architecture. This Subscription Offering specifically extends the support period of SLES 11 SP4 deployments on x86-64 architecture.

The following additional requirements apply to Subscription Offerings for LTSS Extreme Core:

• A Subscription Offering for LTSS Extreme Core entitles You to receive support solely for the following packages: Kernel, openSSL and gLibc. You may be required to install the latest 11-SP4 LTSS Updates as a condition of receiving support.
• LTSS Extreme Core Subscription Offerings may be used only for SLES11SP4 deployments (and for no other version), which are deployed on x86 &x86-64 architectures prior to the date of purchase of the Subscription Offering, and only for the hardware or Virtualization Environment on which those SLES11SP4 instances are deployed as at the date of purchase of the Subscription Offering. You may not use an LTSS Extreme Core Subscription Offering for any other version of SUSE Linux Enterprise Server, or for any Instance of SLES11SP4 that is deployed after, or is migrated to different hardware or Virtualization Environment after, the date of purchase of the Subscription Offering and SUSE will not support such subsequent Instances.
• Instances of SLES11SP4 deployed in a Public Cloud are not eligible for LTSS Extreme Core and will not be supported, with the exception of those covered by a current Subscription Offering that You acquire in accordance with SUSE’s “Bring Your Own Subscription” policy and section 6 above.

LTSS for SLES for z Systems (s390x)

LTSS for SLES for z Systems has the following Subscription Offerings:

• 1 IFL
• Unlimited IFLs

LTSS for SLES for POWER (ppc64) 1-2 Sockets with Inherited Virtualization per Code Stream

This Subscription Offering entitles You to any current LTSS version for ppc64. One LTSS Subscription Offering is required per 1 - 2 Sockets. For Physical Servers with more than 2 Sockets, Subscription Offerings are Stackable to match or exceed the number of Sockets. Virtualization is inherited from the underlying SLES Subscription Offering.

For example, a Physical Server with 4 Sockets needs 2 Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines”. As another example, running two Virtual Machines with different Code Streams on a SLES Virtualization Host with 2 Sockets requires:

• One SUSE Linux Enterprise Server Subscription Offerings for 1-2 Sockets with Unlimited Virtual Machines (for the Virtualization Host) and
• Two LTSS Subscription Offerings (one for each Code Stream)

SUSE Linux Enterprise for High Performance Computing Long Term Service Pack Support (“SLE HPC LTSS”) (x86-64, AArch64) 1-2 Sockets with Inherited Virtualization per Code Stream

This Subscription Offering entitles You to any Current LTSS version for SUSE Linux Enterprise for High Performance Computing x86-64, AArch64.

One SLE HPC LTSS Subscription Offering is required per 1 - 2 Sockets per Code Stream. For Physical Servers with more than 2 Sockets, Subscription Offerings are Stackable to match or exceed the number of Sockets. Virtualization is inherited from the underlying SLES Subscription Offering.

For example, a Physical Server with 4 Sockets needs 2 Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines”. As another example, running two Virtual Machines with different Code Streams on a SLES Virtualization Host with 2 Sockets requires:

• One SUSE Linux Enterprise for High Performance Computing Subscription Offerings for 1-2 Sockets or 1-2 Virtual Machine and
• Two SLE HPC LTSS Subscription Offerings (one for each Code Stream)

Extended Service Pack Overlap Support (SLE HPC ESPOS) for SUSE Linux Enterprise for High Performance Computing (SLES for HPC)

The SLE HPC ESPOS (x86-64, AArch64) extends the Subscription Offering benefit period for a particular SLE HPC (x86-64, AArch64) Service Pack. SLE HPC ESPOS entitles You to continue receiving SLE HPC ESPOS (x86-64, AArch64) Subscription Offering benefits under the same conditions as SLE HPC LTSS (per Code Stream and per Hardware Architecture) according the product lifecycle.

Extended Service Pack Overlap Support (ESPOS) for SLES for SAP Applications

The SLES for SAP Applications (x86-64, ppc64le) Subscription Offering includes ESPOS. ESPOS extends the Subscription Offering benefit period for a particular SLES for SAP Applications (x86-64, ppc64le) Service Pack. ESPOS entitles customers of SLES for SAP Applications (x86-64, ppc64le) to continue receiving Subscription Offering benefits under the same conditions as LTSS (i.e. per Code Stream and Hardware Architecture dependent) according to the product lifecycle.

SUSE Linux Enterprise Server Long Term Service Pack Support (LTSS), 1-2 Sockets or 1-2 Virtual Machines per Code Stream

Subscription Offerings with this metric entitle You to deploy any currently supported SUSE Linux Enterprise Server LTSS version, on a hardware architecture that is specified in the relevant Subscription Offering, and can be used for either Physical Servers or Virtual Machines. For Physical Servers, one Subscription Offering is required for each Physical Server with 1-2 Sockets. For Physical Servers with more than 2 sockets, Subscription Offerings must be stacked to match or exceed the number of populated sockets. For Virtualization Environments, up to 2 Virtual Machines running the same Service Pack can be deployed with one Subscription Offering. This Subscription Offering is not eligible for BYOS.

Note that a single Subscription Offering for “1-2 Sockets or 1-2 Virtual Machines” cannot be used for 1 socket on a Physical Server and 1 Virtual Machine. Neither can it be used for 2 Virtual Machines running at different Service Pack levels.

Appendix H – SUSE Linux Enterprise for High Performance Computing

SUSE Linux Enterprise for High Performance Computing (“SLE HPC”) and SUSE Linux Enterprise for High Performance Computing ESPOS (“SLE HPC ESPOS”)

All SLE HPC Nodes within a SLE HPC Cluster must deploy the same SUSE Linux Enterprise Subscription Offering such as (a) “Standard” with SUSE Linux Enterprise for High Performance Computing ESPOS or without ESPOS or (b) “Priority” with ESPOS or without ESPOS. When You acquire a LTSS Subscription Offering for one node in a particular SLE HPC Cluster, You must acquire sufficient Subscription Offerings in the applicable Unit to cover all acquired, installed, or deployed SLE HPC Nodes in that particular cluster.

The Unit of Measure for a SLE HPC Subscription Offering is per 1-2 Sockets or 1-2 Virtual Machines used as part of a SLE HPC Cluster. One Subscription Offering is required for a 1-2 Socket Physical Server. For Physical Servers with more than 2 Sockets, the number of Subscription Offerings must match or exceed the total number of pairs of Sockets of the Physical Server.

A Subscription Offering for SLE HPC includes a Subscription Offering for SUSE Linux Enterprise Server.

For Physical Servers with more than 2 Virtual Machines, SLE HPC Subscription Offerings are Stackable to match or exceed the number of Virtual Machines. For example, a Physical Server with 2 Sockets and 4 Virtual Machines needs 2 SLE HPC Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines.”

For virtualization environments, such as on a Virtualization Host, or in a private or Public Cloud, up to 2 Virtual Machines can be deployed with one “1-2 Sockets or 1-2 Virtual Machines” Subscription Offering. Note that a Subscription Offering for “1-2 Sockets or 1-2 Virtual Machines” cannot be used for 1 Socket on a Physical Server and 1 Virtual Machine.

A “SLE HPC Cluster” is defined by the following cumulative characteristics:

• One SLE HPC Cluster must consist of a minimum of four (4) Physical Servers or Virtual Machines; and
• The SLE HPC Cluster is solely used for compute-intensive or high-performance data analysis distributed tasks sent to individual SLE HPC Compute Nodes within the SLE HPC Cluster (see “Definitions” for more details); and
• External network communication to and from the SLE HPC Cluster must only happen via the SLE HPC Head Nodes. With the exception of (a) communication for purely administrative purposes which in no way interferes with the computation task distributed to any HPC Compute Node and (b) data transfer directly related to computation of a particular computation task between any HPC Compute Node and a storage system or streaming data source. No direct or indirect communication between HPC Compute Nodes and external systems is allowed.

Appendix I – SUSE Linux Micro

SUSE Linux Micro (formerly SUSE Linux Enterprise Micro) Subscription Offerings and Units of Measure

Effective May 1st 2024 for SUSE Linux Micro on x86-64 and AArch64.

Operating Environments and Unit of Measure

Each Physical Server, Virtualization Host or Virtualization Environment on which SUSE Linux Micro is deployed, installed, used or executed must have a Subscription Offering.

A SUSE Linux Micro Subscription Offering must not be used as Subscription Offering for SUSE Linux Enterprise Server or SUSE Linux Enterprise Server for SAP Applications.

However, a Subscription Offering for SUSE Linux Enterprise Server can be used to run SUSE Linux Micro, if: (1) SUSE Linux Micro is being run as a hypervisor for SUSE Linux Enterprise Server Virtual Machines; (2) each of those SUSE Linux Enterprise Server Virtual Machines is already covered by a Subscription Offering; and (3) the Physical Server running the hypervisor is covered by a Subscription Offering. Note that where you have purchased a SUSE Linux Enterprise Server, 1-2 Sockets with Unlimited Virtual Machines Subscription Offering, that Subscription Offering includes the underlying Physical Server and the Virtual Machines.

For example, a 2-socket system with SUSE Linux Micro as a KVM hypervisor and running two SUSE Linux Enterprise Server Virtual Machines will require two Subscription Offerings for SUSE Linux Enterprise Server, 1-2 Sockets or 1-2 Virtual Machines in total. One Subscription Offering will cover the Physical Server running the SUSE Linux Micro hypervisor, and the other covers the two SUSE Linux Enterprise Server Virtual Machines.

For a 2-socket system running twenty SUSE Linux Enterprise Server Virtual Machines on a KVM hypervisor provided by SUSE Linux Micro, one count of SUSE Linux Enterprise Server 1-2 Sockets with Unlimited Virtual Machines is sufficient to cover both the Virtual Machines and the SUSE Linux Enterprise hypervisor. None of these examples need a separate SUSE Linux Micro subscription.

Subscription Offerings for 1-16 Virtual Cores

These Subscription Offerings are intended for flexible deployments on Physical Servers, Virtualization Environments and in Public Clouds.

Deployment on Physical Servers

The number of Subscription Offerings needed for a Physical Server is determined by the number of Virtual Cores the Physical Server exposes to SUSE Linux Micro.

Physical Servers with up to 16 Virtual Cores need 1 Subscription Offering for “1-16 vCores”.

For Physical Servers with more than 16 Virtual Cores, Subscription Offerings are Stackable to match or exceed the number of Virtual Cores. For example, a Physical Server with 48 Virtual Cores needs 3 Subscription Offerings for “1-16 vCores”. As another example, a single-socket 24-core server would require two subscription offerings for SUSE Linux Micro for 1-16 vCores.

Subscription Offerings can be transferred to new and/or different Physical Servers. For example, when 10 Physical Servers with 16 Virtual Cores each are replaced by 4 Physical Servers with 64 Virtual Cores each, the 10 “1-16 vCores” Subscription Offerings can be transferred to the new Physical Servers. In this example, each of the new servers requires 4 Subscription Offerings for “1-16 vCores”. The total number of Subscription Offerings needs to be

16. 10 Subscription Offerings are transferred, and another 6 Subscription Offerings need to be added.

Deployments as Virtual Machines

Subscription Offerings for “1-16 vCores” can also be repurposed as Virtual Machines on any Virtualization Host or Virtualization Environment.

For Virtual Machines with more than 16 Virtual Cores, Subscription Offerings are Stackable to match or exceed the number of Virtual Cores. For example, a Virtual Machine with 48 Virtual Cores needs 3 Subscription Offerings for “1-16 vCores”.

Deployments in the Cloud

Subscription Offerings for “1-16 vCores” can also be repurposed as Virtual Machines on any SUSE certified Cloud Services Provider (CSP).

As a special exception, for use with any SUSE certified Cloud Service Provider (CSP), a single Subscription Offering for “1-16 vCores” is required per Virtual Machine, and the Virtual Machine is limited to a maximum of 16 Virtual Cores. SUSE Linux Micro must not be used for Virtual Machines with more than 16 Virtual Cores with any SUSE certified CSP.

Appendix J – RGS Prime Subscription Offerings

RGS Prime Subscription Offerings and Units of Measure

Subscription Offerings for RGS Prime are priced per Unit, based on: (a) in the case of a Virtualized Deployment, the number of Cores and vCPUs deployed; or (b) in the case of a Bare Metal Deployment, the number of Sockets and Cores deployed.

For Virtualized Deployments with more than 2 Cores or more than 4 vCPUs Cores, Subscription Offerings are Stackable to match or exceed the number of Cores and/or vCPUs.

For Bare Metal Deployments with more than 2 Sockets or more than 64 Cores, Subscription Offerings are Stackable to match or exceed the number of Sockets and/or Cores.

RGS Kubernetes Engine

A Subscription Offering for RGS Kubernetes Engine entitles You to Subscription Benefits for SUSE Linux Micro and RKE2/K3s, for the number of Units covered by Your Subscription Offering.

RGS Prime

A Subscription Offering for RGS Prime entitles You to Subscription Benefits for the following components, for the number of Units covered by Your Subscription Offering: SUSE Linux Micro; RKE2/K3s; Elemental; RGS Manager; RGS Observability and RGS Application Collection Base.

RGS Suite

A Subscription Offering for RGS Suite entitles You to Subscription Benefits for the following components, for the number of Units covered by Your Subscription Offering: SUSE Linux Micro or RGS HCI; RKE2/K3s; Elemental; RGS Manager; RGS Observability, RGS Platform Optimization, RGS Storage, RGS Security and RGS Application Collection Advanced.

RGS Virtualization (formerly Harvester)

A Subscription Offering for RGS Virtualization entitles You to Subscription Benefits for the following components, for the number of Units covered by Your Subscription Offering: RGS Manager; RGS Storage and RGS HCI.

RGS Observability Platform Optimization Add-on

RGS Observability Add-On is an ‘add-on’ Subscription Offering for RGS Prime, and in order to access and use its Subscription Benefits You must acquire a RGS Observability Add-On Subscription Offering for every RGS Prime Subscription Offering You have.

RGS Security (formerly Neuvector) Add-On

RGS Security Add-On is an ‘add-on’ Subscription Offering for RGS Prime, and in order to access and use its Subscription Benefits You must acquire a RGS Security Add-On Subscription Offering for every RGS Prime Subscription Offering You have.

RGS Storage (formerly Longhorn) Add-On

RGS Storage Add-On is an ‘add-on’ Subscription Offering for RGS Prime, and in order to access and use its Subscription Benefits You must acquire a RGS Storage Add-On Subscription Offering for every RGS Prime Subscription Offering You have.

Appendix K - SUSE Linux Enterprise Real Time

Operating Environments and Unit of Measure

SUSE Linux Enterprise Real Time is available on x86-64. Each Physical Server, Virtualization Host or Virtualization Environment on which SUSE Linux Enterprise Real Time is deployed, installed, used or executed must have a Subscription Offering.

For Virtualization Environments, if the Unit of Measure chosen is per number of Sockets with Unlimited Virtual Machines per Physical Server, only Physical Servers for which the appropriate Subscription Offering has been acquired may be used to deploy such Virtualization Environment, irrespective of whether such Physical Server is actually used or for how long such Physical Server is used.

To change the deployment type of a Product during the Subscription Offering period, You must choose the highest valued Subscription Offering matching Your different deployment types for this Product. For example, if You deploy the higher valued SUSE Linux Enterprise Real Time Subscription Offering for '1-2 Sockets with Unlimited Virtual Machines' during the Subscription Offering period for a deployment scenario matching a lower valued (when compared to the 1-2 Sockets with Unlimited Virtual Machines Subscription Offering) '1-2 Sockets or 1-2 Virtual Machines', You may continue to use the higher valued Subscription Offering for the remaining Subscription Offering period. However, You may not deploy the lower valued SUSE Linux Enterprise Real Time Subscription Offering for '1-2 Sockets or 1-2 Virtual Machines' during the Subscription Offering period for a deployment type matching the higher valued '1-2 Sockets with Unlimited Virtual Machines' Subscription Offering.

Subscription Offerings for 1-2 Sockets or 1-2 Virtual Machines

These Subscription Offerings are intended for flexible deployments on Physical Servers and low-density or cloud virtualization.

Deployment on Physical Servers

The number of Subscription Offerings needed for a Physical Server is determined by the number of Sockets in the Physical Server. Physical Servers with 1-2 Sockets need 1 Subscription Offering for "1-2 Sockets or 1-2 Virtual Machines."

For Physical Servers with more than 2 Sockets, Subscription Offerings are Stackable to match or exceed the number of Sockets. For example, a Physical Server with 4 Sockets needs 2 Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines.”

Subscription Offerings can be transferred to new and/or different Physical Servers. For example, when 10 Physical Servers with 2 Sockets each are replaced by 4 Physical Servers with 4 Sockets each, the 10 “1-2 Sockets or 1-2 Virtual Machines” Subscription Offerings can be transferred to the new Physical Servers. In this example, a total of 8 Subscription Offerings (2 per Physical Server with 4 Sockets) are transferred to the new Physical Servers. You can use the remaining 2 Subscription Offerings for later deployments.

Low-Density or Cloud Deployments

Up to 2 Virtual Machines running on the same Virtualization Host or Virtualization Environment or within the same Private Cloud account or Public Cloud zone can be deployed with one “1-2 Sockets or 1-2 Virtual Machines” Subscription Offering.

Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines” can also be repurposed as Virtual Machines on any Virtualization Host, Virtualization Environment or with any RGS certified Cloud Services Provider (CSP).

At any point in time, a Subscription Offering for “1-2 Sockets or 1-2 Virtual Machines” can only be deployed either on a Physical Server or as Virtual Machines. For clarity, a Subscription Offering for “1-2 Sockets or 1-2 Virtual Machines” cannot be used for 1 Socket on a Physical Server and 1 Virtual Machine.

Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines” may not be used as a Virtualization Host. Virtualization Host capability is provided pursuant to the Subscriptions for 1-2 Sockets with Unlimited Virtual Machine defined below.

Subscription Offerings for 1-2 Sockets with Unlimited Virtual Machines

For high-density Virtualized Deployment a Subscription Offering for “1-2 Sockets with Unlimited Virtual Machines.” is available. This Subscription Offering entitles You to deploy an unlimited number of Virtual Machines per 1-2 Sockets on a Virtualization Host. For Virtualization Hosts with more than 2 Sockets, Subscription Offerings are Stackable to match or exceed the number of Sockets. This Subscription Offering can be used on any third-party Virtualization Host and also includes the entitlement to run SUSE Linux Enterprise for x86-64 Xen or KVM as the Virtualization Host.

Subscription Offerings for “1-2 Sockets with Unlimited Virtual Machines” may be deployed alternatively (but not concurrently) as 1 or 2 Virtual Machines on any Virtualization Host or with any Cloud Services provider which is authorized by SUSE (Bring Your Own Subscription or “BYOS”). Unlike Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines” (“Low-Density”), Subscription offerings for 1-2 Sockets with Unlimited Virtual Machines must be acquired for each Virtualization Host capable of deploying RGS Products within a Virtualization Environment.

SUSE Linux Enterprise Real Time

Starting July 1st, 2021, the Subscription Offering for SUSE Linux Enterprise Real Time with Live Patching, 1-2 Sockets with Unlimited Virtual Machines will replace the existing Subscription Offering for SUSE Linux Enterprise Real Time, 1-2 Sockets with Unlimited Virtual Machines. This has no effect on Subscription Offerings for these products acquired before this date. Both Standard and Priority Subscription Offerings for SUSE Linux Enterprise Server Real Time with Live Patching, 1-2 Sockets with Unlimited Virtual Machines will include SUSE Linux Enterprise Live Patching.

SUSE Linux Enterprise Live Patching must be purchased separately for SUSE Linux Enterprise Server Real Time Subscription Offerings for 1-2 Sockets or 1-2 Virtual Machines.

Appendix L – RGS AI Subscription Offerings

RGS AI Suite Subscription Offerings and Units of Measure

Subscription Offerings for RGS AI Suite are priced per Unit, based on: (a) in the case of a Virtualized Deployment, the number of Cores and vCPUs deployed; or (b) in the case of a Bare Metal Deployment, the number of Sockets and Cores deployed.

For Virtualized Deployments with more than 2 Cores or more than 4 vCPUs Cores, Subscription Offerings are Stackable to match or exceed the number of Cores and/or vCPUs.

For Bare Metal Deployments with more than 2 Sockets or more than 64 Cores, Subscription Offerings are Stackable to match or exceed the number of Sockets and/or Cores.

A Subscription Offering for RGS AI Suite entitles You to Subscription Benefits for the following components, for the number of Units covered by Your Subscription Offering: AI Library; SUSE Linux Micro; RKE2; K3s; SUSE Manager; Rancher Management Server; RGS Platform Optimization; RGS Storage; RGS Security; RGS Virtualization and RGS Prime Application Collection.

Glossary

Capitalized terms used in these Subscription Terms but not defined in this glossary will have the meaning given to them in the Enterprise Agreement or other written contract with RGS governing Subscription Offerings (as applicable).

• “Bare Metal Deployment” means installation of the RGS Product directly on to a computer's hard disk, or the physical hardware components of a computer, without an operating system, hypervisor or applications being installed
• “Client” is the client part of a client-server application.
• “Client Device” is the client device of a solution with client and server device, e.g., SUSE Linux Enterprise Point of Service and SUSE Multi-Linux Manager for Retail product family.
• “Client Server Application” is an application whose design requires two or more parts to fulfill the dedicated purpose: one or more clients and one or more servers acting together.
• “Cloud Computing” means a paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand.
• “Cloud Kubernetes Cluster” means a Kubernetes cluster that has a third party managing the Kubernetes API and etcd Instances associated with the cluster such as (by way of example) EKS and AKS clusters,
• “Cloud Services” means one or more capabilities offered via Cloud Computing invoked using a defined interface.
• “Core” means a subunit within a CPU on a single chip that handles the main computational activities of a computer. A CPU may have one or more Cores and therefore be a “Multi-Core CPU” if it has more than one Core.
• “Code Stream” is a released version of SLES such as GA (initial release) or a particular Service Pack; each is defined to be a different Code Stream.
• “Container” or “Linux Containers” are isolated Linux systems (processes or groups of processes) which share a single Linux kernel.
• “Container Workloads” are processes running in Linux Containers on a scheduler such as Kubernetes, launched from OCI images.
• “CP” means an activated Central Processor and is an IBM mainframe general processor unit for general purpose processing. CPs are also capable of running Linux. Spare CPs are not regarded as “activated CPs.” CPs which are exclusively dedicated to another LPAR (Logical Partition) are not regarded as activated CPs. Shared CPs are regarded as activated CPs.
• “CPU” means “Central Processing Unit” and is the functional unit (i.e., the “computing part”) of the computer that interprets and executes instructions for a specific instruction set; it is made up of one or multiple Cores, including the control unit and the ALU. “CSP”, or cloud service provider means a company offering a cloud-based platform, infrastructure, application, or storage services.
• “Current” means an active, valid Subscription Offering. Once a Subscription Offering passes its expiration date, it is “Expired”.
• “Data Center” means physical location in an enterprise that contains back-end IT systems, infrastructure and data stores, including mainframes, servers and databases, which centrally manage storage, computing and resources for an organization.
• “Decentralized Computing” means a form of computing in which data and applications are distributed among disparate computers or systems, but are connected and integrated by means of network services. “Device” means laptop, desktop, workstation, server or other physical entity which can process and transfer data.
• “EA” or “Enterprise Agreement” means the EA terms referenced in a quote issued by RGS or otherwise attached to that quote, and if no VLA is referenced in or attached to that quote, the terms available at https://ranchergovernment.com/enterprise-agreement
• “Edge” means use cases where the data processing occurs on decentralized computing/data-collecting devices away from centralized processing in data centers or cloud environments.
• “Edge Cluster” means a single Kubernetes cluster with a maximum of 5 Physical Servers, which are not used in a Data Center or Public Cloud environment.
• “Eligible Public Clouds” are those Public Clouds that are approved by RGS and include the Government and commercial regions of Amazon Web Services (AWS), Azure, Oracle, and Google.
• “Engine” see IFL or CP.
• “Extension” is a product which requires another product as a foundation to be operational. Examples are: SLES (as foundation) and SLE HA (as Extension), SLES (as foundation) and SMT (Subscription Management Tool as Extension), SLES (as foundation) and SLE HA and Geo SLE HA (as Extension).
• “Geographically Clustered” means clusters of Physical Servers which are operated with a network signal latency greater than 15 milliseconds.
• “Hardware Architecture” or “Hardware Platform” means a family of systems which is able to execute the same executable code or programs.
• "High Performance Computing Cluster (HPC Cluster)” is defined as a single entity or Physical System to work on specific tasks by performing compute- intensive or I/O intensive operations on sets of data that are networked and managed to perform compute-intensive workloads or high performance data analysis workloads. The HPC Cluster must split tasks into subtasks which are distributed to one or more HPC Compute Nodes for computation. The HPC Cluster consists of a combination of multiple HPC Compute Nodes and at least one HPC Head Node.
• “HPC Head Node” is a Physical Server used exclusively to perform management functions for the HPC Cluster. Typical functions include workload scheduling, input/output management, login nodes, HPC Cluster authentication, performance management, Spark Master and software deployment and patching. An HPC Head Node may not perform any function for systems that are not part of the cluster.
• “HPC Compute Nodes” is a Physical Server in a HPC System which is connected to the HPC Head Node and is used solely to provide computational processing capacity for HPC workloads.
• “IFL” means an Integrated Facility for Linux (“IFL”) on IBM z Systems. An IFL is an IBM mainframe processor capable of running the Linux operating system. An IFL needs to be activated during IML (Initial Microcode Load) and is capable of performing instruction processing. A deactivated IFL cannot execute any instruction. Spare IFLs or deactivated IFLs are not regarded to be activated IFLs. IFL Processors are also available on IBM Power servers with similar characteristics and restrictions as IFL Processors on IBM z Systems.
• "Inherited Virtualization" means that an Extension inherits the virtualization type of the Product. The virtualization type is either i) deployment on a Physical Server with no virtualization ("Physical Deployment") on 1-2 Sockets, or 1-2 Virtual Machines on a VMM, or ii) Virtualized Deployment per “1- 2 Sockets with Unlimited (number of) Virtual Machines”.
• “IFLe” means use of an IFL with an elastic pricing Subscription Offering.
• “Installation Node” has the meaning given in Appendix M.
• “Instance” is a Physical Server or a Virtual Instance .
• “KVM” is the abbreviation for “Kernel Virtual Machine”, a VMM available for different hardware architectures.
• “LPAR or DLPAR” means Logical Partition or Dynamic Logical Partition. Different LPAR technologies vary regarding their features. One LPAR context is considered to represent one VM, and any LPAR technology is considered a VMM within the scope of this document.
• “Metrics Appendices” means Exhibit A to these Subscription Terms, including the Appendices to Exhibit A which specify the metrics and units of measure applicable to Subscription Offerings;
• “Managed Instance” is either an Instance of a third-party product or of a RGS Product which is managed by SUSE Multi-Linux Manager Server.
• “MCM” is a Multi-layer Ceramic Module, typically used to achieve high physical integration of electronic components like Processor and cache components.
• “MLA” or “Master Licensing Agreement” means the terms of the Master Licensing Agreement entered into between You and SUSE.
• “MSP”, or managed service provider means a company that remotely manages a customer's IT infrastructure and/or end-user systems, typically on a proactive basis and under a subscription model.
• “NVMe” means Non Volatile Memory Express.
• “Node” is a physical entity capable of receiving and sending data and temporary storage and reading, writing or performing logical operations with the data. A Node typically consists of one or more Processors, memory, and input / output devices connecting to other Nodes or other types of devices. It can also have access to directly attached persistent storage, and special purpose Processors.
• “Non-Production Environment” means an environment other than a Production Environment, including without limitation, development, testing, backup and pre-deployment (or staging) environments.
• “Operating Environment” can be a Physical Server or Virtualization Host or Virtualization Environment.
• “Order Form” means RGS’s standard ordering document or online form, an authorized RGS Reseller Purchase Order, RGS quote, direct purchase order issued by Customer, or other governing contract that is used to order RGS Products or Services, that has been executed by RGS and You.
• "Patch (Update)" means a fix or compilation of fixes released by SUSE to correct operation defects (program bugs) in RGS Products. A patch can contain one or multiple files to replace or enhance existing executables, programs, applications or documents.
• “Physical Deployment” means deployment or use within a physical hardware environment without abstracting software or Virtualization Host or Virtual Machine Monitor (VMM).
• “Physical Node” means Physical Server.
• “Physical Server” means a physical computer system, whether in a network that is shared by multiple users or on its own, regardless of whether the physical computer system has been partitioned by software. A Physical Server may contain one or multiple CPUs, Cores, or Processors, regardless of production capacity.
• “Physical System” means Physical Server.
• “PowerVM” is a virtualization technology to provide DLPARs or LPARs for IBM POWER systems, similar to a VMM.
• “powerKVM or KVM for POWER” is a virtualization technology based on KVM, to provide VMs for POWER systems, similar to a VMM. PowerKVM has been withdrawn by IBM.
• “POWER or IBM Power or OpenPOWER” is the name used for IBM POWER or third party POWER architecture system offerings. Over time, different names have been in place e.g. “POWER8, POWER7, POWER7+”, referring to different generations of these systems at different times. POWER processors are also used by third parties which offer systems according to the OpenPOWER specifications.
• "Price List" means the Corporate Price List as published periodically by SUSE.
• “Private Cloud” means a deployment model where Cloud Services are controlled and used exclusively by You.
• “Processor” has the same meaning as CPU.
• “Product” is a product, which does not require another product as a foundation to be operational. Non-exhaustive examples are SUSE Linux Enterprise Server and SUSE Linux Enterprise Desktop.
• “Production Environment” is the set of computers where finished, user-ready software is deployed and executed for live, usable operation for the intended end users.
• “Promotional Conditions” has the meaning given in Section 5.1.
• “Promotional Subscriptions” has the meaning given in Section 5.1.
• “PTF” is a Problem Temporary Fix: it is an issue to correct one or more customer issues for the time being and is supported until a regular patch is released. Some PTFs might require resolution in the next Service Pack for technical and quality reasons.
• “Public Cloud” means a deployment model where Cloud Services are potentially available to any Cloud Service customer “Raw Storage Capacity” means the total capacity of all storage devices that are allocated to and managed as part of a single Storage Cluster. This measure applies to all physical storage devices configured as part of the cluster. Each cluster is measured and billed independently.
• “RGS Prime Application Collection Advanced” means the applications made available in the ‘Application Collection Advanced’ from time to time.
• “RGS Prime Application Collection Base” means the applications made available in the ‘Application Collection Base’ from time to time.
• "RGS Software Terms" means the applicable license agreement that accompanies and governs the use of RGS Software which is available at https://ranchergovernment.com/ for Rancher branded products and at https://www.suse.com/licensing/eula/  for SUSE branded products.
• “RGSCC” is the RGS Customer Center
• “RGS Product” is: (1) a software product that you obtain directly from RGS or indirectly from RGS (for example, via a distributor or reseller), that is made available for download by RGS on a trusted RGS registry, the RGSCC (or other
• RGS-authenticated portal) and for which Subscription Offerings are made available, including without limitation, all of the RGS Products listed in the Metrics Appendices; and/or (2) any other open-source software product in respect of which RGS provides a support and maintenance offering for which RGS charges fees, as specified at https://ranchergovernment.com/
• “SCM” is a single chip module, typically used to achieve high physical integration of electronic components.
• “Security Fix” is a corrective fix for a security issue.
• “Service Pack” is a periodically released, installable collection of updates, fixes, and code enhancements.
• “SMT (Simultaneous Multi-Threading)” specifies the capability of a Processor to execute multiple instruction streams concurrently.
• “Socket” is a location on the motherboard or other similar computer circuitry where a CPU has been physically installed on a System (populated). For the purposes of this document, the term Socket is used for Processor Cards, MCMs, SCMs or DCMs for POWER systems.
• “Socket Pair” is up to two Sockets on a Physical Node.
• “Socket Pair Equivalent” is a concept used with IBM Power servers to compute a synthetic Socket Pair count by dividing the number of Physical CPUs assigned to a RGS Product divided by the number of physical cores per Socket on that Physical Node
• "Software" means any SUSE or SUSE Affiliate branded software product that is included in a Subscription Offering.
• “Stackable” means that multiple Subscriptions Offerings may be aggregated or "stacked" to match or exceed the number of Sockets in a Physical Server. For example, a Physical Server with four Sockets needs two Subscription Offerings for “1-2 Sockets or 1-2 Virtual Machines". Odd numbers of Sockets must be rounded up: e.g., three Sockets in a Physical Server scenario must carry two stacked Subscription Offerings for "1-2 Sockets or 1-2 Virtual Machines."
• “Storage Cluster” is a group of servers running SUSE Linux Enterprise Server and SUSE Storage components that are managed as a single entity to deliver storage services.
• “Sub-Capacity” is a concept used with IBM Power that allows for Subscription Offerings for RGS Products to be based on less than the full capacity of activated Processors on the Physical Node for Power servers with four or more Sockets when PowerVM is used to limit the Processor capacity available to a RGS Product.
• “Subscription Offering” means a right to receive technical support, Updates and Upgrades in accordance with Section 5, which You purchase directly or indirectly from RGS for a RGS Product.
• “Subscription Terms” means these terms setting out rules applicable to SUSE’s Subscription Offerings, as available at https://ranchergovernment.com/terms-and-conditions and updated from time to time;
• “SUSE Multi-Linux Support” is a package of fixes, Patches and other software to be applied to certain software products specified at https://www.suse.com/products/suse-liberty-linux/ and updated from time to time.
• "Upgrade" means any new version of RGS Products which bears the same product name, including version changes evidenced by a number immediately to either the left or right of the decimal (e.g. SUSE Linux Enterprise Server 9.x to 10.x). If a question arises as to whether a product offering is an Upgrade or a new product, SUSE’s opinion will prevail, provided that SUSE treats the product offering the same for its end users generally.
• “User” is a user or entity accessing the system and establishing a connection to the system, or an entry in a directory, regardless of which kind, e.g., a person, an object such as a company name.
• “vCPU” - virtual central processing unit. One or more vCPUs are assigned to every Virtual Machine (VM) within a cloud environment. Each vCPU is seen as a single physical CPU core by the VM's operating system.
• “Virtual Core” or “vCore” is a logical CPU exposed to the operating system by the Physical Server or Virtual Machine. Enabling or disabling technologies like Intel Hyper-Threading or the AMD SMT extensions can influence the number of Virtual Cores exposed to the operating system.
• “Virtualized Deployment” means deployment or use of the product involving a VMM.
• “Virtual Device” is a virtualized resource in a Virtual Machine context, e.g. virtualized processor, virtualized block or network device.
• “Virtualization Environment” means a group of Virtualization Hosts on which You can deploy Virtual Machines as if they were running on a single Virtualization Host.
• “Virtualization Host” is a single Physical Server which executes one or more Virtual Machines by a VMM.
• “Virtual Image” see Virtual Instance.
• “Virtual Instance” is one entity of an operating system, workload or application, which is executed in a virtual context created by a VMM.
• “Virtual Machine” or “VM” or “Virtual Guest” means a virtualized context that can execute e.g. one operating system, workload, application, or multiples of such, like a Physical System. Some VMs can be migrated from one VMM context to another, residing on the same Physical System, or on different Physical Systems, or within logical partitions. Some VMMs allow nesting of VMMs (multiple layers of virtualization with the same or different VMMs).
• “Virtual Machine Monitor (VMM) or Hypervisor” describes a software and/or hardware technology, which allows creation of one or multiple virtualized contexts for sharing and/or isolating resources of the underlying hardware. A VMM can, by way of example, manage and expose these resources to an operating system, workload environment or application. VMMs include without limitation. KVM, Xen, Microsoft Hyper-V, VMware vSphere Hypervisor, DLPAR, LPAR, and z/VM.
• “Virtual System” is a virtualized context which is able to abstract a Physical System, like a Virtual Machine. See VM.
• “Virtualization Technology” means software and/or hardware technology used to implement e.g. a Virtual Machine Monitor (VMM) and supporting functions such as to manage the lifecycle of a Virtual Machine.
• “x86, x86-64, ppc64, ppc64le, s390, s390x and AArch64” are the Linux instruction set architecture abbreviations for different types of Physical Systems and Processors instruction sets. By example: x86 for Intel and AMD 32-bit x86 Processors, x86-64 for Intel 64 and AMD64 64-bit Processors, ppc64 for IBM POWER big endian Processor instruction set, ppc64le for POWER little endian Processor instruction set, s390x for IBM z Systems z/Architecture type Processors, and AArch64 for 64-bit Arm architecture Processors.
• “Xen” is a Virtual Machine Monitor.
• “z Systems or IBM z Systems” is the name used by IBM for mainframe type systems. Over time, different names have been used e.g. “IBM Z, IBM LinuxONE”, “IBM z Systems, “IBM System z”, “IBM zEnterprise”, “IBM zSeries”, “IBM mainframe”, “IBM S/390”, referring to different generations of these systems at different times.

Last updated:  08/29/2025