RFE: More intuitive usage of --min and --max arguments in openstack server create
Bug #1703457 reported by
Sai Sindhur Malleni
This bug report is a duplicate of:
Bug #1458122: nova shouldn't error if we can't schedule all of max_count instances at boot time.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
New
|
Undecided
|
Unassigned | ||
Bug Description
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.
Revision history for this message
| Matt Riedemann (mriedem) wrote | #1 |
To post a comment you must log in.
This is a duplicate of bug 1458122.