Hi Tino,
Tino Vazquez wrote on 29/08/11 17:17:
Hi Nikolay,
Ok, if not on system-wide, please copy them to
$ONE_LOCATION/var/remotes, and see how it goes.
A hook script copied into $ONE_LOCATION/var/remotes on front-end node
appears on CNs in $SCRIPTS_REMOTE_DIR. But it's written the following
Hi Nikolay,
Ok, if not on system-wide, please copy them to
$ONE_LOCATION/var/remotes, and see how it goes.
Regards,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79
On Mon, Aug 29, 2011 at 9:19 AM, kna...@gmail.com wrote:
any news/help
Tino Vazquez wrote on 23/08/11 13:54:
Hi Nikolay,
Hi Tino,
The following are the location of the scripts for the FE
* System wide = /usr/share/one/hooks
* Self contained = $ONE_LOCATION/share/hooks
The following the location in the CNs
SCRIPTS_REMOTE_DIR=/var/tmp/one
I set
Hi,
Let's try this, since this seems like a bug. Could you please copy the
hook into /var/lib/one/remotes and onehost sync again?
Regards,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79
On Tue, Aug 23, 2011 at 1:26 PM, kna...@gmail.com
Tino Vazquez wrote on 23/08/11 14:45:
Hi,
Let's try this, since this seems like a bug. Could you please copy the
hook into /var/lib/one/remotes and onehost sync again?
Since in my deployment scenario OpenNebula is installed in
self-contained mode there was no such dir as /var/lib/one/. So I
Hi Nikolay,
Apologies, I was referring to OpenNebula 3.0 (sort of a chaotic dance
of versions in my head right now).
For OpenNebula 2.2, the location of the remotes are
* System wide = /usr/share/one/hooks
* Self contained = $ONE_LOCATION/share/hooks
Regards,
-Tino
--
Constantino Vázquez
Hi,
Sorry, the default for SCRIPTS_REMOTE_DIR is /var/tmp/one. This should
be writable by oneadmin in the CNs, that is probably why ONE is
failing to copy the scripts in your deployment.
Regards,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org |
Tino Vazquez wrote on 19/08/11 20:01:
Hi,
Hi,
Sorry, the default for SCRIPTS_REMOTE_DIR is /var/tmp/one.
In my setup the $SCRIPTS_REMOTE_DIR is set to /tmp/one. The driver
scripts appear there on CNs but hooks scripts don't. And that causes a
problem when hook can not be found on CNs and
Hi there,
The scripts are copied to /var/lib/one/remotes in the CNs, no shared
directories are needed.
They are copied when the host is first monitored, and with onehost sync.
Hope it helps,
-Tino
--
Constantino Vázquez Blanco, MSc
OpenNebula Major Contributor
www.OpenNebula.org | @tinova79
Tino Vazquez wrote on 18/08/11 19:27:
Hi there,
Hi Tino,
The scripts are copied to /var/lib/one/remotes in the CNs, no shared
directories are needed.
For some reason the hooks scripts are not copied to CNs in
/var/lib/one/remotes in my OpenNebula setup.
The 'onehost sync' command was
Hi,
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.
Regards.
--
Carlos Martín, MSc
Project Major Contributor
OpenNebula - The
Carlos Martín Sánchez wrote on 11/08/11 12:55:
Hi,
Hi,
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.
if 'onehost sync' has
forgot to mention that I could not find any info in [1] too about a
necessity to share $ONE_LOCATION/share/hooks dir across CNs in case if
hooks has to be executed on remote node. So I wonder if
$ONE_LOCATION/share/hooks needs to be available across CNs if there is
hook to be executed on CNs
13 matches
Mail list logo
