© 2006 OpenGridForum Standards Orientation OGF-19, Tuesday, January 30, 2007 Lee, Cohen,...

© 2006 OpenGridForum

Standards Orientation

OGF-19, Tuesday, January 30, 2007

Lee, Cohen, Subramanian

2© 2006 OpenGridForum

OGF IPR Policies Apply

• “I acknowledge that participation in this meeting is subject to the OGF Intellectual Property Policy.”• Intellectual Property Notices Note Well: All statements related to the activities of the OGF and addressed to

the OGF are subject to all provisions of Appendix B of GFD-C.1, which grants to the OGF and its participants certain licenses and rights in such statements. Such statements include verbal statements in OGF meetings, as well as written and electronic communications made at any time or place, which are addressed to:

• the OGF plenary session, • any OGF working group or portion thereof, • the OGF Board of Directors, the GFSG, or any member thereof on behalf of the OGF, • the ADCOM, or any member thereof on behalf of the ADCOM, • any OGF mailing list, including any group list, or any other list functioning under OGF auspices, • the OGF Editor or the document authoring and review process

• Statements made outside of a OGF meeting, mailing list or other function, that are clearly not intended to be input to an OGF activity, group or function, are not subject to these provisions.

• Excerpt from Appendix B of GFD-C.1: ”Where the OGF knows of rights, or claimed rights, the OGF secretariat shall attempt to obtain from the claimant of such rights, a written assurance that upon approval by the GFSG of the relevant OGF document(s), any party will be able to obtain the right to implement, use and distribute the technology or works when implementing, using or distributing technology based upon the specific specification(s) under openly specified, reasonable, non-discriminatory terms. The working group or research group proposing the use of the technology with respect to which the proprietary rights are claimed may assist the OGF secretariat in this effort. The results of this procedure shall not affect advancement of document, except that the GFSG may defer approval where a delay may facilitate the obtaining of such assurances. The results will, however, be recorded by the OGF Secretariat, and made available. The GFSG may also direct that a summary of the results be included in any GFD published containing the specification.”

• OGF Intellectual Property Policies are adapted from the IETF Intellectual Property Policies that support the Internet Standards Process.


Standards Orientation

• Goal:• Familiarize and engage OGF and wider

grid community in the Requirements and Standards Alignment Process


OGF Requirements Track

OrientationSession

Requirements Group Sessions(Pharma, Finance, Vendor

Adoption, SN-CG, EGR-RG, etc.

Rollup&

Prioritization

TSCReport-Out

•This is a plenary session for all persons involved in the requirements track•Explain what “Grid” is in terms of the key requirements that OGF is currently addressing•Direct requirements groups to evaluate relevance of OGF requirements relative to the individual needs of each group•Individual requirements group sessions

to determine how relevant are the requirements that OGF is currently addressing•Rollup results from individual requirements groups and be able report-out on relevance of requirements that OGF is currently addressing

•Report-out on alignment gap of the requirements that OGF is currently addressing and the possible gap closure recommendations•Set expectation for timeline of gap closures


Requirements & Standards Alignment

Promote requirements that OGF is already addressing

WIN-WIN!!

Steer OGF standards to be more relevant to the enterprise

Relevance to OGF

Rel

evan

ce t

o E

nter

pris

e


OGF Technical Strategy/Stakeholder Alignment Process

OGF Technical Strategy & Roadmap

Requirements Workshops

Uses Cases

Requirements

Best Practices

Architectures

Specifications

Milestones

OGF Events

OGF Document Series

Technical Strategy Committee Standards Groups

& Workshops

Analysis, Interpretation & Analysis, Interpretation & Prioritization of RequirementsPrioritization of Requirements

Application of Best Known Application of Best Known Practices and Current StandardsPractices and Current Standards


The OGF Alignment Process (A More Detailed View)

ERG-RG

Financial

Telco

Pharma

EDA

SN-CG

Vendors

RequirementsSolicitation

Applications

Compute

Data

Infrastructure

Management

Architecture

Security

StandardsGroups

RequirementsRollup, Analysis

&Prioritization(ERG-RG)

TSCGAP Analysis

What WGs are doing over time (spec roadmap)

• Composite roadmap• Gap analysis btwn WG roadmap vs. prioritized Req• Recommended actions

Prioritized Req and Req Patterns

Req

Req and Req Patterns

RequirementsSpecs

BestPractices

Req

Best PracticeWorkshops

Req


TSC Gap Closure Recommendations

Condition Recommended Action

UC covered by an existing OGF WG/spec(s)

• This is more of a communication issue, so attend existing group and communicate UC/spec association

UC is not covered by an existing OGF WG/spec

• UC out of scope for OGF so no action• Form a new Standards WG to create a specification• Change the scope of existing WG• Use Best Practice as an interim solutions (during standards development)• “Open Letter” to the vendor/developer community to implement• Handoff to another org


Current OGF Standards Work

• ApplicationsDistributed Resource Mgmt App. API WG (drmaa-wg)Grid Checkpoint Recovery WG (gridcpr-wg) Grid Information Retrieval WG (gir-wg)Grid Remote Procedure Call WG (gridrpc-wg)Simple API for Grid Applications Core WG (saga-core-wg)

• ArchitectureOGSA Naming Working Group (ogsa-naming-wg) Open Grid Services Architecture WG (ogsa-wg)

• ComputeGrid Resource Alloc. Agreement Protocol WG (graap-wg) Job Submission Description Language WG (jsdl-wg) OGSA Basic Execution Services WG (ogsa-bes-wg) OGSA High Perf. Computing Profile WG (ogsa-hpcp-wg) OGSA Resource Selection Services WG (ogsa-rss-wg)

• DataData Format Description Language WG (dfdl-wg) Database Access and Integration Services WG (dais-wg) Grid File System Working Group (gfs-wg) Grid Storage Management WG (gsm-wg) GridFTP WG (gridftp-wg) Info Dissemination WG (infod-wg) OGSA ByteIO Working Group (byteio-wg) OGSA Data Movement Interface WG (ogsa-dmi-wg) OGSA-Data Working Group (ogsa-d-wg)

• InfrastructureGrid and Virtualization Working Group (gridvirt-wg) Network Mark-up Language Working Group (nml-wg) Network Measurements Working Group (nm-wg)

• ManagementApplication Contents Service WG (acs-wg) Configuration Description, Deployment, and Lifecycle

Management WG (cddlm-wg) Glue Schema Working Group (glue-wg) OGSA Resource Usage Service WG (rus-wg) Usage Record WG (ur-wg)

• SecurityOGSA Authorization WG (ogsa-authz-wg) Trusted Computing Research Group (tc-rg)


OGF-18 Grid Requirements Roll-up

• INFORMATION ARCHITECTURE• Metadata Schemas, Ontologies & Semantics• Data Profiling• Data-tagging, including managing files

• DISCOVERY• Detailed Asset Discovery• API for Product Capability Discovery

• Extract information about a project or a product• Lets users grab the right data -- categorizing data

• Content/Data Discovery• Catalogue-based Data Access

• RESOURCE VIRTUALIZATION• Dynamic Provisioning

• Capacity on demand• Capacity grows as available

• Content Provisioning• Provisioning and Capacity Management

• JOB MANAGEMENT• Distributed Execution• Job Submission• Job control management• Job Migration

• DATA MANAGEMENT• Data Copy, Data Movement • Backup• Storage Policy Mgmt• Replica Mgmt• Caching (local disk, indexes, memory)• Data Grid APIs

• GRID MANAGEMENT• Mgmt Console GUI• Asset Management and Topology• Policy Management and Quotas• Mitigate management overhead• Transition/evolution models

• WORKFLOW• Planning• Management (Cent. & Dist.)

• SCHEDULING• Meta scheduler, data aware

• MONITORING & EVENT NOTIF.• Monitoring, Auditing and Alert Mgmt

• FAULT TOL. & ERROR MGMT• Deep Error Analysis• Error Audit• Verification & Audit• Root Cause Analysis• Job error management• Very high levels of uptime

• SECURITY• Grid Identity Mgmt• Strong Security• Multiple domains

• ACCOUNTING & AUDITING• Billing and Chargeback

• Chargeback models• Business issues (charge back)

• Sarbanes-Oxley Support• SYSTEM DEVEL & DEPLOY

• Simplify application development• End-User Tools and Envs

• AUTONOMIC BEHAVIORS • Monitoring• Semantics• Planning• Action


TS&RSimplified Specification Roadmap


Synopsis of Some Standards (1/2)

• Simple API for Grid Applications• A simple API that tries to hide most grid complexity while providing

common “look-and-feel” for basic operations, e.g., remote file access, remote job management, etc. Does not replace lower level tools that actually do these functions.

• Distributed Resource Mgmt Application API• Provides an API submit and manage remote jobs. Many attributes can

be set prior to execution.

• Job Submission Description Language• XML-based language for describing jobs to be submitted to a grid. Does

not address actual job submission or management.

• OGSA-Data Movement Interface• Will provide an abstract interface for data movement (point-to-point,

third-party) that is transport-agnostic.


Synopsis of Some Standards (2/2)

• Grid File Transfer Protocol• This document builds on RFC 959 “File Transfer Protocol” for

grids. Grid Security Infrastructure is incorporated, along with disk striping, channel striping, third-party transfer.

• Configuration Description, Deployment and Lifecycle Mgmt• CDDLM consists of five documents and is based on SmartFrog (Smart

Framework for Object Groups). The Configuration Description Language describes system configuration of components in the CDDLM Component Model. The Deployment API uses a deployment descriptor to manage deployment lifecycle.

• Open Grid Services Architecture, Web Services Resource Framework Basic Profile 1.0• The specifications considered in this profile are specifically those

associated with the addressing, modeling, and management of state: WS-Addressing, WS-ResourceProperties, WS-ResourceLifetime, WS-BaseNotification, and WS-BaseFaults.


BACK-UPS


What Are the Failure Modes for this Process?

OGF Technical Strategy & Roadmap

Requirements Workshops

Uses Cases

Requirements

Best Practices

Architectures

Specifications

Milestones

OGF Events

OGF Document Series

Technical Strategy Committee Standards Groups

& Workshops

Analysis, Interpretation & Analysis, Interpretation & Prioritization of RequirementsPrioritization of Requirements

Application of Best Known Application of Best Known Practices and Current StandardsPractices and Current Standards

Skewed ornon-rep.

req’ments

Faulty orincomplete

analysis

WGs lateor off-topic

StandardsNot Adopted


1.Requirements1.Requirements

The Progressionof a Given Standard

What’s really important for Vendors?

2.Standards2.Standards

3.Product3.Product

For standards under development at OGF,For standards under development at OGF,what are the adoption stumbling blocks?what are the adoption stumbling blocks?

1) Concept

2) Working Group

3) Draft Specification

4) Interoperability Testing

5) Proposed Recommendation

6) Full Recommendation

7) Product (commercially supported)

8) Deployment (actual production use)


What Are the Issues Surrounding Adoption of OGF Standards?• Possible Issues:

• Too Broad/Too Large• Too Monolithic• Too Vague• Too Specific (constraining)• Off-target• Don't need it• Too Expensive to adopt• Too Divergent from my business plan• Too Late• Technical Gap in one area prevents adoption of completed standard in another

area• The 800-lb. gorillas (MS, IBM, … ) are going to define it

• What are the Issues for Specific Standards?• What are the Possible Mitigation Efforts?

• Every OGF standard should have an Adoption Strategy


Standards Grid Domains

• 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


Requirements/Standards Roadmap

Requirements RoadmapRequirements Roadmap

R1-R10R1-R10DefinedDefined



OGF Standards RoadmapOGF Standards Roadmap

R1-R10R1-R10Comprehended Comprehended in Specs xyzin Specs xyz



Grid Vendor RoadmapGrid Vendor Roadmap

R1-R10R1-R10Comprehended Comprehended in Products xyzin Products xyz



© 2006 OpenGridForum Standards Orientation OGF-19, Tuesday, January 30, 2007 Lee, Cohen,...

Documents

Transcript of © 2006 OpenGridForum Standards Orientation OGF-19, Tuesday, January 30, 2007 Lee, Cohen,...