Versions Compared

Version Old Version 8 New Version 9
Changes made by

James Casey

Anjali Tyagi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added steps for upgrading from SCS 1.4 to 1.7.1

Directly upgrading from SCS 1.2 to SCS 1.3 is not supported, but this limitation is removed starting with SCS 1.4. Swarm supports upgrading from SCS 1.1, 1.2, or 1.3 to SCS 1.4 and booting from Storage bundle v15.0 with multicast disabled. Insert excerptSCS AdministrationSCS AdministrationnameBackup warningnopaneltrue

Upgrade Notes

  • Any version before SCS 1.4 cannot boot versions of Swarm storage that include the optional multicast feature (version 15.0 and later). This is due to changes required in SCS to properly support this feature.

  • Complete the SCS upgrade first if upgrading both SCS and Swarm Storage simultaneously. Then add the new Swarm Storage component to the SCS repo (using scsctl repo component add ...). During this process, scsctl will prompt as to whether or not to enable multicast for the storage cluster by asking to set a value for cip.multicastEnabled. Select True to enable the use of multicast (this matches the behavior of prior versions of Swarm), or False to disable it. If you are unsure which to choose, contact DataCore Support.

  • Installing a new Swarm Storage component version does not automatically activate the version for PXE booting; the new version must be explicitly activated. Run the below command and choose the new version to activate:

    Code Block
    scsctl storage software activate

...

Info

Info

A customer might see the below error in the output while upgrading to SCS 1.7 or above, but this is safe to ignore it.

Code Block
Running step [4/11]: Re-enable systemd management of SCS Linux services
  Disabling service "swarm-platform.service" for pod "swarm-platform"...
  Failed to disable services: b'Failed to execute operation: No such file or directory\n'
  Deleting service file for pod "swarm-platform": /etc/systemd/system/swarm-platform.service [exists: False, symlink: True]
  Retry: Disabling service "swarm-platform.service" for pod "swarm-platform"...

We would need some additional necessary steps to upgrade directly from SCS 1.4 to 1.7.1 under the following conditions:

  • The current instance is using static IP assignments for storage nodes, using the node.cfg template method.

  • The storage cluster supported by the current instance is running a version of CAStor that does not support direct IP assignment, a version of CAStor that does not include the setting, “network.useStaticAddresses”.

Info

When the above conditions are absent, upgrading SCS and the storage software will go smoothly as described above.

When these conditions are true, the upgrade process requires an additional couple of steps.

  • After SCS is upgraded to 1.7.1, the storage software must be upgraded to the most recent version or to any version that supports direct IP assignment and includes the “network.useStaticAddresses” setting.

  • After the new storage software version is activated, the storage cluster must be rebooted before any direct IP assignment is performed.

After these additional steps, the direct assignment of static IPs and the unsetting of the node.cfg templates can proceed as usual. The cluster gets rebooted again once that process is completed.