openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #13910
Re: Nova and asynchronous instance launching
There's only 1 rpc call unless you're running cactus or something. All schedulers have a loop...not API.
min-count is unfortunately special cased right now to be a single call vs cast, though. I was going to fix that real soon. Problem is scheduler creating the DB records vs API in this case. I can expand on this when I'm not replying from a phone. :)
There's some other things that would be nice to do here with the API but the call can change to a cast with no API behavior change (except for speeding up the response :)
- Chris
On Jun 27, 2012, at 12:53 PM, Devin Carlen <devin@xxxxxxxxxxxxx> wrote:
> We filed a blueprint for this yesterday:
>
> https://blueprints.launchpad.net/nova/+spec/launch-instances-async
>
> "Currently if a user attempts to create a lot of instances with a single API call (using min_count) the request will hang for a long time while all RPC calls are completed. For a large number of instances this can take a very long time. The API should return immediately and asynchronously make RPC calls."
>
> We are looking for creative ways to work around this problem, but in the meantime I'd like to hear from folks on what they think the preferred solution would be.
>
>
> Devin
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
References