1 / 4

Enhancing Condor Grid Computing with JDF Integration and GSI Security Infrastructure

This document outlines the ongoing development of a new Condor BS adaptor interface for handling JDFs across multi-process consumers. It addresses key challenges such as managing file systems, job submission crashes, and improving data management. By exploring the integration of the Globus Security Infrastructure (GSI) with SAM authentication, this project aims to create a robust authorization service and streamline resource usage across various systems. Insights are also provided on optimizing D0 MC production and collaboration initiatives.

odetta
Télécharger la présentation

Enhancing Condor Grid Computing with JDF Integration and GSI Security Infrastructure

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. IC Status – 29/4/02 • Condor BS adaptor • New interface handles • JDF`s (condor,fbs,condorG) • Multi-process consumers. • In progress (crashes smaster on jobSubmitted()) • Some obvious stuff. • Client on same File System as master – reads user JDF. • User code on same FS as master. • Want client FS separate from station and maybe Compute Node FS. • What`s happening with RTE?

  2. Submit D0 MC to EDG • Trivial to tar up mc_runjob prepared directories and run on Grid, but is it useful? • UK money for EU/US re-use. • Trivial because no input data. • Increase D0 MC prod for free. • GridPP Collab. 9/10th May. • 30mins in “tutorial” style. • Point out real issues with Data Management. • .brokerinfo has file locations. Still there at runtime? Pmaster ensures delivery, retries/fail-overs. Optimizer involved. • Draft architecture and differences in information flow.

  3. GSI in Sam • Toy client-server. Using gss-assist globus tools. • mutually authenticate hosts • pass user proxy, • map to user. • Authorization Server. • Use user proxy to transfer files, run jobs, Sam store, query Db, log resource usage. • User sam owns cache areas. • Map all users to sam at all sites. • Give user restricted sam privileges. • CAS • Community Authorization Service • Database of user privileges • Use user proxy to get a CAS proxy. • CAS proxy allows all or subset of users` privileges. E.g gridftp from d0mino:/sam/cache20 to sampc:/sam/cache1. • User still mapped to local unix account and unix permissions always obeyed. • Toy client-server-server model exists. • Client-station-stagerng • All in the detail.

  4. Integration of the Globus Security Infrastructure with SAM Authentication/Authorization Service: using the GSI certificate • identity to identify SAM users; using sam - service proxy for data transfers • GSI - enable Station, FSS , Stager and EWorker Stager/ EWorker Authorization Service Server Proxy Grid FTPd User Proxy Server Proxy Client Server Proxy User Proxy Station User Proxy Server Proxy Gabriele`s picture, from 8th March

More Related