1 / 9

Evolution of High-Performance Computing Standards: Insights from Steven Newhouse, Microsoft

This document outlines the historical development and milestones of the High Performance Computing (HPC) Basic Profile and related working groups. Key achievements include the formation of the HPC Profile Working Group in 2006, the publication and ratification of various specifications, such as the Job Submission Description Language (JSDL) and Basic Execution Service (BES). It highlights Microsoft's engagement with the Open Grid Forum (OGF), the evolution of its HPC products, and the importance of continuous interoperability and user feedback in shaping standards and products over time.

mieko
Télécharger la présentation

Evolution of High-Performance Computing Standards: Insights from Steven Newhouse, Microsoft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The HPC Basic Profile Steven Newhouse Microsoft Corporation

  2. A Short OGF History Lesson… • High Performance Profile (HPCP) WG • Formed – May 2006 • HPCBP 1.0 published – August 2007 • HPCBP 1.0 ratified – Spring 2008 • Job Submission Description Language (JSDL) WG • Formed – Seattle, June 2003 • JSDL 1.0 published – November 2005 • JSDL 1.0 ratified – Spring 2008 • Basic Execution Service (BES) WG • Formed – Seoul, March 2005 • BES 1.0 published – August 2007 • BES 1.0 ratified – Spring 2008 Condor (ClassAds) Globus (RSL) Stephen McGough, July 2001 Globus (WS-GRAM) Unicore GridSAM

  3. Microsoft Interaction with OGF • Decision made to engage in HPC market • Probably 2004 • Engagement with OGF by HPC Group • Late 2005/Early 2006 • Microsoft Compute Cluster Server 2003 v1 • Launched June 2006 • Microsoft HPC Server 2008 • Will be launched Summer 2008 • Will include implementation of HPC Basic Profile 1.0

  4. Engagement Options • Drive • Edit/Submit/Comment/Review documents • Influence • Submit/Comment/Review documents • Monitor • Review documents • Ignore • Do nothing

  5. Implementing the HPC Basic Profile • From 1st draft to Proposed Recommendation • Duration ~2 years • HPCBP was only ~15 months • Develop prototype alongside specification • Essential to make a good specification • Do some interop to validate specification (SC06) • Build experience on P-REC • Duration: minimum 6 months in OGF • Do more interop (SC07) to write experience document

  6. Time & Money • Prototyping • Time: ~0.25 FTE for 18 months • Money: Travel (Meetings, F2F, …) & Telecoms • Experience Document • Time: ~0.25 FTE for 6 months • Money: Server for interop & Telecoms • Into Product • Time: ~0.5 FTE for 6 months

  7. HPC BP into Product • There are still decisions to be made • Username & password • X.509 certificates • Operational and Support model • Development, Testing, Documentation & Training • Partners, Marketing & Adoption • Does solution still meet use cases? • Continuous focus, but part of critical review

  8. HPC Basic Profile 1.0 • Shipped with Windows HPC Server 2008 • Available Summer 2008, beta available NOW! • Uses Windows Communication Foundation • Supporting: • HPC Basic Profile 1.0 • HPC File Staging Profile 1.0 • JSDL 1.0 • HPC Profile Application 1.0 • Basic Execution Service 1.0

  9. Summary • Standards can be vital part of a product • Time to develop standards is not short – 2+ yrs • Product cycle 18-24 months • Big difference between prototype and product • Interop needs to be continuous, but critical points • Two main decision points: • Drive, Influence, Monitor or Ignore • Implement in product

More Related