The Job Constraints/Facts Tab; The Resource Object; Resource Groups - Novell PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE 08-28-2009 Reference

The Policy Selection Dialog Box
Figure 5-4

5.3.6 The Job Constraints/Facts Tab

The Constraints/Facts tab opens a page that shows all of the effective constraints and facts for a Grid
object. Each Grid object has an associated set of facts and constraints that define its properties. In
essence, by changing the policy constraints and fact values for a job, you can change the behavior of
the job and how the PlateSpin Orchestrate Server allocates available system resources to it. The
Orchestrate Server assigns default values to each of the component facts, although they can be
changed at any time by the administrator, unless they are read-only. Facts with mode
only values, which can be viewed (that is, using the edit "pencil" icon) but changes cannot be made.

5.4 The Resource Object

A Resource object in the Explorer Panel represents a physical or virtual machine that is managed by
PlateSpin Orchestrate. If a resource is running the PlateSpin Orchestrate Agent, that resource can be
scheduled for remote execution of a job.
This section includes information about a Resource object that is visible in the Explorer view and
the accompanying Admin view of the Orchestrate Development Client:
Section 5.4.1, "Resource Groups," on page 81
Section 5.4.2, "The Resource Info/Groups Tab," on page 82
Section 5.4.3, "The Provision Info Tab," on page 102
Section 5.4.4, "The Resource Log Tab," on page 103
Section 5.4.5, "The Resource Policies Tab," on page 103
Section 5.4.6, "The Resource Health Debugger Tab," on page 103
Section 5.4.7, "The Resource Constraints/Facts Tab," on page 104

5.4.1 Resource Groups

Any group object displayed in the Explorer panel represents a collection of similar object types.
Groups can also be created automatically, as in the case when a provisioning adapter (PA) discovers
a local repository on a VM host. For example, the
automatically creates a local repository for that VM host and places the created repository in a
PA, upon discovery of a VM host,
xen30
have read-
r/o
The Explorer Tree 81