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

Functionality Atlas LHCb dCache DPM EOS StorRM xrootd Comments
Create, Read, Update, Delete A A Y Y     Y  
WebDAV (which bits?) PROPFIND, MOVE ? ? Y     Y  
X509/VOMS AA A A Y Y     Y  
Multi-range requests D   Y Y     Y  
Directory Space Reporting C C N N     Y via virtual partitions  
Calculate checksum / type     N Y     Y internal  
Set checksum / type     N N     Y internal  
Get checksum C C Y Y     Y internal
3rd Party Copy Source C D Y Y     Y  
3rd Party Copy Destination C D N N     Y  
3rd Party Copy ↔ S3 D D N Y, prototype     N  
3rd Party Copy ↔ gridFTP D D Y       N  
ACL Management D D N N     N  
Monitoring of HTTP traffic D D N(planned) Y     Y  
Endpoint publication to BDII C C Y Y     Y  
Edit | Attach | Watch | Print version | History: r14 | r12 < r11 < r10 < r9 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r10 - 2015-06-02 - AndrewHanushevsky
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

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