Overview

For more information about Swarm Gateway, its concepts, and operations, see https://perifery.atlassian.net/wiki/spaces/public/pages/2443816622.

Prerequisites

• RHEL/CentOS 7 or RHEL/Rocky Linux 8 Setup

• Latest Swarm bundle package

Setup Linux for Cloud Gateway

Below is an example deployment for the site.

Install Swarm Gateway

1. Create a user group.

   groupadd clusteradmins

2. Add a new user.

   adduser admin -g clusteradmins -p datacore passwd admin

3. Update Linux and install EPEL.

   yum -y update yum -y install epel-release

4. Install NTP server and verify NTP starts on system boot.

5. Configure the firewall to allow Swarm Gateway.

6. Restart the firewall service.

7. Add Swarm Gateway firewall rule (permanent)

8. Reload the firewall service.

9. Unzip the Swarm bundle package.

10. Get the latest gateway and UI RPMs from the downloaded Swarm bundle.

11. Install Swarm RPM public key included with the distribution bundle.

12. Install Cloud Gateway components.

13. Complete the IDSYS document for PAM user authentication.

14. Complete policy document for access control.

15. Install Gateway WebUI.

16. Edit the configuration file.

    1. Set adminDomain for the administrative domain name to be created. It is recommended to always set a unique name for each Swarm cluster to prevent replication collision between the Source and Target Swarm Cluster when using replication feeds. Set a unique name for each Swarm cluster to prevent replication collision.

    2. Set hosts for the storage cluster nodes (IP address of storage nodes).

    3. Set indexerHosts to Elasticsearch Servers (IP address of Elasticsearch nodes).

    4. Enable S3.

    5. Enable Cluster Admin on the gateway server to allow usage of the Swarm Storage UI.

    6. Set Management Port to 91. The admin user and password must be the same as configured in SCS.

       1. Set managementUser to the same value as admin.username

       2. Set managementPassword to the same value as admin.password

    7. Enable metering.

Below is a sample Gateway configuration file in its entirety.

Cluster Initialization

The Gateway must be initialized to guarantee a proper runtime environment once the configuration is complete. This guarantees the administrative domain exists within the storage cluster and also secures all plaintext passwords entered into the configuration files.

1. Verify Gateway is not running.

2. Perform the initialization of the environment.

3. Start CloudGateway and verify the gateway service is running on system boot once initialization is successfully completed.