availability zone quota

Registered by Kevin Fox on 2015-03-19

Say I had two availability zones in one region. HA and NON-HA. Nodes in the first are UPS backed, and are few in number. Nodes in the second are not and more numerous.

I want to be able to per project specify quotas separately on the HA AZ vs the NON-HA AZ so that a user can't use his or her entire quota to fill up the expensive but limited resources.

This could be done with a whole region, but its a lot of effort to setup that up when a secondary, az level quota would do the trick.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Kevin Fox
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Hi. Did this get any air time in Vancouver? There was a relevant session on quotas: https://etherpad.openstack.org/p/YVR-nova-quotas-and-database, and there seems to be some need to support nested project quotas (with nested projects now a thing in Keystone), so it would be really nice to make sure the per-zone requirement is included too.

kfox1111 - no. The session was busy trying to work through how to solve the existing quota bugs.

Please note this will require a spec, and thats the best place to move this discussion forward. The scheduler unconference would have been a good place to bring this up. Please note we already have this spec merged: http://specs.openstack.org/openstack/nova-specs/specs/liberty/approved/nested-quota-driver-api.html
--johnthetubaguy 4th June 2015

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.