Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel1
outlinefalse
styledisc
typelist
printabletrue

Important

Important

CentOS 7 becomes EOL in June 2024, as a result, it will be required to migrate from CentOS7 to another distribution. DataCore has decided to standardize the Rocky Linux distribution, starting with v8. Therefore, this guide is intended to describe the process of migrating all the components running on CentOS 7 to Rocky Linux 8 (RL8).

Info

Info

This process is intended for Swarm platforms where SCS is the platform server. It is not intended for systems using CSN or for systems not running CentOS 7. The process for the Elasticsearch and Gateway components can be used, but as it requires upgrading to the latest versions of each component first, this may not be achievable with older systems. Please contact DataCore support before running this process on any older clusters.

...

  1. Upgrade SCS to the same version as the packages to be installed on RL8 or the OVA images. It is assumed that you are currently at v1.7.1-el7.
    If the existing SCS server is less than 1.7.1, perform the upgrade to 1.7.1. Full instructions for the upgrade can be found here.

  2. If static IP addresses were previously assigned before this migration, skip this step and proceed to the “boot/reboot” step (see step 3).

    1. Use case #1: Allow DHCP to assign IP addresses
      When the cluster nodes are rebooted, DHCP will assign an IP address to each node. If the nodes have already been booted with manually assigned IPs, the assigned IP addresses will remain the same. If IP addresses were not manually assigned, but existing DHCP leases are still in effect, then currently assigned IP addresses will remain the same. If existing DHCP leases have expired (or this is the first boot of the storage cluster), DHCP will assign IP addresses from the allocated pool in no particular order. When this use case is selected, proceed to the “Boot/reboot” step.

    2. Use case #2: Pre-assign an IP address to each storage node
      In this case, an IP address must be manually assigned to each storage node before it is rebooted. The procedure for manual assignment is fully explained in Configuring Swarm for Static IPs with Swarm Cluster Services (SCS)).
      The summary of the manual assignment procedure is:

      1. Get an instance list that provides a node ID to use in the next step.

        Code Block
        scsctl storage instance list
      2. Assign an IP address to each node.

        Code Block
        scsctl storage config set -d -i {chassis ID} "network.ipV4Address={your.static.address.here}"
    3. If the storage cluster was previously using static IP addresses defined in SCS 1.5 (or an earlier version), remove the customized node.cfg files for each storage node.

      Code Block
      scsctl storage config file unset -d -i {chassis ID} node.cfg
  3. Boot/reboot storage nodes.

  4. Create a support bundle. If you run an issue, please contact DataCore Support including the support bundle.

    Code Block
    languagebash
    cd /root/dist && ./updateBundle.sh
    cd /root && /root/dist/techsupport-bundle-grab.sh -U ${SWARM_ADMIN_USER} -A ${SWARM_PASSWORD}
  5. Create a backup of the SCS system configuration and Swarm software repo.

    Code Block
    mkdir /root/mig2rl8
    scsctl backup create -o /root/mig2rl8/scs_backup_full.YYYYMMDD.tgz

...

Configure the (new) RL8 SCS server

Info

Important

  • The version of SCS installed on the RL8 server must match the major.minor version that is running on the old C7 SCS server, but be aware there is a specific variant for RL8 (-el8).

  • Verify that the Backup (Swarm) interface is disconnected at the virtual machine level. This allows the configuration below to proceed using the same IP as the old C7 SCS instance, without creating an IP conflict.
    This is not necessary if you plan to use a different IP for the Backend Swarm network

...