Authors

Public Pad

Latest text of pad swift-features-ods-d
Saved April 19, 2012
 
    * access log delivery (scheduled)
    * self-destructing files (scheduled) [Use tombstone metadata for deletion date target]
      - E.g., leasing or dead-man's trigger
      
      - Would be nice to sync with burrow syntax: http://burrow.openstack.org/overview.html#message
      - Once marked, do access semantics change? Answer TBD is fine.
    * Read-only files
    * tiny URLs (scheduled)
      - watch out for hash collisions, etc. (as always)
      - example?  like bit.ly?  or just a slightly shortened URL to the same domain?
    * server side chunking on upload (upload >5GB) (scheduled)
      - Append operation with arbitrary chunk sizes if manifest contains section 0 of object
    * metadata search (not scheduled)
    * quota support (not scheduled)
      quota is just policy applied to monitoring results, rate limiting is applied to 1st derivative
      provide policy hooks on everything we can monitor / alert
    * versioned files (not scheduled)
    * s3 import/export (not scheduled)
      - why not make it generic.  cloud to cloud.  support replication from multiple swift clouds.
      - more generic URL import/export so you don't need to bounce through a 3rd party
    * webdav/ftp/fuse interfaces (not scheduled)
    * analytics for logs (not scheduled)
         - (Out of scope?)
         - (Shouldn't this consume the same results of https://blueprints.launchpad.net/openstack-devel/+spec/notification-and-statistics as the other services?)
         - locality tags would be useful
    * support content-encoding (auto-compression) on the proxy (not scheduled)
     - Build as plugins to general "filter" stack (compression, future support for encryption, etc)
    * unlimited objects per container (not scheduled)
    * batch requests (not scheduled)
    * Pluggable hashing mechanism 
         Ring-as-a-service component: 
         AuthContext for SLA