Hi Joe,
On Wed, 2011-05-25 at 08:43 -0400, Joseph VLcek wrote:
Mark, et al.
The Big Question:
------------------
Should the COW file be what is used to pass the Config Server contact
info. to a RHEV-m instance at launch time?
Or is there a better way to inject user data into a launching
instance on RHEV-m?
Brief:
------
A solution is needed for passing the Audrey Config Server contact
information (IP address:port/UUID) into an Audrey enabled instance on
RHEV-m. This is required so the IP address of the launching instance can
be picked up.
Okay, the last time this was discussed, my understanding was that:
- RHEV-M doesn't currently support injecting user data through
SMBIOS, modifying COW images, or anything else
- Before starting a RHEV-M instance, we would pass the config server
the RHEV-M VM UUID, along with the config for the instance
- On startup, the audrey script would connect to the config server,
supply its UUID and return the config
- The config server would record the IP address of the request and
report it back to conductor
Now, there are two problems here:
- This requires the config server IP address to be baked into the
image
- The VM UUID isn't some secret key that we can rely on for
authentication to prevent other VMs from spoofing.
AFAIK, there may have been some confusion that RHEV-M has OTP support,
which would solve the latter problem. The only OTP in RHEV-M is for the
display server, which the guest knows nothing about. So that doesn't
help.
I don't know if we ever thought we had a solution for the former
problem.
Cheers,
Mark.