<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi,<br>
<br>
I've rewrote and improved the TM LVM for one 3.4. It's designed to work
with filesystem datastore on the frontend and LVM storage on the host. Support for cLVM between hosts will come soon.<br><br>I've also added some functionnalty, to save space on the frontend and speed up transferts. It can handle raw image (as usual), gzipped images and tgz filesystem (usefull when using XEN paravirt).<br>
<br>
See patch at http://dev.opennebula.org/issues/1240<br>
<br>
Nicolas AGIUS<br><br>--- En date de : <b>Mer 4.4.12, Jaime Melis <i><jmelis@opennebula.org></i></b> a écrit :<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>De: Jaime Melis <jmelis@opennebula.org><br>Objet: Re: [one-users] opennebula 3.4 LVM<br>À: "Juanra" <amon.raj@gmail.com><br>Cc: users@lists.opennebula.org<br>Date: Mercredi 4 avril 2012, 17h03<br><br><div class="plainMail">Hello,<br><br>actually in OpenNebula 3.4 the TM LVM drivers have been superseeded by<br>the iSCSI drivers. Today we removed the tm_lvm folder from the source,<br>but it's possible that we will bring them back for the final release.<br><br>However, the iSCSI drivers are a starting point for integrators to<br>develop their own TM drivers. The iSCSI commands can be nicely<br>substitued with specific SAN commands. Our initial idea is that<br>integrators will hack the iSCSI drivers to fit their san
solutions<br>thus eliminating the dependency on CLVM.<br><br>So I encourage you to take a look at the TM iSCSI drivers and see if<br>it works with some adaption and hacking with your SAN.<br><br>Cheers,<br>Jaime<br><br>On Wed, Apr 4, 2012 at 2:37 PM, Juanra <<a ymailto="mailto:amon.raj@gmail.com" href="/mc/compose?to=amon.raj@gmail.com">amon.raj@gmail.com</a>> wrote:<br>> Hello list.<br>><br>> We have a fiber channel SAN shared betwen host and we want to use shared LVM<br>> (clvm) without iscsi.<br>> In new beta version there is not any LVM datastore but there is an tm_lvm.<br>> Can we use tm_lvm with fs datastore?<br>> How can I configure shared lvm?<br>><br>> Thanks in advice<br>><br>> _______________________________________________<br>> Users mailing list<br>> <a ymailto="mailto:Users@lists.opennebula.org" href="/mc/compose?to=Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>> <a
href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>><br><br><br><br>-- <br>Jaime Melis<br>Project Engineer<br>OpenNebula - The Open Source Toolkit for Cloud Computing<br>www.OpenNebula.org | <a ymailto="mailto:jmelis@opennebula.org" href="/mc/compose?to=jmelis@opennebula.org">jmelis@opennebula.org</a><br>_______________________________________________<br>Users mailing list<br><a ymailto="mailto:Users@lists.opennebula.org" href="/mc/compose?to=Users@lists.opennebula.org">Users@lists.opennebula.org</a><br><a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br></div></blockquote></td></tr></table>