[pve-devel] ZFS storage

Pablo Ruiz pablo.ruiz at gmail.com
Sat Aug 2 16:44:22 CEST 2014


Implementing a simple provider which would simple call an script was my
initial attempt at.. and I even sent to the list a first initial set of
patches, which then as requested by list members I evolved into the more
radical approach you've seen now. :?

I'll try to refactor the code back into an specific LunCmd implementation
which simply invokes an script and send the results to the list.

Regards
Pablo



On Sat, Aug 2, 2014 at 8:59 AM, Dietmar Maurer <dietmar at proxmox.com> wrote:

> an easy one. I was refering to a few patches I sent regarding
> > decoupling PVE/Storage/LunCmd/* into external scripts, so supporting new
> kinds
> > of ZFS backend was a bit more easy to develop/maintain independently of
> > promox's source and release schedule.
>
>
> -    iscsiprovider => {
> -        description => "iscsi provider",
> -        type => 'string',
> -    },
> +        devbase => {
> +            description => "ZFS device's base path at remote host (ie.
> /dev)",
> +            type => 'string',
> +        },
> +        lunhelper => {
> +            description => "Helper command used by ZFS plugin handle lun
> creation/deletion/etc.",
> +            type => 'string',
> +        },
> +        remotehelper => {
> +            description => "Wether helper command should be invoked
> locally (at pmx host) or remotelly (at ZFS server).",
> +            type => 'boolean',
> +            optional => 1,
> +        },
>
> Thought a bit about that, but this change is incompatible with existing
> setups - it will break existing installation.
> Maybe we can add it as an additional provider:
>
> iscsiprovider: 'script'
>
> and keep the existing lun plugins?
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pve.proxmox.com/pipermail/pve-devel/attachments/20140802/003e8b49/attachment.html>


More information about the pve-devel mailing list