Swarm Storage UI Installation

This section describes how to install the Swarm Storage UI. No additional installation is required to use the legacy Admin Console (http://{cluster}:90).

See also Storage UI Release Notes and Swarm Storage UI (usage guide).

System Requirements

Network

The system where the Storage UI is installed must have direct access to the Swarm Storage VLAN.

Adjust firewall rules to allow the direct access required:

  • Swarm Storage nodes (port 91 by default)

  • Elasticsearch nodes (port 9200 by default).

Swarm

Swarm Storage must be running, with additional configuration to enable the trend charts to display data:

Browser

The Storage UI requires a JavaScript-enabled internet browser.

Info

Use the most recent versions of Firefox and Chrome for conducting test and development.

Installing the Storage UI

The Swarm UI supports different installation methods, depending on where it is installed. The best practice is that install Storage UI where a Content Gateway is implemented.

Info

The UI defaults to using port 91. If the bind port is changed to anything other than 91, users need to specify it when logging in:
{host}:{custom-port}

Installing on Content Gateway

The Storage UI installs on a server running the Content Gateway, and it is the recommended implementation. To add the UI to a server running Gateway:

  1. Locate the Storage UI RPM in the Swarm bundle.

  2. Copy the UI rpm to the directory where the Gateway was installed, and run the following:  

    yum install caringo-storage-webui-{version}.rpm
  3. To access the UI, browse to:

    http://{hostname}/_admin/storage

Installing on CSN 8.3

See Scenarios for Swarm UI for how to add Storage UI under different CSN usage scenarios.

Upgrading the Storage UI

Follow this sequence according to the guidance in the Storage UI Release Notes to upgrade the Storage UI:

  1. As needed for this release, complete the upgrades of Swarm components in this order:

    1. Swarm CSN Platform Server

    2. Swarm Storage UI

    3. Installing Elasticsearch (for S3 and https://perifery.atlassian.net/wiki/spaces/DOCS/pages/2443813497) - Create a new feed, allow it to finish, then make it Primary.

    4. Content Gateway Release Notes

  2. Copy the UI rpm to the directory where the Gateway was installed, and run the following: 

See Troubleshooting UI Upgrades.

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