© 2007 Open Grid Forum OGF Modeling Activities DMTF Alliance Partner Symposium Portland, 2007 July 18 Ellen Stokes

© 2007 Open Grid Forum 2 Agenda Workgroup Overview wrt Models OGSA GLUE Reference Model Conclusion

© 2007 Open Grid Forum 3 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

© 2007 Open Grid Forum 4 Output of Three Workgroups Information model (UML) Data model (XML, MOF, LDAP) Meta Model Common Model Reference Model V2.0 spec (publish 7/2008) hierarchy & relationships GLUE 1.x spec LDAP, XML, RDB Example DAGs Component models OGSA information Modeling guideline (publish 9/2007) OGSA info model OGSA XML Data tag Container/BES service info model (publish 9/2007) container/BES service MOF rendering (publish 8/2007) GLUE 1.x spec UML & table GLUE 2.0 spec XML GLUE 2.0 spec UML & table JSDL 1.0 BES1.0

© 2007 Open Grid Forum 5 Overlap or consolidation? Information model (UML) Data model (XML, MOF, LDAP) Meta Model Common Model Reference Model V2.0 spec hierarchy & relationships Example DAGs Component models OGSA information Modeling guideline OGSA info model OGSA XML Data tag GLUE 2.0 spec XML GLUE 2.0 spec UML & table JSDL 2.0? BES 2.0? consistent

© 2007 Open Grid Forum OGSA OGSA resource model design team, OGSA-BES WG, JSDL WG

© 2007 Open Grid Forum 7 OGSA Information Model Concept Managed Info Instances (Native Language) Advertised Capabilities (XML) Activity’s Requirements (XQuery) algorithms simple mapping and 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 have compatible language for easy mapping and selection – XML to advertise capabilities and XQuery to express requirements

© 2007 Open Grid Forum 8 OGSA Information Model Relationship matching advertisement request algorithms Managed Information Instances Various “detailed” information models including Glue, CIM, SDD/IUDD, SDM, and others Actual devices and components Monitoring Instrumentation

© 2007 Open Grid Forum 9 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 Managed Info Instances (Native Language) Advertised Capabilities (XML) Activity’s Requirements (XQuery) algorithms simple mapping and selection BES container GLUE schema JSDL requirements

© 2007 Open Grid Forum 10 Approved for CIMv2.16 experimental Basic Execution Service class Container is a profile of ComputerSystem (formal definition is TBD)

© 2007 Open Grid Forum GLUE Glue workgroup

© 2007 Open Grid Forum 12 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

© 2007 Open Grid Forum 13 Glue Resources Main Entities Compute Entities Storage Entities

© 2007 Open Grid Forum Reference Model

© 2007 Open Grid Forum 15 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

© 2007 Open Grid Forum 16 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

© 2007 Open Grid Forum 17 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