Hi, As Rolandas said, there should not be any problem running the drivers in 3.6. OpenNebula 3.6, includes LVM TM [1] contributed by Nicolas AGIUS. If there is any missing feature in the current ones, let us know.
Cheers Ruben [1] http://dev.opennebula.org/issues/1240 On Sun, Jul 1, 2012 at 12:21 PM, Rolandas Naujikas < rolandas.nauji...@mif.vu.lt> wrote: > On 2012-06-30 19:14, Shankhadeep Shome wrote: > >> Will this work with 3.6? Is there any reason clustered lvm is required >> over >> > > I didn't try yet 3.6, but as seen in release notes for beta version, there > are no changes in transfer manager drivers part, so it should work (but > please test before using in production). > > For normal LVM with shared disks (SAN), there I have no experience. I > suspect, that in this case probably "mv" script could be improved, by not > copying from one node to another in some cases (and/or not creating the > copy in file for STOP). > > Regards, Rolandas Naujikas > > normal lvm with shared disks? I've been using glusterfs for shared storage >> but it's been unstable and I've lost data with high i/o. >> >> Shank >> >> On Tue, Jun 26, 2012 at 6:58 AM, Rolandas Naujikas < >> rolandas.nauji...@mif.vu.lt> wrote: >> >> Hi, >>> >>> Because Debian 6.0 Xen doesn't support tap:aio: and because LVM disks are >>> faster, I wrote modified transfer manager driver for opennebula 3.4.x, >>> that >>> use LVM volumes on local disks in virtualization hosts. >>> >>> There are 3 kinds: >>> >>> *) lvm2 - works with shared or not shared filesystem datastore (for >>> system >>> datastore there is parameter in lvm.conf to tell shared or not it is). >>> >>> *) lvm2ssh - the same, but removed code to detect that datastore is >>> shared. >>> >>> *) lvm2shared - the same, but with only assumption, than datastore is >>> shared. >>> >>> URL of all them is at >>> http://mif.vu.lt/~rolnas/one/****one34/tm/<http://mif.vu.lt/~rolnas/one/**one34/tm/> >>> <http://mif.vu.lt/~**rolnas/one/one34/tm/<http://mif.vu.lt/~rolnas/one/one34/tm/> >>> > >>> >>> >>> Regards, Rolandas Naujikas >>> >>> P.S. This driver was in almost working condition in opennebula 3.2, but >>> was lost in opennebula 3.4. lvm driver in opennebula 3.4.1 is not for >>> system datastore and is different by design. >>> ______________________________****_________________ >>> Users mailing list >>> Users@lists.opennebula.org >>> http://lists.opennebula.org/****listinfo.cgi/users-opennebula.****org<http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**org> >>> <http://lists.opennebula.**org/listinfo.cgi/users-**opennebula.org<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org> >>> > >>> >>> >> > > ______________________________**_________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**org<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org> > -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
