HTTP Storage Requirements

This page tracks the required and desired functionality requested from HTTP storage, as defined by the HTTP Deployment Task Force.

We can classify these requirements in different ways, to discuss at the next meeting, but one possibility is

  • A: required for the deployment of HTTP to be worth pursing at all
  • B: required for SRM-free operation of disk storage
  • C: required for single-protocol (ie HTTP-only) disk storage
  • D: desirable feature
  • E: irrelevant

FunctionalitySorted ascending Atlas LHCb dCache DPM EOS StorRM xrootd Comments
WebDAV (which bits?) PROPFIND, MOVE Partially Partially Y Partially: MKCOL PROPFIND PROPPATCH COPY MOVE LOCK UNLOCK - some special header support PROPFIND, CP, MV Y (AP: complex to answer, impossible to put Y here)
3rd Party Copy ↔ gridFTP D D Y ?   N N  
3rd Party Copy ↔ S3 D D N Y, prototype ? N N  
3rd Party Copy Destination C D N N N N Y  
3rd Party Copy Source C D Y Y N N Y  
ACL Management D D N N Y (custom rest API) N N  
Calculate checksum / type C, e.g., md5   N Y (md5, adler32) implicit (md5,adler32,crc32c,crc32,sha1) Y (adler32) Y internal  
Create, Read, Update, Delete A A Y Y Y (GET HEAD PUT DELETE OPTIONS) Y Y (AP: what is HTTP update?)
Directory Space Reporting C C N N (planned) custom Rest API using subtree accounting N (planned) Y via virtual partitions To what hierarchical depth is this required?
Endpoint publication to BDII C C Y Y N Y Y  
Get checksum C C Y Y Y (PROPFIND, custom Rest API) Y Y internal
Monitoring of HTTP traffic C (network monitoring, popularity ?) D N(planned) Y Y (internal, not via xrootd) N Y This refers to i/o monitoring (like xrootd fstream or similar)
Multi-range requests D   Y Y Y Y Y  
Set checksum / type C, e.g., md5   N N set XS: support for custom header to preset checksum on PUT for OC - set type:Y N (if this means setting the checksum after the transfer) Y internal  
X509/VOMS AA A A Y Y RFC Proxies at VO granularity per storage area Y  


This topic: LCG > WebHome > WLCGCommonComputingReadinessChallenges > WLCGOperationsWeb > WLCGOpsCoordination > HTTPDeployment > HTTPStorageRequirements
Topic revision: r14 - 2015-06-03 - OliverKeeble
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback