1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. PLATESPIN ORCHESTRATE 2.0.2 - UPGARDE GUIDE...
  6. Upgrade manual

Novell PLATESPIN ORCHESTRATE 2.0.2 - UPGARDE GUIDE 10-09-2009 Upgrade Manual

Hide thumbs Also See for PLATESPIN ORCHESTRATE 2.0.2 - UPGARDE GUIDE 10-09-2009:
Table of Contents

Advertisement

Quick Links

Download this manual
AUTHORIZED DOCUMENTATION
Upgrade Guide
Novell
®
PlateSpin
Orchestrate
®
TM
2.0.2
October 9, 2009
www.novell.com
PlateSpin Orchestrate 2.0 Upgrade Guide

Advertisement

Table of Contents
loading

Related Manuals for Novell PLATESPIN ORCHESTRATE 2.0.2 - UPGARDE GUIDE 10-09-2009

Summary of Contents for Novell PLATESPIN ORCHESTRATE 2.0.2 - UPGARDE GUIDE 10-09-2009

  • Page 1 AUTHORIZED DOCUMENTATION Upgrade Guide Novell ® PlateSpin Orchestrate ® 2.0.2 October 9, 2009 www.novell.com PlateSpin Orchestrate 2.0 Upgrade Guide...
  • Page 2 Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
  • Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.
  • Page 4 PlateSpin Orchestrate 2.0 Upgrade Guide...

  • Page 5: Table Of Contents

    Contents About This Guide 1 Upgrade Overview Basic Functions of the Upgrade ..........9 Compatibility Checking Behavior .
  • Page 6 2.8.5 Configuring Upgraded Orchestrate Servers in the High Availability Environment . . . 51 2.8.6 Installing and Configuring Monitoring in the High Availability Environment ..52 A Documentation Updates October 9, 2009 ............59 July 15, 2009 .

  • Page 7: About This Guide

    About This Guide ® ® This Upgrade Guide introduces the process of upgrading Novell ZENworks Orchestrator 1.3 to ® PlateSpin Orchestrate 2.0.2. The guide provides an introductory overview of the requirements for upgrading and explains which components are compatible. Further, it provides specific instructions for performing the upgrade.
  • Page 8 For the most recent updates for this Upgrade Guide, visit the PlateSpin Orchestrate 2.0 Web site (http://www.novell.com/documentation/pso_orchestrate20/). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark.

  • Page 9: Upgrade Overview

    Upgrade Overview ® ® PlateSpin Orchestrate from Novell has been engineered to allow upgrading of Novell ® ZENworks Orchestrator 1.3 components to continue working in the PlateSpin Orchestrate 2.0 environment. The upgrade process affects the following Orchestrator components: the Orchestrator Server (1.3) upgrades to PlateSpin Orchestrate Server (2.0.2) the Orchestrator Console (1.3) upgrades to PlateSpin Orchestrate Development Client (2.0.2)

  • Page 10: Compatibility Checking Behavior

    , located in the directory. server.log /var/opt/novell/zenworks/zos/server/logs 1.2 Compatibility Checking Behavior For managed agents (nodes), the agents report the version incompatibility in the agent log file. On the server, the attempted connection by an incompatible agent is detected, and the agent is listed on the Orchestrator Console as incompatible and in need of either an upgrade or downgrade to the correct version.

  • Page 11: Behavior Shown By The Orchestrate Vm Client When Detecting Incompatibility

    1.2.1 Behavior Shown by the Orchestrate VM Client When Detecting Incompatibility The information in this section lists the known behaviors exhibited when the PlateSpin Orchestrate VM Client (formerly referred to as Orchestrator VM Manager) is upgraded to version 2.0 when other Orchestrator components are not upgraded.
  • Page 12 When an Agent Version Does Not Match the Server Version When an older, incompatible version of the agent communicates with the server, the server detects it and flags the agent as “old.” This incompatibility is displayed in the Orchestrate Development Client, where an older version of the agent is shown in the Tree view with an “old”...

  • Page 13: Configuring The Upgrade

    1.3 Configuring the Upgrade Following the installation of the new software, you need to configure the software for your PlateSpin Orchestrate system. You can do this by launching either a terminal-based config script or a GUI Configuration Wizard from the command line. When you use the GUI Configuration Wizard, you have the option of configuring the software now or saving the config script for use during an automated mass upgrade.
  • Page 14 PlateSpin Orchestrate 2.0 Upgrade Guide...

  • Page 15: Upgrading Zenworks Orchestrator 1.3 Components To Platespin Orchestrate

    Orchestrator 1.3 to ® PlateSpin Orchestrate 2.0 from Novell. It is important that you upgrade the ZENworks Orchestrator components you have installed in the sequence that follows: Section 2.1, “Upgrading the ZENworks Orchestrator Server Components,” on page 15 Section 2.2, “Orchestrator Components That Are Not Upgraded,” on page 32 Section 2.3, “Recovering from a Failed Orchestrator Server Upgrade,”...

  • Page 16: Checking Out The Vms That Are To Be Used In Platespin Orchestrate

    Before you upgrade the ZENworks Orchestrator packages from version 1.3 to the PlateSpin Orchestrate 2.0.2 packages, you should check which packages of the older Orchestrator version need to be upgraded and which non-Novell packages are included in the product packages. To do this, run the following command: rpm -qa | grep 'novell-zen' PlateSpin Orchestrate 2.0 Upgrade Guide...

  • Page 17: Snapshotting The Existing Server Installation

    /etc/init.d/novell-zosserver start 2 Create a snapshot of the server’s current configuration with the following command: /etc/init.d/novell-zosserver stop --snapshot You can also create the snapshot by using the Development Client to shut down the server. To do so, select Server > Shutdown Server to display the Server Shutdown Confirmation dialog box.

  • Page 18: Upgrading The Zenworks Orchestrator Server Packages

    2.1.5 Upgrading the ZENworks Orchestrator Server Packages There are two methods for upgrading ZENworks Orchestrator Server Packages. If you want to use a graphical user interface (GUI) see “Upgrading ZENworks Orchestrator Server Packages Using YaST” on page If you want to use the command line to upgrade the packages, see “Upgrading ZENworks Orchestrator Server Packages at the Command Line”...
  • Page 19 Component packages already installed to the server are checked. NOTE: Package names for this release of PlateSpin Orchestrate continue to use “novell- zenworks” in the prefix or “ZENworks Orchestrator” in the summary description. 2f Right-click on any of the installed package names, click All in This List > Update if newer version available, then click Accept to install the upgraded packages.
  • Page 20 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 or ISO view. 7 In the Path to Directory or ISO Image field of the Local Directory or ISO view, enter the mount point: /mnt/iso Adding a Local Directory As An Installation Source in YaST...
  • Page 21 IMPORTANT: A known problem in the pattern and package versioning of SLES generates a list of patterns that are upgraded (in this case, to version 2.0.2) but the subordinate packages might still appear to be ZENworks Orchestrator 1.3 patterns. Some upgrade packages might also be missing from the list.

  • Page 22: Removing Obsolete And Unneeded Zenworks Orchestrator Patterns

    The following packages will be removed: zw_mon_server 1.3-0 (system) 5 Use the following command to remove the remainder of the Monitoring component on this machine: rug rm novell-zenworks-monitor-gmetad novell-zenworks-monitor-web -y A system message is displayed: The following packages will be removed: novell-zenworks-monitor-gmetad 3.0.4-44 (system) novell-zenworks-monitor-web 3.0.4-44 (system)

  • Page 23: Running Discover On Vm Images

    After you upgrade the ZENworks Orchestrator packages to PlateSpin Orchestrate 2.0.2, 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-Novell packages have been updated. Upgrading ZENworks Orchestrator 1.3 Components to PlateSpin Orchestrate 2.0...

  • Page 24: Configuring The Upgraded Server Packages

    To do this, change to the directory where the current version of PlateSpin Orchestrate was 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 2.1.3, “Checking the Current Version of ZENworks Orchestrator,”...
  • Page 25 Select from the following: 1 - 4) toggle selection status none finished making selections quit -- exit the program Selection [finish]: 4 Select the products you want to upgrade either by entering their individual product numbers ( ) or by entering to select all of the products for upgrade.
  • Page 26 If you decide to use the GUI Configuration Wizard to configure the upgraded Orchestrator packages, follow these steps: 1 Run the script for the PlateSpin Orchestrate Configuration Wizard as follows: /opt/novell/zenworks/orch/bin/guiconfig The GUI Configuration Wizard launches. IMPORTANT: If you only have a keyboard to navigate through the pages of the GUI Configuration Wizard, use the Tab key to shift the focus to a control you want to use (for example, a Next button), then press the spacebar to activate that control.
  • Page 27 2 Click Next to display the license agreement. 3 Accept the agreement, then click Next to display the PlateSpin Orchestrate Configuration Selection page. 4 Select Upgrade, then click Next to display the PlateSpin Orchestrate components page. This page lists the components that are available for configuration. By default, all installed components are selected for configuration.
  • Page 28 5 Deselect any PlateSpin Orchestrate components that you do not want to upgrade, then click Next to open the wizard page where you choose to configure the server for a High Availability clustered environment. NOTE: You might not want to upgrade all components. For example, you might want to keep an older version of the Orchestrate Aagent installed on an Orchestrate Server machine when the agent is used to connect to a different (that is, a non-upgraded) Orchestrate server, such as in a “grid-of-grids”...
  • Page 29 If you need clarification for the data to enter into the fields of the configuration pages, refer to the table in “PlateSpin Orchestrate Configuration Information” section of the PlateSpin Orchestrate 2.0 Installation and Configuration Guide. Make sure you provide the path to the new PlateSpin Orchestrate license file during the configuration.
  • Page 30 Orchestrator server or client and apply the settings .conf either manually or with an installation script. Use the following command to run the configuration: /opt/novell/zenworks/orch/bin/config -rs 12 Click Next to display a message asking whether you want to overwrite the . response file. conf 13 To upgrade, you need to overwrite the existing file.
  • Page 31 Use the following procedure to manually upgrade the audit database: 1 On the PlateSpin Orchestrate host machine, use your favorite editor to edit the script /opt/ novell/zenworks/zos/server/conf/audit_db_upgrade.sql 1a Replace the variable with the PostgreSQL database name (for example, ${DB_NAME}...

  • Page 32: Orchestrator Components That Are Not Upgraded

    2 Use the following commands to run the modified script as the PostgreSQL database administrator for the remote database: su - postgres psql -h <psql-server-addr> -d postgres -U postgres -f audit_db_upgrade.sql 3 Use the following command to log into PostgreSQL, using the database name and schema owner substituted in Step 1 above: su - postgres psql -h <psql-server-addr>...

  • Page 33: Recovering From A Failed Orchestrator Server Upgrade

    1 Remove the new instance directory for the Orchestrator server, not including the datagrid. 2 Copy the old instance directory to restore the /var/opt/novell/zenworks/zos.bak Orchestrator Server data from the snapshot. 3 Restore the previous version RPMs of the ZENworks Orchestrator software.

  • Page 34: Requirements

    Linux Management. ZENworks Linux Management records data about each package that it installs, deletes, or upgrades. For more information about using ZENworks Linux Management for rollback, see Reverting to a Previously Installed Software Configuration State (http://www.novell.com/documentation/zlm72/ lm7admin/index.html?page=/documentation/zlm72/lm7admin/data/b94fftd.html) in the ZENworks 7.2 Linux Management Administration Guide.
  • Page 35 RPM package versions as PlateSpin Orchestrate 2.0.2. For more information about adding repositories, see the ZENworks 7.2 Linux Management Administration Guide (http://www.novell.com/documentation/zlm72/lm7admin/data/ front.html). 5b Run the following command to list and confirm existing repositories: rug sl...
  • Page 36 Because the 2.0.2 packages are installed but not configured, you cannot use them to start the Orchestrate Server. 11 Run the follow command to confirm that an instance of the Orchestrate Server was created: ls /var/opt/novell/zenworks/zos/ folders should be listed. agent server server.save...

  • Page 37: Upgrading The Zenworks Orchestrator Agents And Clients

    PlateSpin Orchestrate version, you should check which packages of the older Orchestrator version need to be upgraded and which non-Novell packages are included in the product packages. To do this, change to the directory where the current version of the Orchestrator was extracted, .iso...

  • Page 38: Backing Up The Orchestrator Agent Prior To Upgrading

    As with the installation of any software, it is always a wise precaution to back up a working copy of ZENworks Orchestrator 1.3 Agent directories before you install the newer version, such as PlateSpin Orchestrate 2.0. To back up the old version, copy the /var/opt/novell/zenworks/ directory. zos/agent 2.5.3 Automatically Upgrading the Orchestrate Agent from the...
  • Page 39 Upgrading ZENworks Orchestrator Agent Packages Using YaST Use the following procedure if you want to use YaST, a graphical user interface, to upgrade the ZENworks Orchestrator packages to PlateSpin Orchestrate packages. If you want to use the command line to upgrade, see “Upgrading ZENworks Orchestrator Agent Packages Using the rug Command”...
  • Page 40 WARNING: The preceding steps have been tested and validated in YaST. Using other methods to update packages in YaST have not proven successful. 2e Run the configuration program on the machine where the agents or clients are installed. You have two options for running the script: Run the PlateSpin Orchestrate product configuration script.
  • Page 41 To do this, change to the directory where the PlateSpin Orchestrate 2.0.2 was extracted, then .iso...
  • Page 42 Agents using the GUI Configuration Wizard referred to in Step 2e on page 1 Run the script for the PlateSpin Orchestrate Configuration Wizard as follows: /opt/novell/zenworks/orch/bin/guiconfig The GUI Configuration Wizard launches. IMPORTANT: If you only have a keyboard to navigate through the pages of the GUI Configuration Wizard, use the Tab key to shift the focus to a control you want to use (for example, a Next button), then press the spacebar to activate that control.
  • Page 43 3 Accept the agreement, then click Next to display the PlateSpin Orchestrate Configuration Selection page. 4 Select Upgrade, then click Next to display the PlateSpin Orchestrate components page. This page lists the components that are available for configuration (already installed). By default, all previously installed components are selected for configuration.
  • Page 44 Orchestrator Agent and apply the settings .conf either manually or with an installation script. Use the following command to run the configuration: /opt/novell/zenworks/orch/bin/config -rs 7 Click Next to display a message asking whether you want to overwrite the . response file. conf 8 To upgrade, you need to overwrite the existing file.

  • Page 45: Using The Iso To Upgrade The Orchestrator Agent And Clients On Red Hat Enterprise Linux 4 Machines

    4 Navigate to the directory path where the RHEL 4 packages reside. For example: cd /mnt/RHEL4 There are five packages in the directory (the list below is for a 64-bit ISO): /RHEL4 novell-zenworks-monitor-gmond-3.0.4-50.x86_64.rpm novell-zenworks-orch-config-2.0.2-141.noarch.rpm novell-zenworks-orch-config-gui-2.0.2-57039.noarch.rpm novell-zenworks-zos-agent-2.0.2-57039.i586.rpm novell-zenworks-zos-java-1.5.0_sun_update17-0.x86_64.rpm 5 Use the command to install the packages: rpm -Uvh *.rpm...

  • Page 46: Using The Iso To Upgrade The Orchestrator Agent On Red Hat Enterprise Linux 5 Machines

    Client to manage a large number of objects. 6a Open the bash shell script at /opt/novell/zenworks/zos/server/bin 6b Inside the script, find the following line where the JVM parameters are defined: JVMARGS="-Xmx256m -Xms256m -Xmn64m -XX:NewSize=64m -XX:MaxNewSize=64m" argument specifies the maximum heap size for the JVM*. Increasing the heap -Xmx size prevents a JVM out of memory condition.

  • Page 47: Using The Iso To Upgrade The Orchestrator Agent Or The Orchestrator Clients On Windows Machines

    6a Open the bash shell script at /opt/novell/zenworks/zos/server/bin 6b Inside the script, find the following line where the JVM parameters are defined: JVMARGS="-Xmx256m -Xms256m -Xmn64m -XX:NewSize=64m -XX:MaxNewSize=64m" argument specifies the maximum heap size for the JVM. Increasing the heap -Xmx size prevents a JVM out of memory condition.

  • Page 48: Upgrading The Zenworks Vm Manager Console To Platespin Orchestrate Vm Client

    2 Uninstall the ZENworks VM Manager client: Windows: Click Start > Control Panel > Add or Remove Programs, select the ZENworks Orchestrator VM Manager item, then click Remove. Linux: Run the following command: /opt/novell/zenworks/vmmanagement/Uninstall_ZENworks_VMM/ Uninstall_ZENworks_Orchestrator_VM_Manager_1.3.0 3 Follow the steps in “Installing the Orchestrate VM Client”...

  • Page 49: Snapshotting The Zenworks Orchestrator Environment

    2 From the command line of both Orchestrate Servers (c114 and c115) use the following command to back up your server instance before you upgrade. cp -rH /var/opt/novell/zenworks/zos/server ~/server.bkp You can use the command to list the rpms that are currently...

  • Page 50: Upgrading The Zenworks Orchestrator Server

    This is one of the ZENworks Orchestrator Servers. Its RPM packages include: novell-zenworks-orch-config-1.3.0-41 novell-zenworks-orch-config-gui-1.3.0-33604 novell-zenworks-zos-clients-1.3.0-33604 novell-zenworks-zos-java-1.5.0_sun_update17-0 novell-zenworks-zos-server-1.3.0-33604 novell-zenworks-zos-server-data-agent-1.3.0-33604 novell-zenworks-zos-server-data-clients-1.3.0-33604 novell-zenworks-zos-server-data-jre-1.3.9-33604 c115: This is another ZENworks Orchestrator Server. Its RPM packages include: novell-zenworks-orch-config-1.3.0-41 novell-zenworks-orch-config-gui-1.3.0-33604 novell-zenworks-zos-clients-1.3.0-33604 novell-zenworks-zos-java-1.5.0_sun_update17-0 novell-zenworks-zos-server-1.3.0-33604 novell-zenworks-zos-server-data-agent-1.3.0-33604 novell-zenworks-zos-server-data-clients-1.3.0-33604 novell-zenworks-zos-server-data-jre-1.3.9-33604 c122: This is the server with Monitoring (Agent and Server), the VM Warehouse, the Orchestrator Agent, the Orchestrator Clients, and the Heartbeat Client for high availability.

  • Page 51: Removing Obsolete Zenworks Orchestrator Patterns

    (in this scenario, it will be c114). 1 From the command line of the machine where you last ran commands to upgrade patterns (c114) run the following command to begin the upgrade configuration: /opt/novell/zenworks/orch/bin/config The upgrade script introduction is displayed: Welcome to PlateSpin Orchestrate.

  • Page 52: Installing And Configuring Monitoring In The High Availability Environment

    8 On other machines in the cluster where the Orchestrate Server was upgraded, copy the new license key ( ) in key.txt /opt/novell/zenworks/zos/server/license 2.8.6 Installing and Configuring Monitoring in the High Availability Environment When you have completed configuring the Orchestrate Servers for the high availability environment, you need to install PlateSpin Orchestrate Monitoring (both the Monitoring Server and the Monitoring Agent) and then restart the Orchestrate Server instance in the clustering tools.
  • Page 53 Installing the Monitoring Components You need to install PlateSpin Orchestrate Monitoring (both the Server and the Agent) on both Orchestrate Servers (c114 and c115) after they have been initially upgraded. 1 Log in to the target SLES 10 SP2 server as , then open YaST2.
  • Page 54 /opt/novell/zenworks/orch/bin/config When the script runs, the following information is initially displayed: Welcome to PlateSpin Orchestrate. This program will configure PlateSpin Orchestrate 2.0 Select whether this is a new install or an upgrade i) install u) upgrade - - - - - - Selection [install]: 3 Press Enter to select the default (install).
  • Page 55 /zos mkdir -p /zos/monitor cp -av /etc/apache2 /zos/monitor ln -sf /etc/mime.types /zos/monitor/apache2/mime.types mv /etc/apache2/ /etc/apache2.orig ln -sf /zos/monitor/apache2 /etc cp -av /etc/opt/novell/zenworks/monitor /zos/monitor mv /etc/opt/novell/zenworks/monitor /etc/opt/novell/zenworks/monitor.orig ln -sf /zos/monitor/monitor /etc/opt/novell/zenworks/monitor cp -av /var/opt/novell/zenworks/monitor/rrds /zos/monitor mv /var/opt/novell/zenworks/monitor/rrds /var/opt/novell/zenworks/monitor/rrd.orig ln -sf /zos/monitor/rrds /var/opt/novell/zenworks/monitor...
  • Page 56 You can use the example script below as a template for this script. Paste it into an file and run it on a secondary monitoring server. mv /etc/apache2/ /etc/apache2.orig ln -sf /zos/monitor/apache2 /etc mv /etc/opt/novell/zenworks/monitor /etc/opt/novell/zenworks/monitor.orig ln -sf /zos/monitor/monitor /etc/opt/novell/zenworks/monitor mv /var/opt/novell/zenworks/monitor/rrds /var/opt/novell/zenworks/monitor/rrd.orig ln -sf /zos/monitor/rrds /var/opt/novell/zenworks/monitor chkconfig apache2 off chkconfig gmond off...
  • Page 57 <op id="Gmetad_Status" name="status" description="Monitor the status of Gmetad" interval="300" timeout="15" start_delay="15" role="Started" on_fail="restart"/> </operations> </primitive> <primitive id="Gmond" class="lsb" type="novell-gmond" provider="heartbeat"> <instance_attributes id="gmond_attr"> <attributes> <nvpair id="gmond_target_role" name="target_role" value="started"/> </attributes> </instance_attributes> <operations> <op id="Gmond_Status" name="status" description="Monitor the status of Gmetad" interval="300" timeout="15" start_delay="15"...
  • Page 58 PlateSpin Orchestrate 2.0 Upgrade Guide...

  • Page 59: A Documentation Updates

    Documentation Updates This section contains information about documentation content changes that were made in this PlateSpin Orchestrate Installation and Configuration Guide after the initial release of PlateSpin Orchestrate 2.0. The changes are listed according to the date they were published. The documentation for this product is provided on the Web in two formats: HTML and PDF.
  • Page 60 Location Update Section 2.1.8, “Running Discover on VM Images,” New content. on page 23 “Manually Configuring the Remote Audit Database Added content to explain updating audit database. after PlateSpin Orchestrate Is Upgraded” on page 31 Section 2.5.3, “Automatically Upgrading the New content.

This manual is also suitable for:

Platespin orchestrate 2.0.2

Table of Contents