[one-users] What kinds of shared storage are you using?

[Ignacio M. Llorente]

Happy to read this, please see the details at
http://www.opennebula.org/community:ecosystem and you can get an
account in our blog by sending an email to Borja at
<community-manager at opennebula.org>,

Thanks!

2010/9/3 Székelyi Szabolcs <szekelyi at niif.hu>:
> On Friday 03 September 2010 14.54.06 Ignacio M. Llorente wrote:
>> You could consider to contribute the new driver to our ecosystem
>> and/or write a post in our blog describing your customization.
>
> Our development is sponsored by the state, thus everything we develop will be
> open sourced, and so, it'd be an honour to contribute this to the OpenNebula
> ecosystem.
>
> This is an ongoing development, and the TM driver is just a small part of it.
> On the other hand, in our environment it has been quite stable for a couple of
> weeks now, so I think it's time to do an alpha release.
>
> I'll use the weekend to gather all its dependencies, wrap it up and write some
> docs about it. Expect a release in the beginning of next week.
>
> Thank you for your interest.
>
> Cheers,
> --
> cc
>
>> On Fri, Sep 3, 2010 at 1:07 AM, Andreas Ntaflos <daff at pseudoterminal.org>
> wrote:
>> > On Friday 03 September 2010 00:28:23 Székelyi Szabolcs wrote:
>> >> We're using iSCSI targets directly (one target per vm), automatically
>> >> created and initialized (cloned) from images on vm deploy. Althogh
>> >> the target is based on IET behind gigabit links, it works quite
>> >> well: we haven't done performance benchmarks (yet), but the
>> >> installation time of virtual machines is kinda same than on real
>> >> hardware.
>> >
>> > That sounds interesting and very similar to what we hope to achieve
>> > using OpenNebula and a central storage server (as I've posted a few
>> > hours ago, not realising this thread here is very similar in nature).
>> >
>> >> We developed a custom TM driver for this, because this approach makes
>> >> live migration trickier, since just before live migration the target
>> >> host needs to log in to the iSCSI target hosting the disks of the
>> >> vm, and this is something ONE can't do, so we used libvirt hooks to
>> >> do this -- works like a charm. Libvirt hooks are also good for
>> >> reattaching virtual machines to their virtual networks on live
>> >> migration -- again something ONE doesn't do.
>> >
>> > Would you care to go into a little detail regarding your custom TM
>> > driver? Maybe even post the sources? I'd be very interested in learning
>> > more about your approach to this.
>> >
>> > Thanks!
>> >
>> > Andreas
>> > --
>> > Andreas Ntaflos
>> >
>> > GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC  7E65 397C E2A8 090C A9B4
>> >
>> > _______________________________________________
>> > Users mailing list
>> > Users at lists.opennebula.org
>> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>



-- 
Ignacio M. Llorente, Full Professor (Catedratico):
http://dsa-research.org/llorente
DSA Research Group:  web http://dsa-research.org and blog
http://blog.dsa-research.org
OpenNebula Open Source Toolkit for Cloud Computing: http://www.OpenNebula.org