22.4 Upgrading Orchestration Components

There are two methods for upgrading Orchestration Server packages.

If you want to use a graphical user interface (GUI) see Upgrading Orchestration Packages Using YaST2.
If you want to use the command line to upgrade, see Upgrading Orchestration Packages Using the zypper Command.

22.4.1 Upgrading Orchestration Packages Using YaST2

Use the following procedure if you want to use YaST, a graphical user interface, to upgrade the Cloud Manager Orchestration packages.

Download the Cloud Manager 2.5 ISO (64-bit), then prepare it for installation:

HINT:The Cloud Manager 2.5 product ISO includes the packages for Cloud Manager Orchestration components, which carry the 3.5 version.
1. (Optional) Burn a DVD of the ISO image and load it into the DVD drive of the target machine.
2. (Optional) Copy the ISO image to the local file system.
  
  To mount the ISO image file on a particular machine,
  1. Log in to the target server as root.
  2. Open YaST2.
  3. In the YaST Control Center, click Software, then click Software Repositories to display the Configured Software Repositories view.
  4. In the Configured Software Repositories view, click Add to open the Media Type view.
  5. In the Media Type view, select Local ISO Image, then click Next to open the Local ISO Image view.
  6. In the Repository Name field, enter a name for the repository.
  7. In the Path to ISO Image field of the Local Directory or ISO view, browse to the path where you copied the ISO image file, then click Next.
3. (Optional) Mount the ISO image file on the machine where Cloud Manager Orchestration is to be installed (the “target” machine).
  
  If you want to mount the ISO image file on a particular machine,
  1. Log in to the target server as root.
  2. From the command line of the target machine, enter the following commands
    mkdir /mnt/iso mount -o loop NetIO_Cloud_Manager-2.5<SLES_version>.x86_64.iso /mnt/iso
    
    (where you substitute the name of the ISO (64-bit) that you are using).
  3. Open YaST2.
  4. In the YaST Control Center, click Software, then click Installation Source to display the Configured Software Catalogs view.
  5. In the Configured Software Catalogs view, click Add to open the Media Type view.
  6. In the Media Type view, select Local Directory, then click Next to open the Local Directory view.
  7. In the Repository Name field, enter a name for the repository.
  8. In the Path to Directory field of the Local Directory view, enter the mount point:
    /mnt/iso
4. (Optional) If you are installing the ISO image to a large network, extract the product files from the ISO image to a Web server / FTP server that can be accessed by the target machine without the need for authentication or anonymous login.
  
  To add an .iso file or Web URL as an installation source in YaST,
  1. Log in to the target SLES server as root, then open YaST2.
  2. In the YaST Control Center, click Software, then click Installation Source to display the Configured Software Catalogs view.
  3. In the Configured Software Catalogs view, then click Add to open the Media Type view.
  4. In the Media Type view, select an installation media type.
    
    (Example) If you extracted the ISO image to a Web Server or FTP Server, select HTTP (or FTP), then click Next to open the Server and Directory view.
    
    In the Server Name field of the Server and Directory view, enter the Server Name (IP Address or DNS Name), in the Directory on Server Field, enter the directory name where you extracted the ISO, then click Next.
Upgrade Orchestration Server software packages to Orchestration Server software packages:
1. Log in to the target SLES server as root, then open YaST2.
2. In YaST2, select Software > Software Management, select the method to open the product ISO on your machine, click Next, then follow the procedures to mount the ISO.
3. From the License Agreement page, select the option to agree to the license terms, then click Next.
4. In YaST2, open the Filter drop-down list, select Patterns or Install Sources to display the Patterns and Packages view, then click Details to close the information pane and open the Package frame.
5. In the Patterns frame (left-hand side of the view), select a Cloud Manager Orchestration pattern already installed on this server. The Package frame lists the packages either installed or not yet installed for this pattern.
  
  Component packages already installed to the server are checked.
  
  NOTE:Package names for this release of Cloud Manager Orchestration continue to use “novell-zenworks” in the prefix or “Cloud Manager Orchestration” in the summary description.
6. Right-click on any of the installed package names, click All in This List > Update if newer version available.
7. Add the new novell-zenworks-zos-server-data-livecd package, then click Accept to install the upgraded packages.
8. Repeat Step 2.e through Step 2.g for each installed pattern you are upgrading.
  
  After the RPM files are upgraded, scripts are run that do the following:
  - Back up the existing server instance directory
  - Upgrade the RPM files for the selected Orchestration patterns
Configure the Cloud Manager Orchestration Server. You can use one of two information gathering methods to perform the configuration:
- Run the Orchestration Server product configuration script. If you use this method, continue with the steps in Configuring the Upgraded Orchestration Components.
- Run the GUI Configuration Wizard. If you use this method, skip to the steps in Configuring the Upgraded Orchestration Components.

22.4.2 Upgrading Orchestration Packages Using the zypper Command

Use the following procedure if you want to use zypper commands to upgrade the Cloud Manager Orchestration packages on SLES machines. If you want to use the GUI Configuration Wizard to upgrade, see Configuring an Upgraded Orchestration Agent Installed on the Server.

For more zypper commands, see Other Useful zypper Commands for Upgrade.

Download the appropriate Cloud Manager 2.5 ISO, then prepare it for installation:
- (Optional) Burn a DVD of the ISO image, mount the DVD, then extract the contents of the .iso folder to the local file system of the server.
- (Optional) Extract the contents of the .iso folder to the local file system of the server.
At the command line, change to the directory where the Cloud Manager .iso folder was extracted, then run the commands to upgrade Cloud Manager 2.4 to Cloud Manager 2.5:
1. Run the following command:
```
zypper sa -t yast2 "http://<ip_address_of_local_server>/<directory_location_of_iso_files>"
```
  Alternative 1: If you have chosen not to extract the files and you want to use the .iso image to upgrade, use the following command:
```
zypper sa -t yast2 "iso:/?iso=<directory_location_of_iso>/<iso_name>" <service_name>
```
  or
```
zypper sa -t yast2 "iso:/?iso=<directory_location_of_iso>/<iso_name>" "<repo_alias>"
```
  For example, for the ISO located at /root/Desktop/NetIQ_Cloud_Manager-2.5-SLE11.x86_64.iso, you could use this command:
```
zypper sa -t yast2 "iso:/?iso=/root/Desktop/NetIQ_Cloud_Manager-2.5-SLE11.x86_64.iso" "CMOS_Server"
```
  Alternative 2: If you are using an ftp server and you want to use the .iso image to upgrade, use the following command:
```
zypper sa -t yast2 "ftp://<ip_address_of_local _server>/<directory_location_of_iso_files>"
```
2. Run the following command:
```
zypper ref <repo_alias>
```
3. Run the following command:
```
zypper dup -r <repo_alias>
```

22.4.3 Other Useful zypper Commands for Upgrade

You might find the other zypper commands listed in the table below to be useful during the server upgrade process.

Table 22-1 zypper Commands That Might Be Useful During Server Upgrade

Command	Description
zypper refresh $REPO_ALIAS	Builds metadata and cache.
zypper pa $REPO_ALIAS	Displays all packages in the repository.

22.4.4 Checking the Upgraded Version of the Orchestration Components

After you upgrade the Cloud Manager Orchestration packages to Cloud Manager Orchestration 3.4 components, you should check the upgraded software packages to confirm that all of the earlier versions of the product components are now updated and which of the non-NetIQ packages have been updated.

To do this, change to the directory where the current version of Cloud Manager Orchestration components were extracted, then run the following command:

rpm -qa | grep 'novell-zen'

Compare the results of this command with the results you had with the check you performed before the upgrade (see Section 22.2, Checking the Current Version of Cloud Manager Orchestration Components). If some of the components have not been upgraded from the earlier version, the incompatibility between the components could cause unexpected behavior.