On Wed, 2011-05-25 at 08:57 -0400, John R. Dunning wrote:
Caveat: I know essentially nothing about the flow of control through
the API and RHEV control software. My hope is that we could find a
place in the api layer, where we know the COW has been created, but
the launch hasn't yet happened. We could add something to reach in
with libguestfs or something similar and drop our cookies in a known
place in the COW image.
What you're describing would be a new RHEV-M feature. One that isn't
planned yet.
One way of implementing this might be to use RHEV-M's new "custom hook"
support. You can install scripts on RHEV hosts which can hook into
various parts of the VM lifecycle.
You can only pass parameters to these scripts via the API, though. The
scripts themselves must be installed separately on the hosts. In the
case of RHEV-H, that effectively means a custom version of RHEV-H.
Cheers,
Mark.