Run the Swarm Cluster Services (SCS) Initialization Wizard

By Bala Harish A(AC)
4 min

Run the initialization wizard once the installation is complete.

Important

  • 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:

  1. Run the SCS initialization wizard with default settings.

    scsctl init wizard --allow-all-system-updates

Note

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

  • It is recommended that you take a snapshot of the SCS VM (if applicable) before performing the init wizard.

Warning

Running the init wizard step again after it has been attempted is highly likely to result in system corruption.

If this corruption occurs, the user needs to either revert to the snapshot before the init wizard step (if available), or perform a system reset and re-initialize SCS.

  1. 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

  2. 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

Note

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.

When configuring SCS for use with an existing storage cluster, you must enter the existing cluster administrator password. Failure to do so will prevent SCS from contacting or administering the existing cluster.

  1. Select the internal network interface (see Network Planning for detail); this interface contains the private subnet restricted to Swarm use.

    Running step [3/36]: Choose Swarm-internal interface Please specify the network interface that will be used for internal Swarm operations: lo ens192 > ens224 ┌── preview ──────────────────────────────────────────────────────────────────────────────────────┐ │ 3: ens224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 │ │ link/ether 00:50:56:83:3a:1e brd ff:ff:ff:ff:ff:ff │ │ inet 192.168.9.10/24 brd 192.168.9.255 scope global noprefixroute ens224 │ └─────────────────────────────────────────────────────────────────────────────────────────────────┘

  2. 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.

    Running step [4/36]: Ensure NetworkManager is up Running step [5/36]: Detect external interface Running step [6/36]: Detect network mode Running step [7/36]: Define Swarm-internal network The internal interface requires a *static* IP address to be defined on it! It looks like your internal interface is already configured with an IP address: 192.168.9.10/24 Do you wish to continue to use this address and netmask? [Y/n] : Y

  3. The SCS wizard verifies the network interface definition matches the configured values.

    Running step [8/36]: Ensure Swarm-internal network is defined An existing network definition for interface ens224 has been found. It will be overwritten! Running step [9/36]: Ensure Swarm-internal network is up

  4. The wizard performs the following actions:

    1. Generates internal SCS component references.

      Running step [10/36]: Generate platform group name Running step [11/36]: Generate network boot group name

    2. Verifies podman is up-to-date and available for use.

      Running step [12/36]: Ensure up-to-date version of podman (may take a while) Running step [13/36]: Enable API access to podman Running step [14/36]: Establish connection to podman API

    3. Starts loading SCS containers to podman into the runtime environment.

      Running step [15/36]: Load Swarm Cluster Services container images (may take a while) Loading image: quay.io_coreos_etcd-v3.3 Loading image: swarm-platform-pxelinux-<version> Loading image: swarm-platform-full-<version> Loading image: swarm-platform-tftp-<version> Running step [16/36]: Make networking survive firewall restarts Running step [17/36]: Prepare etcd data volume Running step [18/36]: Prepare API repo volume

    4. Sets up the automatic launch of SCS services on system startup.

      Running step [19/36]: Build pod definition for SCS Linux services  Running step [20/36]: Enable systemd management of SCS Linux services  Running step [21/36]: Launch the API service (may take a while)

    5. Secures the SCS.

      Running step [22/36]: Lock down network access to Swarm Cluster Services (may take a while) Running step [23/36]: Enable TFTP via podman bridge  Running step [24/36]: Enable NAT from internal network 

    6. Performs the initial configuration of SCS services.

      Running step [25/36]: Enable syslog from internal network  Running step [26/36]: Enable telemetry access from internal network Running step [27/36]: Create global platform group  Running step [28/36]: Set known default Swarm Cluster Services settings (may take a while) Running step [29/36]: Create network booting group  Running step [30/36]: Pre-register network booting instance  Running step [31/36]: Set known default Swarm Cluster Services network settings Running step [32/36]: Configure NTP server  Running step [33/36]: Configure syslog server  Running step [34/36]: Ensure SSH access Running step [35/36]: Re-launch the API service (may take a while) Running step [36/36]: Show the next steps after this wizard

    7. Shows “next steps” to customize the installation for site-specific needs.

        ********************************************************************************    Congratulations, your Swarm Cluster Services server is now initialized!    Please use the following command to learn about adding Swarm storage software:      > scsctl repo component add help   Once Swarm storage has been added, please run the following to complete your installation:      > scsctl diagnostics config scan_missing      > scsctl init dhcp   To learn about installing a Swarm license:      > scsctl license add help    If you need this list again, please run:      > scsctl init wizard --next-steps    ******************************************************************************** 

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

Next, Add the Swarm Storage Component.

Related content

© DataCore Software Corporation. · https://www.datacore.com · All rights reserved.