1 / 8

EGEE is a project funded by the European Union under contract IST-2003-508833

Data Management Data Access From WN Paolo Badino ( paolo.badino@cern.ch ) Ricardo Rocha ( ricardo.rocha@cern.ch ). JRA1 all-hands meeting, 29-June-2004. www.eu-egee.org. EGEE is a project funded by the European Union under contract IST-2003-508833. glite I/O. Goals

makani
Download Presentation

EGEE is a project funded by the European Union under contract IST-2003-508833

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. Data ManagementData Access From WNPaolo Badino (paolo.badino@cern.ch)Ricardo Rocha (ricardo.rocha@cern.ch) JRA1 all-hands meeting, 29-June-2004 www.eu-egee.org EGEE is a project funded by the European Union under contract IST-2003-508833

  2. glite I/O • Goals • Provides a library for accessing files stored on a remote a SE in a transparent way • Release Plan • First version foreseen for PM03 • Two weeks late… JRA1 all-hands meeting, 29-June-2004 - 2

  3. Guiding Principles • Based on existing libraries • Aiod, gfal, rfio, dcap • Stable Quickly deployable • POSIX-like I/O API • Remote open, read, write • Minimum impact on existent code • Extensible • Plug-ins and callouts to support additional protocols and authorization models JRA1 all-hands meeting, 29-June-2004 - 3

  4. API • POSIX-like I/O API glite_handle glite_open(char * name, int32 flags, int32 mode) int32 glite_read(glite_handle fh, void * buf, size_t count) int32 glite_write(glite_handle fh, void *buf, size_t count) int32 glite_lseek(glite_handle fh, int64 offset, int32 whence) int32 glite_close(glite_handle fh) int64 glite_size(glite_handle fh) • Support both GUID and LFN name = “guid:2cd59291-7ae7-4778-af6d-b1f423719441” name = “lfn:egee/foo12345” JRA1 all-hands meeting, 29-June-2004 - 4

  5. Flow FC FAS GUID GUID ACL glite-io daemon Authorization callout LFN LFN glite-io client GUID Name Resolution callout RC GUID aiod SURL AlienIOclient gfal HANDLE SURL Protocol Plug-in HANDLE SRM TURL GUID TURL LFN HANDLE rfio HANDLE SE JRA1 all-hands meeting, 29-June-2004 - 6

  6. Open Issues • Is Read-Only access ok for now? • Writes (later): updating is not a problem, synchronization with other replicas is. Depends on semantics of file update policy – single master, multi-master with reconciliation, etc. • Creation of a new file through this interface? We think not..Problems: glite_open (name, O_WRONLY | O_CREAT, mode) • Is name a GUID/LFN? • Should the file name already be registered or should it be inserted into the File Catalog later? • When should the file be inserted in Replica Catalog? During open or close? JRA1 all-hands meeting, 29-June-2004 - 7

  7. File Access Service File Access Service (FAS) GUID USER (RWX) GROUP (RWX) OTHER (RWX) ACL PRINCIPAL (RWX) GET PERMISSIONS Storage Element Authz Framework SITE POLICY VO POLICY SRM Transfer FILE request CLIENT User Mapping VOMS CERTIFICATE GROUPS / ROLES File Transfer Service XFER Buffer Use protocol X JRA1 all-hands meeting, 29-June-2004 - 8

  8. Security Implementation • Authentication • GSI / Proxy Certificates • Authorization • VOMS – Attribute Certificates • Authz Framework • XACML compatible • End of summer (alpha / beta before that) • Toolkits • Java – Java CoG • C++ – gSOAP with GSI plugin • Delegation • JRA3 magic JRA1 all-hands meeting, 29-June-2004 - 9

More Related