<div dir="ltr">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. :?<div>
<br></div><div>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.</div><div><br></div><div>Regards</div><div>Pablo</div><div><br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Aug 2, 2014 at 8:59 AM, Dietmar Maurer <span dir="ltr"><<a href="mailto:dietmar@proxmox.com" target="_blank">dietmar@proxmox.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">an easy one. I was refering to a few patches I sent regarding<br>
> decoupling PVE/Storage/LunCmd/* into external scripts, so supporting new kinds<br>
> of ZFS backend was a bit more easy to develop/maintain independently of<br>
> promox's source and release schedule.<br>
<br>
<br>
</div>- iscsiprovider => {<br>
- description => "iscsi provider",<br>
- type => 'string',<br>
- },<br>
+ devbase => {<br>
+ description => "ZFS device's base path at remote host (ie. /dev)",<br>
+ type => 'string',<br>
+ },<br>
+ lunhelper => {<br>
+ description => "Helper command used by ZFS plugin handle lun creation/deletion/etc.",<br>
+ type => 'string',<br>
+ },<br>
+ remotehelper => {<br>
+ description => "Wether helper command should be invoked locally (at pmx host) or remotelly (at ZFS server).",<br>
+ type => 'boolean',<br>
+ optional => 1,<br>
+ },<br>
<br>
Thought a bit about that, but this change is incompatible with existing setups - it will break existing installation.<br>
Maybe we can add it as an additional provider:<br>
<br>
iscsiprovider: 'script'<br>
<br>
and keep the existing lun plugins?<br>
<br>
<br>
</blockquote></div><br></div>