On Wed, Apr 3, 2013 at 7:05 PM, Chris Behrens wrote:
> I'm having a hard time understanding the original problem. nova boot
> should return in milliseconds. There's no blocking on provisioning.
>
>
The only thing that could block is DB access, as AFAIK the RPC to the
scheduler is still pass by
I'm having a hard time understanding the original problem. nova boot should
return in milliseconds. There's no blocking on provisioning.
- Chris
On Apr 3, 2013, at 8:32 PM, Rafael Rosa wrote:
> API wise I was thinking about something like "nova boot
> --custom-instance-uuid ABC..." or somet
API wise I was thinking about something like "nova boot
--custom-instance-uuid ABC..." or something like that. To avoid problems
with any current implementation I would set it to disabled by default and
add a config option to enable it.
As for collisions, my take is that if you're passing a custom
On Thu, Apr 4, 2013 at 9:16 AM, Rafael Rosa wrote:
> Hi,
>
> In our OpenStack installation we have an issue when creating new instances,
> we need to execute some long running processes before calling "nova boot"
> and the call blocks for the end user for a while. We would like to return
> "immedi
Hi,
In our OpenStack installation we have an issue when creating new instances,
we need to execute some long running processes before calling "nova boot"
and the call blocks for the end user for a while. We would like to return
"immediately" to the caller with a final instance UUID and do the work
5 matches
Mail list logo
