OGF Standards Development

1. OGF Standards Development Chris Smith, VP of Standards, OGF DMTF Alliance Partner Technical Symposium Portland July 17th, 2007

2. Overview • OGF History & Mission • Organization of OGF • Groups & Documents • Standards Function • Technical Strategy for Standards • OGF & DMTF Alliance 2

3. History http://www.ggf.org http://www.gridalliance.org • Birthed in high performance computing community in 1998 • Merged with European & Asian grid efforts in 2001 • 52 groups and 81 documents • Birthed in enterprise data center community in 2004 • Raised awareness of grids in “end-user” organizations • 5 groups and several important documents Merger completed, June ’06; OGF Launched September of ‘06 3

4. Open Grid Forum Events & Forums Community Practice Industry Standards Bring communities together to share, innovate, workshop and outreach Leverage expertise & experience of the community to enable successful building and operating of grids Align with/influence other SDOs and/or develop specifications that lead to interoperable software standards 4

5. Events & Activities • Events enable our “Open Forum” mission • Assembles grid topic experts from around the world • Provides opportunity for grid professionals to network together • Allows buyers and sellers to interact • Provides a venue for major grid projects to collaborate • Enables cross-OGF alignment on technical strategy • Delivers relevant content to interested parties • Enables collaboration for the development of specifications 5

6. Events & Activities • 3 major events a year: Winter, Spring, Fall • Spread roughly equally by region (US, Europe, APAC) • Driven by attendance and host offers • Several types of content: • Group Sessions: BoFs and chartered group f2f meetings • eScience Program: refereed workshops and in-depth sessions on grid innovations and best practices • Enterprise Program: end-user deployment-focused sessions and requirements gathering • Tutorials: hands-on sessions; educational • Shorter, more focused events also possible • Occasional webcasts 6

7. BoD Advisory Committee Nominating Committee President Editor Technical Strategy Committee Enterprise eScience Standards Marketing Regional Operations Organization OGF Overview Document available at: http://www.ogf.org/rotate_headers/rotate_launch.php 7

8. Functions/Areas/Groups/Chairs Standards Function Functions consolidate Areas of like focus Standards Council VP, Standards Area Directors Program Manager OGF Editor Areas consolidate Groups of like focus Areas managed by Area Directors Standards Areas Liaisons Application Architecture Security Management Data Compute Groups are led by Chairs Infrastructure 8

9. Example: SAGA-Working Group Standards Function Standards Council Chris Smith, VP Steven Newhouse, Dieter Kranzlmueller, AD’s Joel Replogle Greg Newby Standards Areas Each group has an email list (saga-wg@ogf.org) and a GridForge project Application Area Note that SAGA-WG is one of many groups in this Area Simple API for Grid Applications (SAGA-WG) Co-Chaired by: Shantenu Jha , Thilo Kielmann , Tom Goodale 9

10. Group Types • Working Groups (WG) • Crisp focus on development of a specification or guideline • Clear milestones based on delivery of drafts and publication dates • Research Groups (RG) • Focus can be broader than WG, but must be clear • Milestones based on delivery of drafts, organization of workshops, and workshop reports • Technology exploration (e.g., Semantic Grid-RG) • Community Groups (CG) • Explore grid usage and requirements in a sector (e.g., Telco-CG) • Milestones based on delivery of requirements documents • Full Listing: • http://www.ogf.org/gf/group_info/areasgroups.php 10

11. How Groups Work • Because every group has a different charter and leadership, every group is different • Consistent things: • Work is announced on the group email list • Deliverables are normally one or more documents • Documents follow the same publication process (OGF Editor) • “Rough consensus and working code” is the rule of thumb • All work done under OGF IPR Policy • Inconsistent things: • Meeting cadence • Use of GridForge (web-based collaboration tool) for group work • Group deliverables differ based on chartered work 11

12. OGF Editor • Manages the publication process (GFD-C.1) and “pipeline” • Ensures documents are consistently formatted • Works with Area Directors/VPs to ensure technical viability of documents • Drafts submitted to the “editor pipeline” • Editor project in GridForge • http://forge.ogf.org/sf/projects/ggf-editor 12

13. Deliverables • Different Groups have different deliverables • Research groups may hold workshops and create proceedings documents and/or “best practice” documents • Working groups will likely deliver specifications but may have preliminary “informational” documents to lay the foundation • Community groups may hold workshops that capture requirements which are documented and given to working groups • Other groups may document a well-used process in the grid industry or in the OGF organization • Different deliverables require different document types 13

14. OGF Document Types • Informational • Informs the community of an interesting and useful Grid-related technology, architecture, framework, or concept • Specifies requirements related to a particular vertical application • Experimental • Informs the community of the results of Grid-related experiments, implementations, operational experience, or to propose an experimental specification 14

15. Document Types • Community Practice • Inform and influence the community regarding an approach or process that is considered to be widely accepted by consensus and practice in the Grid community or within the OGF organization • Recommendations (2 stage) • Documents a particular technical specification or a particular set of guidelines for the application of a technical specification. The recommendations documents are intended to guide interoperability and promote standard approaches. 15

16. Standards Function Overview • Set in the context of of alignment with • e-Science • Enterprise • Promote • Uptake • Interoperability • Run a Process • Output in the form of Standards Technical Strategy Committee Applications Architecture Management Security Data Compute Infrastructure OGF Liaison Standards 16

17. Standards Development • Short Version of the Process • A group of people interested in creating a standard hold a BoF (optional). • Grid Forum Steering Committee Approves a WG • In an open forum, the WG writes the specification • GFSG Review • Public Review • Final approval and publication • Complex Open Process, … • but things can move very fast when there is energy available. 17

18. Technical Strategy Overview • Defines the overall OGF technical strategy for the development of standards • Three-year timeframe from 2006 to 2010 • Describes the output of the OGF standards working groups as well as the requirements that drive them. • Technical Strategy Document • Focus Areas • Goals • Alignment Process • Use Cases • Roadmap 18

19. Broad and Narrow Grids • The concept allows for clearer communication encompassing all aspects and points of view on Grids. • A Broad Grid is any collection of services • A Narrow Grid is defined by both the technologies used, as well as the application focus. Some examples: • OGSA compliant Enterprise compute cluster • Web 2.0 Sensor Net linked to Google maps 19

20. Narrow Grids of Focus • Collaboration Grids • Multiple institutions, secure, widely distributed, VOs • Collaborative agreements & commercial partnerships • Financial Model: Increase overall revenue • Data Centre Grids • Centralized management of multiple platforms • Aggregation of enterprise resources and applications • Financial Model: Reduce Total Cost of Ownership (TCO) • Cluster Grids • Networks of Workstations, Blades, etc. • Cycle scavenging, Homogeneous workload • Financial Model: Lower marginal costs 20

21. Goals of the TSC • Identify use-cases, patterns, and scenarios • Publish documents • Design and drive the standards process. • Identify and highlight core architectural standards • Encourage software developers • From open source community and the commercial • To develop and implement standards • Hold regular alignment summits 21

22. Technical Strategy Process Open forum for grid innovation and outreach Open standards for grid software interoperability Alignment & Prioritization Uses Cases Architectures OGF Events Requirements Milestones Technical Strategy Committee Standards Groups & Workshops Requirements Workshops OGF Technical Strategy & Roadmap OGF Document Series Best Practices Specifications Alignment & Prioritization 22

23. A More Refined View Standards Groups Requirements Solicitation Best Practice Workshops Best Practices EGR-RG Applications Best Practices Req Req SN-CG Architecture Requirements Rollup, Analysis & Prioritization (EGR-RG) TSC GAP Analysis Financial Compute Telco Req Prioritized Req and Req Patterns Data Pharma Infrastructure What WGs are doing i.e. WG roadmap Req and Req Patterns EDA Management • Overall standards roadmap • Gap analysis of WG roadmap vs. prioritized Req • Recommended actions Security Vendors Requirements Specs 23

24. Technical Strategy & Roadmap “Moon Shot” Goal The Open Grid Forum should commit all its available resources to the goal that before this decade is out, commercial and academic organizations will build real operational grids using Open Grid Forum defined components. 24

25. High Value Use Cases • Grid APIs • Job Submit • File Movement • Application Provisioning • Data Provisioning and Data Grids • Grid Security 25

26. Lifecycle of a Standard • Concept - hold BOF to form… • Working Group - generates a… • Draft Specification - public comment… • Proposed Recommendation - implementations… • Interop - experience documents… • Full Recommendation - GFSG review… • Product - implemented in product… • Deployment - customer use of standard 26

27. Roadmap Snapshot 27

28. There is a Gap Analysis too • The Maturity column indicates the rough State of the Art with respect to each capability. • Categories: • Out of Scope for the OGF • Gap that OGF should be investigating • Area of Grid Research • Evolving area either in OGF or some other SDO • Capability with Mature specifications or solutions. 28

29. Gap Analysis 29

30. TS&R Document Status • Like all OGF documents it is always accessible in Gridforge • forge.gridforum.org/sf/projects/tsc • Has been through its Public Comment period • To be published in time for OGF21 in October 2007 30

31. OGF & DMTF Alliance • Intention of the alliance is to cross-leverage each organization’s domain strength • DMTF focus on distributed management infrastructure and information/data modeling of resources • OGF focus on the deployment, operation and access to resources in a Grid 31

32. Alliance Benefits • Collaboration on broadening CIM to encompass Grid concepts • Leverage technical and marketing resources in both DMTF and OGF • Coordinate development processes and priorities between DMTF and OGF to ensure DMTF modeling standards address Grid technology, and that OGF Grid services address management requirements • Education about technologies and activities across the organizations, and participation in each others events 32

33. Current Work Register • Review / Comment (1Q2007) • DSP 0225: URI Format for Published XML Schema • DSP 0230: WS-CIM Mapping Specification • Extrapolate from the OGSA-BES work and submit to DMTF a general container model (current work in progress) • Identify the base set of grid resources that need to be advertised that applications can consume (via requirements) and update the CIM as needed including how best to map/leverage information models. (current work in progress) 33

34. Liaisons • Tom Roney, OGF liaison to the DMTF • troney@ncsa.uiuc.edu • Mike Baskey, DMTF liaison to the OGF • mbaskey@us.ibm.com 34

35. Other OGF Sessions Information Modeling of Grid Resources: the OGF GLUE WG Approach • Sergio Andreozzi • Tuesday, 3pm OGSA Information Model Updates • Ellen Stokes • Wednesday, 10am OGSA Reference Model • Paul Strong • Wednesday, 1pm 35

36. Questions? 36