openstack team mailing list archive

[Rafael Rosa <rafaelrosafu@xxxxxxxxx>]

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 UUID you know
what you're doing and is generating them in a way that won't be duplicated.
Just by using standard UUID generators the possibility of collisions are
really really small.

Thanks for the feeback :)

Rafael Rosa Fu


2013/4/3 Michael Still <mikal@xxxxxxxxxxx>

> On Thu, Apr 4, 2013 at 9:16 AM, Rafael Rosa <rafaelrosafu@xxxxxxxxx>
> 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
> > "immediately" to the caller with a final instance UUID and do the work on
> > the background, but it's only generated when during actual instance
> > creation, which is a no go in our situation.
>
> The instance_create database call already accepts an instance UUID as
> an argument, so that bit looks like it should work out well for you.
> So, I guess this is mostly a case of working out how you want the API
> to work.
>
> Personally, I would have no problem with something like this, so long
> as we could somehow "reserve" the instance UUID so that another caller
> doesn't try and create an instance with the same UUID while you're
> doing your slow thing.
>
> Cheers,
> Michael
>