Changes to file names.

Author: 0rnela

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

@@ -1,4 +1,4 @@
-= Migrating the {productname} Server to a Containerized Environment
+= {productname} Server Migration to a Containerized Environment
 ifeval::[{uyuni-content} == true]
 :noindex:
 endif::[]
@@ -62,14 +62,11 @@ After the migration, it will be necessary to manually update the DHCP and DNS re
 .Procedure: Initial preparation on the 4.3 server
 . Stop the {productname} services:
 +
-
 ----
 spacewalk-service stop
 ----
-
 . Stop the PostgreSQL service:
 +
-
 ----
 systemctl stop postgresql
 ----
@@ -84,14 +81,11 @@ The migration process will take care of the server installation.
 . Ensure that for [systemitem]``root`` an SSH key exists on the new {productnumber} server.
   If a key does not exist, create it with:
 +
-
 ----
 ssh-keygen -t rsa
 ----
-
 . The SSH configuration and agent should be ready on the new server for a passwordless connection to the 4.3 server.
 +
-
 [NOTE]
 ====
 To establish a passwordless connection, the migration script relies on an SSH agent running on the new server.
@@ -103,12 +97,10 @@ You will be prompted to enter the password for the private key during this proce
 . Copy the public SSH key to the {productname} 4.3 Server ([literal]``<oldserver.fqdn>``) with [command]``ssh-copy-id``.
   Replace [literal]``<oldserver.fqdn>`` with the FQDN of the 4.3 server:
 +
-
 ----
 ssh-copy-id <old server.fqdn>
 ----
 +
-
 The SSH key will be copied into the old server's [path]``~/.ssh/authorized_keys`` file.
 For more information, see the [literal]``ssh-copy-id`` manpage.
 +
@@ -129,8 +121,7 @@ For more information, see the [literal]``ssh-copy-id`` manpage.
 
 When planning your migration from {productname} 4.3 to {productname} 5.0, ensure that your target instance meets or exceeds the specifications of the old setup.
 
-This includes, but is not limited to, [literal]``Memory (RAM)``, [literal]``CPU Cores``, [literal]``Storage``, and [literal]``Network Bandwidth``.
-
+This includes, but is not limited to, memory (RAM), CPU Cores, Storage, and Network Bandwidth.
 
 .Procedure: Performing the Migration
 . This step is optional.
@@ -140,7 +131,6 @@ This tool simplifies creating the container storage and database volumes.
 
 ** Use the command in the following manner:
 +
-
 ----
 mgr-storage-server <storage-disk-device> [<database-disk-device>]
 ----
@@ -160,11 +150,9 @@ For more information, see xref:installation-and-upgrade:container-management/per
 . Execute the following command to install a new {productname} server.
   Replace [literal]``<oldserver.fqdn>`` with the FQDN of the 4.3 server:
 +
-
 ----
 mgradm migrate podman <oldserver.fqdn>
 ----
-
 . Migrate trusted SSL CA certificates.
 
 
@@ -180,7 +168,6 @@ Because {suse} does not install RPM packages in the container, the administrator
    For example, as [path]``/local/ca.file``.
 . Copy the file into the container with:
 +
-
 ----
 mgrctl cp /local/ca.file server:/etc/pki/trust/anchors/
 ----

modules/installation-and-upgrade/pages/container-management/updating-proxy-containers.adoc

@@ -1,4 +1,4 @@
-= Update Containers
+= Proxy Upgrade
 
 Before running the upgrade command, it is recommended to upgrade the [literal]``mgrpxy`` tool first.
 

modules/installation-and-upgrade/pages/container-management/updating-server-containers.adoc

@@ -1,7 +1,8 @@
-= Update Containers
+= Server Upgrade
 
 Before running the upgrade command, it is recommended to upgrade the [literal]``mgradm`` tool first.
 
+.Procedure
 . One can do so by running the following command:
 +
 ----