If the shared datastore is mounted in the same place in both nodes
there wont be any problem. The base image will be accessible from both
nodes (shared) and the qcow delta is moved to the host.
On Wed, Jul 11, 2012 at 12:59 PM, Andreas Calvo andreas.ca...@scytl.com wrote:
Javier,
Thanks for
The shared storage is mounted in the same place in all the nodes.
The directory structured is as follows:
/var/lib/one/datastores (shared storage)
-- 0 - link to /one/datastores/0
-- 1
-- 100
/one/datastores/ (local storage)
-- 0
-- 1 - link to /var/lib/one/datastores/1
-- 100 - link to
Hi,
Did you follow the configuration steps to enable TCP [1]?
Regards
[1] http://opennebula.org/documentation:rel3.6:kvmg#configuration
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNebula.org | cmar...@opennebula.org |
Dear OpenNebula users,
I'd like to share with you a collection of scripts for OpenNebula CLI
administrators:
https://github.com/jmelis/one-tools
Currently these are the available scripts:
onelog -- Displays OpenNebula logs.
oneinstantiate -- Instantiates template with a name.
onedeploy --
You are right. I've overlooked the driver. In qcow the mv driver is
dummy as it expects the qcow image to be shared. You can just copy mv
script from ssh tm to qcow remotes directory. I have not tested that
but it should work. The qcow image will me moved on stop to the
frontend and on resume back
Thanks for the reply. It worked out now. The problem was that, the two
machines were having different versions of libvirtd.
*
Thanks Regards
Mohit Dhingra *
On 11 July 2012 21:50, Carlos Martín Sánchez cmar...@opennebula.org wrote:
Hi,
Did you follow the
