Table of Contents |
---|
How to Deploy
Enlist the chassis and deploy them for management and orchestration to install Swarm Storage. Swarm Platform supports any chassis equipped with IPMI 2.0 or newer.
Power on each chassis planned as a Swarm storage node. Each chassis PXE boots from the Platform server, enlists itself with Platform, and shuts itself down.
List the chassis currently available to run Swarm after enlistment completes:
Code Block language bash platform list nodes
The number of chassis returned is the value to use in the next step for
-n
, unless some are kept in reserve.Deploy Swarm Storage to the chassis being managed by Platform:
Code Block language bash platform deploy storage -v {#.#.# Version of Swarm Storage} -c {Path to cluster.cfg} -n {# Nodes To Deploy}
At this point, the Platform will power on each of the nodes twice. The first power on is commissioning, involving hardware interrogation and other tasks, which ends with a power off. The second power on is to boot Swarm Storage on the chassis.
Once Swarm is running, deploy Content Gateway, or, if not using Content Gateway, proceed to Deploying a Proxy.
Code Block language bash platform deploy proxy -b {Path to Service Proxy Bundle zip}
...
When using manual power control, you need to use CLI commands to know when to power on each chassis, so use the -y <system-id>
flag, rather than -n <# of nodes>
.
Run the deploy command for an individual chassis, using the
--manual
flag and the-y <system-id>
flag.To know when to turn the chassis on, use the
--state Commissioning
flag:Code Block language bash platform list nodes --state Commissioning
As soon as the chassis appears in the list, you can power on the chassis.
After you power on the chassis, it will go through commissioning and then power itself off.
To know when to power on the chassis for the final time (to deploy the Storage software), use the
--state Deploying
flag:Code Block language bash platform list nodes --state Deploying
As soon as the chassis appears in the list, you can power on the chassis for the final time.
Info | ||||||
---|---|---|---|---|---|---|
title | TipYou can also use the following CLI command to follow the chassis through its lifecycle stages.
|
...
Code Block | ||
---|---|---|
| ||
platform add bonding-mode --default-bonding-mode "<bonding-mode-to-use>" |
Info |
---|
NoteThis setting is not retroactive. Changing the default bonding mode only applies to the chassis that are deployed after the default mode is set. |
Use a mode for the Linux bonding driver that is tested and supported for Swarm:
active-backup | Active-backup |
---|---|
balance-alb | (Platform default) Adaptive load balancing |
802.3ad | IEEE 802.3ad |
Info | |
---|---|
title | Bonding modesSee Network Devices and Priority for details on bonding modes. |
To use a different bonding mode when deploying an individual chassis, override the default value by using the --bondingMode
flag:
...
To assign a chassis to a subcluster, use the assign
command:
Add to subcluster
Code Block | ||||
---|---|---|---|---|
| ||||
platform subcluster assign -y <system-id> --subcluster <subcluster-name> |
Info | |
---|---|
title | NoteAssignment is not immediate. Allow time for every node on the chassis to be migrated to the new subcluster. |
To review the subcluster assignments, use the list
command:
List subclusters
Code Block | ||||
---|---|---|---|---|
| ||||
platform subcluster list |
Child pages (Children Display) |
---|