Re: [one-users] SunStone Monitoring

Hi Tino, Thanks for your advise and sorry that I missed this configuration. I can get the graph display for physical host and virtual machines. But for virtual machines' graph, it does not contain any data. By checking on /var/log/one/10.log, it shows Fri Aug 19 14:16:56 2011 [VMM][I]:

Re: [one-users] the nfs mount point

Hi, Yes, it will be. In this kind of configuration it is recommended to export the .ssh as well, so no need to configure the keys for oneadmin in all the machines, but rather just mount the /var/lib/one (with .ssh). Regards, -Tino -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor

[one-users] Cannot start oned after upgrading to 3.0

Hello, I had a working installation of OpenNebula 2.2 and I decided to upgrade it to 3.0 Beta1. I downloaded the tarball 2.9.80, installed it, upgraded the database (had to add require 'fileutils' in lib/ruby/onedb/onedb_backend.rb) and tried to run the daemon. If I run command 'one

Re: [one-users] Cannot start oned after upgrading to 3.0

Hi, Try a one stop; one start. If that doesn't fix it, try erasing /srv/cloud/one/var/.lock and doing a one start again. Regards, -Tino -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor www.OpenNebula.org | @tinova79 On Fri, Aug 19, 2011 at 1:13 PM, makhan makhanm...@gmail.com

Re: [one-users] Cannot start oned after upgrading to 3.0

Hi Tino, No, unfortunately it doesn't solve the problem. If I don't remove the .lock file manually it just says 'Stale .lock detected. Erasing it.'. So that's not where I would look for the problem. Wouldn't also concentrate on 'one', but 'oned' instead. If I remember correctly from previous

Re: [one-users] Cannot start oned after upgrading to 3.0

Hi, Please era the oned.log and try running oned by hand. Any output (from the command line, or from the log)? Regards, -Tino -- Constantino Vázquez Blanco, MSc OpenNebula Major Contributor www.OpenNebula.org | @tinova79 2011/8/19 makhan makhanm...@gmail.com: Hi Tino, No, unfortunately

[one-users] Can Not Find VMware ssh transfer driver for OpenNebula

Hello, We have already configured OpenNebula with ESXi with NFS Shared Storage approach, now we need to configure it through non-shared ssh approach. We are following the link mentioned below on OpenNebula but there is no driver files in the repository. Can anybody point us from where to find

Re: [one-users] Cannot start oned after upgrading to 3.0

Hi, The same error from the command line: Error: Can not start oned, opening lock file /srv/cloud/one/var/.lock No oned.log file. Regards, -Maciej -Original Message- From: Tino Vazquez [mailto:tin...@opennebula.org] Sent: Friday, August 19, 2011 2:17 PM To: makhan Cc:

Re: [one-users] Can Not Find VMware ssh transfer driver for OpenNebula

Dear Omar, Please find the old ssh tm for vmware attached. Please be aware that this is a development release. This project was discontinued due to old versions of ESX packing a dropbear client, not suitable for large file transfers. It is not linked from the documentation anymore and the

Re: [one-users] Disk image type not propagated by saveas

I am also seeing this behavior in OpenNebula 2.9.80 (of not propagating the qcow2 driver attribute) and I think it is a bug. Are there any plans of changing this in the final version of OpenNebula 3.0? Best regards, Florian On Wed, Aug 17, 2011 at 1:09 PM, Tino Vazquez tin...@opennebula.org

Re: [one-users] Can Not Find VMware ssh transfer driver

Dear Arsalaan, Please find the old ssh tm for vmware here [1]. Please be aware that this is a development release, not suited for production environments. This project was discontinued due to old versions of ESX packing a dropbear client, not suitable for large file transfers. It is not linked

Re: [one-users] hooks execution on remote nodes without shared ONE installation dir

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 | 

Re: [one-users] hooks execution on remote nodes without shared ONE installation dir

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