...
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Info |
---|
ImportantIf the SCS environment is ever expected to be offline or air-gapped in the future, follow the instructions for offline installation instead. Several dependencies must be put into place to support future upgrades. |
Refer to the following steps to install SCS RPM with Internet access:
Installation on Red Hat/Rocky Linux 8
For SCS installation on Red Hat/Rocky Linux 8, please skip to Installing SCS Software.
Preparing Red Hat/CentOS 7 System
Note |
---|
For SCS 1.7.1 and onward, Red Hat/CentOS 7 support is deprecated and will be removed in the next release. SCS 1.7.1 should only be installed on these systems as an upgrade to an existing SCS installation, and solely for the purpose of generating a full backup for migrating to a newer supported operating system. |
Info |
---|
These instructions assume Swarm packages are unzipped to the Swarm zip file- downloaded from here- that looks like |
When installing on RHEL, the best practice is to run the following command first of all:
Code Block sudo subscription-manager refresh
Install the EPEL release.
Download the latest EPEL package.
Code Block language bash curl -fLO https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
Install the downloaded RPM.
Code Block language bash yum install -y epel-release-latest-7.noarch.rpm
If running Red Hat, enable the server extras repository.
Code Block language bash subscription-manager repos --enable=rhel-7-server-extras-rpms
Copy '/root/datacore/Swarm-<version>/SCS/podman-packages-scs-<version>.tar’ and place it into the folder ‘/root/datacore’.
Code Block cp /root/datacore/Swarm-<version>/SCS/podman-packages-scs-<version>.tar /root/datacore/
Extract the file ‘podman-packages-scs-<version>.tar’.
Code Block language bash tar xvfcd /root/datacore/ tar xvf podman-packages-scs-<version>.tar
Note
This creates the ‘podman_packages’ directory under the ‘/root/datacore/’ directory. This location is used in the next step to set up the podman repo.
Add a new local repo.
Code Block language bash printf "[podman] name=Dependencies for install podman 3.0.1 baseurl=file:///root/datacore/podman_packages enabled=true gpgcheck=0" > /etc/yum.repos.d/podman.repo
Enable the new Podman repo.
CentOS (no additional steps are required)
codelanguage bash yum repolist enabled
Red Hat
Code Block language bash yum install -y yum-utils yum-config-manager enable podman.repo yum repolist enabled
Verify Podman is listed as an enabled repo.Example output:
Code Block # yum repolist enabled repo id repo name status base/7/x86_64 CentOS-7 - Base 10,072 epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 13,768 extras/7/x86_64 CentOS-7 - Extras 518 podman Dependencies for install podman 3.0.1 12 updates/7/x86_64 CentOS-7 - Updates 5,283 repolist: 29,653
Change back to the /root/datacore/Swarm-<version>/SCS/ directory
Code Block cd /root/datacore/Swarm-<version>/SCS/
Import the GPG key if needed.
Code Block rpm --import RPM-GPG-KEY
Installing SCS Software
Install the SCS RPM.
Red Hat/CentOS 7:Code Block yum -y install swarm-scs-<version>.el7.x86_64.rpm
Red Hat/Rocky Linux 8:
Code Block yum -y install swarm-scs-<version>.el8.x86_64.rpm
Verify SCS is installed properly. The
...
message about being unable to connect to the Swarm Cluster Services API is expected at this step and is not cause for concern.
Code Block scsctl help
Example output:
Code Block language
...
none usage: scsctl [-v | --info-log | --debug-log | --trace-log] options: ... Provides basic control and visibility into Swarm Cluster Services (SCS). output options: These options affect the way output is displayed. -v, --verbose Increase output verbosity (ex: -v, -vv, -vvv). Verbose output is always sent to stdout. (default: None) --info-log Set info-level verbosity (equivalent to -v). (default: None) --debug-log Set debug-level verbosity (equivalent to -vv). (default: None) --trace-log Set trace-level verbosity (equivalent to -vvv). (default: None) subcommands: Which action you wish to perform. To get detailed help, add 'help' to the end. For example: 'scsctl auth help' options: auth Manages persisted credentials for contacting the Swarm Cluster Services API. backup Manages backing up and restoring Swarm Cluster Services. diagnostics Performs diagnostics on the SCS server setup. init Utilities for setting up a Swarm environment. license Manages the license for this Swarm ecosystem installation. repo Manages the Swarm Cluster Services repository. The repository contains installed component versions and other third-party software. system Performs administrative operations on the system. help Outputs this help and exits. ERROR: Cannot connect to the Swarm Cluster Services API service at 172.30.4.103:8095. Please ensure the service is up and running.
Tip |
---|
Next, Run the Swarm Cluster Services (SCS) Initialization Wizard. |