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

[Pablo Ruiz]

This is an interesting idea, however in such a case, my main issue would be
validating new store.cfg parameters each new plugin would need/add. As json
schema validation needs to be done before store.cfg' contents are loaded
and thus we would have not loaded the plugins either.

Any ideas?


On Wed, Feb 26, 2014 at 7:35 AM, Dietmar Maurer <dietmar at proxmox.com> wrote:

> > This is just an additional plugin under LunCmd which allows developing
> lun
> > plugins without depending on proxmox's release schedle. And which canbe
> > used in cases where the plugin to be developed is going to be too
> specific to
> > be usefull for others.
> > The way I see it, ending up with a lot of specific lun plugins into
> proxmox's
> > code base would entail a lot of overhead, specially when it comes to add
> > features or improve the zfs plugin, as you have to dig into one and each
> of
> > the lun plugins behind the zfs plugin. Something not ease, as not every
> > developer have access to every kind of lun system.
> > Having a generic lun plugin like the one I am proposing allows third
> parties to
> > develop their own lun driver without imposing an extra overhead on
> > proxomox (as a company) nor on proxomox's developers/community. But it
> > also allows developing and improving such drivers independently of
> > proxmox's release schedule. (Ie. Not having to wait for the next release
> to
> > incorporate new fixes into the lun management code).
>
> I think you should improve the current plugin code to dynamically
> load/find new
> plugins. That way you will have all above advantages, without defining a
> "plugin inside a plugin" infrastructure.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20140226/413e0749/attachment.htm>