Quota Policy Engine
Registered by
Vilobh Meshram
Going ahead with the need for Quota by Flavor, Quota by AZ, Quota by Flavor and AZ or Quota by X it would be helpful to introduce the concept of a policy engine to prevent adding more hardcoded ways of defining quotas because there are many different ways that deployers may want to slice things in there OpenStack deployments. The policy engine will introduce concepts like quota_classes, flavor_classes, tenant_groups etc
Blueprint information
- Status:
- Not started
- Approver:
- John Garbutt
- Priority:
- Undefined
- Drafter:
- Vilobh Meshram
- Direction:
- Needs approval
- Assignee:
- Vilobh Meshram
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Quota Policy Engine
(?)