First take on LTSS documentation #35
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -584,4 +584,119 @@ | |
| </para> | ||
| </sect2> | ||
| </sect1> | ||
| <sect1 xml:id="ltss"> | ||
| <title>Enabling LTSS support</title> | ||
| <para> | ||
| <literal>Long Term Service Pack Support</literal> (LTSS) extends the lifecycle of | ||
| &productname;. It is available as an extension. For more information about LTSS, refer to | ||
| <link xlink:href="https://www.suse.com/products/long-term-service-pack-support/"/>. | ||
| </para> | ||
| <note> | ||
| <title>LTSS subscriptions are version-specific</title> | ||
| <para> | ||
| LTSS subscriptions are version-specific. If you have a subscription for | ||
| &slsa; 15 SP4, you cannot use that registration code to register LTSS on a | ||
| 15 SP3 image. Make sure to use the correct registration code for your instance | ||
| and upgrade it if necessary. | ||
| </para> | ||
| </note> | ||
| <sect2 xml:id="ltss-byos"> | ||
| <title>LTSS on BYOS</title> | ||
| <para> | ||
| If you do not have an LTSS subscription for your BYOS instance, contact a &suse; | ||
| representative or visit <link xlink:href="https://www.suse.com/how-to-buy"/> for purchase | ||
| options. | ||
| </para> | ||
| <procedure> | ||
| <para> | ||
| To enable the LTSS extension, perform the following steps: | ||
| </para> | ||
| <step> | ||
| <para> | ||
| Log in to the <link xlink:href="&sccurl;">&scc;</link> to look up your LTSS registration | ||
| code. | ||
| </para> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Make sure your system is registered with a subscription that is eligible for LTSS. If | ||
| the system is not yet registered, register it | ||
| (see <xref linkend="sec-admin-register"/>). | ||
| </para> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Make sure the LTSS extension is available for your system: | ||
| </para> | ||
| <screen>&prompt.sudo;<command>SUSEConnect --list-extensions | grep LTSS</command> | ||
| SUSE Linux Enterprise Server LTSS &productnumber; x86_64 | ||
| Activate with: SUSEConnect -p SLES-LTSS/&productnumber-regurl;/x86_64 -r ADDITIONAL REGCODE</screen> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Activate the module as instructed: | ||
| </para> | ||
| <screen>&prompt.sudo;<command>SUSEConnect -p SLES-LTSS/<replaceable>&productnumber-regurl;</replaceable>/<replaceable>x86_64</replaceable> -r <replaceable>REGISTRATION_CODE</replaceable></command></screen> | ||
| </step> | ||
| </procedure> | ||
| </sect2> | ||
| <sect2 xml:id="ltss-payg"> | ||
| <title>LTSS on PAYG</title> | ||
| <para> | ||
| LTSS subscriptions for PAYG can be transacted through a private offer on the CSPs market | ||
| place or via direct transaction with SUSE. Reach out to <link | ||
| xlink:href="mailto:[email protected]">[email protected]</link> to work out the | ||
| commercial details. You will receive a subscription and access to the <link | ||
| xlink:href="&sccurl;">&scc;</link>). With your subscription, you can activate a | ||
| registration code for LTSS. | ||
| </para> | ||
| <tip> | ||
| <title>Existing LTSS subscriptions</title> | ||
| <para> | ||
| If you already have an LTSS subscription that you are using in your data center, it will | ||
| work in the cloud just fine. You can deregister a system in your data center and move that | ||
| use of your LTSS subscription to an instance in the cloud. | ||
| </para> | ||
| </tip> | ||
| <procedure> | ||
| <para> | ||
| To enable the LTSS extension, perform the following steps: | ||
| </para> | ||
| <step> | ||
| <para> | ||
| Log in to the <link xlink:href="&sccurl;">&scc;</link> to activate a registration code. | ||
| Note that LTSS subscriptions are version-specific. If you have a subscription for | ||
| &slsa; 15 SP4, you cannot use that registration code to register LTSS on a | ||
| 15 SP3 image. <emphasis>Make sure to activate the LTSS registration code for | ||
| the correct version and service pack (SP) of your instance!</emphasis> | ||
| </para> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Log in to your instance and make sure your system is registered with a subscription that | ||
| is eligible for LTSS. If the system is not yet registered, register it | ||
| (see <xref linkend="sec-admin-register"/>). | ||
| </para> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Log in to your instance and update <package>cloud-regionsrv-client</package> to the | ||
| latest version. | ||
| </para> | ||
| <screen>&prompt.sudo;zypper up cloud-regionsrv-client</screen> | ||
| <para> | ||
| You will need at least version 10.3.4. | ||
| </para> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Register the LTSS extension: | ||
| </para> | ||
| <screen>&prompt.sudo;registercloudguset -r $REGISTRATION_CODE | ||
| Running LTSS registration...this takes a little longer | ||
| LTSS registration succeeded</screen> | ||
|
There was a problem hiding this comment. Should we have a side note here to clarify that |
||
| </step> | ||
| </procedure> | ||
| </sect2> | ||
| </sect1> | ||
| </chapter> | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we not tell users how to check that there instance is registered? And should we not tell users that for PAYG a registered system is the default state?
Since there is a difference between PAYG and BYOS I think we should not have the exact same wording.