Bug 1041600

Summary: [RFE][swift]: Read Only Middleware
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/swift/+spec/read-only-middleware
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_new
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:16:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 18:11:07 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/swift/+spec/read-only-middleware.

Description:

For non service provider deployments of swift, it is conceivable that an organization may want to place limits on the amount of data stored. Budgeting or capacity limitations could lead to a use case where it would be desirable for the entire deployment to be marked as read only, and any requests to write objects or create containers would be denied.

The need for this is made more clear by the fact that when a swift deployment fills up, "bad things happen."

The most logical way to implement this would be with a simple WSGI middleware that could be deployed in this scenario.

Specification URL (additional information):

None