Skip to content

5.0 - Fixed the procedures formatting #4522

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 2 commits into from
Nov 12, 2025
Merged

5.0 - Fixed the procedures formatting #4522

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
316208f
Fixed the procedures formatting.
0rnela Nov 12, 2025
3be826f
Cont.
0rnela Nov 12, 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
40 changes: 36 additions & 4 deletions ...-upgrade/pages/container-deployment/suma/server-air-gapped-deployment-suma.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,19 +42,29 @@ To upgrade {productname} Server, users should upgrade all packages in the system
User should make the needed RPM available on the internal network. That can be done by using a second {productname} Server or an RMT server.
====

.Procedure: Install {productname} on SLE Micro in Air-gapped
. Install SLE Micro
. Update the system
. Install tools packages and image packages (replace $ARCH$ with the correct architecture)
.Procedure: Install {productname} on SLE Micro in air-gapped deployment
[role=procedure]
____
. Install SLE Micro.

. Update the system.

. Install tools packages and image packages (replace $ARCH$ with the correct architecture).

+

[source,shell]
----
transactional-update pkg install mgradm* mgrctl* suse-manager-5.0-$ARCH$-server-*
----

+

. Reboot.

. Deploy {productname} with mgradm.

____

For more detailed information about installing {productname} Server on {sle-micro}, see xref:container-deployment/suma/server-deployment-suma.adoc[Deploy Server as a Virtual Machine].

Expand All @@ -68,7 +78,10 @@ The PTF images are not available as packages.
This means that they should be pulled using [command]``podman`` on a machine with internet access, then saved in an archive, transferred to the air-gapped machine and loaded there.

.Procedure: Pulling the image on a machine with internet access
[role=procedure]
____
. Install [command]``podman``.

. Authenticate against the {suse} Registry using the SCC credentials:

+
Expand All @@ -79,9 +92,14 @@ set +o history
echo SCC_MIRRORING_PASSWORD | podman login -u "SCC_MIRRORING_USER" --password-stdin registry.suse.com
set -o history
----

+

. Create a [path]``/tmp/ptf-images`` temporary file with the URL of the PTF images, one per line.
In most of the cases only the server image is needed and it can be created with a command like the following, after replacing the [command]``SCC_USERID`` and [command]``PTFID`` values.

+

[source,shell]
----
SCC_USERID=aXXXX
Expand All @@ -100,10 +118,19 @@ for image in `cat /tmp/ptf-images`; do
done
podman save -o /tmp/ptf-images.tar `cat /tmp/ptf-images`
----

+

. Transfer the [path]``/tmp/ptf-images.tar`` images archive on the server to patch.

____


.Procedure: Loading the images on the server to patch
[role=procedure]
____
. Ensure the [path]``ptf-images.tar`` file is available on the server.

. Load the images from the archive:

+
Expand All @@ -112,5 +139,10 @@ podman save -o /tmp/ptf-images.tar `cat /tmp/ptf-images`
----
podman load -i ptf-images.tar
----

+

. Install the PTF using `mgradm support ptf podman` as would be done on a connected machine.
Because the images are already loaded they will not be pulled.

____
Loading