Table of Contents
Advertisement
Understanding Policy Elements
B
XML is the representation for PlateSpin
the server and associated with any grid object. The policy element is the root element for policies.
Policies contain constraints and fact definitions for grid objects.
Section B.1, "Constraints," on page 137
Section B.2, "Facts," on page 137
Section B.3, "Computed Facts," on page 137
B.1 Constraints
The constraint element defines the selection of grid objects such as resources. The required type
attribute defines the selection type. Supported types are:
Resource
Provision
Allocation
Accept
Start
Continue
vmhost
Repository
Constraints can also be constructed in JDL and in the Java Client SDK. A JDL constructed
constraint can be used for grid search and for scheduling. A Java Client SDK constructed constraint
can only be used for grid object search. For additional information, see
Constraints" in the
PlateSpin Orchestrate 2.0 Developer Guide and
B.2 Facts
The XML fact element defines a fact to be stored in the grid object's fact namespace. The name, type
and value of the fact are specified as attributes. For list or array fact types, the element tag defines
list or array members. For dictionary fact types, the dict tag defines dictionary members.
See the examples in the directory,
representation for all the fact types.
Facts can also be created and modified in JDL and in the Java Client SDK.
B.3 Computed Facts
Computed facts are used when you want to run JDL to generate the value for a fact. Although
computed facts are not jobs, they use the same JDL syntax.
®
Orchestrate policy elements. A policy can be deployed to
. This example policy has an XML
/allTypes.policy
"Working with Facts and
Reference.
Understanding Policy Elements
B
137
Advertisement
Table of Contents
