[one-users] contribution of LVM2 transfer manager driver for opennebula 3.4.x

[Shankhadeep Shome]

Will this work with 3.6? Is there any reason clustered lvm is required over
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.naujikas at 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/>
>
> 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 at lists.opennebula.org
> http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**org<http://lists.opennebula.org/listinfo.cgi/users-opennebula.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120630/80cd8d8c/attachment-0003.htm>