OGF Modeling Activities

1. OGF Modeling Activities DMTF Alliance Partner Symposium Portland, 2007 July 18 Ellen Stokes (stokese@us.ibm.com)

2. Agenda • Workgroup Overview wrt Models • OGSA • GLUE • Reference Model • Conclusion 2

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 3

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

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

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

7. Managed Info Instances (Native Language) Advertised Capabilities (XML) Activity’s Requirements (XQuery) simple mapping and selection algorithms OGSA Information Model Concept Capabilities and Requirements have compatible language for easy mapping and selection – XML to advertise capabilities and XQuery to express requirements • 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 • Instances info, e.g. CIM, GLUE • Granular • Expresses managed • information in the environment • May be virtualized 7

8. OGSA Information Model Relationship Various “detailed” information modelsincluding Glue, CIM, SDD/IUDD, SDM, and others advertisement request <Job> </Job> <Resource> </Resource> <Capabilities> </Capabilities> <Capabilities> </Capabilities> ManagedInformation Instances algorithms matching <Requirements> </Requirements> <Requirements> </Requirements> Monitoring Instrumentation Actual devices and components 8

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

10. Approved for CIMv2.16 experimental • Basic Execution Service class • Container is a profile of ComputerSystem (formal definition is TBD) 10

11. GLUE Glue workgroup

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 12

13. Glue Resources • Main Entities • Compute Entities • Storage Entities 13

14. Reference Model

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 15

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 16

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 17