#1567 closed defect (wontfix)

S3 backend: restore s3.max_space option

Reported by: davidsarah Owned by:
Priority: normal Milestone: soon
Component: code-storage Version: 1.9.0b1
Keywords: s3-backend security storage max_space lae Cc:
Launchpad Bug:

Description

The s3.max_space option, which limits the space used by a storage server using an S3 backend, was removed in [5482/ticket999-S3-backend] because it wasn't completely implemented. The intention of this option is to protect the user from being charged for excessive space usage, perhaps due to a rogue file copy that is copying more than expected, or someone gaining access to the introducer FURL and maliciously uploading a large amount of data.

The attached patch adds back the partial implementation.

Attachments (1)

s3-restore-max-space.darcs.patch (39.4 KB) - added by davidsarah at 2011-10-19T02:07:32Z.
S3 backend: restore max_space option (partially implemented).

Download all attachments as: .zip

Change History (3)

Changed at 2011-10-19T02:07:32Z by davidsarah

S3 backend: restore max_space option (partially implemented).

comment:1 Changed at 2012-03-29T19:17:37Z by davidsarah

  • Priority changed from major to normal

comment:2 Changed at 2012-11-29T21:03:50Z by davidsarah

  • Resolution set to wontfix
  • Status changed from new to closed

This should probably be implemented generically using the leasedb, rather than with any S3- or cloud-backend-specific code. Strictly speaking that could have a different result because there may be objects in the S3 bucket that do not correspond to shares in the leasedb (and need not even look like share objects), but that doesn't seem like it is our problem.

Note: See TracTickets for help on using tickets.