Description of problem: Currently vdsm is just looking in one directory for hooks. To allow a better integration with Node (and other image based delivery models) it would be good if vdsm was looking in multiple locations for hooks. i.e. the search order could be 1. /usr/libexec/vdsm/hooks/ 2. /usr/lib/vdsm/hooks.d/ # See below, for vendor side (by default) enabled hooks 2. /etc/vdsm/hooks.d/ # For user enabled hooks In addition it would be very useful, to separate the hook delivery from the hook enablement. i.e. the hooks could be delivered in /usr/libexec/vdsm/hooks, but to enable them, a symlink needs to be placed into /usr/lib/vdsm/hooks.d/ or /etc/vdsm/hooks.d/.
Fabian - is that still relevant in next-gen node?
Yes, it is _especially_ relevant for ngn.
Any plans for this RFE?
(In reply to Fabian Deutsch from comment #3) > Any plans for this RFE? We will do our best to accomplish that in 4.0, but note that it might be pushed out eventually.
Spoke with Fabian offline - there is no actual need for additional hook path folder right now. please re-open if the requirement is indeed needed