3.7 Configuring the Orchestration Agent

The Cloud Manager Orchestration Agent manages the life cycle of VMs in your hypervisor environment under the direction of the Orchestration Server. You install the agent on computers where those VMs reside.

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

    Server Configuration Requirement

    Explanation and Action

    Configuration Type

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

    This section discusses standard installation, so specify s (for standard) or press Enter to accept the default. For more information about High Availability configuration, see the NetIQ Cloud Manager 2.1.4 Orchestration Server High Availability Configuration Guide.

    Agent Name

    The Orchestration Agent requires a name to authenticate to the Orchestration Server.

    Orchestration Server Hostname or IP Address

    The DNS name or IP address of the Orchestration Server that this agent binds to.

    Always Implement the Orchestration Server Certificate and Key?

    The Agent relies on the Orchestration Server’s TLS certificate as verification that it is communicating with the corrrect Orchestration Server.

    Decide whether you want to always trust the server certificate after the agent initially downloads it from the server, or if you want to exercise the certificate and key every time the agent connects to the server.

    Is the Node a Physical or a Virtual Machine?

    If the computer where you installed the agent is actually a VM, the Cloud Manager Server approaches its management in a unique way.

    Agent Port

    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.

    For an Agent installed on ESX, configure port 8101.

    (Optional) Agent IP Address

    You can specify a local bind address for the agent if you want to.

    If you specify an address, the agent tries to use this address locally when it connects to the Orchestration Server. If you don’t specify an address, the operating system automatically sets the local address for each connection.

    Path to Server Certificate

    Specify the path to the Orchestration Server certificate file. The default path is /root/zos_server_cert.pem.

    NOTE:This configuration parameter is considered an advanced setting for the Orchestration Agent in the GUI Configuration Wizard, but only if you set Provide Existing Orchestration Server Certificate to yes.

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

    /opt/novell/zenworks/orch/bin/config

    or

    /opt/novell/zenworks/orch/bin/guiconfig

  3. Follow the prompts to complete the configuration of the Orchestration Agent.

NOTE:Some configuration parameters for the agent are considered “advanced setting” in the GUI 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.

You can also configure the agent as part of the silent installation procedure. See Section A.1, Silent Installation of the Orchestration Agent.