Fix the ports list, volumes and air-gapped install after DB split (#4417)

Co-authored-by: Ornela Marić <[email protected]>

Author: cbosdo

CHANGELOG.md

@@ -1,3 +1,4 @@
+- Fix volumes, ports and air-gapped install after database split
 - Added troubleshooting section for mass duplicate machine_id
 - Improved recommendation in Large Deployments Guide
   (bsc#1252723)

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

@@ -11,34 +11,29 @@ endif::[]
 
 Air-gapped deployment refers to the setup and operation of any networked system that is physically isolated from insecure networks, especially the internet. This type of deployment is commonly used in high-security environments such as military installations, financial systems, critical infrastructure, and anywhere sensitive data is handled and must be protected from external threats.
 
-You can easily deploy container images using [systemitem]``Podman``, [systemitem]``Docker``, or [systemitem]``Skopeo`` on a machine with internet access. 
+You can easily pull container images using [systemitem]``Podman`` or [systemitem]``Docker`` on a machine with internet access. 
 
 .Procedure
-. Pull the desired image, then save the image as a [literal]``tar`` archive. 
+. Pull the desired images, then save the images as a [literal]``tar`` archive. 
 For example:
 +
 .Podman
 ----
-podman pull registry.opensuse.org/uyuni/server:latest
-podman save --output server.tar registry.opensuse.org/uyuni/server:latest
+podman pull registry.opensuse.org/uyuni/server:latest registry.opensuse.org/uyuni/server-postgresql:latest
+podman save --output images.tar registry.opensuse.org/uyuni/server:latest registry.opensuse.org/uyuni/server-postgresql:latest
 ----
 +
 .Docker
 ----
-docker pull registry.opensuse.org/uyuni/server:latest
-docker save --output server.tar registry.opensuse.org/uyuni/server:latest
+docker pull registry.opensuse.org/uyuni/server:latest registry.opensuse.org/uyuni/server-postgresql:latest
+docker save --output images.tar registry.opensuse.org/uyuni/server:latest registry.opensuse.org/uyuni/server-postgresql:latest
 ----
 +
-.Skopeo
-----
-skopeo copy docker://registry.opensuse.org/uyuni/server:latest docker-archive:server.tar:registry.opensuse.org/uyuni/server:latest
-----
-+
-. Transfer the resulting [filename]``server-image.tar`` to the Server container host and load it using the following command:
+. Transfer the resulting [filename]``images.tar`` to the Server container host and load it using the following command:
 +
 .Load the server image
 ----
-podman load -i server.tar
+podman load -i images.tar
 ----
 
 === Deploy {productname} on {opensuse} {tumbleweed}
@@ -51,7 +46,7 @@ User should make the needed RPM available on the internal network. That can be d
 ====
 
 .Procedure: Install {productname} on {opensuse} {tumbleweed} in Air-gapped
-. Install {opensuse} {tumbleweed.
+. Install {opensuse} {tumbleweed}.
 . Update the system.
 . Install tools packages and image packages (replace $ARCH$ with the correct architecture):
 

modules/installation-and-upgrade/pages/container-management/persistent-container-volumes.adoc

@@ -51,7 +51,7 @@ The following  volumes are stored under the **Podman** default storage location
 | [path]``/var/lib/salt``
 
 | **var-pgsql**
-| [path]``/var/lib/pgsql``
+| [path]``/var/lib/pgsql/data``
 
 | **var-pgsql-backup**
 | [path]``/var/lib/pgsql-backup``
@@ -129,9 +129,6 @@ The following  volumes are stored under the **Podman** default storage location
 | **etc-sysconfig**
 | [path]``/etc/sysconfig``
 
-| **etc-tls**
-| [path]``/etc/pki/tls``
-
 | **etc-postfix**
 | [path]``/etc/postfix``
 
@@ -141,6 +138,17 @@ The following  volumes are stored under the **Podman** default storage location
 |===
 
 
+.Persistent Volumes: **run/**
+[cols="name,directory"]
+|===
+|Volume Name | Volume Directory
+
+| **run-salt-master**
+| [path]``/run/salt/master``
+
+|===
+
+
 
 == Proxy
 

modules/installation-and-upgrade/pages/network-requirements.adoc

@@ -175,6 +175,7 @@ Opening these ports allows external network traffic to access the {productname}
 The client initiates the connection, and it stays open to receive commands from the Salt master.
 | 4506        | TCP      | salt       | Required to accept communication requests from clients.
 The client initiates the connection, and it stays open to report results back to the Salt master.
+| 5432        | TCP      | PostgreSQL | Required to access the reporting database.
 | 5556        | TCP      | Prometheus | Required for scraping Taskomatic JMX metrics.
 | 5557        | TCP      | Prometheus | Required for scraping Tomcat JMX metrics.
 | 9100        | TCP      | Prometheus | Required for scraping Node exporter metrics.