Before you begin the Orchestration components upgrade process, you need to know the underlying assumptions of the process so that you can better understand how to proceed. The following list details the most important of those assumptions:
To check the installed Cloud Manager Orchestration components for version number:
Linux: Run the following command on a Linux machine where agent, client, or server components are installed.
rpm -qa | grep 'novell-zen'
Windows: On a Windows machine, open the Add or Remove Programs console in Windows and look for the agent or client version number in the programs list.
The upgrade to Cloud Manager Orchestration 3.5 must be done for all Orchestration Servers, Orchestration Consoles, and all Orchestration Agent components. Running older agents with newer server components or running older Orchestration Consoles and interfaces with newer server components (or vice versa) is not supported.
Upgrading a prior release of a 32-bit Cloud Manager Orchestration Server installation to a newer 64-bit version of Cloud Manager Orchestration Server is not supported. Similarly, upgrading a prior release of a 64-bit Cloud Manager Orchestration Server installation to a newer 32-bit version of Cloud Manager Orchestration Server is not supported.
The Orchestration Server must be upgraded before Orchestration Agents are upgraded. The Cloud Manager Orchestration Server operates with older agents running, but newer 3.5 agents cannot communicate with the Cloud Manager Orchestration Server 3.4. You can upgrade the agents by selecting the Upgrade option on the Resource Registration dialog in the Cloud Manager 3.5 Orchestration Console. For more information, see Section 10.0, Creating a Resource Account.
After you upgrade the server components, older versions of the Orchestration Agents, the Orchestration Console might not work with the newer server components. The Cloud Manager Orchestration Console identifies the managed nodes that have non-compatible agents. For more information about component compatibility, see Section B.0, Compatibility Checking Behavior for Orchestration Components.
After an upgrade to Cloud Manager Orchestration Server 3.5, some specific provisioning adapter jobs (such as vsphere) and existing VMs will not be available for use, even though their files still reside on the Orchestration Server. These provisioning adapter jobs need to be reconfigured.
If errors occur during the upgrade process, you can attempt to resolve those errors and run the upgrade process again. For more information about how this recovery works, see Section C.1, Upgrade Failure Scenarios.
After the Cloud Manager Orchestration Server 3.4 is upgraded to Cloud Manager Orchestration Server 3.5, rolling back to Cloud Manager Orchestration Server 3.4 is not supported.
Step-by-step information about the events occurring during the upgrade process is recorded in server.log, located in the /var/opt/novell/zenworks/zos/server/logs directory.
In some situations, the server log might not exist. You can also check the install log at /var/opt/novell/novell_zenworks_orch_install.log for upgrade information.
If you understand what to expect from the upgrade, you are ready to proceed to Section 22.0, Upgrading Orchestration Server Components.