Graphics & Design

WP5 Progress Report. John Gordon EDG Conference Barcelona, May escience Centre

Description
WP5 Progress Report EDG Conference Barcelona, May 2003 escience Centre Outline Status of release 2.0 Testing and support structures Priorities up to TB3 Open issues Status of release 2.0 Core SE Software
Published
of 15
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Transcript
WP5 Progress Report EDG Conference Barcelona, May 2003 escience Centre Outline Status of release 2.0 Testing and support structures Priorities up to TB3 Open issues Status of release 2.0 Core SE Software Interfaces to various MSS CLI Built from C programme creating and transferring XML to core via Apache Web Service Developed using AXIS and Tomcat Now using WP2 build system Java API, CLI, demo Reptor interface getsecosts for Optor Prototype via MDS, now a webservice GLUE Storage Schema information providers Release 2.0 SRM-like API Needs more work before it will interwork with other implementations of SRM Layered beneath Replica Manager API and CLI can be used directly by users Not a simple interface eg create/getturl/copy/commit cache/getturl/copy/abandon Wrapped by rm-commands Release 2.0 MSS supported Castor, RAL DataStore, Disk Coming soon HPSS via RFIO (CC-IN2P3) Started discussions with ESA/ESRIN, SARA, (INSA/WP10) Ready to talk to other Castor sites Testing and support structures Handlers unit tested Test harness for individual functions Uses curl to send sample XML without client Webservice test suite for API Limited performance tests Create=0.3sec using CLI on modest PC Total transaction time dominated by data transfer Need stress tests Testing and support structures Q staff months delivered to WP5 ~ 7FTE of which 2 working on Castor WP5 roles WP Manager PTB, WPM, emergency meetings, crisis meetings, emergency crisis meetings. ATF Iteam - 2 people now Packaging, configuration, CVS, autobuild QAG Internal roles Documentation, maintaining web site Not much left for coding or support from 5 FTE Testing and support structures Q staff months delivered to WP5 ~ 7FTE of which 2 working on Castor Support structure is Owen assigns Bugzilla reports Individuals support an area of SE Security (Jens), Handlers (Regina), Core (Owen) Information providers (Regina), webservice (Glen), API (Jens) No guarantee we have a second person Priorities up to TB3 Address some deficiencies now Would like release 2.1 for LCG1 Rest for TB3.0 TB2.1 Improve error handling RFIO TURL Non-blocking calls Generate request_id and GetStatus SRM v1.1 single file use For LCG1 Native data transfer Eg GridFTP support in Castor allows SE to return a TURL that points direct to Castor TB3.0 Security Fuller SRM File instance metadata Required for pinning Security Webservice will use edg-trust-manager (+authorisation manager) Gives access to user DN now and VOMS credentials later Implement file and transaction level ACLs Can this user access this file in this mode? Can this user perform this action? Intend to use GACL GACL From Andrew McNab V3 supports VOMS credentials in ACLs ACL can use DN, groups, roles Already have a hook in file metadata for ACL/file Implemented a prototype handler with GACL v2 library but it didn t make TB2.0 cut Just add check_acl handler to sequence of handlers called for each function Initial step to implement checking only sysadmins can add ACLs to VO tree by hand (or rpm) Later add API to manipulate ACLs Open issues Webservice only? Data transfer? Posix I/O? SRMcopy requires proxy delegation. Can we do this? How do we replicate ACLs with files? Where do we get default ACLs for a VO? What is the trust tree for ACLs? Ie who do we allow to define ACLs for a VO? When does the emergency stop?
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks