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 16 Next »

Adding the Software

Add the storage software bundle for the cluster.

Important

Use the tarball ending in .TGZ.

The .ZIP and .RPM files are used for Swarm deployments without SCS.

scsctl repo component add -f swarm-scs-storage-<version>.tgz

Prompting for Settings

Certain component settings ship without defaults, as these settings are unique to the environment in which Swarm runs. The CLI prompts for the component values while adding the software. If any of these settings are skipped, the CLI prompts again during the finalization of Swarm configuration settings.

disk.encryptNewVolumes

This setting enables encryption at rest. It is recommended to avoid encryption at rest unless specified by DataCore Support team. Contact DataCore Support team for configuration assistance after SCS installation and configuration if use of encryption at rest is desired. Choose Later at the group and/or instance level to skip this step.

disk.volumes

This setting governs which volumes on the chassis Swarm storage will use. Enter all when prompted for the disk.volumes setting’s default value unless instructed by DataCore.

cip.multicastEnabled

Available since: Swarm 15.0

This setting controls the use of multicast for Swarm Storage node intercommunication. Prior to Swarm v15.0, multicast was required. For clusters already using multicast, it is advised to continue using it as changing the setting value requires a full, non-rolling cluster reboot. New installations may require a special network configuration to support multicast. Therefore, do not use multicast for new installations. If not sure about enabling multicast, contact DataCore Support.

Prompting for the Cluster/Group Name

Once the software is added, provide a group name when prompted to define a cluster for Swarm Storage nodes.

Warning

If you are deploying an SCS with an existing storage cluster, this group value MUST be the same as the cluster.name value of the existing storage cluster.

The failure causes an initialization error for the cluster on boot-up (the Persistent Settings Stream stores the cluster.name and does not match the cluster name stored in SCS) and requires resetting and re-initializing the SCS. https://perifery.atlassian.net/wiki/spaces/public/pages/1223491694/SCS+CLI+Commands#scsctl-system-reset

The group name is used as the cluster name. The group description is optional and for human administrator purposes.

Example:

$> scsctl repo component add -f swarm-scs-storage-15.0.0.tgz
Missing setting: storage/disk.volumes
Missing setting: storage/cip.multicastEnabled

The following setting(s) require a default value:

 disk.volumes [type: str] (Required. Specifies the volume storage devices for Swarm to use. Valid entries: all, or a space-separated list of Linux volume identifiers, such as /dev/sda, /dev/sdb. all (recommended) is required for hot plugging and lets Swarm to use all volumes larger than disk.minGB. If a node is shut down longer than disk.obsoleteTimeout, all of its volumes are stale and cannot be used unless you force a volume remount by adding the :k (keep) policy option modifier. To specify the size, add a modifier with units: vols1:100m vols2:250g.):
 all

 cip.multicastEnabled [type: bool] (Whether or not multicast should be used for communication within Swarm.):
 False

added: storage - 15.0.0 (15.0.5)

 Please enter a name for the group (FQDN format encouraged) - Required to be able to boot instances of "storage":
 a.storage.cluster


 Please enter a description for the group (purpose, etc). [OPTIONAL]:
 Store it all!

group added

=============================================================================================================================================================================================================================================
Please run the following command to check for missing config in the new group:
  > scsctl diagnostics config scan_missing
=============================================================================================================================================================================================================================================

  • No labels