Hi,
I upgraded to 4.2 and the cloud view is quite nice. I modified the user
view to include the easy provisioning (for some reason create image does
not work in cloud view, even if I enable it) and now it is pretty much like
it should be - the user can create a persistent image (or clone a
On 09/10/2013 12:30 PM, Zeeshan Ali Shah wrote:
Hi, Any one tried to work with cloudinit with open nebula ?
https://cloudinit.readthedocs.org/en/latest/topics/examples.html
OpenNeubal is not available via CloudInit, but it is possible to develop
new providers and contribute to upstream effort.
Hi,
If you use the metadata-server, cloud-init works out of the box without any
change.
Just make sure the instance uses the regular EC2 provider.
https://bitbucket.org/ricardoduarte/opennebula-metadata
Regards,
Ricardo Duarte
Date: Tue, 10 Sep 2013 12:33:52 +0200
From:
There's an ongoing work adding OpenNebula support to cloud-init. I
hope it gets included soon:
https://code.launchpad.net/~vlastimil-holer/cloud-init/opennebula/+merge/184278
Any help or idea is appreciated
On Tue, Sep 10, 2013 at 12:33 PM, Olivier Sallou
olivier.sal...@irisa.fr wrote:
On
Hi,
Let's say a user created a VM using a non persistent image (a template). Is
there a way to now clone the image and make it persistent (remember - the
user does not own the original non persistent image) without losing data.
Alternatively, is there a way to allow a user to clone the image but
I agree on the non-persistent images, so long as you are careful it shouldn't
be a problem. I understand their purpose, and for particular use cases
(development environments, hypervisors with local rather than shared storage)
they make sense. I compare non-persistent images to instance store
Hello,
On 09/09/13 11:17, Daniel Molina wrote:
Hi,
On 5 September 2013 18:04, Wojciech Giel wojciech.g...@cimr.cam.ac.uk
mailto:wojciech.g...@cimr.cam.ac.uk wrote:
Hello,
I have installed and configured open nebula 4.2 in centos 6 from
opennebula repository. command line tools
While we use hypervisors with local storage, the images has to be
persistent. As I said, it should not be easy to lose data. Right now, the
users do not get access to the VM controls (a simple libvirt setup with
virt-manager and local logical volumes for storage) but even for me or some
other
Hi,
I get the following error when trying to create an image from a
QCOW2 file:Error copying image in the datastore: Not allowed to
copy image file /var/lib/one/datastores/1/DELETEME.qcow2
Below are the commands I use to create the QCOW2 file before trying
to create the image
Same as context, use TARGET in the DISK attribute
DISK = [ IMAGE=CentOS-root , TARGET=sda1 ]
Probably, setting it at the image level is a better idea as the TARGET
value is inherited from there. So update the image template and simply add
TARGET=sda1
to it.
Cheers
On Mon, Sep 9, 2013 at
Hi,
This seems to be a general issue not specific to QCOW2. For the
moment I've solved the issue by mounting the datastores (which are NFS
exports for a filestore) on the root partition at /datastores and
created a symlink form /var/lib/one/datatstore to /datastores.
Is this
On 09/03/2013 09:08 PM, Duverne, Cyrille wrote:
Hello guys,
I'd like to start a little feed on the mailing list : How are you
industrializing your VM images ?
How are you creating your images ? Which OS are you using ? How do you
maintain the images ? Do you use a specific tool ?
Take a
HI
i am using opennebula 4.2 how to handle vms running on specific host to
move (not recreate) to another host when host error(down)
please could any on help me ?
Thanks
-- Forwarded message --
From: Romany Nageh engromanyna...@gmail.com
Date: Sep 9, 2013 9:46 PM
Subject: how
13 matches
Mail list logo
