Tino Vazquez wrote on 22/08/11 13:54:
Hi Nikolay,
Hi Tino,
thanks for reply but it doesn't clarify much for me (please, see below).
For OpenNebula 2.2, the location of the remotes are
* System wide = /usr/share/one/hooks
* Self contained = $ONE_LOCATION/share/hooks
I have OpenNebula (version 2.2.1) installed in self-contained mode.
Are those hooks locations for 1) front-end node or 2) for CNs?
If it is for CNs then it looks like it is mandatory to have
$ONE_LOCATION/share/hooks mounted on all CNs. Or it's not true and one
can have non-shared FS setup?
Carlos wrote in [1]:
===========
> The mechanism you are referring to is the 'onehost sync', it has to
be executed as oneadmin in the front-end. This will force the hooks and
drivers scripts to be copied to the hosts in the next monitorization cycle.
===========
So one can assume that it's not mandatory to have shared
$ONE_LOCATION/share/hooks dir and in case of non-shared
$ONE_LOCATION/share/hooks dir the hooks have to be copied on CNs. But it
didn't happen in my case.
So my questions still are the following:
1) is it mandatory to have shared $ONE_LOCATION/share/hooks on CNs? If
the answer is 'no' then do I have to create on CNs the same directory
structure (with proper permissions for oneadmin user) as on FN to make
hooks be available in the same path on both FN and CNs?
2) is $SCRIPTS_REMOTE_DIR for specifying remote path for drivers scripts
only or for hooks as well?
3) is there any way to configure remote location for hooks scripts (e.g.
$SCRIPT_REMOTE_DIR/hooks)?
Sorry about taking your time with that issue.
[1] http://www.mail-archive.com/users@lists.opennebula.org/msg03892.html
Thanks in advance,
Nikolay.
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
