1 / 10

Interoperability of gLite and UNICORE for Supercomputing Access

This research aims to enable interoperability between gLite and UNICORE to provide access to both the EGEE infrastructure and supercomputers. The architecture, job submission process, and user authentication and authorization mechanisms are discussed. The outlook includes switching to gLite CREAM CE, UNICORE 6, and IBM systems.

howarddiaz
Télécharger la présentation

Interoperability of gLite and UNICORE for Supercomputing Access

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. gLite – UNICORE interoperability Daniel Mallmann Research Centre JuelichEGEE Review, CERN 8th July 2008

  2. Motivation and Overview Motivation • UNICORE offers access to supercomputers, e.g. DEISA infrastructure • Several applications demand access to the EGEE infrastructure as well as supercomputers Overview • Introduction to UNICORE • Overview of interoperability environment • Example: job submission • Outlook

  3. UNICORE5 Architecture Client UserCertificate GUIJava application Job PreparationWorkflow Editor Job Monitoring ApplicationPlugin User authenticationbased on full X509 certificates Gateway Gateway Usite A Usite B Vsite A1 Vsite B1 Vsite B2 User authorisation based on full X509 certificates NJS NJS UnicoreUserDatabase UnicoreUserDatabase NJS UnicoreUserDatabase WorkflowEngine WorkflowEngine WorkflowEngine IncarnationDatabase IncarnationDatabase IncarnationDatabase TargetSystem TargetSystem TargetSystem Bunch of Perl scripts TSI TSI TSI BatchSystem FileSystem BatchSystem FileSystem BatchSystem FileSystem

  4. Interoperability Architecture gLite Environment UNICORE5 Environment gLite UI UserCertificate glite-job-submit glite-job-status … Proxy-awareGateway Usite A Resource BrokerNode Vsite A1 FileCatalogue Network Server NJS Proxy-awareUUDB MatchMakerBroker WorkflowEngine WorkloadManager BDII IncarnationDatabase JobAdapter TargetSystem TSI BatchSystem FileSystem Interoperability gLite-CE UNICOREBLAH UNICORE Information Provider UNICORE CLI

  5. Interoperability gLite-CE gLite Environment UNICORE5 Environment gLite UI UserCertificate glite-job-submit glite-job-status … Proxy-awareGateway Usite A Resource BrokerNode Vsite A1 FileCatalogue Network Server NJS Proxy-awareUUDB MatchMakerBroker WorkflowEngine WorkloadManager BDII IncarnationDatabase JobAdapter BLAH scripts for • job submission • job status • job management TargetSystem TSI UNICORE command line interface(based on results from OpenMolGrid)enhanced with • job management • usage of VOMS proxy certificates for job signing and transfer • logging BatchSystem FileSystem static information Interoperability gLite-CE UNICOREBLAH UNICORE Information Provider UNICORE CLI

  6. UNICORE Environment gLite Environment UNICORE5 Environment gLite UI UserCertificate Gateway authenticates users based on their VOMS proxy certificates glite-job-submit glite-job-status … Proxy-awareGateway Usite A NJS authorises users based on their VOMS proxy certificates Resource BrokerNode Vsite A1 FileCatalogue Network Server NJS Proxy-awareUUDB MatchMakerBroker WorkflowEngine WorkloadManager BDII IncarnationDatabase JobAdapter TargetSystem TSI BatchSystem FileSystem Interoperability gLite-CE UNICOREBLAH UNICORE Information Provider UNICORE Target system • SuSE Linux 9.3 • running gLite WorkerNode for data management (ported by TCD) UNICORE CLI

  7. Example: job submission gLite User Interface (UI) • standard job submission • JDL containsRequirements = other.GlueCEInfoLRMSType == "UNICORE“ gLite Resource Broker (WMS) • chooses the appropriate CE based on information from the BDII gLite CE • uses BLAHP (Basic Local ASCII Helper Protocol) scripts for submission to UNICORE • builds an xml file in UNICORE CLI (Command line interface) syntax • calls UNICORE CLI to build and submit the job (proprietary UNICORE5 Abstract Job Object)

  8. Example: job submission UNICORE Gateway • authenticates user based on VOMS proxy certificate UNICORE NJS • authorizes user based on VOMS proxy certificate andmaps to the login name UNICORE TSI • executes UNICORE job, i.e. wrapper around gLite job gLite WorkerNode (on Target system) • executes gLite job

  9. Outlook Switching to gLite CREAM CE • BLAH scripts need to be adapted (minor changes) Switching to UNICORE 6 • UNICORE 6 command line client • input: JSON (JavaScript Object Notation) syntax • output JSDL (Job Submission Description Language) • BLAH scripts need to be adapted • UNICORE 6 Gateway user authentication based on proxy certificates (already implemented) • UNICORE 6 XNJS user authorisation based on proxy certificates (implementation ongoing)

  10. Outlook Switching to IBM systems • Porting of gLite WorkerNode ongoing Users • Wide In Silico Docking On Malaria (WISDOM) initiative • EU Fusion for ITER Applications (EUFORIA) project

More Related