Novell PLATESPIN ORCHESTRATE 2.0.2, Руководство по установке и настройке, Страница: 110 / 132

110 PlateSpin Orchestrate 2.0 Installation and Configuration Guide
no
vd
ocx
(e
n)
13
Ma
y 20
09
When the resource is online, the Resources Monitor displays a labeled box representing the
registered agent. This box includes information about the agent, including the number of available
slots it has and a status color indicating its state of readiness for PlateSpin Orchestrate jobs.
The status color window can be white (inactive), blue (in use), yellow (available for use), or blue (in
use). If the color changes from yellow to blue, a job is running on this resource. To find out what
kind of job is running, you can click on the
Jobs monitor button on the toolbar.
3.4 Walkthrough: Observing Discovery Jobs
When you created a resource account for the first time, you might have noticed the status window of
the Resource object change colors (see
Step 2 on page 109 ) from blue to yellow. You might also
notice new jobs displayed as objects in the Explorer panel. What you are observing are the
“discovery” jobs that are shipped with PlateSpin Orchestrate (different discovery jobs are shipped
with PlateSpin Orchestrate, depending on which management pack you license).
To understand the reason why these jobs run:
1
In the PlateSpin Orchestrate Development Client, click Scheduler to open the Job Schedule
view in the workspace.
In this walkthrough of basic PlateSpin Orchestrate functionality, you can see that several jobs are
configured to run. If you select one of the jobs, such as
cpuInfo
, you will see that it was configured
with a trigger called RESOURCE_ONLINE. All of the discovery jobs, like
cpuInfo
, are configured
to run when the resource is online, that is, when the resource agent has logged into the Orchestrate
Server.
The discovery jobs run basic operations at resource start as a convenience, to gather data that you or
a job developer might need later when creating jobs, or that the PlateSpin Orchestrate system might
need as it allocates resources to run jobs. For example, the
cpuInfo
job and the
osInfo
job do some
basic probing of the computing node (the machine where the agent is installed and has a resource
account) for later reference.