On Tue, Jul 26, 2011 at 8:52 AM, David Lutterkort <lutter(a)redhat.com> wrote:
On Mon, 2011-07-25 at 15:39 +1000, Andrew Beekhof wrote:
> On Sat, Jul 23, 2011 at 5:30 AM, Greg Blomquist <gblomqui(a)redhat.com> wrote:
> > So, it looks like this (I think--assuming we're talking about a cloud
> > engine environment):
> > 1. conductor tells deltacloud to launch guest
> > 2. guest boots in cloud provider
> > 3. audrey client starts
> > 4. audrey client contacts config server, but finds nothing there...yet
> > 5. deltacloud driver tells conductor deltacloud ID for guest
> What about:
> 5. deltacloud calls into the cloud provider to obtain the/a
> hardware-based UUID for the guest and tells conductor
Just a minor nit: I don't know any cloud provider that exposes a
'hardware-based UUID' through their API.
I used the term "hardware-based UUID" to cover things not part of a
traditional image or non-guest installation.
Something that is part of the guest's definition or the underlying
hardware in the non-guest case.
What you referred to as the user_data parameter in your following
email would do just fine.
Best case, they create a unique
ID for the instance out of whole cloth.