On 2012/02/08 5:42 PM, Alberto Zuin - Liste wrote:
In past we used OpenNebula 2.2 with MooseFS driver for immediate
deployment via snapshot, but the driver wasn't updated to OpenNebula 3.0.
We are very happy with MooseFS: it's very easy and robust. The only
consideration is on disk side: SATA
On 2012/02/08 7:54 PM, Chris Picton wrote:
On 2012/02/08 5:42 PM, Alberto Zuin - Liste wrote:
In past we used OpenNebula 2.2 with MooseFS driver for immediate
deployment via snapshot, but the driver wasn't updated to OpenNebula
3.0.
We are very happy with MooseFS: it's very easy and robust
Hi
I have the following vnet:
oneadmin@one-mgr ~ $ onevnet show 16
VIRTUAL NETWORK 16
INFORMATION
ID : 16
USER : oneadmin
GROUP : oneadmin
PUBLIC : No
On Thu, 2011-12-29 at 15:21 +0100, richard -rw- weinberger wrote:
On Thu, Dec 29, 2011 at 10:20 AM, Chris Picton ch...@ecntelecoms.com wrote:
1. Create a machine which will be long-lived, setting the hostname and
specific parameters of this VM. Machines of this sort will probably
last
Hi
I have a current libvirt installation over four hosts, and am looking at
a way of 'cloudifying' it.
Opennebula looks good on many levels, but I would like some input on the
recommended way of performing the following tasks which I am used to on
my existing setup.
1. Create a machine which
On Thu, 2011-12-29 at 10:34 +0100, richard -rw- weinberger wrote:
On Thu, Dec 29, 2011 at 10:20 AM, Chris Picton ch...@ecntelecoms.com wrote:
Disclaimer
The information contained in this communication from the sender is
confidential. It is intended solely for use by the recipient
Hi All
I get the following in my logs when deleting a VM with a persistent
disk:
The error stems from the fact that the disk to be moved
is /var/lib/one/32/images/disk.0, not /var/lib/one/32/disk.0 as below
Is this a known problem in opennebula 3.0.0, or is it a config error on
my side?
