1. Adopting and Setting Standards The NAREGI Strategy Satoshi Matsuoka Professor, Global Scientific Information and Computing Center, Deputy Director, NAREGI Project Tokyo Institute of Technology / NII GGF16 Thursday Keynote, Athens with Dave Snelling

2. National Research Grid Infrastructure (NAREGI) 2003-2007 Petascale Grid Infrastructure R&D for Future Deployment –$45 mil (US) + $16 mil x 5 (2003-2007) = $125 mil total –PL: Ken Miura (Fujitsu  NII) Sekiguchi(AIST), Matsuoka(Titech), Shimojo(Osaka-U), Aoyagi (Kyushu-U)… –Participation by multiple (>= 3) vendors, Fujitsu, NEC, Hitachi, NTT, etc. –NOT AN ACADEMIC PROJECT, ~100FTEs –Follow and contribute to GGF Standardization, esp. OGSA AIST Grid Middleware R&D SuperSINET Grid R&D Infrastr. 15 TF => 100TF National AAA Infr. “NanoGrid” IMS ~10TF (BioGrid RIKEN) OtherInst. National Research Grid Middleware R&D Nanotech Grid Apps (Biotech Grid Apps) (Other Apps) Titech Fujitsu NEC Osaka-U U-Kyushu Hitachi Focused “Grand Challenge” Grid Apps Areas IMS

3. Industry/Societal Feedback International Infrastructural Collaboration ● Restructuring Univ. IT Research Resources Extensive On-Line Publications of Results Management Body / Education & Training Deployment of NAREGI Middleware Virtual Labs Live Collaborations Towards a Cyber-Science Infrastructure for R & D UPKI: National Research PKI Infrastructure ★ ★ ★ ★ ★ ★ ★ ☆ SuperSINET and Beyond: Lambda-based Academic Networking Backbone Cyber-Science Infrastructure （ CSI) Hokkaido-U Tohoku-U Tokyo-U ＮＩＩＮＩＩ Nagoya-U Kyoto-U Osaka-U Kyushu-U （ Titech, Waseda-U, KEK, etc.) NAREGI Output GeNii (Global Environment for Networked Intellectual Information) NII-REO (Repository of Electronic Journals and Online Publications

4. Standards: Setting & Adoption Critical to Grid Adoption & Longevity Project lifetimes limited Most production centers, commercial entities, and users won’t commit their time & money unless longevity guaranteed –A few brave ones… (high-risk, high-return) –Success legacies overtold Responsible Action for major research grid infrastructural projects (e.g. NAREGI) to guarantee longevity beyond project lifetime Commercial Adoption by IT vendors: ISPs, ISVs, ASPs, etc. key for such longevity –But how do we achieve that?

5. Approach: “Bait and Catch” --- Typical Japanese National Project Strategy --- IT vendors involved (seriously) from Day 1 Public entity project benefactors should not solely expend its grants to sustain itself –Most money going to IT vendors to have them commit OTOH, vendors are later pressured by the government not to make direct profit (Exclusive IPR acquisition or) standardization used as bait for commercial adoption –Thus, even a research grid infrastructural project MUST FOCUS on standards, above all other priorities Then, standards & supporting technologies are DIRECTLY transferred to IT vendors –Productization and support => longevity => adoption !

6. A Picture is Worth a 1000 Words… Picture deleted due to copyright reasons. It had a snapshot of an European Toyota car TV commercial where a prop car was being used to bait a young guy to approach a lake where a gigantic octopus would suddenly appear and instantly whisk him away with his huge tentacles. Thus the joke “catch-and-bait”, and if you are reading this slide you have to roll over laughing here :-)

7. Work Package Structure (~100 FTEs): –Universities and National Labs: technology leadership –Vendors (Fujitsu, NEC, Hitachi, etc.): professional development, commercial support WP-1: Resource Management: –Matsuoka(Titech), Nakada(AIST/Titech) WP-2: Programming Middleware: –Sekiguchi(AIST), Ishikawa(U-Tokyo), Tanaka(AIST) WP-3: Application Grid Tools: –Usami (new FY2005, NII), Kawata(Utsunomiya-u) WP-4: Data Management (new FY 2005, Beta): –Matsuda (Osaka-U) WP-5: Networking & Security –Shimojo(Osaka-u), Oie( Kyushu Tech.) WP-6: Grid-enabling Nanoscience Appls –Aoyagi(Kyushu-u) R&D in Grid Software and Networking Area (Work Packages)

8. FY2003FY2004FY2005FY2006FY2007 UNICORE/Globus/Condor-based R&D Framework Globus4/OGSA/WSRF-based R&D Framework Utilization of NAREGI NII-IMS Testbed Utilization of NAREGI-Wide Area Testbed Prototyping NAREGI Middleware Components Development and Integration of αrelease Development and Integration of βrelease Evaluation on NAREGI Wide-area Testbed Development of OGSA-based MW beta 1, 2, Verification & Evaluation Of Ver. 1 Apply Component Technologies to Nano Apps and Evaluation Evaluation of α release in NII-IMS Testbed Evaluation of βRelease By IMS and other Collaborating Institutes Development and deployment of β1, 2, 3,… αRelease (internal) OGSA(subset)/ Unicore+GT2/3/3.9 β1 Release (public) OGSA/WSRF/GT4 GGF17 Version 1.0 Release Midpoint Evaluation NAREGI Middleware Roadmap

9. List of NAREGI “Standards” (beta 1 and beyond) GGF Standards and Pseudo-standard Activities set/employed by NAREGI GGF “ OGSA CIM profile ” GGF AuthZ GGF DAIS GGF GFS (Grid Filesystems) GGF Grid CP (GGF CAOPs) GGF GridFTP GGF GridRPC API (as Ninf-G2/G4) GGF JSDL GGF OGSA-BES GGF OGSA-Byte-IO GGF OGSA-DAI GGF OGSA-EMS GGF OGSA-RSS GGF RUS GGF SRM (planned for beta 2) GGF UR GGF WS-I RUS GGF ACS GGF CDDLM Other Industry Standards Employed by NAREGI ANSI/ISO SQL DMTF CIM IETF OCSP/XKMS MPI 2.0 OASIS SAML2.0 OASIS WS-Agreement OASIS WS-BPEL OASIS WSRF2.0 OASIS XACML De Facto Standards / Commonly Used Software Platforms Employed by NAREGI Ganglia GFarm 1.1 Globus 4 GRAM Globus 4 GSI Globus 4 WSRF (Also Fujitsu WSRF for C binding) IMPI (as GridMPI) Linux (RH8/9 etc.), Solaris (8/9/10), AIX, … MyProxy OpenMPI Tomcat (and associated WS/XML standards) Unicore WF (as NAREGI WFML) VOMS Necessary for Longevity and Vendor Buy-In Metric of WP Evaluation Implement “Specs” early even if nascent if seemingly viable

10. NAREGI Software Stack (Beta Ver. 2006) Computing Resources and Virtual Organizations NII IMS Research Organizations Major University Computing Centers （ WSRF (GT4+Fujitsu WP1) + GT4 and other services) SuperSINET Grid-Enabled Nano-Applications (WP6) Grid PSE Grid Programming (WP2) -Grid RPC -Grid MPI Grid Visualization Grid VM (WP1) Packaging Distributed Information Service (CIM) Grid Workflow (WFML (Unicore+ WF)) Super Scheduler Grid Security and High-Performance Grid Networking (WP5) Data (WP4) WP3 WP1

11. The NAREGI SSS Architecture (2007/3) Grid Resource Grid-Middleware PETABUS (Peta Application services Bus) NAREGI- SSS WESBUS (Workflow Execution Services Bus) CESBUS (Coallocation Execution Services Bus; a.k.a. BES+ Bus) BESBUS (Basic Execution Services Bus) Globus WS-GRAM I/F (with reservation) GridVM UniGridS Atomic Services (with reservation) UniGridS-SCGRAM-SC AGG-SC with RS (Aggregate SCs) CSGEPS FTS-SC JM BPEL Interpreter Service Application Specific Service

12. NAREGI SSS Structure (2006/06) WFML2BPEL SS NAREGI JM(SS) Java I/F module NAREGI-WP3 WorkFlowTool, PSE, GVS JM-Client Submit Status Delete Cancel EPS CSG IS Cance l StatusSubmit BPEL2WFST CreateActivity(FromBPEL) GetActivityStatus RequestActivityStateChanges CE S OGSA-DAI CIM DB PostgreSQL JSDL MakeReservation CancelReservation globus-url-copy uber-ftp CES S SR R BPEL ( include JSDL) Invoke EPS Invoke SC JSDL NAREGI- WFML NAREGI- WFML JSDL Co-allocationFileTransfer CreateActivity(FromJSDL) GetActivityStatus RequestActivityStateChanges MakeReservation CancelReservation JSDL Delete JSDL NAREGI JM (BPEL Engine) S JSDL Abbreviation SS: Super Scheduler JSDL: Job Submission Description Document JM: Job Manager EPS: Execution Planning Service CSG: Candidate Set Generator RS: Reservation Service IS: Information Service SC: Service Container AGG-SC: Aggregate SC GVM-SC: GridVM SC FTS-SC: File Transfer Service SC BES: Basic Execution Service I/F CES: Co-allocation Execution Service I/F (BES+) CIM: Common Information Model GNIS: Grid Network Information Service SelectResource FromJSDL GenerateCandidate Set Generate SQL Query From JSDL AGG-SC /RS SC CES PBS, LoadLeveler S GRAM4 specific SC(GVM-SC) SC CES PBS, LoadLeveler S GRAM4 specific SC(GVM-SC) R R WS-GRAM GridVM WS-GRAM GridVM FTS-SC Fork/Exec is-query Fork/Exec globusrun-ws Fork/Exec GFarm server GNIS GetGroups- OfNodes

13. NAREGI SSS “Standards” (1/3) Service NameDescriptionStandards NAREGI-JM is an OGSA-EMS Job Manager implementation. accepts NAREGI-WFML (Work-Flow Markup Languange), which is an intermediate workflow language for workflow-to-workflow language conversion generates a BPEL document for each NAREGI-WFML (workflow-job) as a OGSA-EMS/RSS service ohrchestration script. @ OGSA-WG [OGSA-EMS] $ OGSA WFM-RG # OASIS WS-BPEL NAREGI-BPEL is an BPEL script execution service implementation. accepts a BPEL document. interpret and execute a BPEL document. # OASIS WS-BPEL NAREGI-EPS is an OGSA-RSS Execution Planning Service implementation. accepts a NAREGI Complex Job Instance document or a (simple) Job Instance document, which express a job execution instance for a coupling job. Each Job Instance document contains a JSDL document as a resource requirement description. provides a co-allocation-enabled resource selection service as a whole. is a aggregation point of the following underlying selection services: single CSG (Candidate-Set Generator) service and multiple "Narrowing down candidates" services such as Grid Storage Service, Network Neighborhood Information Serivce and Reservation Cache Service. @ OGSA-RSS-WG @ JSDL-WG $ GSM-WG (Grid Storage Management WG) $ GHPN-RG (Grid High Performance Networking RG; network services) $ GSA-RG (Grid Scheduling Architecture RG) $ CDDLM-WG @: GGF Standard we use, $ GGF Standard we will use, # Industry Standard % De-facto Standard

14. NAREGI SSS “Standards” (2/3) Service NameDescriptionStandards NAREGI-CSG -is an OGSA-RSS Candidate Set Generator service implementation. - accepts a NAREGI Complex Job Instance document or a (simple) Job Instance document, which express a job execution instance for a coupling job. -extracts JSDL documents from a Job Instance document, generates resource-database query expressions from these JSDL documents, and reflects query results (resource candidates) into the Job Instance document. -Virtual Organization aware resource query by VOMS @ OGSA-RSS-WG @ JSDL-WG @ DAIS-WG @ OGSA-WG [Resource Management] % MyProxy, VOMS # DMTF CIM, ANSI/ISO SQL $ RUS-WG NAREGI-AGG with RS -is a virtual Service Container for a coupling job at coallocation execution services level, and aggregates "real" Service Containers at basic exeuction services level. -accepts a NAREGI Complex Job Instance document or a (simple) Job Instance document, including final candidates. -provides logical service operations: MakeReservations() and CommitReservations() to co-allocate and co- schedule a coupling job, and Cancel() and Destroy() to control the coupling job execution. -contains Reservation (Cache) Service to efficiently select available resources over "time-space" during final candidates. A Reservation Cache Service tracks each resource usage (including reservation) on Aggregation Service Container as possible. @ OGSA-RSS-WG $ GRAAP-WG [WS-Agreement] $ GSA-RG @: GGF Standard we use, $ GGF Standard we will use, # Industry Standard % De-facto Standard

15. NAREGI SSS “Standards” (3/3) Service NameDescriptionStandards NAREGI-FTS -is a file operation service, support basic file operations such as 3rd-party-file-transfer and check-file-existence -accepts single NAREGI Job Instance document, including DataStaging job without Application in JSDL. @ GridFTP-WG % GFarm (a Grid File System) $ WS-Naming-WG, $ GFS-WG (Grid File System WG) NAREGI-SC (GRAM-SC) (UniGridS-SC) -is a tentative wrapper service to hide grid-middleware- specific service interfaces (in particular for OGSA-BES to become widely used and standardize reservation operation in OGSA-BES). -accepts single NAREGI Job Instance document. @ OGSA-BES @ JSDL-WG % Globus [GRAM4] % UniGridS [Atomic Services] % Proxy Certificate, MyProxy $ GRAAP-WG [WS-Agreement] (infrastructure ) -native https/soap and wsrf processor [WS/RF 1.2 r/rp/rl/bf, WS/N 1.3 bn/topic] in C -native WSRF-aware WSDL compiler (WSDL to C compiler) -native BPEL interpretor (BPEL4WS) in C @ OASIS WS/RF @ OASIS WS/N # OASIS WS-BPEL @: GGF Standard we use, $ GGF Standard we will use, # Industry Standard % De-facto Standard

16. NAREGI Info Service (beta) Architecture Client (Resource Broker etc.) Client Library Java-API RDB Light- weight CIMOM Service Aggregator Service OS Processor File System CIM Providers ● ●● ● Resource Usage Service RUS::insertURs Chargeable Service (GridVM etc.) Job Queue Cell Domain Information Service Node B Node A Node C ACL Grid VM Cell Domain Information Service Information Service Node … Hierarchical filtered aggregation Parallel Query … Performance Ganglia Data Service Viewer User Admin. ・ CIMOM Service classifies info according to CIM based schema. ・ The info is aggregated and accumulated in RDBs hierarchically. ・ Client library utilizes OGSA-DAI client toolkit. ・ Accounting info is accessed through RUS. Client (publisher)

17. NAREGI IS: Standards Employed in the Architecture GT4.0.1Distributed Information Service Client (OGSA- RSS etc.) Client library Java-API RDB Light- weight CIMOM Service Aggregator Service OS Processor File System CIM Providers ● ●● ● WS-I RUS RUS::insertURs GridVM (Chargeable Service) Job Queue Cell Domain Information Service Node B Node A Node C ACL Grid VM Cell Domain Information Service Information Service Node … Hierarchical filtered aggregation... Distributed Query … Performance Ganglia OGSA-DAI WSRF2.1 Viewer User Admin. OGSA-DAI Client toolkit CIM Schema 2.10 /w extension GGF/ UR GGF/ UR APP CIM spec. CIM/XML Tomcat 5.0.28 Client (OGSA- BES etc.) APP

18. NAREGI Dist. Info Standards GGF Standards we help set within a WG –“OGSA CIM profile” GGF and related Standards we employ –OGSA-DAI –WS-I RUS –GGF UR –OGSA-EMS Other industry standards we employ –DMTF-CIM Other de-facto “standards” we employ –Globus 4 –Tomcat (and associated WS/XML standards)

19. IS Future Plans GLUE → CIM translation OGSA Information producer / consumer i/f Access control with XACML policy Service separability  having a set of sites all communicate some minimal set of data (a simple subset of GLUE schema)  getting the information from GLite/R-GMA consumer i/f, Globus/WS-MDS Aggregator  translating it to CIM/XML format, archiving it in RDBs and retrieving it through OGSA-DAI Data Service.

20. NAREGI GridVM (beta) Architecture Virtual execution environment on each site Virtualization of heterogeneous resources Resource and job management services with unified I/F Super Scheduler Information Service AIX/LoadLeveler GridVM Scheduler GRAM4 WSRF I/F Local Scheduler GridVM Engine Linux/PBSPro GridVM Scheduler GRAM4 WSRF I/F Local Scheduler GridVM Engine GridMPI site Policy Advance reservation, Monitoring, Control Accounting Resource Info. Sandbox Job Execution site Policy

21. NAREGI GridVM: Standards Employed in the Architecture Super Scheduler Information Service GridVM Scheduler GRAM4 WSRF I/F Local Scheduler GridVM Engine GridVM Scheduler GRAM4 WSRF I/F Local Scheduler GridVM Engine GridMPI site Policy xacml-like access control policy CIM-based resource info. provider GT4 GRAM-integration and WSRF-based extension services UR/RUS-based job accounting Job submission based on JSDL and NAREGI extensions site Policy

22. GT4 GRAM-GridVM Integration GridVM scheduler RFT File Transfer Local scheduler GridVM Engine SS globusrun RSL+JSDL’ Delegate Transfer request GRAM services Delegation Scheduler Event Generator GRAM Adapter GridVMJobFactory GridVMJob SUDO Extension Service Basic job management ＋ Authentication, Authorization Site Integrated as an extension module to GT4 GRAM Aim to make the both functionalities available

23. NAREGI GridVM Standards GGF Standards we help set within a WG –OGSA BES (made a presentation at BOF of GGF13) GGF and related Standards we employ –JSDL –WS-I RUS –GGF UR –WSRF2.0 Other industry standards we employ –DMTF-CIM –XACML Other de-facto “standards” we employ –Globus Toolkit version 4

24. NAREGI Software Stack (Beta Ver. 2006) Computing Resources and Virtual Organizations NII IMS Research Organizations Major University Computing Centers （ WSRF (GT4+Fujitsu WP1) + GT4 and other services) SuperSINET Grid-Enabled Nano-Applications (WP6) Grid PSE Grid Programming (WP2) -Grid RPC -Grid MPI Grid Visualization Grid VM (WP1) Packaging Distributed Information Service (CIM) Grid Workflow (WFML (Unicore+ WF)) Super Scheduler Grid Security and High-Performance Grid Networking (WP5) Data (WP4) WP3 WP1 WP2

25. Ninf-G: A Reference Implementation of the GGF GridRPC API Large scale computing across supercomputers on the Grid user ① Call remote procedures ② Notify results Utilization of remote supercomputers Call remote libraries Internet What is GridRPC? Programming model using RPCs on a Grid Provide easy and simple programming interface The GridRPC API is published as a proposed recommendation (GFD-R.P 52) What is Ninf-G? A reference implementation of the standard GridRPC API Built on the Globus Toolkit Now in NMI Release 8 (first non-US software in NMI) Easy three steps to make your program Grid aware –Write IDL file that specifies interface of your library –Compile it with an IDL compiler called ng_gen –Modify your client program to use GridRPC API

26. Architecture of Ninf-G Client WS/Pre-WS GRAM NAREGI-SS Invoke Executable Connect back IDL file Numerical Library IDL Compiler Remote Library Executable Generate Interface Request Interface Reply Server sideClient side MDS2/4 Interface Information LDIF File retrieve Globus-IO

27. GridRPC Standards and contributions to GGF GGF Standards we help set within a WG –Grid RPC WG (WG ではなく、スペック自身への ref が必要 ) GGF and related Standards we employ –GridRPC API –GridFTP –WSRF 2.0 –JSDL Other de-facto “standards” we employ –Globus Toolkit Versions 4 –UNICORE Ninf-G is a reference implementation of the GridRPC API Standardization of the GridRPC API –GGF GridRPC API WG (spinned off from APM RG) Co-chair: Hidemoto Nakada (AIST) Secretary: Yoshio Tanaka (AIST) –GridRPC API is published as a proposed recommendation (GFD- R.P 52) A GridRPC Model and API for End-User Applications –Co-Authors: Hidemoto Nakada (AIST), Satoshi Matsuoka (TITECH)

28. GridMPI MPI applications run on the Grid environment Metropolitan area, high-bandwidth environment:  10 Gpbs,  500 miles (smaller than 10ms one-way latency) –Parallel Computation Larger than metropolitan area –MPI-IO Wide-area Network Single (monolithic) MPI application over the Grid environment computing resource site A computing resource site A computing resource site B computing resource site B

29. GridMPI Software Architecture and Standards MPI 2.0 (test suite compliant) IMPI (Interoperable MPI) –The original IMPI is defined only for the MPI-1.2 feature –Extension for MPI-2 Porting the extended IMPI protocol to Open MPI Planning to submit the protocol to NIST MPI API TCP/IP PMv2MXO2GVendor MPI P2P Interface Request Layer Request Interface IMPI LACT Layer (Collectives) IMPI sshrshSCoreGlobus Vendor MPI RPIM Interface

30. NAREGI Software Stack (Beta Ver. 2006) Computing Resources and Virtual Organizations NII IMS Research Organizations Major University Computing Centers （ WSRF (GT4+Fujitsu WP1) + GT4 and other services) SuperSINET Grid-Enabled Nano-Applications (WP6) Grid PSE Grid Programming (WP2) -Grid RPC -Grid MPI Grid Visualization Grid VM (WP1) Packaging Distributed Information Service (CIM) Grid Workflow (WFML (Unicore+ WF)) Super Scheduler Grid Security and High-Performance Grid Networking (WP5) Data (WP4) WP1 WP3

31. Provisioning Deployment Configuration App. Contents Service (ACS) Information Services Service Container Data Container Accounting Services Execution Planning Services Candidate Set Generator (Work -Resource mapping) Job Manager Reservation RSS ① JSDL Expansion (WP1) ③ NAREGI-PSE(WP3) ② Resource Information Model (WP1) ④ Security (WP5) Architectural Positioning of NAREGI ‐ PSE （ WP3 ）

32. NAREGI-PSE Architecture Application Pool Deployment Service NAREGI WFT Client Register GetContent compile deploy un-deploy Register-UI EPR Deploy-UI EPR GetContent EPR Deploy Register deploy info. Submit AA File Contents (WF) NAREGI-PSE Register application info. NAREGI IS NAREGI SS Request to deploy EPR Application Information Application Repository ACS

33. NAREGI ‐ PSE （ WP3 ） Standards GGF Standards we help set within a WG –ACS （ Application Contents Service) WG GGF and related Standards we employ –CDDLM –GridFTP –WSRF 2.0 –JSDL –SRM (planned for beta 2) Other industry standards we employ –BPEL Other de-facto “standards” we employ –Globus 4 –Tomcat (and associated WS/XML standards)

34. 34 Web server(apache) Workflow Servlet tomcat Wokflow Description By NAREGI-WFML Server NAREGI Superscheduler server NAREGI WP3 Workflow Tool BPEL ↓ JSDL -A ↓ JSDL -A ………………….. NAREGI JM I/F module BPEL+JSDL http(s) Data icon Program icon Appli-A Appli-B JSDL applet Data Access Management (WP4) Global file information Application Information PSE /gfarm/.. GridFTP (Stdout Stderr) IS

35. 35 GGF Standards we help set within a WG –Workflow Management Research Group WFM_RG （ currently observing ） GGF and related Standards we employ –GridFTP –JSDL Other industry standards we employ –BPEL+JSDL NAREGI WFML has roots in Unicore WF but is heavily extended, and is translated into BPEL + JSDL Other de-facto “standards” we employ –Apache+Tomcat –Unicore NAREGI WFT Standards

36. GVS Framework Demo System Coupled Simulation Computation Results DB (DataGrid, etc.) Adaptor Coupled Sim. Visualization Service Particular Visualization Service Coupled Sim. Visualization Service Post-proc. Visualization Service DB Visualization Service Molecular Visualization Service CFD Visualization Service GridMPI Information Service NAREGI Middleware GVS Client (Reference Implementation) Particular Client Conformed to the Standard I/F Workflow Tool Adaptor Coupled Sim. Parallel Visualizer Coupled Sim. Parallel Visualizer Post-proc. Parallel Visualizer DB Parallel Visualizer Molecular Visualization Software CFD Visualization Software Particular Visualization Software Integrative use of various visualization software through the standard I/F Integrated WSRF-based remote visualization environment Control Images Integration of other existing visualization software (PyMOL, etc.)

37. GVS Architecture Grid/Internet Web/Grid Service Machine Tomcat/Globus Visualization Service GVS Server Adapter jpg Server Machine GVS Server IOIO OIOI IOIO para jpg IOIO OIOI IOIO para User Machine Web/Grid Client Visualization API GVS Client IOIO OIOI IOIO para

38. GVS Standards GGF Standards we help set in WG/RG –SAGA W/RG & OGSA-Byte-IO WG GGF and related Standards we employ –GridMPI –WSRF 2.0 –JSDL Other de-facto “ standards ” we employ –Globus 4 –Tomcat (and associated WS/XML standards)

39. NAREGI Software Stack (Beta Ver. 2006) Computing Resources and Virtual Organizations NII IMS Research Organizations Major University Computing Centers （ WSRF (GT4+Fujitsu WP1) + GT4 and other services) SuperSINET Grid-Enabled Nano-Applications (WP6) Grid PSE Grid Programming (WP2) -Grid RPC -Grid MPI Grid Visualization Grid VM (WP1) Packaging Distributed Information Service (CIM) Grid Workflow (WFML (Unicore+ WF)) Super Scheduler Grid Security and High-Performance Grid Networking (WP5) Data (WP4) WP1 WP3 WP4

40. Data 1 Data 2 Data n Grid-wide File System Metadata Management Data Access Management Data Resource Management Job 1 Meta- data Meta- data Data 1 Grid Workflow Data 2Data n NAREGI Data Grid beta1 Architecture (WP4) Job 2Job n Meta- data Job 1 Grid-wide Data Sharing Service Job 2 Job n Data Grid Components Import data into workflow Place & register data on the Grid Assign metadata to data Store data into distributed file nodes

41. Data 1 Data 2Data n Gfarm 1.2 PL4 (Grid FS) Data Access Management NAREGI WP4: Standards Employed in the Architecture Job 1 Data Specific Metadata DB Data 1Data n Job 1Job n Import data into workflow Job 2 Computational Nodes Filesystem Nodes Job n Data Resource Information DB OGSA-DAI WSRF2.0 OGSA-DAI WSRF2.0 Globus Toolkit 4.0.1 Tomcat 5.0.28 PostgreSQL 8.0 Workflow (NAREGI WFML =>BPEL+JSDL) Super Scheduler (SS) (OGSA-RSS) Data Staging Place data on the Grid Data Resource Management Metadata Construction OGSA-RSS FTS SC GridFTP GGF-SRM (beta2)

42. NAREGI WP4 Standards GGF Standards we help set within a WG –Grid FileSystems WG (discussion about functionality and usecase scenario) GGF and related Standards we employ –OGSA-DAI –OGSA-RSS –GridFTP –WSRF 2.0 –JSDL –SRM (planned for beta 2) Other industry standards we employ –BPEL Other de-facto “standards” we employ –Globus 4 –Tomcat (and associated WS/XML standards)

43. Roadmaps, Future Plans Extension of Data Sharing Service based on Grid FileSystem –VO support based on VOMS and/or XACML VO group permissions –Shared StorageResource Reservation for Work- Resource Mapping (OGSA-RSS) Data Transfer Service –Stream-like Data Transfer for huge amount of data (OGSA ByteIO?) Virtualization and/or Integration of Metadata –For Data Exchange among different storage/file- systems (SRM, SRB, …) –Logical Namespace Service (OGSA RNS, WS- Name)

44. NAREGI Software Stack (Beta Ver. 2006) Computing Resources and Virtual Organizations NII IMS Research Organizations Major University Computing Centers （ WSRF (GT4+Fujitsu WP1) + GT4 and other services) SuperSINET Grid-Enabled Nano-Applications (WP6) Grid PSE Grid Programming (WP2) -Grid RPC -Grid MPI Grid Visualization Grid VM (WP1) Packaging Distributed Information Service (CIM) Grid Workflow (WFML (Unicore+ WF)) Super Scheduler Grid Security and High-Performance Grid Networking (WP5) Data (WP4) WP1 WP3 WP5

45. User Web Server (PSE,WFT,GVS) Policy Enforcement Point CRL Grid Job Submission OCSP/ XKMS SS CA Service VO and Certificate Management Service User Authentication Proxy Certificate XACML, ACL GRAM (Grid VM) Policy information description CSR NAREGI-1.0 Security Architecture Credential Renewal NAREGII S VO Context System Administrator System Administrator Discussed in GGF SAML2.0 GT4.2 or later Security Attribute (GGF AuthZ) Accredited by APGridPMA NAREGI-CA GCA GPKI CP/CPS GRID CP (GGF CAOPs) Audit Criteria Subset of WebTrust Programs for CA GPMA NAREGI-PMA

46. NAREGI-beta1 Security Architecture NAREGI CA Client Environment Portal WFT PSE GVM SS client Proxy Certificate with VO Proxy Certificate with VO Super Scheduler Proxy Certificate with VO Proxy Certificate with VO log-in Request/Get Certificate Certificate VOMS Certificate Management Server Certificate Management Server Proxy Certificate withVO Proxy Certificate withVO User Certificate Private Key Put ProxyCertificate with VO Get VOMS Attribute MyProxy Proxy Certificate with VO Proxy Certificate with VO voms-myproxy-init Information Service Resources Info incl. VO Resource GridVM local Info. incl. VO CA Service ssh + voms-myproxy-init ProxyCertificate with VO query(requirements +VO info) resources in the VO globusrun-ws GridVM services GridVM services (incl. GSI) Resource Info. (Incl. VO info) SignedJobDescription VO 、 Certificate Management Service VO Info 、 Execution Info, Resource Info CP/CPS GRID CP (GGF CAOPs) Audit Criteria Subset of WebTrust Programs for CA

47. WP5 Security Roadmaps, Future Plans TOPICStandardizatio n Status Standardization To GGFFrom GGFComment Attribute Propagation －◎ Definition of VO －◎ NAREGI Security Architecture －◎ ID federation ◎ SAML2.0 × Grid －◎ Security Attribute (OGSA-AuthZ WG) ○ ◎◎ Policy Description － ○

48. NAREGI WP5 Network Architecture Grid Network Service Components GridVM Provider Service Client Super Scheduler Distributed Information Service DAI CIM-XML (network topology and measurement) Workflow GridVM CIM Provider Grid Network Resource / Policy Manager Grid Network Resource DB Network Monitoring Elements Active measurement Passive measurement Real time flow measurement Network Control Elements Path / Bandwidth RTT/delay/utilization flow packet counts NetworkControl Grid Network Service WSDL SuperSINET Operators GUI Visualization of Network Topology and Measurement

49. NAREGI WP5 Network Standards GGF Standards we help set within a WG –Grid High-Performance Networking (We presented network measurement, control and measurement architecture as NAREGI activities) –Network Measurement (in Future) GGF and related Standards we employ –Grid network service use-case scenario between NAREGI Grid middleware and grid network services (discussion currently and contribution in Future) –IETF Network Standards such as OCSP Other de-facto “standards” we employ –Apache + Tomcat

50. NAREGI WP5 Sec Standards GGF Standards we help set within a WG –CAOPs,AuthZ(in Future) GGF and related Standards we employ –GRID CP[CAOPs] –OCSP (in Future) –Security Attibutes[AuthZ] (in Future) –Grid Policy Management Authority –Grid Certificate Authorities Other industry standards we employ –WebTrust Programs for CA(referred to define the grid audit criteria) Other de-facto “standards” we employ –GT4.2 or later(in Future) –MyProxy, VOMS –SAML 2.0(in Future)

51. NAREGI Software Stack (Beta Ver. 2006) Computing Resources and Virtual Organizations NII IMS Research Organizations Major University Computing Centers （ WSRF (GT4+Fujitsu WP1) + GT4 and other services) SuperSINET Grid-Enabled Nano-Applications (WP6) Grid PSE Grid Programming (WP2) -Grid RPC -Grid MPI Grid Visualization Grid VM (WP1) Packaging Distributed Information Service (CIM) Grid Workflow (WFML (Unicore+ WF)) Super Scheduler Grid Security and High-Performance Grid Networking (WP5) Data (WP4) WP1 WP3 WP6

52. Information Service NAREGI Application Mediator (WP6) for Coupled Applications Job 1 Workflow NAREGI WFT co-allocated jobs Super Scheduler GridVM Simulation A Mediator Simulation A Simulation B Mediator A Mediator A Mediator A Mediator B Mediator B Sim.B Sim.A Support data exchange between coupled simulation ＭＰ Ｉ OGSA-DAI WSRF2.0 SQL JNI ・ Semantic transform- ation libraries for different simulations Data transfer management ・ Synchronized file transfer Mediator Components ・ Multiple protocol GridFTP/MPI Job n ＭＰ Ｉ Data transformation management ・ Coupled accelerator ＭＰ Ｉ GridFTP Mediator Globus Toolkit 4.0.1 GridFTP API Data1 Data2 Data3 * SBC: Storage-based communication SBC * -XML ・ Global Job ID ・ Allocated nodes ・ Transfer Protocol etc.

53. NAREGI WP6 Standards GGF and related Standards we employ –GridFTP –OGSA-DAI –WSRF 2.0 Other industry standards we employ –MPI Standard 1.1 –SQL Other de-facto “standards” we employ –JNI 1.2 (Java TM Native Interface) –Globus Toolkit 4.0.1

54. Lessons Learned Relieving Delivery pressure –Standards unavailable, process slow => “screw with it” attitude –=> Long-term planning, staged delivery plans Time/Money/Personnel Investment –=> Commitment from leadership & companies –=> made part of yearly budget/plan Valuation/Accreditation –May conflict with academic valuations –=> Students not involved, only “established” academia and commercial pros –=> made primary metric for project success

55. NAREGI and Standards: Summary Interoperability and longevity is the key for grid adoption NAREGI believes, as a major national grid project, that committing to standards is the best bet for interoperation, industry adoption, and resulting longevity –Will be working next 5 years to set and adopt more standards Will be working with other parties, within and outside GGF to achieve common standards

56. Backups

57. NAREGI Software Stack (beta 1 2006) Computing Resources and Virtual Organizations NII IMS Research Organizations Major University Computing Centers （ WSRF (GT4+Fujitsu WP1) + GT4 and other services) SuperSINET Grid-Enabled Nano-Applications (WP6) Grid PSE Grid Programming (WP2) -Grid RPC -Grid MPI Grid Visualization Grid VM (WP1) Packaging Distributed Information Service (CIM) Grid Workflow (WFML (Unicore+ WF)) Super Scheduler Grid Security and High-Performance Grid Networking (WP5) Data (WP4) WP3 WP1

58. Grid Interoperations---Ideal World: Ubiquitous VO & user management for international e-Science Europe: EGEE, UK e-Science, … US: TeraGrid, OSG, Japan: NII CyberScience (w/NAREGI), … Other Asian Efforts (GFK, China Grid, etc.)… Grid Regional Infrastructural Efforts Collaborative talks on PMA, etc. HEP Grid VO NEES -ED Grid VO Astro IVO Standardization, commonality in software platforms will realize this All different software stacks but users don’t see them

59. The Reality: Convergence/Divergence of Project Forces (original slide by Stephen Pickles, edited by Satoshi Matsuoka) NGS(UK) TeraGrid(US) OSG(US) EGEE(EU) LCG(EU) GridPP(UK) OMII(UK) GT4 WSRF (OGSA?) gLite / GT2 Own WSRF & OGSA Globus(US) GGF DEISA(EU) common staff & procedures common users NAREGI (JP) interoperable infrastructure talks WSRF & OGSA  : GT234/Unicore,  GT4/Fujitsu WSRF NMI(US) IBM Unicore CSI (JP) UniGrids(EU) WS-I+ & OGSA? AIST-GTRC interoperable infrastructure talks Condor(US)

60. NAREGI is/has/will… Is THE National Research Grid in Japan –Part of CSI and future Petascale initiatives –METI “Business Grid” counterpart 2003-2005 Has extensive commitment to WS/GGF-OGSA –Entirely WS/Service Oriented Architecture –Set industry standards e.g. 1st impl. of OGSA-EMS Will work with EU/US/AP counterparts to realize a “global research grid” –Various talks have started, incl. SC05 interoperability meeting Will deliver first OS public beta in May 2006 –To be distributed @ GGF17/GridWorld in Tokyo

61. NAREGI is not/doesn’t/won’t… Is NOT an academic research project –All professional developers from Fujitsu, NEC, Hitachi, (No students) –IMPORTANT for Vendor buy-in and tech transfer Will NOT develop all software by itself –Will rely on external components in some cases –Must be WS and other industry standards compliant –IMPORTANT for Vendor buy-in and tech transfer Will NOT hinder industry adoption at all costs –Intricate open source copyright and IP policies –We want companies to save/make money using NAREGI MW –IMPORTANT for Vendor buy-in and tech transfer

62. Nano-Science : coupled simluations on the Grid as the sole future for true scalability The only way to achieve true scalability! --- Coupled Simulations as “Killer Apps” for Grid --- 10 -6 10 -9 m Material physics 的 (Infinite system) ・ Fluid dynamics ・ Statistical physics ・ Condensed matter theory … Molecular Science ・ Quantum chemistry ・ Molecular Orbital method ・ Molecular Dynamics … Multi-Physics Multi-Resolution Limit of Computing Capability Limit of Idealization Coordinates decoupled resources on Grid; Meta-computing, High throughput computing, Multi-Physics simulation w/ components and data from different groups within VO composed in real-time Old HPC environment: ・ decoupled resources, ・ isolated users, ・ special software,... ・ no coupling!

63. Distributed Servers LifeCycle of Grid Apps and Infrastructure MetaComputing Workflows and Coupled Apps / User Many VO Users Application Contents Service HL Workflow NAREGI WFML (Unicore+) Grid Info Service (CIM) GridRPC/Grid MPI User Apps VO Application Developers&Mgrs GridVM+ GRAM4 SuperScheduler (OGSA-RSS) Data 1 Data 2 Data n Meta- data Meta- data Meta- data Grid-wide Data Management Service (GridFS, Metadata, Staging, etc.) Place & register data on the Grid Assign metadata to data Implementation of OGSA-EMS Architecture GridVM+ GRAM4 GridVM+ GRAM4

64. Highlights of NAREGI Beta (May 2006, GGF17/GridWorld) Professionally developed and tested “Full” OGSA-EMS incarnation –Full C-based WSRF engine (Java -> Globus 4) –OGSA-EMS/RSS WSRF components –Full WS-Agreement brokering and co-allocation –GGF JSDL1.0-based job submission, authorization, etc. –Support for more OSes (AIX, Solaris, etc.) and BQs Sophisticated VO support for identity/security/monitoring/accounting (extensions of VOMS/MyProxy, WS-* adoption) WS- Application Deployment Support via GGF-ACS Comprehensive Data management w/Grid-wide FS Complex workflow (NAREGI-WFML) for various coupled simulations Overall stability/speed/functional improvements To be interoperable with EGEE, TeraGrid, etc. (beta2)