[pve-devel] New Feature: ZFS 'generic' support for LUN management.

[Pablo Ruiz]

Hi Dietmar,

What I am using is a customized redhat cluster setup with ZFS on linux,
plus some resource agent & helper scripts (available here:
https://github.com/pruiz/zfs-cluster) which allow management of NFS/iSCSI
exports, along with raking care of mounting/unmounting (export/import in
ZFS terminology) of ZFS pools, and re-sharing of all defined LUNs, etc. in
case of node failure/promotion.

Regarding the licensing, etc. there is nothing (source) closed in our
setup, but it is simply non-standard setup as all ZFS<>iSCSI-Luns
management related stuff has been designed specifically so it was easy to
be invoked remotely from proxmox nodes by hidding it all in an independent
script.

I would love other users to have other users replicate our setup, and even
improve my cluster resource scripts and all related stuff, and even the LUN
management plugin, however being something so specific, honestly, I didnt
count on it.. But once again, that would be great and that's why I shared
the code on github and was willing to make a writeup or a blog article once
this feature was merged into proxmox.

So, regarding writing an specific plugin.. Truth is, my LUN Plugin would
simply invoke remote iscsi management command vía SSH. As this is what I
modelled my setup after.. So I can send a patch for an specific LUN plugin,
however it would pretty much reassemble what if sent already, but using a
fixed helper's command name, without letting the user specify/override it.

If that would be accepted I will surely send an specific patch as
requested, but I thought that would be of less usage for others than a
dynamic one. :?

Please let me know where to move forward with this change and I will be
after it right away.

Regards
Pablo

PS: Thanks for merging the other patch. ;)


On Thu, Feb 27, 2014 at 6:29 AM, Dietmar Maurer <dietmar at proxmox.com> wrote:

> > I am going to deep into dynamic loading of lun plugins and wil be
> seinding a
> > new version of the code ASAP.
>
> I would still prefer if you simply use the current framework and simply
> send patches for your new
> ZFS LUN plugin. That way everybody can see what you are working on, and we
> can also
> help to improve the code.
>
> The introduction of dynamic plugin is against the spirit of AGPL, because
> it allows you to
> simply hide your code (instead of releasing it to the public).
>
> > However, would you consider merging the
> > second patch ([PATCH 2/2] Improve parsing of zfs volumes (ZVOLs) in order
> > to avoid) which indeed is not related to the lun plugins?
>
> applied. thanks for the patch!
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20140227/d61f998f/attachment.htm>