Run the Swarm Cluster Services (SCS) Initialization Wizard

Run the initialization wizard once the installation is complete.

SCS requires RHEL/CentOS 7 or RHEL/Rocky Linux 8 installed.
Use the --debug-log flag to see debug logging on the screen:
scsctl init wizard --allow-all-system-updates --debug-log

Refer to the following steps to run the SCS initialization wizard:

Run the SCS initialization wizard with default settings.
scsctl init wizard --allow-all-system-updates

Before running scsctl init wizard, validate that no HTTP(S)_PROXY has been set, by running env | grep -i http.

Provide a Swarm site name, which is a human-oriented name used to identify the particular Swarm site within the overall organization. The scs-lab1.datacore.internal example used below generates other default names later. A DNS-style hostname format is recommended (where the value does not need to be DNS-resolvable).
Running step [1/36]: Set site name Please enter a name for this Swarm site. It should be unique within your organization: scs-lab1.datacore.internal
Provide an administrative password for Swarm, which the Swarm cluster and SCS both use internally.
Running step [2/36]: Set administrative password Please enter an administrative password

For security purposes, entered keystrokes will not be echoed back to the screen. Hence, enter the password carefully.

After entering the password, a confirmation prompt will ask for the password to be re-submitted; the two passwords must match each other.

Select the internal network interface (see Network Planning for detail); this interface contains the private subnet restricted to Swarm use.
Ensure the Swarm internal interface is correctly defined and running. Enter ‘Y’ to verify the internal network IP address and network mask if the network interface has been configured; otherwise, enter 'N' and provide the interface IP address and subnet mask when prompted.
The SCS wizard verifies the network interface definition matches the configured values.
The wizard performs the following actions:
1. Generates internal SCS component references.
2. Verifies podman is up-to-date and available for use.
3. Starts loading SCS containers to podman into the runtime environment.
4. Sets up the automatic launch of SCS services on system startup.
5. Secures the SCS.
6. Performs the initial configuration of SCS services.
7. Shows “next steps” to customize the installation for site-specific needs.

The basic setup of the SCS is complete. Continue by adding the Swarm Storage component.

Swarm Documentation