Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

If the SCS environment is ever expected to be offline or air-gapped in the future, please 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:

These instructions assume Swarm packages are unzipped to /root/datacore.

  1. Install the EPEL release.

    1. Download the latest EPEL package.

      curl -fLO https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
    2. Install the downloaded RPM.

      yum install -y epel-release-latest-7.noarch.rpm
  2. If running Red Hat, enable the server extras repository.

    subscription-manager repos --enable=rhel-7-server-extras-rpms
  3. Copy '/root/datacore/Swarm-<version>/SCS/podman-packages-scs-<version>.tar and place it into the folder ‘/root/datacore’.

    cp /root/datacore/Swarm-<version>/SCS/podman-packages-scs-<version>.tar /root/datacore/
  4. Extract the file ‘podman-packages-scs-<version>.tar’.

    tar xvf podman-packages-scs-<version>.tar

    Note:
    This creates a folder ‘podman_packages’ under the ‘/root/datacore/’ folder.

  5. Add a new local repo at '/etc/yum.repos.d/podman.repo' with the below content:

    [podman]
    name=Dependencies for install podman 3.0.1
    baseurl=file:///root/datacore/podman_packages
    enabled=true
    gpgcheck=0
  6. Enable the new Podman repo.

    • CentOS (no additional steps are required)

      yum repolist enabled
    • Red Hat

      yum install -y yum-utils
      yum-config-manager enable podman.repo
      yum repolist enabled
  7. Verify Podman is listed as an enabled repo.

  8. Import the GPG key if needed.

    rpm --import RPM-GPG-KEY
  9. Install the SCS build.

    yum -y install swarm-scs-<version>.el7.x86_64.rpm
  10. Check the scsctl help command to verify the SCS is installed.

    usage: scsctl [-v | --info-log | --debug-log | --trace-log] 
                  [--user USER | --token TOKEN] 
                  options: ... 
    Provides basic control and visibility into the Platform service. 
    
    optional arguments: 
      --user USER    User name and (optionally) password. 
                    If password is included, then this must be in the form "{user_name}:{password}" 
                    (default: None) 
      --token TOKEN  Authentication token. (default: None) 
      
    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 Platform API. 
        backup       Manages backing up and restoring the Platform service. 
        diagnostics  Performs diagnostics on the Platform server setup. 
        init         Utilities for setting up a Swarm environment. 
        license      Manages the license for this Swarm ecosystem installation. 
        repo         Manages the Platform 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 Platform API service at 172.16.33.10:8095. 
    Please ensure the service is up and running.
  • No labels