per-flavor-quotas
Registered by
Sergio Cazzolato
Currently when an operator creates a new user, is not able to define the
quotas based on the # of a given flavor, for instance, define the user
quotas as 3 x m1.medium flavor.
This blueprint comes from the operators feedback:
https:/
To address this request I propose to add a new resource for the flavors
that can be use when the operator set up the user quotas.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Sergio Cazzolato
- Direction:
- Needs approval
- Assignee:
- Sergio Cazzolato
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
28-Mar: Working on the specification
Spec not approved yet, un-targeting blueprint from juno-1 --johnthetubaguy (28th May 2014)
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(?)