Skip to content

Restructure Server Install scenario micro/sles #3830

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Mar 31, 2025
Merged

Restructure Server Install scenario micro/sles #3830

Show file tree
Hide file tree
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
5ff8712
Restructure Server Install scenario micro/sles
keichwa Mar 26, 2025
cbc0267
more adjustments (per feedback)
keichwa Mar 26, 2025
3a72dce
move note about SLEM update behavior to SLE Micro section
keichwa Mar 26, 2025
6d179e6
add links where to continue after host OS install (micro/sles)
keichwa Mar 26, 2025
9417259
make sure mgradm mgradm-bash-completion gets installed
keichwa Mar 27, 2025
a460ff7
Merge branch 'manager-5.0' into manager50-iau-sles-as-host-#1239801-k…
keichwa Mar 27, 2025
c5b18ea
reboot is safe net
keichwa Mar 27, 2025
ccf720f
Merge branch 'manager-5.0' into manager50-iau-sles-as-host-#1239801-k…
keichwa Mar 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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 additional registry link to Installation and Upgrade Guide
(bsc#12400101)
- Added instructions for Proxy installation on SUSE Linux
Expand Down
4 changes: 2 additions & 2 deletions modules/common-workflows/pages/workflow-install-from-selfinstall-on-ppc.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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].
172 changes: 111 additions & 61 deletions ...llation-and-upgrade/pages/container-deployment/suma/server-deployment-suma.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}


==== Download the Installation Media

.Procedure: 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.
Expand All @@ -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.
Expand Down Expand Up @@ -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.
Expand Down Expand Up @@ -198,9 +214,9 @@ transactional-update register -p SUSE-Manager-Server/5.0/x86_64 -r <reg_code>
. Reboot.


=== Update the System
==== Update the System

.Procedure
.Procedure: Updating the System
. Log in as *root*.
. Run **transactional-update**:
Comment on lines +217 to 221
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just out of curiosity, why do we not mention to install mgradm and mgradm-bash-completion here, like we do for the proxy?
image
image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it now will get installed automatically. Trying to ping @mcalmer for clarification: Do we still need to install mgradm and completion tools with the first transactional-update run after preparing Micro as the server host OS? On both, 5.0.4 and 5.1.x?


Expand All @@ -213,7 +229,93 @@ transactional-update

. Reboot.

=== Configure Custom Persistent Storage
[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
----
====

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]]
=== 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
----

. 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 mgradm mgradm-bash-completion
----

// 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
// ----

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]]
== 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.
Expand Down Expand Up @@ -253,46 +355,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.
Expand Down Expand Up @@ -339,20 +403,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}.

Expand Down
Loading