On Fri, 2011-07-22 at 13:05 -0400, Greg Blomquist wrote:
If the deltacloud ID is the UUID presented to deltacloud by the
provider for the launched instance, then the only reason not to use the
deltacloud ID for the config server and audrey startup script is that it
requires the guest to launch and report this ID before the
configurations can be handed to the config server.
Yeah, it's not ideal.
That's not terrible, but just makes the launch sequence more
instead of parallelizing the launch and seeding the configs to the
config server. If it's necessary to reduce the number of IDs floating
around, we can do this.
Well, AFAICT, the only ID that the cloud HA stuff will know about from
conductor or deltacloud is the deltacloud instance ID. So, that's what
we want the guest agent to use when reporting back.
If you choose to add another ID for config server purposes, that would
mean the cloud HA stuff would need to find that out. And I think that's
a step too far in terms of intertwining the architecture. The cloud HA
stuff should work with standalone deltacloud, without conductor or
config server IMHO.