Bug 1041010

Summary:	[RFE][nova]: Flavor-specific instance quotas
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/flavor-specific-instance-quotas
Whiteboard:	upstream_milestone_none upstream_status_not-started upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:20:23 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 13:24:28 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/flavor-specific-instance-quotas.

Description:

Support per-instance-type quota resources so that for each existing instance-type, there is the potential to add a new quota limiting *only* that instance type (and keep the existing instances quotas as an over-arching limit).

For example, if the following quotas were set:

  instances:          110
  instances-m1.xlarge: 10
  instances-m1.large:  20
  instances-m1.small:  50
  instances-m1.tiny:  100

and a user requested an additional xlarge instance, we'd first check if we had headroom on the instances-m1.xlarge quota and then if we also had headroom on the over-arching instances quota (before going on to check the ram & cores 
if necessary). Whereas, if a medium instance was requested, we would only check the overarching limit, as there is no instances-medium quota defined.

This would require some change to the quotas logic, to allow the set of resources that may be limited by quotas to be more dynamic (currently we have a fairly fixed set, whereas new instance types may be defined at any time).

The requirement was raised on this ML thread:

  https://lists.launchpad.net/openstack/msg14925.html

Specification URL (additional information):

None