On Thu, Nov 24, 2016 at 02:23:11AM -0500, Arik Hadas wrote:
----- Original Message -----
Does this mean we will be able to move the hooks to the engine side at some point? That would be much better than needing it on VDSM.
Well, it sounds feasible to provide a hooking mechanism that enables to alter the domain XML in the engine, at some point. I'm not sure though that it could actually replace the hooks in VDSM since: 1. The XML won't be complete (host-specific configuration will be missing). 2. If the user wants to do some operation on the host with the hook, he'll need to send a request from the engine to the host, which is more complicated.
Still, many hooks are intended only for feature velocity - to make use of a libvirt feature without disturbing Engine or Vdsm. It makes a lot of sense to add a hooking point on Engine side, where people can plug their code.