Deployment Process

Following is a high-level view of the nature and order of tasks that need to be performed for a full-stack Swarm implementation.

Phase 1: Prepare Environment

The work to prepare the environment must be completed before adding any Swarm components:

• Rack and stack hardware designated for Swarm, replacing and upgrading as needed. (See Hardware Setup.)

• Upgrade firmware to latest versions:

  • All servers

  • All disk controllers

  • All disk drives

• Configure networking and switches (see Network Infrastructure), including the following:

  • VLAN configuration

  • IGMP snooping disabled (or IGMP querier implemented)

• Configure IPMI management.

• Provide access for the storage cluster to phone home. (See Cluster Health Report.)

• Ensure the servers and base operating systems meet the Swarm system requirements. (See Hardware Requirements for Storage and Hardware Requirements for Elasticsearch Cluster.)

• Configure IPMI (remote server management)

• Complete licenses and agreements
  

  • Obtain any needed storage capacity and capability licenses from DataCore. (See Licensing Swarm.)

  • A user in the organization must register the Red Hat license and accept the EULA if installing or updating RHEL.

  • Accept the DataCore EULA.

Phase 2: Platform Server and Storage Cluster

Swarm Platform Server is installed and configured first, so that it can install Storage nodes on the designated hardware.

• Install Platform Server. (See Legacy Platform Implementation.)

• Configure Platform Server to integrate with the environment.

• Configure Platform Server to boot the current version of Swarm Storage.

• Boot the Storage nodes and configure the cluster-wide settings. (See Configuring Swarm Storage.)

• Install the Swarm Storage UI. (See Swarm Storage UI Installation.)

• Verify that the storage cluster is operational: read, write, and delete test objects

• Optional: Install the open-source components to make use of Swarm's exports to Prometheus. (See Prometheus Node Exporter and Grafana.)

Phase 3: Elasticsearch

Install and configure an Elasticsearch cluster on designated hardware, providing the Storage cluster its search and metrics capabilities.

• Base install the chosen operating system (RHEL/Centos 7.9).

• Install Elasticsearch nodes on designated hardware. (See Elasticsearch Implementation.)

• Configure Elasticsearch based on DataCore recommendations. (See Configuring Elasticsearch.)

• Create a Search feed to populate the Elasticsearch metadata index. (See Managing Feeds.)

• Configure Elasticsearch Curator and Swarm Metrics. (See /wiki/spaces/DOCS/pages/2443810001.)

Phase 4: Content Gateway

Install and configure Content Gateways, which provide the primary access to the Storage cluster.

• Base install the chosen operating system (RHEL/Centos 7.9).

• Install the Content Gateway. (See Content Gateway Implementation.)

• Install the Content UI. (See Content UI Installation.)

• Configure basic gateway setup for verification and initialization of primary domain. (See Gateway Configuration and Configuring Swarm Storage for Gateway.)

• Verify that the Gateway is operational: read, write, and delete test objects via the Content UI, S3, and SCSP.

• Create the initial domains, with policy definitions. (See Gateway Access Control Policies.)

Phase 5: Swarm Clients

As fits with the implementation plan, extend access to Swarm storage by installing one or more Swarm client applications, such as the following:

• SwarmFS Implementation

• FileFly

Phase 6: Post-installation

• Conduct performance measurement and tuning.

• Test and debug third-party/custom applications and integration.

• Train administrators and staff.