converted from BZ/EPIC to Feature

Feature Overview 
Glance currently lacks per-tenant quota capabilities, which is something that other OpenStack projects have had for quite some time. Especially since Glance is a key project for a working cloud, and because it involves consumption of expensive resources, quotas are necessary for operators to properly restrict usage. Public clouds charge for every resource, and thus per-tenant limits may be less important. However, private clouds generally do not bill for usage, and instead rely on pre-paid quotas for resource sharing.

Goals

• Deliver upstream feature to RHOSO-18
• Customer facing documentation
• Automated Test
• Plan support enablement

Requirements 

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):

1. Unified quota per tenant should work as per upstream spec
2. Full unit test coverage
3. Tempest test coverage running in upstream gates
4. Tempest test coverage running in downstream jobs
5. Manual test with keystone integration.
6. Doc verification

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

Out of Scope __(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.
<your text here>

Documentation Considerations __(Initial completion while in Refinement status):
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
<your text here>

Questions to Answer __(Initial completion while in Refinement status):
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

• …