Bug 1469289

Summary:	RFE: More intuitive usage of --min and --max arguments in openstack server create
Product:	Red Hat OpenStack	Reporter:	Sai Sindhur Malleni <smalleni>
Component:	openstack-nova	Assignee:	OSP DFG:Compute <osp-dfg-compute>
Status:	CLOSED WONTFIX	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	low	Docs Contact:
Priority:	low
Version:	11.0 (Ocata)	CC:	berrange, dasmith, eglynn, kchamart, lyarwood, mbooth, sbauza, sferdjao, sgordon, srevivo, vromanso
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	scale_lab, aos-scalability-36,scale_lab
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-05 17:42:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sai Sindhur Malleni 2017-07-10 21:08:14 UTC

Description of problem:
Currently the --min argument passed to openstack server create is only used to check the Quota but once the Quota check passes, if the --max number of instances can't be scheduled all instances go into ERROR state. However, when --min and --max are passed, it would be great if nova schedules as many instances as possible upto --max and only fails when even the --min number of instances can't be scheduled.

Version-Release number of selected component (if applicable):
11

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: