Bug 981282

Summary:	[RFE] [engine-backend] adding new hooks to host cluster should be done by engine and not by adding them host by host
Product:	[oVirt] ovirt-engine	Reporter:	Elad <ebenahar>
Component:	RFEs	Assignee:	Scott Herold <sherold>
Status:	CLOSED DEFERRED	QA Contact:	Gil Klein <gklein>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.3	CC:	bkorren, bugs, lpeer, rbalakri, Rhev-m-bugs, srevivo
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-future? sherold: Triaged+ rule-engine: planning_ack? ebenahar: devel_ack? rule-engine: testing_ack?
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-13 07:48:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Elad 2013-07-04 11:24:55 UTC

Description of problem:

As for now, adding new hooks process is being done by adding them to hooks directory /usr/libexec/vdsm/hooks/ on the host.
This process can be painful for user, in a case of large number of hosts (user has to go host by host and create his hook).
In order to optimize the process, I would recommend about delegating the process to engine.
The idea is that user would be able to add his new hooks using engine.
For example, creating a new sub tab under cluster main tab in UI, where user will be able to upload his scripts and there he also would be able to add the hosts he would like them to contain the new hook.

Comment 2 Barak Korren 2016-05-30 14:39:21 UTC

+1
It seems that this becomes even more relevant when considering RHEV-H

Comment 3 Yaniv Kaul 2017-03-13 07:48:39 UTC

These days, I'd suggest using Ansible to do this - closing for the time being.