I know there were discussions during the summit on how to fix quota bugs, and in particular the multi instance code was making the solution harder.
I agree with you though, if the api is to stay, the current behavior seems broken. Thanks, Kevin ________________________________________ From: Chris Friesen [[email protected]] Sent: Wednesday, May 27, 2015 6:38 PM To: [email protected] Subject: Re: [openstack-dev] [nova] I think nova behaves poorly when booting multiple instances On 05/27/2015 05:09 PM, Fox, Kevin M wrote: > If the current behavior is broken, and the behavior is causing problems with > things like fixing quota's, should it just be deprecated and pushed off to > orchestration rather then change it? Is this causing problems with quotas? The problem I brought up isn't with quotas but rather with all the instances being set to an error state when we could have actually booted up a bunch of them. In any case, even if we wanted to deprecate it (and I think an argument could be made for that) we still have to decide what the "correct" behaviour should be for the API as it exists today. In my view the current behaviour doesn't match what a reasonable person would expect given the description of the "min count" and "max count" parameters. Chris __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
