Rule-Based Events - Novell PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE 08-28-2009 Reference

The
RESOURCE_ONLINE
discovering operating system and CPU information (
job archives (
cpuInfo
allows these jobs be started when notification of the
C.3.3 Rule-based Events
Rule-based Events are defined in an XML document and deployed to the PlateSpin Orchestrate
Server and managed using the PlateSpin Orchestrate Development Client. Rules can be a simple
object attribute (fact) equivalency check or they can use AND,OR, IF, ELSE logic, among other
things, in an Event ruleset.
The rules follow the same syntax as the constraints that are defined in XML policy files for all Grid
Objects, such as Jobs, VM Hosts, etc.
The PlateSpin Orchestrate Event Service evaluates the rules; if the rules pass, an Event notification
occurs.
The XML Schema document specification can be found in
event_1_0_0.xsd
The Event XML specification is composed of three sections.
<context>
<trigger>
<reset>
NOTE: Both the
<context> section
The context section defines the context in which the Event rules are evaluated. With Events, you
specify what objects are in the Event rule context in this section. The available objects are
Jobinstance
object set to iterate over and optionally a single instance of the object.
<trigger> section
The trigger section defines the rules for when an Event notification occurs. The <
is the same syntax as <
<reset> section
The optional
used, an Event is reset based on a timeout. The
<constraints>
The
resetInterval
is not used, the default timeout for resetting is 10 minutes.
<reset>
The following example (taken from the
defines that a notification occurs when a VM Host becomes overloaded.
148 PlateSpin Orchestrate 2.0 Development Client Reference
built-in Event is used by the embedded discovery jobs, such as for
) include a schedule file (
.job
.
and
<context> <trigger>
, ,
Resource Repository
> used in policies.
constraints
section defines the rules for when an Event is reset. If the
<reset>
used in policies.
attribute is set on the
and
osInfo
) specifying a trigger (
.sched
RESOURCE_ONLINE
<install dir>/doc/xsds/
sections are required.
, , and . From these objects, you can specify one
User VMHost
format is also the same syntax as in
<reset>
XML element. If
<event>
in
"vmhost.event" <install dir>/examples/events
jobs). Both
cpuInfo osInfo
.trig
Event occurs.
trigger
rule is not
<reset>
"resetInterval"
and
) that
,
Job
> format
and
)