1 / 7

NAREGI Interoperability/Interoperation, Short Term Policy (for EGEE, GIN, and BES/ESI)

NAREGI Interoperability/Interoperation, Short Term Policy (for EGEE, GIN, and BES/ESI). May 2006 NAREGI-WP1 National Institute of Informatics. Interoperability: NAREGI Short Term Policy. NAREGI has three interoperability/interoperation plans. Interoperation with EGEE (gLite)

vladimir-compton
Download Presentation

NAREGI Interoperability/Interoperation, Short Term Policy (for EGEE, GIN, and BES/ESI)

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. NAREGI Interoperability/Interoperation,Short Term Policy(for EGEE, GIN, and BES/ESI) May 2006 NAREGI-WP1 National Institute of Informatics

  2. Interoperability: NAREGI Short Term Policy NAREGI has three interoperability/interoperation plans. • Interoperation with EGEE (gLite) Discussed in CERN (March) and Condor Week (April) • Demonstration @ SC06 • Simple/Single Job (up to SPMD) • Bi-Directional Submission • NAREGI  gLite: GT2-GRAM • gLite  NAREGI: Condor-G • Exchange Resource Information • GIN Interoperability (WS-GRAM) • Demonstration @ SC06 • Simple/Single Job (up to SPMD) • One way Submission (NAREGI  GIN) • GIN  NAREGI is difficult to support in the current NAREGI implementation • WS-GRAM • Exchange Resource Information (depends on activity of Information Service Area) • GIN Interoperability (BES/ESI) • Under study • Schedule is TBD

  3. gLite to NAREGI bridge NAREGI client lib NAREGI-SS [JSDL] Interop-SC NAREGI-SC Interoperation with EGEE (gLite) gLite-WMS [JDL] gLite-IS [GLUE] IS bridge NAREGI-IS [CIM] • GLUE  CIM Bridge-CE [JDL] EGEE user Condor-G Adapter NAREGI user Condor-G NAREGI Portal [JSDL] • ClassAd  JSDL • NAREGI-WF generation • Job Submission/Control • Status propagation • Certification ? • JSDL  RSL • Job Submission/Control • Status propagation gLite-CE NAREGI GridVM GT2 GRAM

  4. anotherGrid [JSDL] GT4 NAREGI-SS [JSDL] Interop-SC NAREGI-SC GIN Interoperability (WS-GRAM) anotherGrid-IS [CIM or GLUE] IS bridge NAREGI-IS [CIM] • GLUE  CIM another grid’s user NAREGI user Sorry, One way now !! NAREGI Portal (Short Term ) • JSDL  RSL • Job Submission/Control • Status propagation anotherGrid-CE NAREGI GridVM WS-GRAM WS-GRAM

  5. Study: BES/ESI Interoperability Comparison: Goals *1: Extended

  6. Study: BES / ESI Interoperability cont. Job Factory Operations • State Model • NAREGI state model is similar with BES state model

  7. Interoperability: NAREGI Long Term Policy • Support standard I/Fs for interoperability (BES/ESI etc.) • Improve independency of Super Scheduler (SS) and Job Execution Service (SC) • SS • Support job submission to other grids • Support execution services which have no advanced reservation capability • Simplify input workflow • Separate user process workflow and service workflow • Study: BES/ESI as SS I/F • Problem: No workflow I/F • SC • Support job submission from other grids • Support non advanced reserved job submission • Improve job submission and advanced reservation I/Fs for upper layer • Reservation table synchronization etc. • Study: BES/ESI as SC I/F • Problem: No advanced reservation I/F

More Related