NAREGINAREGI Interoperability/Interoperation, Interoperability/Interoperation,

Short Term PolicyShort Term Policy(for EGEE, GIN, and BES/ESI)(for EGEE, GIN, and BES/ESI)

May 2006May 2006

NAREGI-WP1NAREGI-WP1

National Institute of InformaticsNational Institute of Informatics

2

Interoperability: NAREGI Short Term PolicyInteroperability: NAREGI Short Term PolicyNAREGI 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

Interoperation with EGEE (gLite)Interoperation with EGEE (gLite)

gLite to NAREGIbridge

NAREGI client lib

• ClassAd JSDL• NAREGI-WF generation• Job Submission/Control• Status propagation• Certification ?

NAREGI-IS[CIM]

IS bridgegLite-IS[GLUE]

• GLUE CIM

Bridge-CE [JDL]

Condor-G

NAREGI-SS[JSDL]

NAREGI-SCInterop-SC

gLite-CE NAREGI GridVM

• JSDL RSL• Job Submission/Control• Status propagation

GT2GRAM

NAREGI Portal[JSDL]

EGEE userNAREGI user

gLite-WMS[JDL]

Condor-GAdapter

4

GIN Interoperability (WS-GRAM)GIN Interoperability (WS-GRAM)

NAREGI-IS[CIM]

IS bridgeanotherGrid-IS[CIM or GLUE]

• GLUE CIM

anotherGrid[JSDL]

GT4

NAREGI-SS[JSDL]

NAREGI-SCInterop-SC

anotherGrid-CE NAREGI GridVM

• JSDL RSL• Job Submission/Control• Status propagation

WS-GRAM

NAREGI Portal

anothergrid’s user NAREGI user

WS-GRAM

Sorry,One way now !!

(Short Term )

5

Study: BES/ESI InteroperabilityStudy: BES/ESI Interoperability

ESI BES NAREGI

SS SC

Use JSDL ✔*1 ✔ ✔*1 ✔*1

WSRF OGSA Base Profile 1.0 Platform ✔ ✔ ✔ ✔

Job Management Service ✔ ✔ ✔ ✔

Extensible Support for Resource Models ✔ ✔

Reliability ✔ ✔ ✔ ✔

Use WS-RF modeling conventions ✔ ✔ ✔ ✔

Use WS-Agreement

Advance reservation ✔ ✔

Bulk operations ✔

Generic management frameworks (WSDM)

Define alternative renderings

Server-side workflow ✔

*1: Extended

Comparison: Goals

6

ESI (0.6) BES (Draft v16) NAREGI (

Service-specific CreateManagedJob

(there is a subscribe option)

CreateActivityFromJSDL

GetActivityStatus

RequestActivityStateChanges

StopAcceptingNewActivities

StartAcceptingNewActivities

IsAcceptingNewActivities

GetActivityJSDLDocuments

MakeReservations

CommitReservations

WS-ResourceProperties GetResourceProperty

GetMultipleResourceProperties

QueryResourceProperties

GetResourceProperty

GetMultipleResourceProperties

QueryResourceProperties

GetResourceProperty

GetMultipleResourceProperties

SetResourceProperties

WS-ResourceLifeTime ImmediateResourceDestruction

ScheduledResourceDestruction

Destroy

SetTerminationTime

WS-BaseNotification NotificationProducer Notify

Subscribe

Job Factory Operations

Study: BES / ESI Interoperability Study: BES / ESI Interoperability cont.cont.

State Model• NAREGI state model is similar with BES state model

7

Interoperability: NAREGI Long Term PolicyInteroperability: 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