[Users] smbios hook

[Dan Kenigsberg]

On Wed, Feb 26, 2014 at 11:47:36AM +1300, Liviu Elama wrote:
> Thank you Dan
> 
> That actually works but I still have on more question: how can I add more
> than just one key in custom properties to use with more than one hook?
> the above method seems to allow only one key to be set for the same cluster
> version
> 
> Regards
> Liviu
> 
> 
> On Tue, Feb 25, 2014 at 8:05 PM, Dan Kenigsberg <danken at redhat.com> wrote:
> 
> > On Tue, Feb 25, 2014 at 02:53:54PM +1300, Liviu Elama wrote:
> > > Hi
> > >
> > > I have a 2 node hosted engine cluster using 3.4 beta3 on centos 6.5 and
> > I'm
> > > trying to use smbios hook(first try to use a hook) and I can't see the
> > > smbios key in custom properties when I edit a VM.
> > >
> > > I have installed the vdsm-hook-smbios on both hosts and restarted vdsm
> > and
> > > restarted the engine as well.
> > > I can see the hooks available on each hosts from the engine GUI but I
> > can't
> > > see the custom property to modify at VM level.
> > >
> > > Can anyone advise if I'm doing the right thing here or what logs should I
> > > provide for debugging ?
> >
> > You have to explicitly enabled your custom property in Engine's
> > database.
> >
> > See http://www.ovirt.org/Vdsm_Hooks#VM-level_hooks for an example how
> > this can be done with the engine-config utility. You could make your
> > users cozy by limiting their input to the likes of
> >
> >     {'serial': '1234'}^{'vendor': 'oVirt'}
> >
> > or be lazy and allow everything
> >
> >     engine-config -s "UserDefinedVMProperties=smbios=.*

You should separate different properties with a semicolon, e.g.:

    UserDefinedVMProperties=smbios=.*;some_other_prop=(true|false)