We have several users using the fs_lvm in production, so yes, the
driver is completed and tested.
You can execute the monitoring script manually to check what could be
happening. In the remote host, as oneadmin, go to
/var/tmp/one/im/kvm-probes.d and execute:
bash -x ./monitor_ds.sh kvm
Hi again,
2nd Question... regarding to the Docs fs_lvm whould be the recommended
LVM Driver today. Unfortanly i was not able to get it working, nor on
4.6.0 or on 4.6.1.
It just doesnt recognize the VG, which is correctly named vg-one-dsid.
After Changing the Driver back to the legacy Block LVM
Hi,
On Wed, May 14, 2014 at 3:46 PM, Benadik, Jan jan.bena...@atos.net wrote:
Hello all,
I have a question - because of one free SUN T2000 machine (8 cores CPU,
16GB RAM, Debian 7 SPARC) I've decided to try it as node for OpenNebula.
KVM is not available on this HW platform, maybe LXC
We are fixing some minor bugs in the UI and running the tests. If
everything goes as expected it'll be ready by Friday - Monday next week.
Cheers
On Tue, Apr 22, 2014 at 2:34 PM, ML mail mlnos...@yahoo.com wrote:
Hi,
When is the final version of ONE 4.6 coming out? Quite excited to have it
Hi,
When is the final version of ONE 4.6 coming out? Quite excited to have it
running in prod!
Cheers,
ML
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Hi
How is it going to affect the upgrade procedure? I would like to enlarge
my current vm lab and I would like to divide it into more VDCs and at least
two zones. Question is: do it now or wait for the One 4.6 to avoid
potential upgrade issues?
Please wait for 4.6, we are going to release
Thank you for the information.
How is it going to affect the upgrade procedure? I would like to enlarge my
current vm lab and I would like to divide it into more VDCs and at least two
zones. Question is: do it now or wait for the One 4.6 to avoid potential
upgrade issues?
Ondra
On
Hi,
I was briefly looking at roadmap for one 4.6 and discovered the feature
#2691: Remove ozones code.
What kind of change is that? Just some refactoring or are you remove
ozones completely? If yes, what will replace them?
Thank you in advance
Ondra
This e-mail and any attachment is for
Hi Ondrej,
Ozones has been redesign and integrated in OpenNebula core, you can have
more information about the VDC part here [1]. We need to find some time to
make a screencast of the federation part, meanwhile take a look to the new
documentation [2,3] Note that we are working on the docs