Global Grid Forum 6, October 17, 2002 1

CIM-based Grid SchemaWorking Group

(CGS-WG)

GGF6Session 2

Global Grid Forum 6, October 17, 2002 2

GGF6 Agenda• Session 1 – 2:00-3:30PM Tuesday 10/15

(Gleacher 400)– Review of group charter and goals (25 mins)– Brief CIM Modeling Tutorial (45 mins)– Session 2 Planning (20 Mins)

• CGS/DAMED/NM joint meeting 2:00-3:30PM Wednesday (Sheraton Ohio)

• Session 2 – 8:00-9:30AM Thursday 10/17 (Sheraton 1)– Document/Mapping discussions

Global Grid Forum 6, October 17, 2002 3

CGS WG 2nd Session Planning

• Strawman JSIM document (http://www.isi.edu/~flon/cgs-wg/jsim.doc)– Please download and review prior to session.

• Process for updating/enhancing the document.

• Discussion and plan for delivering MOF, XML, LDAP versions of the schema.

Global Grid Forum 6, October 17, 2002 4

(See Core Model)

EnabledLogicalElement

System

(See Core Model)

Process

CreationClassName : string {key}Handle : string {key}Priority : uint32ExecutionState : uint16OtherExecutionDescription : stringCreationDate : datetimeTerminationDate : datetimeKernelModeTime : uint64UserModeTime : uint64WorkingSetSize : uint64

OSProcess

1

CreationClassName : string {key}Name : string {override, key}

JobDestination

HostedJobDestination

JobStatus : stringTimeSubmitted : datetimeScheduledStartTime : datetimeStartTime : datetimeElapsedTime : datetimeUntilTime : datetimeNotify : stringOwner : stringPriority : uint32PercentComplete {units}DeleteOnCompletion : booleanErrorCode : uint16ErrorDescription : string

KillJob ([IN] DeleteOnKill :boolean) : uint32 {enum}

Job

JobDestination

Jobs

*

*w

OperatingSystem

(See System Model(Operating System)

Batch Jobs, Submission, and Processing

ServiceProcess

*

*

*w

1

(See Core Model)

LogicalElement

(See Core Model)

ManagedSystemElement

(See Core Model)

ManagedElement

(See Core Model)

SettingData

(See Core Model)

ScopedSettingData

ScheduledStartTime : datatimeReoccuringElapsedTime : datetimeUntilTime : datetimeNotify : stringOwner : stringPriority : uint32DeleteOnCompletion : boolean

ScheduledJob

OwningJobElement

0..1

*

AffectedJobElement

*

*

ConcreteJob

InstanceID : string {key}Name : string {override, req'd}

ProcessOfJob

* *

Association

AggregationAssociation with WEAK reference

Inheritance

Aggregation with WEAK reference

w

w

* Equivalent to: 0 .. nComposition Aggregation

OwningBatchJobQueue

BatchSAP

BatchProtocol : uint16[ ] {enum}BatchProtocolInfo : string[ ]

BatchService

<insert properties for a batch service>

*

*

(See Core Model)

Service

(See Core Model)

ServiceAccessPoint

BatchJob

JobID : string {key}SchedulingInformation :stringMaxCPUTime : uint32 {units}CPUTimeUsed : uint32 {units}BatchJobStatus : uint16 {enum}TimeCompleted : datetimeJobOrigination : string

BatchQueue

QueueEnabled : booleanQueueAccepting : booleanNumberOnQueue : uint32QueueStatus : uint16 {enum}QueueStatusInfo : stringDefaultJobPriority : uint32JobPriorityHigh : uint32JobPriorityLow : uint32MaxJobWallTime : uint32 {units}MaxJobCPUTime : uint32 {units}MaxTotalJobs : uint32MaxRunningJobs : uint32RunningJobs : uint32WaitingJobs : uint32

QueueForBatchService*w

1

*

*w

QueueForwardsToBatchSAP*

Logical File

(See System Model(File System)

DataFile

(See System Model(File System)

*

ProcessExecutable

*

OSServicingJob

OSServicingQueue

*

*

*

*

RecurringBatchJob

<any addtl properties needed?>

BatchSchedulingData

*

*

Global Grid Forum 6, October 17, 2002 5

JSIM Document IssuesIn the UML diagram, the link type between ScheduledJob and JobData must be changed from association to inheritance. Maybe it would also make sense to add a section where changes to the document are listed. In order to facilitate the comparison between the LTC/NCSA model and this proposal I've compiled the following list of classes in the models

Equivalent Classes (w/o associations)

ClusterQueue BatchQueue

ClusterJob BatchJob

ClusterScheduler BatchService

Classes only in JSIM proposalBatchSAPRecurringBatchJob

Classes only in LTC/NCSA modelClusterClusterResourceClusterHost

I am not so sure whether we can get away without defining resources (meaning groups of candidate execution hosts) to get the complete picture. They need not to be fully fleshed out, but could exist as abstract classes. Further, I like and support the approach to have a separate class for recurring/planned Jobs.

There's one system hosting the BatchService, which is maintaining the BatchQueues and is scheduling the BatchJobs to run on some other systems. If you exchange the class names according to the list above, the same is true for the LTC/NCSA model. In order to make such semantic information available to readers, it would help to add some use case scenarios. We should reuse (and extend) the use cases the NPi work group has developed so far.

Global Grid Forum 6, October 17, 2002 6

JSIM Document Issues

• Job dependencies? • Jobs are not necessarily just a job, but

rather a work flow (do we need to model this?) i.e. traditional batch job vs. grid job