From 5ff87126a08e9359f8fc63dfe6e394518554482d Mon Sep 17 00:00:00 2001 From: Karl Eichwalder Date: Wed, 26 Mar 2025 12:40:33 +0100 Subject: [PATCH 1/6] Restructure Server Install scenario micro/sles * https://bugzilla.suse.com/show_bug.cgi?id=1239801 * https://github.com/SUSE/spacewalk/issues/26739 --- CHANGELOG.md | 3 + ...kflow-install-from-selfinstall-on-ppc.adoc | 4 +- .../suma/server-deployment-suma.adoc | 145 ++++++++++++------ 3 files changed, 103 insertions(+), 49 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 0915968e79d..bae83f2f7ba 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,6 @@ +- Restructured Server Installation to better distinguish between + SUSE Linux Enterprise Micro and SUSE Linux Enterprise Server + as host operating system respectively (bsc#1239801) - Added instructions for Proxy installation on SUSE Linux Enterprise Server 15 SP6 to Installation and Upgrade Guide - Documented handling of pub directory of the web server in the diff --git a/modules/common-workflows/pages/workflow-install-from-selfinstall-on-ppc.adoc b/modules/common-workflows/pages/workflow-install-from-selfinstall-on-ppc.adoc index 8cc5baf4866..836c5811763 100644 --- a/modules/common-workflows/pages/workflow-install-from-selfinstall-on-ppc.adoc +++ b/modules/common-workflows/pages/workflow-install-from-selfinstall-on-ppc.adoc @@ -71,7 +71,7 @@ mgr-storage-server $device + Ensure [literal]``$device`` points to the fast, persistent storage. + -For more information, see xref:installation-and-upgrade:container-deployment/mlm/server-deployment-mlm.adoc#_persistent_volumes[Persistent Volumes]. +For more information, see xref:installation-and-upgrade:container-deployment/suma/server-deployment-suma.adoc#deploy-suma-server-persistent-storage[Persistent Volumes]. -To continue with deployment, see xref:installation-and-upgrade:container-deployment/mlm/server-deployment-mlm.adoc#_deploy_with_mgradm[Server Deployment]. +To continue with deployment, see xref:installation-and-upgrade:container-deployment/suma/server-deployment-suma.adoc#deploy-suma-server-mgradm[Server Deployment]. diff --git a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc index 8428fea9fbb..daa184df2d8 100644 --- a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc +++ b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc @@ -92,14 +92,30 @@ This adds to the complexity of a {productname} deployment, and may affect the re For a list of all persistent volumes in the container, see xref:installation-and-upgrade:container-management/persistent-container-volumes.adoc[]. -// To set up custom persistent volumes see: + + + +[[deploy-suma-server-host]] +== Deploy {productname} + +// FIXME +// Maybe, here we'd better use a section title such as: +// _Prepare Host OS for {productname} Deployment_ + +You can deploy {productname} on {sle-micro} {microversion} or {sles} {bci-suma}. +{sle-micro} is a transactional system, while {sles} is a full server operating system. + +Depending on your decision, either continue with xref:installation-and-upgrade:container-deployment/suma/server-deployment-suma.adoc#deploy-suma-server-micro[] or with xref:installation-and-upgrade:container-deployment/suma/server-deployment-suma.adoc#deploy-suma-server-sles[] and skip the not selected section. [[deploy-suma-server-micro]] -== Deploy {productname} on {sle-micro} {microversion} +=== Deploy on {sle-micro} {microversion} + -.Procedure: Download the Installation Media +==== Download the Installation Media + +.Procedure: Downloading the Installation Media . Locate the {sle-micro} {microversion} installation media at https://www.suse.com/download/sle-micro/. . Download [filename]``SLE-Micro-5.5-DVD-x86_64-GM-Media1.iso``. . Prepare a DVD or USB flash drive with the downloaded [filename]``.iso`` image for installation. @@ -111,7 +127,7 @@ For a list of all persistent volumes in the container, see xref:installation-and For more information about preparing your machines (virtual or physical), see link:https://documentation.suse.com/sle-micro/5.5/html/SLE-Micro-all/book-deployment-slemicro.html[{sle-micro} {microversion} Deployment Guide]. -.Procedure: {sle-micro} {microversion} Installation +.Procedure: Installing {sle-micro} {microversion} . Use the arrow keys to select [systemitem]``Installation``. . Adjust keyboard and language. . Click the [systemitem]``checkbox`` to accept the license agreement. @@ -155,7 +171,7 @@ This concludes installation of {sle-micro} {microversion} and {productname} {pro -=== Registration from the Command Line (Optional) +==== Registration from the Command Line (Optional) If you added {productname} {productnumber} as an extension during {sle-micro} {microversion} installation then you can skip this step. However, optionally you may skip registration during {sle-micro} {microversion} installation by selecting the btn:[Skip Registration] button. This section provides steps on registering your products after {sle-micro} {microversion} installation. @@ -198,9 +214,9 @@ transactional-update register -p SUSE-Manager-Server/5.0/x86_64 -r . Reboot. -=== Update the System +==== Update the System -.Procedure +.Procedure: Updating the System . Log in as *root*. . Run **transactional-update**: @@ -213,7 +229,80 @@ transactional-update . Reboot. -=== Configure Custom Persistent Storage + + +[[deploy-suma-server-sles]] +=== Deploy on {sles} {bci-suma} + +Alternatively, you can deploy {productname} on {sles} {bci-suma}. + + +The following procedure describes the main steps of the installation process. + +.Procedure: Installing {productname} on {sles} {bci-suma} +. Locate and download {sles} {bci-suma} [literal]``.iso`` at https://www.suse.com/download/sles/. +// FIXME Do we need the following step? ++ +. Make sure that the {scc} code you plan to use has the Extensions enabled. +. Start the installation of {sles} {bci-suma}. + .. On the [literal]``Language, keyboard and product selection`` select the product to install. + .. On the [literal]``License agreement`` read the agreement and check [guimenu]``I Agree to the License Terms``. +. Select the registration method. + ++ + +[[NOTE]] +==== +Please note that for {sles} {bci-suma}, you are required to have a valid {sles} subscription and corresponding regcode, which you must provide on this screen. +You will be required to enter the {productname} Extension regcode below. +==== +. In the screen [literal]``Extensions and Modules Selection`` check the following: ++ + + * {productname} Server Extension + * Basesystem Module + * Containers Module ++ + +Enter the {productname} Extension regcode. +. Complete the installation. +. When the installation completes, log in to the newly installed server as root. +. Update the System (optional, if the system was not set to +download updates during install): + ++ + +[source,shell] +---- +zypper up +---- + ++ + +// FIXME: where is the following "Reboot" actually required? + +. Reboot +. Log in as root and install podman + ++ + +[source,shell] +---- +zypper install podman +---- +. Finish the {productname} installation on {sles} {bci-suma} by running command: + ++ + +[source,shell] +---- +mgradm install podman +---- + + + +[[deploy-suma-server-persistent-storage]] +== Configure Custom Persistent Storage Configuring persistent storage is optional, but it is the only way to avoid serious trouble with container full disk conditions. It is highly recommended to configure custom persistent storage with the [command]``mgr-storage-server`` tool. @@ -253,46 +342,8 @@ For more information, see ==== -ifeval::[{suma-content} == true] -== Install {productname} on {sles} {bci-suma} - -Alternatively, you can install {productname} on {sles} {bci-suma}. -The following procedure describes the main steps of the installation process. - -.Procedure: Installing {productname} on {sles} {bci-suma} -. Locate and download {sles} {bci-suma} [literal]``.iso`` at https://www.suse.com/download/sles/. -. Make sure that the {scc} code you plan to use has the Extensions enabled. -. Start the installation of {sles} {bci-suma}. - .. On the [literal]``Language, keyboard and product selection`` select the product to install. - .. On the [literal]``License agreement`` read the agreement and check [guimenu]``I Agree to the License Terms``. -. Select the registration method. -. In the screen [literal]``Extensions and Modules Selection`` check the following: - * {productname} Server Extension - * Basesystem Module - * Containers Module -. Complete the installation. -. When the installation completes, log in to the newly installed server as root. -. As root, run - -+ - -[source,shell] ----- -zypper install podman ----- -. Finish the {productname} installation on {sles} {bci-suma} by running command: - -+ - -[source,shell] ----- -mgradm install podman ----- -endif::[] - - [[deploy-suma-server-mgradm]] -== Deploy with [literal]``mgradm`` +== Deploy {productname} with [literal]``mgradm`` .Procedure: Deploying {productname} {productnumber} Using [literal]``mgradm`` . Log in as root. From cbc0267c0e09829a8fa08ae088aa7d1c1a8db98b Mon Sep 17 00:00:00 2001 From: Karl Eichwalder Date: Wed, 26 Mar 2025 13:59:50 +0100 Subject: [PATCH 2/6] more adjustments (per feedback) --- .../suma/server-deployment-suma.adoc | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc index daa184df2d8..2d6f461975c 100644 --- a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc +++ b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc @@ -290,14 +290,16 @@ zypper up ---- zypper install podman ---- -. Finish the {productname} installation on {sles} {bci-suma} by running command: -+ - -[source,shell] ----- -mgradm install podman ----- +// FIXME: Should come later, after configuring storage and then run with FQDN +// . Finish the {productname} installation on {sles} {bci-suma} by running command: +// +// + +// +// [source,shell] +// ---- +// mgradm install podman +// ---- From 3a72dce069042d94a13975bd2aa812ef3e18a115 Mon Sep 17 00:00:00 2001 From: Karl Eichwalder Date: Wed, 26 Mar 2025 15:45:50 +0100 Subject: [PATCH 3/6] move note about SLEM update behavior to SLE Micro section (per feedback) --- .../suma/server-deployment-suma.adoc | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc index 2d6f461975c..dc089733156 100644 --- a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc +++ b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc @@ -229,6 +229,20 @@ transactional-update . Reboot. +[IMPORTANT] +==== +{sle-micro} is designed to update itself automatically by default and will reboot after applying updates. +However, this behavior is not desirable for the {productname} environment. +To prevent automatic updates on your server, {productname} disables the transactional-update timer during the bootstrap process. + +If you prefer the {sle-micro} default behavior, enable the timer by running the following command: + +[source, shell] +---- +systemctl enable --now transactional-update.timer +---- +==== + [[deploy-suma-server-sles]] @@ -392,20 +406,6 @@ than 48 characters in length. . Open a browser and proceed to your servers FQDN. . Enter your username (default is [literal]``admin``) and the password you set during the deployment process. -[IMPORTANT] -==== -{sle-micro} is designed to update itself automatically by default and will reboot after applying updates. -However, this behavior is not desirable for the {productname} environment. -To prevent automatic updates on your server, {productname} disables the transactional-update timer during the bootstrap process. - -If you prefer the {sle-micro} default behavior, enable the timer by running the following command: - -[source, shell] ----- -systemctl enable --now transactional-update.timer ----- -==== - In this guide you deployed {productname} {productnumber} Server as a container. Proceed to the next section to add your organization credentials for syncing with {scclongform}. From 6d179e66ed2ee13744557592302d52442e4466c2 Mon Sep 17 00:00:00 2001 From: Karl Eichwalder Date: Wed, 26 Mar 2025 16:08:46 +0100 Subject: [PATCH 4/6] add links where to continue after host OS install (micro/sles) --- .../container-deployment/suma/server-deployment-suma.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc index dc089733156..eaa8bd2ab15 100644 --- a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc +++ b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc @@ -243,6 +243,7 @@ systemctl enable --now transactional-update.timer ---- ==== +To continue with deployment, see xref:installation-and-upgrade:container-deployment/suma/server-deployment-suma.adoc#deploy-suma-server-persistent-storage[]. [[deploy-suma-server-sles]] @@ -315,6 +316,8 @@ zypper install podman // mgradm install podman // ---- +To continue with deployment, see xref:installation-and-upgrade:container-deployment/suma/server-deployment-suma.adoc#deploy-suma-server-persistent-storage[]. + [[deploy-suma-server-persistent-storage]] From 941725998e2e5c99f41d28e063248d64969442ea Mon Sep 17 00:00:00 2001 From: Karl Eichwalder Date: Thu, 27 Mar 2025 13:54:03 +0100 Subject: [PATCH 5/6] make sure mgradm mgradm-bash-completion gets installed --- .../container-deployment/suma/server-deployment-suma.adoc | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc index eaa8bd2ab15..c716e34e529 100644 --- a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc +++ b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc @@ -296,14 +296,12 @@ zypper up // FIXME: where is the following "Reboot" actually required? -. Reboot -. Log in as root and install podman - -+ +. Reboot. +. Log in as root and install [package]``podman`` plus [package]``mgradm`` and [package]``mgradm-bash-completion`` (if not already automatically installed): [source,shell] ---- -zypper install podman +zypper install podman mgradm mgradm-bash-completion ---- // FIXME: Should come later, after configuring storage and then run with FQDN From c5b18ea77ae8b7dea0d5cf27d0609b46af1f1fa0 Mon Sep 17 00:00:00 2001 From: Karl Eichwalder Date: Thu, 27 Mar 2025 14:38:48 +0100 Subject: [PATCH 6/6] reboot is safe net --- .../container-deployment/suma/server-deployment-suma.adoc | 4 ---- 1 file changed, 4 deletions(-) diff --git a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc index c716e34e529..7a84cc8a2af 100644 --- a/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc +++ b/modules/installation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc @@ -292,10 +292,6 @@ download updates during install): zypper up ---- -+ - -// FIXME: where is the following "Reboot" actually required? - . Reboot. . Log in as root and install [package]``podman`` plus [package]``mgradm`` and [package]``mgradm-bash-completion`` (if not already automatically installed):