Remove SUSE Liberty Linux Base Media section

CHANGELOG.md

@@ -1,3 +1,5 @@
+- Fixed layout in Liberate Formula in Specialized Guides
+- Removed SUSE Liberty Linux Base Media section from Client Configuration Guide
 - Removed outdated disclaimer in CLM examples regarding AppStreams
   (bsc#1226687)
 - Documented proper --mirrorPath parameter in disconnected setup chapter of

modules/client-configuration/pages/clients-sleses.adoc

@@ -28,13 +28,6 @@ endif::[]
 
 
 
-
-[IMPORTANT]
-====
-You are responsible for arranging access to {redhat} or {centos} base media repositories and installation media.
-====
-
-
 ifeval::[{suma-content} == true]
 [IMPORTANT]
 ====
@@ -179,75 +172,6 @@ endif::[]
 
 
 
-[[add.base.media]]
-=== Add Base Media
-
-The {sll} software channels only provide updates, not the packages themselves.
-To register {sll} clients, first register the {sll} Product (outlined below) to create the base channel, then import the necessary Red Hat or CentOS packages as custom child channels.
-Initial packages must be obtained directly from {redhat} or {centos} before applying updates from {sll}.
-Importantly, you do not need to maintain your Red Hat subscriptions, but consult your legal department to check for any ongoing payment obligations to Red Hat during migration.
-To ensure you have all the packages you need, use a full DVD image, not a minimal or {jeos} image.
-
-You can use {productname} custom channels to set up the {rhel} or {centos} media.
-All packages on the base media must be mirrored into a child channel.
-
-You can freely choose the names for the channels.
-
-include::snippets/manual_channels.adoc[]
-
-
-[IMPORTANT]
-====
-For {redhat} 8 clients, add both the Base and AppStream channels.
-You require packages from both channels.
-If you do not add both channels, you cannot create the bootstrap repository, due to missing packages.
-====
-
-If you are using modular channels, you must enable the Python 3.6 module stream on the client.
-If you do not provide Python 3.6, the installation of the [package]``spacecmd`` package will fail.
-
-
-.Procedure: Adding Base Media to Custom Channels
-. Copy the base media image to the {productname} Server container host to the [path]``/tmp/`` directory.
-. To get the base media image into the {productname} Server container, use:
-+
-----
-mgradm distribution copy /tmp/SLES-ES-7.9-x86_64-DVD.iso sles-es-7
-----
-+
-The destination in the container will be [path]``/srv/www/distributions/sles-es-7``.
-. Import the packages into the child channel you created earlier:
-+
-----
-spacewalk-repo-sync -c <channel-label> -u file:///srv/www/distributions/sles-es-7/
-----
-
-
-==== OPTIONAL: Add Base Media from a Content URL
-
-Alternatively, if you have access to a content URL provided by {redhat} CDN or {centos}, you can create a custom repository to mirror the packages.
-
-The details you need for this procedure are:
-
-[[es-repos-manual]]
-[cols="1,1", options="header"]
-.ES Custom Repository Settings
-|===
-
-| Option                 | Parameter
-| Repository URL         | The content URL provided by {redhat} CDN or {centos}
-| Has Signed Metadata?   | Uncheck all {redhat} Enterprise repositories
-| SSL CA Certificate     | [systemitem]``redhat-uep`` ({redhat} only)
-| SSL Client Certificate | [systemitem]``Entitlement-Cert-date`` ({redhat} only)
-| SSL Client Key         | ``Entitlement-Key-date`` ({redhat} only)
-
-|===
-
-include::snippets/manual_repos.adoc[]
-
-include::snippets/manual_associate.adoc[]
-
-
 == Check Synchronization Status
 
 ifeval::[{suma-content} == true]

modules/specialized-guides/pages/salt/salt-formula-liberate.adoc

@@ -65,7 +65,7 @@ tail -f /var/log/rhn/reposync/*
 Description::
 Enter some text describing the activation key.
 Key::
-Enter the identifier of the key.  For example [literal``sll9-default`` for EL 9 systems.
+Enter the identifier of the key.  For example [literal]``sll9-default`` for EL 9 systems.
 Note: Keys will have a numeric prefix depending on the organization, so that they are unique.
 Usage::
 Leave blank.