© 2007 open grid forum ogf modeling activities dmtf alliance partner symposium portland, 2007 july...

© 2007 Open Grid Forum

OGF Modeling Activities

DMTF Alliance Partner SymposiumPortland, 2007 July 18Ellen Stokes ([email protected])

2© 2007 Open Grid Forum

Agenda

• Workgroup Overview wrt Models

• OGSA

• GLUE

• Reference Model

• Conclusion


Resource Information Usage (An Observation)

• Resources are modeled for 3 purposes• Managing resources/information in the system/network• Advertising existence & capabilities of resources in the

system/network• Expressing (requesting) set of requirements to accomplish an

activity in the system/network• System/Network management is focused on

managing…..Grid is focused on advertising and requesting• System/Network management: models are granular & detailed;

examples are CIM, GLUE, Unicore, SDD, CMDB, TPM DCM, …• Grid: models similar but different focus…higher level, user friendly,

simpler, capabilities, requirements, more abstract• But Grid modeled information can and should build on and

re-use System/Network information…• For example, to route workload successfully, you don’t need to

know/specify lots of requirements


Output of Three Workgroups

Information model (UML) Data model (XML, MOF, LDAP)

MetaModel

CommonModel

Reference ModelV2.0 spec (publish 7/2008)

hierarchy & relationships

GLUE 1.x specLDAP, XML, RDB

Example DAGsComponent models

OGSA informationModeling guideline

(publish 9/2007)

OGSA infomodel

OGSA XMLData tag

Container/BES service info model (publish 9/2007)

container/BES serviceMOF rendering (publish 8/2007)

GLUE 1.x specUML & table

GLUE 2.0 specXML

GLUE 2.0 specUML & table

JSDL 1.0

BES1.0


Overlap or consolidation?

Information model (UML) Data model (XML, MOF, LDAP)

MetaModel

CommonModel

Reference ModelV2.0 spec

hierarchy & relationships

Example DAGsComponent models

OGSA informationModeling guideline

OGSA infomodel

OGSA XMLData tag

GLUE 2.0 specXML

GLUE 2.0 specUML & table

JSDL 2.0?

BES 2.0?consistent


OGSA OGSA resource model design team, OGSA-BES WG, JSDL WG


OGSA Information Model Concept

ManagedInfo Instances(Native Language)

AdvertisedCapabilities

(XML)

Activity’sRequirements

(XQuery)algorithms simple mappingand selection

• Instances info, e.g. CIM, GLUE• Granular• Expresses managed information in the environment• May be virtualized

• Abstracted and generated from managed information via algorithms • Simple, meaningful, and user friendly• Expresses the capabilities of an entity, e.g. container• May be virtualized• May be refreshed as managed information changes

• Simple, meaningful, and user friendly• Expresses an activity’s needs• May be virtualized

Capabilities and Requirements havecompatible language for easy mappingand selection – XML to advertise capabilitiesand XQuery to express requirements


OGSA Information Model Relationship

<Resource>

</Resource>

<Capabilities>

</Capabilities>

<Requirements>

</Requirements>

<Job>

</Job>

<Capabilities>

</Capabilities>

<Requirements>

</Requirements>

match

ing

advertisement request

algorithms

ManagedInformationInstances

Various “detailed” information models

including Glue, CIM, SDD/IUDD,

SDM, and others

Actual devices and components

MonitoringInstrumentation


Approach

• BES, JSDL, and GLUE provide insights into base capabilities and requirements of what’s needed to produce a draft set of elements (in XML) for advertisement and query for the Information Model

• GLUE• Glue 2.0 provides initial set of model elements to advertise• Subset and modified for ease of use, understanding, and

satisfying (matching) requirements with advertisements

ManagedInfo Instances(Native Language)

AdvertisedCapabilities

(XML)

Activity’sRequirements

(XQuery)algorithms simple mapping

and selection

BEScontainer

GLUEschema

JSDLrequirements


Approved for CIMv2.16 experimental

• Basic Execution Service class

• Container is a profile of ComputerSystem (formal definition is TBD)

ManagedSystemElement

(See Core Model (ManagedSystem Element))

LogicalElement

(See Core Model (Managed System Element))

System

(See Core Model(Enabled Logical Element))

Association

AggregationAssociation with WEAK reference

Inheritance

Aggregation with WEAKreference

w

w

* Equivalent to: 0 .. nComposition Aggregation

{E} Experimental Class or Property{D} Deprecated Class or Property

*

Service

CreationClassName: string {key}Name: string {override, key}PrimaryOwnerName : string {write}PrimaryOwnerContact : string {write}StartMode: string (10) {D, enum}Started: boolean

StartService(): uint32StopService(): uint32

*

*

ServiceAvailableToElement

ServiceAffectsElement

* *

BasicExecutionService {E}

CreateActivity( [IN] Request : string, [OUT] Identifier : string, [OUT] Job : ref CIM_ConcreteJob) : uint32 {enum}

TerminateActivity( [IN] Identifier : string[ ], [OUT] Response : boolean[ ], [OUT] Job : ref CIM_ConcreteJob) : uint32 {enum}

GetActivityStatus( [IN] Identifier : string[ ], [OUT] StatusResponse : string[ ], [OUT] Job : ref CIM_ConcreteJob) : uint32 {enum}

GetActivityDocuments( [IN] Identifier : string[ ], [OUT] Response : string [ ], [OUT] Job : ref CIM_ConcreteJob) : uint32 {enum}

GetAttributesDocument( [OUT] AttrsDoc : string[ ], [OUT] Job : ref CIM_ConcreteJob) : uint32 {enum}

HostedService

*w

1

HostedDependency

0..1

*

ComputerSystem

NameFormat {override, enum}Dedicated : uint16[ ] {enum}OtherDedicatedDescriptions : string[ ]ResetCapability : uint16 {enum}PowerManagementCapabilities : uint16 [ ] {D, enum}

SetPowerState ( [IN] PowerState : uint32 {enum}, [IN] Time : datetime) : uint32 {D}

EnabledLogicalElement

EnabledState : uint16 {enum}OtherEnabledState : stringRequestedState : uint16 {enum}EnabledDefault : uint16 {enum}TimeOfLastStateChange: datatimeOverwritePolicy : uint16 {E}{enum}PrimaryStatus : uint16 {E}{enum}DetailedStatus : uint16 {E}{enum}OperatingStatus : uint16 {E}{enum}CommunicationStatus : uint16 {E}{enum}RequestStateChange( [IN] RequestedState {enum}, [OUT] Job: CIM_ConcreteJob, [IN] TimeoutPeriod: dateTime): uint32 {enum}

Caption : stringDescription : stringElementName : string

ManagedElement

SystemComponent


GLUEGlue workgroup


GLUE Workgroup

• Building on 5 years modeling work carried out outside of OGF

• Goal: provide a recommendation for an abstract information model of Grid resources and reference implementations based on use cases• Unification of existing information models (e.g.,

GLUE Schema 1.x, NorduGrid Schema)• Scope: model all the information needed for

• Supporting Grid-level Scheduling• Inventory of available resources• Monitoring including jobs


Glue Resources

• Main Entities

• Compute Entities

• Storage Entities


Reference Model


Purpose

• A common language, glossary, taxonomy, ontology and formal model to describe Grids, what they are, how they are composed, managed, etc• Nouns• Relationships• Life-cycles

• Basis for • Interface design/specification• Architecture

• A foundation to build, extend, and link existing efforts, e.g. EGA Reference Model v1.5, OGSA, CDDLM


Reference Model v2.0

• Formal meta-model based on EGA Reference Model v1.5

• Basic UML 2.0 representation• Static Classes• State Transitions• Sequence Diagrams

• Extensive text annotation


Conclusion

• Common models of Grid resources are key for integration and usage

• Leverage of existing models and experience is necessary to advance the state of modeled information in a timely fashion

• Appropriate collaboration with DMTF is needed to expand the realm of managed information