120 likes | 136 Views
Status of. FJPPL Lyon, 13 March 2012 Sylvain Reynaud, Lionel Schwarz. Plan. Overview of JSAGA Adaptors New adaptors New contributors Standardization of Python bindings Perspectives. Overview of JSAGA. a J ava implementation of the SAGA specification focuses on
E N D
Status of FJPPL Lyon, 13 March 2012 Sylvain Reynaud, Lionel Schwarz
Plan • Overview of JSAGA • Adaptors • New adaptors • New contributors • Standardization of Python bindings • Perspectives JSAGA
Overview of JSAGA • a Java implementation of the SAGA specification • focuses on • uniform usage of middleware…. (beyond what they natively support) • ease of extension………………. • efficiency and scalability………. • control of the API behavior........ (contexts bound to remote systems) • operating-system independency (tested on ) • Under LGPL license (thanks to the design of adaptor interfaces) JSAGA
Used by end users web portals, GUI, CLI… Used by application developers a single uniform interface object oriented, high-level Implemented by adaptors each "way" to implement a given feature has 1 interface service oriented, low-level Implemented by middleware each technology has its own interfaces SAGA Java binding core engine JSAGA adaptors interfaces JSAGA adaptors JSAGA interface Layered software architecture implementation user applications middleware APIs JSAGA
done in progress Supported technologies Grid techno. Others Execution gatekeeper gLite-WMS wsgram BES ARC Unicore6 Genesis II Cream SSH local Batch SSH Grid techno. Others Data Logical Physical LFC SRB iRODS Local catalog gsiFTP SRM iRODS HTTP HTTPS SFTP SRB file ftp zip Unicore6 Grid techno. Others Security InMemCred Globus G. Legacy Secret Svc G. RFC820 MyProxy VOMS JKS SSH Login / pwd X509 .netrc
New contributors for JSAGA • From CHAIN • Diego Scardaci • OurGrid (Brazil and Latin America) • a Desktop Grid • Meng You • Grid Operating System for CNGRID (China) • ? • GARUDA (India) consortium JSAGA
SAGA : the specification a Simple API for using Grid middleware execution management job submission, monitoring... data management transfer, list files, search… service discovery … in user Applications implementations (or wrappers) exist for C++, Java and Python …in a uniform way The SAGA specification A S use middlewares in a uniform way (independent of middlewares) G use functionalities in a uniform way (consistent "look-and-feel") A use language bindings in a similar way (language-independent specification) …but not yet uniform between Python implementations JSAGA
SAGA Python bindings application (Java) application (Python) application (Python) SAGA (Python) SAGA interfaces (Python) JPySAGA JySAGA legacy python binding (C++) SAGA interfaces (Java) SAGA-CPP JSAGA Java SAGA JSAGA
SAGA Python binding application (Java) application (Python) SAGA interfaces (Python) TO BE DONE JPySAGA JySAGA legacy python binding (C++) SAGA interfaces (Java) SAGA-CPP JSAGA Java SAGA JSAGA
Standardization of Python binding • Based on PySAGA • Designed by Vrije University • Implemented by • JySAGA (Vrije University) • JPySAGA (CC-IN2P3) • OGF doc in progress • HTML (generated from commented python code) • PDF • By • Julien Devemy (CC-IN2P3) • Mark Santcroos (CCT-LSU) JSAGA
Next adaptors Grid Engine DRMAA-based CLI-based, with SSH … Engine improvement adaptors isolation ease integration of contributions Implement API extensions Service Discovery API with plug-ins for technologies BDII with plug-ins for schemas GLUE CIM Resource API with plug-ins for pilot-jobs DIRAC with plug-ins for clouds OpenNebula openstack Perspectives JSAGA
Questions ? JSAGA