2.8 Upgrading a PlateSpin Orchestrate 2.0.2 or 2.1 High Availability Configuration

This section provides the steps you need to follow to upgrade a PlateSpin Orchestrate 2.0.2 or 2.1 environment to a PlateSpin Orchestrate 2.5 high availability configuration. Use the following steps for the upgrade:

  1. Using the high availability manager (such as Heartbeat 2) , shut down the PlateSpin Orchestrate service.

  2. Manually bind the cluster IP address using the following command:

    ip addr add {CIDR_IP_ADDRESS} dev {Ethernet Device}

  3. Manually start a PlateSpin Orchestrate Server instance on the first node in the cluster using the following command:

    /etc/init.d/novell-zosserver start

  4. Manually stop the instance with snapshot. See Section 2.1.3, Snapshotting the Existing Server Installation for more information.

  5. Manually unbind the IP address using the following command:

    ip addr del {CIDR_IP_ADDRESS} dev {Ethernet Device}

  6. Upgrade the RPMs on the first node (the one you started in Step 3) of the cluster. For more information, see Section 2.1.4, Upgrading the PlateSpin Orchestrate Server Packages.

  7. Run the configuration script. For more information, see Running the PlateSpin Orchestrate Product Configuration Script to Configure the Upgraded Packages.

  8. Manually bind the IP address using the following command:

    ip addr add {CIDR_IP_ADDRESS} dev {Ethernet Device}

  9. Start the Orchestrate Server instance on the upgraded node (see Step 3 and Step 6).

  10. Verify the upgraded server state by attempting to connect to the server (with the Development Client, for instance).

  11. Manually stop the following services using the /etc/init.d/<service_name> stop command:

    • novell-zosserver

    • apache2

    • novell-gmond

    • novell-gmetad

    where <service_name> is novell-zosserver, novell-gmond, novell-gmetad, or apache2, and stop is the action you want to perform.

    IMPORTANT:Do not snapshot to stop the server instance.

  12. Manually unbind IP address using the following command:

    ip addr del {CIDR_IP_ADDRESS} dev {Ethernet Device}

  13. Upgrade the RPMs on the second node of the cluster.

  14. Using the high availability manager (see Step 1) start the Orchestrate Server instance.