GIN the Standards Activity The HPC Profile WG

GIN & the Standards Activity The HPC Profile WG © 2006 Open Grid Forum GIN

Where are we now? • GIN is 1 year old: • I=Interoperation • I=Interoperability • Pragmatic operational decisions (Interoperation) • • • GIN Authentication/Authorisation Identity Management Information Services Jobs Submission Data & Files Applications © 2006 Open Grid Forum 2

The Interoperability • Initially a lower priority • Some demonstration with JSDL • NGS (Grid. SAM gateway), NAREGI, CROWN • Expanding importance within GIN • Feedback to standards group • Requirements to software providers for products • Early operational experience • Effectively ‘closing the loop’ between: Standards, Implementers & deployers GIN © 2006 Open Grid Forum 3

The state of play in jobs in 2006 • JSDL (Job Submission Description Language) • Recommended specification Jan 2006 • BES (Basic Execution Service) • Draft describing job submission API • HPCP (High Performance Computing Profile) • Pragmatic combination of BES & JSDL • Focussed on job submission to HPC clusters GIN © 2006 Open Grid Forum 4

HPCP Interoperability at SC 06 • Started as implementation activity • Validate specifications • Expanded engagement with GIN • Software providers engaged with production grids • Grid. SAM, Globus, CREAM/g. Lite, China. Grid, … GIN © 2006 Open Grid Forum 5

Feedback from SC 06 • Revised BES & HPCP specifications • Revised Security Support • Username/password over SSL • X. 509 certificates • Both WG’s moving to last call • Future Work: • Data staging GIN © 2006 Open Grid Forum 6

Further Interaction • Main topic of next session • Information Systems • Formation of GLUE-WG • Standard definition of attributes • Rendering into different systems • BDII, CIM, UDDI, MDS, … • Data Management • Activity within GSM WG GIN © 2006 Open Grid Forum 7

Notes from the discussion © 2006 Open Grid Forum GIN

Notes from Discussion • BES model maps to many different systems • Proxy services using standards ontop of production grids • Access to production resources • Without need to redeploy production software GIN © 2006 Open Grid Forum 9

Big Issues - Authentication • Username/password mixed enthusiasm • Need delegation & strong authentication • • • Production grids ‘demand’ X. 509 • • • Enterprise grids ‘demand’ username/password Need to decide Policy as to which deployers support Part of service meta-data • • Some split between proxy certs and pure certs If not going to use proxy certs. BIG migration issues X. 509 support varied in toolkits If multiple security profiles implementors (& deployers) will need to support several to ensure interoperability • • • Different emphasis in web service world Delegation MUST not be made a blocker to interoperation Pragmatic half-way house needed to go ANYWHERE Migration path from where we are now to Client discovery issue Discussed elsewhere – need report back to GIN • • • AG to send report back to SJN for redistribution to GIN Proposed solution for HPCP – traction elsewhere in OGF & OGSA? Use my. Proxy as a way of providing delegation. GIN © 2006 Open Grid Forum 10

Actions • GIN participants want to be able to use multiple auth mechanisms: • Provide feedback to OGF security actions • My. Proxy use: Grid for research majority • Username/password use: Enterprise & some research grids • What constraints come from GIN that need to be made visible to OGF? • Security conversion services may be one way forward • EL to send email to Security Ads for discussion at area meeting. GIN © 2006 Open Grid Forum 11

Process Interaction • GIN Standards • ‘Large fraction of production grids believe that JSDL & BES are a way forward for job submission’ • First instance standards compliant service gateways will provide means of accessing production grid resources • Expand beyond JSDL & BES GIN © 2006 Open Grid Forum 12

Deployment of HPCP • Deploy ‘permanent’ services for support • GENESIS II, NGS (Grid. SAM), EGEE, DEISA • Commitment to implement HPCP and track changes • First phase: deploy SC 06 service (now!) • Second phase: deploy revised service after HPCP public comment period (~3 -6 months) Discussed this week at OGF go out to public comment Code changes needed are small (~few days work) Have a ‘sensible’ security story (revised profile) • Third phase: part of native code (In the future – maybe!) • GIN ‘leaders’ to forward notifications of specs entering public comment to GIN lists GIN © 2006 Open Grid Forum 13

Big Issues • Data Staging • Support in JSDL • HPCP has optional data staging support • HPCP focussed on core use case • Data staging not essential for this use case GIN © 2006 Open Grid Forum 14

HPCP Profile(s) • Core profile: ‘pure’ job submission • First Extension: data staging as important GIN © 2006 Open Grid Forum 15

Need to discuss • SRM Specification GIN © 2006 Open Grid Forum 16