Hi,
I have tried Opennebula 4.2.0 and liked the easy provisioning wizard - a
user could select a template and combine it with his persistent image to
create a VM without the need to create a separate template.
It seems that this function is missing from Opennebula 4.8.0, requiring
eveyone to
Hello,
I am testing OpenNebula with local storage (local SSDs are faster than
shared storage), however, I do not understand how (and if) OpenNebula
monitors the available free space in each hypervisor.
Let's say I add filesystem datastore with ssh TM. It looks to me like
only the free space on
the backup. It should not be easy to lose data.
On Thu, Sep 5, 2013 at 12:53 PM, Daniel Molina dmol...@opennebula.orgwrote:
Hi,
On 4 September 2013 13:30, Pentium100 pentium...@gmail.com wrote:
Hello,
While trying out OpenNebula, I noticed that the VM creation process is
quite inconvenient if I
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
.
--
*From: *Pentium100 pentium...@gmail.com
*To: *Daniel Molina dmol...@opennebula.org
*Cc: *users@lists.opennebula.org
*Sent: *Tuesday, September 10, 2013 3:27:50 AM
*Subject: *Re: [one-users] Simplified VM creation?
Hi,
I upgraded to 4.2 and the cloud view is quite nice. I
Hello,
While trying out OpenNebula, I noticed that the VM creation process is
quite inconvenient if I want different VMs (as opposed to scaleout
situation).
1. Create the image (upload a new one or copy some other image), set it as
persistent (I don't want the VM to disappear if I shut it down).
Hello,
As far as I understand the documentation, it looks like all storage options
for OpenNebula are shared - ceph, iSCSI, nfs, cLVM.
However, configuring the storage locally on the node would allow for better
performance (especially if using SSDs), even though the VM then would not
be fault
From what I understand, OpenNebula encodes the IP in the MAC, for example,
the VM with assigned IP 10.0.0.2 would get a MAC 02:00:0a:00:00:02. Just
create an IP:MAC list for the DHCP server and it will work.
host a10-0-0-1 { hardware ethernet 02:00:0a:00:00:01; fixed address
10.0.0.1; }
host
Hello,
I am trying out OpenNebula as a replacement for our current system of just
using virt-manager to manage the VMs.
We use the VMs as replacements of real server - which means that each VM is
unique and should not be deleted (unless, of course, it is no longer
needed). There are no multiple
