Install and configure Symphony 4.1 on all the hosts

These steps are described in detail in the installation documention for a new cluster. However, do not follow all of the steps as if you are installing a cluster on new hosts. The following steps describe how the installation is different when you have an existing cluster.

  1. Plan and prepare for installation. You must customize the installation to avoid conflicts with the original cluster.
  2. Install the package on the master host and configure but do not start or test. Consider the following:
    • Do not set up a new database, you will reuse the existing database to preserve the original data.

    • License the cluster as usual.

    • On Linux, you need to specify a different installation directory, you will probably install with the --prefix option.

    • On Linux, set up automatic startup as usual. This will break the feature in the original cluster.

    • On Linux, run egosetsudoers.sh -p.

    • On Linux, join the cluster as usual.

    • On Linux, define the host as a management host, as usual.

    • On Windows, specify a different installation directory and different base port, specify cluster ID, and choose advanced workload execution mode.

  3. Install the package on the the remaining management hosts and configure but do not start or test. Consider the following:
    • On Linux, you probably need to specify a different installation directory, you will probably install with the --prefix option.

    • On Linux, set up automatic startup as usual. This will break the feature in the original cluster.

    • On Linux, run egosetsudoers.sh -p.

    • On Linux, join the cluster as usual.

    • On Linux, define the host as a management host, as usual.

    • On Windows, specify a different installation directory and different base port, specify cluster ID, and choose advanced workload execution mode.

  4. Install the package on the compute hosts and configure but do not start or test. Consider the following:
    • On Linux, you probably need to specify a different installation directory, you will probably install with the --prefix option.

    • On Linux, set up automatic startup as usual. This will break the feature in the original cluster.

    • On Linux, run egosetsudoers.sh -p.

    • On Linux, join the cluster as usual.

    • On Windows, specify a different installation directory and different base port, specify cluster ID, and choose advanced workload execution mode.

Enable master host failover later on, after you have the new cluster running.