LTSS in the Public Cloud
This document (000021193) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server any version
SUSE Linux Enterprise Desktop any version
SUSE Linux Enterprise Desktop any version
Situation
A regular SLES workload in the Public Cloud cannot be upgraded to a newer version after its General Support lifecycle, or an upgrade seems to be more trouble than paying for extended support and maintenance. What options are available for Public Cloud customers to add LTSS (Long-Term Service Pack Support) to their existing workloads?
Resolution
Bring Your Own Subscription (BYOS) model:
It is as easy as registering the workload with an additional LTSS registration code. This code can be obtained through SUSE by purchasing an LTSS subscription. BYOS implies that an end-customer and SUSE already have a business relationship.
Pay As You Go (PAYG, also on-demand) model:
Starting with cloud-regionsrv-client version 10.3.4, registration with an LTSS registration code on PAYG instances is supported. The cloud-regionsrv-client should be at version 10.3.4 or above, provided the system has been consistently maintained with regular patches. One may keep their relationship with the cloud provider for general support, while also getting extended support directly from SUSE for LTSS. This requires a direct relationship with SUSE for the LTSS subscription, only.
Example syntax:
Other Alternatives for PAYG:
1. Azure allows an instance conversion from PAYG to BYOS with the Azure Hybrid Benefit (AHB) feature. The instance can then be registered like a BYOS with a registration code and this conversion removes the additional software license fees paid to Azure for VM support. At least one entitlement for SLES and an additional entitlement for LTSS are required for updates and ongoing support.
2. A SUSE Manager (SUMA) server can be used to manage updates on both BYOS and PAYG instances. This requires a specialty SUSE Manager entitlement. A SLES and additional LTSS entitlement are required to enable SUMA to mirror the needed repository channels.
3. An RMT server (formerly known as SMT) can be set up to mirror the SLES and LTSS channels. RMT can be set up on a SLES15 registered with a regular SLES entitlement and an additional LTSS entitlement must be purchased to mirror the LTSS channels. Keep in mind the RMT, itself, will count toward one system in a SLES subscription. It is recommended to only use RMT as a dedicated appliance, and not combine it with any system that is used for another purpose.
More information about options 2 and 3 can be found in the links provided in the Additional Information section.
It is as easy as registering the workload with an additional LTSS registration code. This code can be obtained through SUSE by purchasing an LTSS subscription. BYOS implies that an end-customer and SUSE already have a business relationship.
Pay As You Go (PAYG, also on-demand) model:
Starting with cloud-regionsrv-client version 10.3.4, registration with an LTSS registration code on PAYG instances is supported. The cloud-regionsrv-client should be at version 10.3.4 or above, provided the system has been consistently maintained with regular patches. One may keep their relationship with the cloud provider for general support, while also getting extended support directly from SUSE for LTSS. This requires a direct relationship with SUSE for the LTSS subscription, only.
Example syntax:
# zypper up cloud-regionsrv-client # registercloudguest -r LTSS_REGISTRATION_CODEIn the public cloud, the instances with LTSS remain connected with SUSE operated update infrastructure and receive updates from it.
Other Alternatives for PAYG:
1. Azure allows an instance conversion from PAYG to BYOS with the Azure Hybrid Benefit (AHB) feature. The instance can then be registered like a BYOS with a registration code and this conversion removes the additional software license fees paid to Azure for VM support. At least one entitlement for SLES and an additional entitlement for LTSS are required for updates and ongoing support.
2. A SUSE Manager (SUMA) server can be used to manage updates on both BYOS and PAYG instances. This requires a specialty SUSE Manager entitlement. A SLES and additional LTSS entitlement are required to enable SUMA to mirror the needed repository channels.
3. An RMT server (formerly known as SMT) can be set up to mirror the SLES and LTSS channels. RMT can be set up on a SLES15 registered with a regular SLES entitlement and an additional LTSS entitlement must be purchased to mirror the LTSS channels. Keep in mind the RMT, itself, will count toward one system in a SLES subscription. It is recommended to only use RMT as a dedicated appliance, and not combine it with any system that is used for another purpose.
More information about options 2 and 3 can be found in the links provided in the Additional Information section.
Additional Information
LTSS for PAYG Instances:
https://www.suse.com/c/long-term-service-pack-support-for-payg-instances-simplified/
Addons in the Public Cloud:
https://www.suse.com/c/add-ons-in-the-public-cloud/
RMT: Repository Mirroring Tool - Introduced with SLES15
SMT: Subscription Management Tool - Used with SLES12 and prior
https://www.suse.com/c/long-term-service-pack-support-for-payg-instances-simplified/
Addons in the Public Cloud:
https://www.suse.com/c/add-ons-in-the-public-cloud/
RMT: Repository Mirroring Tool - Introduced with SLES15
SMT: Subscription Management Tool - Used with SLES12 and prior
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000021193
- Creation Date: 05-Sep-2023
- Modified Date:11-Oct-2024
-
- SUSE Linux Enterprise Desktop
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
