1.3 Configuring the Orchestration Server for High Availability

Configure the Orchestration Server that you installed on the first node of the cluster. Component configuration is done either with a text-based configuration tool or with a GUI Wizard configuration tool.

The text-based configuration script detects which RPM patterns are installed, but the GUI Configuration Wizard requires that you specify the components to be configured, whether the patterns have been installed on the server or not.

It is possible to execute the text-based configuration file Orchestration components from the Cloud Manager configuration utility, but this occurs only if you install Cloud Manager Application components on the same server as the Cloud Manager Orchestration components, which is only likely if you are setting up your system for a demonstration.

Both the text-based tool and the GUI Wizard tool produce a configuration file that can be used to automatically reconfigure your system after an upgrade. If you use the tools to reconfigure your server after the original configuration has been done, make sure you reconfigure all of the components that are installed on the system (this is the default).

When you have configured the SLES 10x or the SLES 11 SP1 Orchestration Server, you need to complete the other items necessary for a high availability setup in the following order:

  1. Section 1.4, Installing and Configuring Orchestration Server Packages for High Availability on Other Nodes in the Cluster.

  2. Section 1.5, Creating the Server Cluster Resource Group.

  3. Section 1.6, Testing the Failover of the Orchestration Server in a High Availability Grid

  4. Section 1.7, Installing and Configuring other Orchestration Components to the High Availability Grid.

1.3.1 Some Considerations When Configuring with the GUI Wizard

If you have only 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 this control.

When you have finished answering the configuration questions in the wizard, the Cloud Manager Orchestration Configuration Summary page displays. Although this page of the wizard lets you navigate by using the Tab key and the Spacebar, you need to use the Ctrl+Tab combination to navigate past the summary list. Click Back if you accidentally enter the summary list, and re-enter the page to navigate to the control buttons.

By default, the Configure now check box on the page is selected. If you accept this default, the wizard starts the Orchestration Server and applies the configuration settings. If you deselect the check box, the wizard writes out the configuration file to /etc/opt/novell/novell_zenworks_orch_install.conf without starting the Orchestration Server or applying the configuration settings.

You can use this .conf file to start the Orchestration Server or Agent and apply the settings either manually or with an installation script. Use the following command to run the configuration:

/opt/novell/zenworks/orch/bin/config -rs

When the installation and configuration are complete, you need to validate and optimize the configuration.

1.3.2 The Configuration Procedure

To configure the Orchestration Server for use in a high-availability environment,

  1. Make sure you are logged in as root to run the configuration.

  2. Make sure you are ready with the information that you’ll be prompted for during the configuration procedure (GUI or text-based):

    Server Configuration Requirement

    Explanation and Action

    Configuration Type

    Your answer here determines whether this configuration takes place on a standard installation or on a High Availability installation.

    This section discusses standard installation, so specify h (for ha which means “high availability”).

    Cluster Hostname or IP Address

    Specify the fully qualified cluster hostname or the IP address that is used for configuring the Orchestration Server instance in a high availability cluster.

    The configuration script binds the IP address of the cluster to this server.

    Grid Name

    A grid is an administrative domain container holding all of the objects in your network or data center. The Orchestration Server monitors and manages these objects, including users, resources, and jobs.

    The grid name you create here is displayed as the name for the container placed at the root of the Explorer tree in the Orchestration Console.

    Administrator User

    Specify a name for the Orchestration Server Administrator user.

    This name is used to log in as the administrator of the Orchestration Server and the objects it manages.

    Administrator Password

    Specify a password for the Orchestration Administrator user, then retype the password to validate it.

    You should remember this username for future logins.

    Path to License File

    A license key (90-day evaluation license or a full license) is required to use this product. You should have received this key from NetIQ, then you should have subsequently copied it to the network location that you specify here. Be sure to include the name of the license file in the path.

    Auditing Database

    We recommend that you do not install the audit database on this server.

    Orchestration Agent Port1

    Port 8100 is used for communication between the Orchestration Server and the Orchestration Agent. Specify another port number if 8100 is reserved for another use.

    If your Orchestration Server communicates with ESX servers, we recommend you configure port 8101. This requires that you configure all other Orchestration Agents communicating with this server to use port 8101.

    This configuration parameter is considered an advanced setting for the Orchestration Server in the GUI Configuration Wizard. If you select the Configure Advanced Settings check box in the wizard, you have the option of changing the default values. If you leave the check box deselected the setting is configured with normal defaults.

    Administrator Information Port1

    Port 8001 on the Orchestration Server provides access to an Administrator Information page that includes links to product documentation, agent and client installers, and product tools to help you understand and use the product. Specify another port number if 8001 is reserved for another use on this server.

    TLS Certificate and Key1

    Choose whether to generate a TLS certificate and key.

    • Default = yes (the Orchestration Server must generate a certificate and key for authentication)

    • A PEM-encoded TLS certificate and key is needed for secure communication between the Orchestration Server and Orchestration Agent.

    • If you respond with no, you need to provide the location of an existing certificate and key.

    TLS Server Certificate2

    Specify the full path to the TLS server certificate.

    • Default = /etc/ssl/servercerts/servercert.pem

    • Specify the path to the existing TLS certificate.

    TLS Server Key2

    Specify the full path to the TLS server private key.

    • Default = /etc/ssl/servercerts/serverkey.pem

    • Specify the path to the existing TLS private key.

    1 This configuration parameter is considered an advanced setting for the Orchestration Server in the Orchestration Components Configuration Wizard. If you select the Configure advanced settings check box in the wizard, the setting is configured with normal defaults. Leaving the check box deselected lets you have the option of changing the default value.

    2 This configuration parameter is considered an advanced setting for the Orchestration Server in the Orchestration Components Configuration Wizard. If you select the Configure advanced settings check box in the wizard, this parameter is listed, but default values are provided only if the previous value is manually set to no.

  3. At the computer where you installed the Cloud Manager Orchestration Server pattern, run the Cloud Manager Orchestration configuration utility:




  4. Continue with Checking the Configuration.

1.3.3 Checking the Configuration

When the configuration is completed, the first node of the Orchestration Server cluster is set up. You then need to check the configuration.

  1. Open the configuration log file (/var/opt/novell/novell_zenworks_orch_install.log) to make sure that the components were correctly configured.

    You can change the configuration if you change your mind about some of the parameters you provided in the configuration process. To do so, rerun the configuration and change your responses.

    The configuration tool performs the following functions in sequence on the Orchestration Server:

    1. Binds the cluster IP on this server by issuing the following command internally:

      IPaddr2 start <IP_address_you_provided>

      IMPORTANT:Make sure you configure DNS to resolve the cluster hostname to the cluster IP.

    2. Configures the Orchestration Server.

    3. Shuts down the Orchestration Server because you specified that this is a high availability configuration

    4. Unbinds the cluster IP on this server by issuing the following command internally:

      IPaddr2 stop <IP_address_you_provided>
  2. Continue with Running the High Availability Configuration Script.

1.3.4 Running the High Availability Configuration Script

Before you run the high availability configuration script, make sure that you have installed the Orchestration Server to a single node of your high availability cluster. For more information, see Section 1.2.5, Installing the Orchestration Server on the First Clustered SLES 11 Node

IMPORTANT:The high availability configuration script asks for the mount point on the Fibre Channel SAN. Make sure that you have that information (/zos) before you run the script.

The high availability script, zos_server_ha_post_config.sh, is located in /opt/novell/zenworks/orch/bin/ha with the other configuration tools. You need to run this script on the first node of the cluster (that is, the node where you installed the Orchestration Server) as the next step in setting up Cloud Manager Orchestration Server to work in a high availability environment.

The script performs the following functions:

  • Verifies that the Orchestration Server is not running

  • Copies Apache files to shared storage

  • Copies gmond and gmetad files to shared storage

  • Moves the Orchestration files to shared storage (first node of the cluster)

  • Creates symbolic links pointing to the location of shared storage (all nodes of the cluster)

The high availability configuration script must be run on all nodes of the cluster. Make sure that you follow the prompts in the script exactly; do not misidentify a secondary node in the cluster as the primary node.