White Papers

10 Version 1.2.0
the Lifecycle Controller is to perform the system reboot needed to execute update jobs, a reboot job is
260
included in the job queue definition.
261
6.4 Scheduling Jobs
262
Jobs, such as firmware updates, that are created as a result of extrinsic method invocations are initially
263
unscheduled. One or more job can be scheduled to start immediately or at a specified start time by
264
setting up a job queue. Job queues are setup by calling the SetupJobQueue() method on the job service.
265
6.5 Canceling Jobs
266
Jobs may be canceled by management application. Job can be cancelled either by calling delete instance
267
method on a job instance or through invoking DeleteJobQueue() method but note that using the
268
“JID_CLEARALL” parameter value in the DeleteJobQueue() method will delete all the jobs including the
269
completed or failed ones.
270
When a pending job is cancelled, all the tasks related to the job will be deleted. If the job is already
271
running, then the instrumentation will delete all the job’s pending tasks and will attempt to undo all the
272
job’s completed tasks. If the job was already completed, cancelling the job will not undo its tasks.
273
6.6 Auto-Deleting Completed Jobs
274
Completed jobs will be deleted as a result of the auto-delete policy. Management applications may
275
specify the threshold for activating the auto-delete policy and the time criterion for auto-deleting
276
completed jobs. Once the auto-delete policy is activated, it will delete the jobs that have been completed
277
for more than the specified time criterion. The DCIM_JobService.DeleteOnCompletionTimeout property
278
represents the time criterion for the auto-delete policy with default value of 2880 minutes that can be
279
modified through the SetDeleteOnCompletionTimeout() method. The
280
DCIM_JobService.StartAutoDeleteAtThreshold represents the auto-delete policy activation threshold and
281
has a default value of 50% of the maximum number of jobs possible in the job queue.
282
6.7 Maintenance Windows
283
A client script or application that performs platform hardware management, may define specific
284
maintenance time slots. Time slot specification includes being able to specify a scheduled job start time
285
and a duration interval after which, if the job has not been executed, then the job has failed.. The time slot
286
is defined using the StartTimeInterval and Untiltime parameters on the extrinsic method.
287
6.8 Job Status Lifecycle
288
LC jobs have a specific workflow associated with their lifecycle. These workflows are provided as a
289
sample to clarify the job lifecycle and the changes to the job status as it progresses from creation to
290
completion. Typically, LC jobs fall within two categories configuration jobs and update jobs.
291
6.8.1 Configuration Job
292
The workflow below details the configuration job workflow for setting RAID attributes. NIC and BIOS
293
attribute configuration follows a similar workflow with an additional terminal state, “Completed with Errors”.
294
Importantly, in all the configuration job workflows, the CreateTargetedConfigJob() method can schedule
295
both the reboot and the created job at the same time. If the CreateTargetConfigJob() method is invoked
296
with parameter values to schedule both the reboot and the created job, then the job state transitions
297
directly from “No Job” to the “JobStatus=Scheduled.”
298