Standards, Industry, and the Roadmap to Grid Adoption. Dr. David Snelling Vice Chair of Standards Global Grid Forum / Fujitsu Labs Europe. Motivation. Need for Standards Stability, Choice, Flexibility, Competition, Collaboration, ... To Develop Standards we Need Clarity - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Leading the pervasive adoption of grid computing for research and industry
Dr. David SnellingVice Chair of StandardsGlobal Grid Forum / Fujitsu Labs Europe
Motivation
• Need for Standards− Stability, Choice, Flexibility, Competition,
Collaboration, ...
• To Develop Standards we Need Clarity− Definitions of concepts− Organization of work through Architectural
Frameworks
• We also Need a Roadmap− Accelerate the development of the “right”
specifications− Track gaps and requirements− Demonstrate progress− Support planning in industry and research
Notions of Grid
• Collaboration Grids− Multiple institutions, secure, widely distributed, VOs− Service level agreements & commercial partnerships− Business model: Increase overall revenue
• Enterprise Grids− Virtualization of enterprise resources and applications − Aggregation and centralization of management− Business model: Reduce total cost of ownership
• Clusters− Networks of Workstations, Blades, etc.− Cycle scavenging, Homogeneous workload− Business model: Lower marginal costs
• Parallel Processing Systems− Parallel processing for single applications Incr
• Enterprise Grids are about− Virtualization: Uniform encapsulation of resources:
• Compute, data, applications, support, ...− Integration: Creation of a structured whole from the parts.− Automation: Most management tasks, mostly automatic.
• Unimplemented, Implemented, Interoperable, Community, Adopted, and Ubiquitous.
Adoption Level Definitions
• Unimplemented− Although the specification exists and may be viewed as
stable, no implementation exists. There may be prototypes under development within various organizations, which are not available outside that organization.
• Implemented− There exists at least one implementation that is generally
available for testing and/or deployment that according to the authors (or third parties) implement the specification.
• Interoperable− There exists at least two implementations, as defined above,
that interoperate. There must be a report detailing at least one interoperability workshop.
Adoption Level Definitions Continued
• Community− At least one of the interoperable implementations, as defined
above, is deployed and used on a regular basis by a specific community. This may be due to either a lack of acceptance of the specification by the community at large or due to the specialist nature of a specific specification.
• Adopted− There exists more than one interoperable implementation, as
defined above, and each implementation is used across several communities. Commercially supported implementations are available. This may be either as a product or support for an open source implementation. There may be some restriction on which platforms support the implementations or other aspects that restrict the availability of the implementations.
• Ubiquitous− Interoperable implementations exist for virtually all platforms.
Commercial support is available, but provided transparently as part of the supporting infrastructure.