Page Comparison

...

1. 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.

2. 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.

3. 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}

4. At this point, the Platform will power powers 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.

5. 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}

...

1. Run the deploy command for an individual chassis, using the  --manual flag and the -y <system-id> flag.

2. To know when to turn the chassis on, use the --state Commissioning flag:

   Code Block
   language bash
   platform list nodes --state Commissioning

3. As soon as the chassis appears in the list, you can power on the chassis.

4. After you power on the chassis, it will go goes through commissioning and then power powers itself off.

5. 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

6. As soon as the chassis appears in the list, you can power on the chassis for the final time.

platform list nodes -y <system-id> --short

Changing Network Bonding Mode

By default, the Platform server will boot boots all Storage chassis using the "balance-alb" bonding mode. You can modify the default bonding mode to use for future deployments by using the following command:

...