22.10 Upgrading a Orchestration High Availability Configuration

This section provides the steps you need to follow to upgrade a prior version of the Cloud Manager environment to a Cloud Manager high availability configuration. Use the following steps for the upgrade:

  1. Using the high availability manager (such as Heartbeat 2), shut down the Cloud Manager Orchestration 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 Cloud Manager Orchestration Server instance on the first node in the cluster (this should be a node that does not include high-availability components) using the following command:

    /etc/init.d/novell-zosserver start

  4. Manually stop the instance with snapshot. See Section 22.3, Snapshotting the Existing Orchestration 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 RPM files on the first node (the one you started in Step 3) of the cluster. For more information, see Section 22.4, Upgrading Orchestration Components.

  7. Run the configuration script. For more information, see Configuring the Upgraded Orchestration Components.

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

    ip addr add {CIDR_IP_ADDRESS} dev {Ethernet Device}

  9. Start the Orchestration 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 Orchestration Console, 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 RPM files on the second node of the cluster.

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