RE: [cgs-wg] updated JSIM UML and MOF

["Andrea Westerinen" <andreaw@cisco.com>]

Title: Message

A few more minor changes, since the MOF would not compile.

 

1. BatchJobGroup needs a key property since it is a concrete class.  I added InstanceID as this is the convention for all new classes in CIM.

 

2. I thought that it would be useful to clarify in the Descriptions that a completed Job that is not recurring is not on any Queue.  And, the status of a recurring Job toggles between running and completed, and is only pending before it starts running for the first time. The fact that the Job is still on a Queue should indicate that it is Recurring even though it has a Completed status.

3. We should design a statistics class to keep information on a recurring Job's completions.  Otherwise, we only know the last/current state of the Job.

4. We should note that JobScheduleSettingData is scoped by a Job, or by a BatchService (ie, the defaults for any Jobs submitted to the Service).

The new files (addressing 1 and 2, above) are attached.  Do these changes seem reasonable?  We are finding these issues as we implement the model for the demo.

Andrea

-----Original Message-----
From: owner-cgs-wg@gridforum.org [mailto:owner-cgs-wg@gridforum.org] On Behalf Of Ellen Stokes
Sent: Wednesday, February 26, 2003 12:56 PM
To: cgs-wg@gridforum.org
Subject: [cgs-wg] updated JSIM UML and MOF
Importance: High

Attachment: batchjob022803.mof
Description: Binary data

Attachment: batch job - 28 feb 20031.pdf
Description: Adobe PDF document

Attachment: batch job - 28 feb 2003.vsd
Description: application/vnd.visio