4.1 Resource Discovery

Resource discovery jobs introspect a resource’s environment to set resource facts stored with the resource grid object.

As shown in the following figure, resource discovery jobs automatically discover the resource attributes (fully extensible facts relating to CPU, memory, storage, bandwidth, load, software inventory, and so forth) of the resources being managed by the ZENworks Orchestrator server. This enables the Orchestrator Server to automatically detect new resources and to integrate resource provisioning of on-line resources. The server can also keep account of these facts for managed resources that are off line.

Figure 4-1 Resource Discovery Overview

For more information, see Walkthrough: Observe Discovery Jobs Run in the Novell ZENworks Orchestrator 1.2 Installation and Getting Started Guide, and Discovering Virtual Machines in the Novell ZENworks Orchestrator 1.2 Virtual Machine Management Guide.

4.1.1 Provisioning Jobs

Provisioning jobs are included in the Orchestrator VM Management Pack and are used for interacting with a VM Technology for VM life cycle management and for cloning, moving VMs, and other management tasks.These type of jobs are called Provisionng Adapters and are members of the job group called “provisionAdapters.”

For more information, see Section 9.2, Virtual Machine Management and Provisioning Adapters in the Novell ZENworks Orchestrator 1.2 Virtual Machine Management Guide.

4.1.2 Resource Targeting

Resource targeting jobs typically match constraints on the client and server, then test for conditions required by specific grid resources.

4.1.3 Resource Discovery Jobs

Some of the commonly used resource discovery jobs include:


Cleans up the audit database, which frequently becomes cluttered because of massive audit files.


Gets CPU information of a resource.


Generates the CPU, operating system, and application information for testing.


Finds and reports what applications are installed on the data grid.


Rotates server logs.


Gets the operating system of a grid resource. On Linux, it reads the /proc/cpuinfo; on Windows, it reads the registry; on UNIX, it executes uname.

    resource.cpu.mhz (integer) e.g., "800" (in Mhz)
    resource.cpy.vendor (string) e.g. "GenuineIntel"
    resource.cpu.model (string) e.g. "Pentium III"
    resource.cpu.family (string) e.g. "i686"