White Papers

Version 1.2.0 9
DCIM_LCRegisteredProfile
RegisteredProfile = “Job Control”
OwningEntity = “DCIM”
DCIM_ JobService
DCIM_LifeCycleJob
“interop”
namespace
“root/dcim”
Implementation
namespace
DCIM_LCElementConformsToProfile
238
Figure 1 – Job Control Profile: Class Diagram
239
6.1 Job Types
240
Different kinds of system management tasks, such as firmware updates, reboots, configurations, and so
241
on often take a while to complete. In order to provide a means of performing and tracking tasks and task
242
results, individual tasks are defined as jobs that can be run immediately or at a scheduled time.
243
Tasks of different types typically have state sequences that are unique to the task performed and the
244
state is represented as the job status. For the purposes of managing these tasks as jobs, several job
245
types have been identified; these include firmware download, firmware update, and reboot. Each job type
246
has a different sequence of states it may pass through. The job may contain one action, or there may be
247
a series of actions taken as part of the job execution.
248
Refer to Table 7 for a list of job types.
249
6.2 Creating Jobs
250
Platform management jobs are created as the result of invoking an extrinsic method for performing a
251
specific task. Jobs that are created as the result of an extrinsic method invocation are initially created
252
without a start time defined and require a management client script or application to subsequently set the
253
scheduled start time by specifying job(s) and start time in a job queue. Note that the reset of the iDRAC
254
itself due to a requested reset or hard reboot does not cause the created jobs to be cancelled. The
255
created jobs will persist and could be executed.
256
6.3 Grouping Jobs
257
One or more jobs are be grouped together in job queues to define job order, start time, and to prepare the
258
job grouping for execution in another environment such as Unified Extensible Firmware Interface(UEFI). If
259