Skip to content

Commit 9383f5e

Browse files
authored
5.0 - Fixed the procedures formatting (#4522)
* Fixed the procedures formatting. * Cont.
1 parent 487bffa commit 9383f5e

File tree

1 file changed

+36
-4
lines changed

1 file changed

+36
-4
lines changed

modules/installation-and-upgrade/pages/container-deployment/suma/server-air-gapped-deployment-suma.adoc

Lines changed: 36 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -42,19 +42,29 @@ To upgrade {productname} Server, users should upgrade all packages in the system
4242
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.
4343
====
4444

45-
.Procedure: Install {productname} on SLE Micro in Air-gapped
46-
. Install SLE Micro
47-
. Update the system
48-
. Install tools packages and image packages (replace $ARCH$ with the correct architecture)
45+
.Procedure: Install {productname} on SLE Micro in air-gapped deployment
46+
[role=procedure]
47+
____
48+
. Install SLE Micro.
49+
50+
. Update the system.
51+
52+
. Install tools packages and image packages (replace $ARCH$ with the correct architecture).
53+
4954
+
55+
5056
[source,shell]
5157
----
5258
transactional-update pkg install mgradm* mgrctl* suse-manager-5.0-$ARCH$-server-*
5359
----
60+
5461
+
62+
5563
. Reboot.
64+
5665
. Deploy {productname} with mgradm.
5766
67+
____
5868

5969
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].
6070

@@ -68,7 +78,10 @@ The PTF images are not available as packages.
6878
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.
6979

7080
.Procedure: Pulling the image on a machine with internet access
81+
[role=procedure]
82+
____
7183
. Install [command]``podman``.
84+
7285
. Authenticate against the {suse} Registry using the SCC credentials:
7386
7487
+
@@ -79,9 +92,14 @@ set +o history
7992
echo SCC_MIRRORING_PASSWORD | podman login -u "SCC_MIRRORING_USER" --password-stdin registry.suse.com
8093
set -o history
8194
----
95+
96+
+
97+
8298
. Create a [path]``/tmp/ptf-images`` temporary file with the URL of the PTF images, one per line.
8399
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.
100+
84101
+
102+
85103
[source,shell]
86104
----
87105
SCC_USERID=aXXXX
@@ -100,10 +118,19 @@ for image in `cat /tmp/ptf-images`; do
100118
done
101119
podman save -o /tmp/ptf-images.tar `cat /tmp/ptf-images`
102120
----
121+
122+
+
123+
103124
. Transfer the [path]``/tmp/ptf-images.tar`` images archive on the server to patch.
104125
126+
____
127+
128+
105129
.Procedure: Loading the images on the server to patch
130+
[role=procedure]
131+
____
106132
. Ensure the [path]``ptf-images.tar`` file is available on the server.
133+
107134
. Load the images from the archive:
108135
109136
+
@@ -112,5 +139,10 @@ podman save -o /tmp/ptf-images.tar `cat /tmp/ptf-images`
112139
----
113140
podman load -i ptf-images.tar
114141
----
142+
143+
+
144+
115145
. Install the PTF using `mgradm support ptf podman` as would be done on a connected machine.
116146
Because the images are already loaded they will not be pulled.
147+
148+
____

0 commit comments

Comments
 (0)