<div dir="ltr">There are a number of drivers that require closed-source tools to communicate with the storage.  3 others that I've come across recently:<div><ul><li>EMC VNX: requires Navisphere CLI v7.32 or higher<br></li><li>Hitachi storage volume driver: requires RAID Manager Ver 01-32-03/01 or later for VSP G1000/VSP/HUS VM, Hitachi Storage Navigator Modular 2 (HSNM2) Ver 27.50 or later for HUS 100 Family</li><li>Infortrend driver: requires raidcmd ESDS10</li></ul><div class="gmail_extra">Many appliances support REST, SSH, or something similar, but some still use proprietary protocols/tools available only as binaries to customers.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra">Avishay</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 8, 2016 at 12:37 AM, Matt Riedemann <span dir="ltr"><<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 9/7/2016 8:47 AM, John Griffith wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
On Tue, Sep 6, 2016 at 9:27 AM, Alon Marx <<a href="mailto:ALONMA@il.ibm.com" target="_blank">ALONMA@il.ibm.com</a><br>
<mailto:<a href="mailto:ALONMA@il.ibm.com" target="_blank">ALONMA@il.ibm.com</a>>> wrote:<br>
<br>
    I want to share our plans to open the IBM Storage driver source<br>
    code. Historically we started our way in cinder way back (in Essex<br>
    if I'm not mistaken)<br>
<br>
​You're mistaken, Cinder didn't exist at that time... but it's irrelevant.<br>
​<br>
<br>
<br>
    with just a small piece of code in the community while keeping most<br>
    of the driver code closed. Since then the code has grown, but we<br>
    kept with the same format. We would like now to open the driver<br>
    source code, while keeping the connectivity to the storage as closed<br>
    source.<br>
<br>
​It might help to know *which* driver you are referring to.  IBM has a<br>
number of Storwiz and GPFS drivers in Cinder... what drivers are you<br>
referring to here?​<br>
<br>
<br>
<br>
    I believe that there are other cinder drivers that have some stuff<br>
    in proprietary libraries.<br>
<br>
​Actually we've had a hard stance on this, if you have code in Cinder<br>
that requires an external lib (I personally hate this model) we<br>
typically require it to be open source.<br>
<br>
    I want to propose and formalize the principles to where we draw the<br>
    line (this has also been discussed in<br>
    <a href="https://review.openstack.org/#/c/341780/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/341780/</a><br>
    <<a href="https://review.openstack.org/#/c/341780/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/341780/</a>>) on what's acceptable by<br>
    the community.<br>
    ​<br>
<br>
<br>
<br>
    Based on previous discussion I understand that the rule of thumb is<br>
    "as long as the majority of the driver logic is in the public<br>
    driver" the community would be fine with that. Is this acceptable to<br>
    the community?<br>
<br>
​No, I don't think that's true.  It's quite possible that some people<br>
make those sorts of statements but frankly their missing the entire point.<br>
<br>
In case you weren't aware, OpenStack IS an OPEN SOURCE project, not a<br>
proprietary or hybrid project.  We are VERY clear as a community about<br>
that fact and what we call the "4 Opens" [1].  It's my opinion that if<br>
you're in then you're ALL in.​<br>
<br>
[1]: <a href="https://governance.openstack.org/reference/opens.html" rel="noreferrer" target="_blank">https://governance.openstack.o<wbr>rg/reference/opens.html</a><br>
​<br>
<br>
<br>
<br>
    Regards,<br>
    Alon<br>
<br>
<br>
        <br>
        <br>
<br>
<br>
<br>
<br>
<br>
    ______________________________<wbr>______________________________<wbr>______________<br>
    OpenStack Development Mailing List (not for usage questions)<br>
    Unsubscribe:<br>
    <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
    <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><br>
    <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
    <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-dev</a>><br>
<br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</blockquote>
<br>
I'm assuming this is the XIV driver which is a shim:<br>
<br>
<a href="https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/ibm/ibm_storage.py" rel="noreferrer" target="_blank">https://github.com/openstack/c<wbr>inder/blob/master/cinder/volum<wbr>e/drivers/ibm/ibm_storage.py</a><br>
<br>
As for the open source part of it, vcenter isn't open source but there is a vmdk driver to talk to it, I imagine this is similar.<span class="gmail-HOEnZb"><font color="#888888"><br>
<br>
-- <br>
<br>
Thanks,<br>
<br>
Matt Riedemann<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b style="font-size:12.7273px"><font color="#666666">Avishay Traeger, PhD</font></b><br></div><div><font color="#666666"><i>System Architect</i></font></div><div><span style="color:rgb(102,102,102);font-size:12.7273px"><br></span></div><div><span style="color:rgb(102,102,102)">Mobile:</span><span style="color:rgb(102,102,102)"> </span><a value="+972524317955" style="color:rgb(17,85,204)">+972 54 447 1475</a><br></div><div><font color="#666666">E-mail: <a href="mailto:avishay@stratoscale.com" style="color:rgb(17,85,204)" target="_blank">avishay@stratoscale.com</a></font></div><div><font color="#666666"><br></font></div><div><img src="http://www.stratoscale.com/wp-content/uploads/Logo-Signature-Stratoscale-230.jpg"><br></div><div><font color="#666666"><br></font></div><div><p style="margin:0in"><a href="http://www.stratoscale.com/" style="color:rgb(17,85,204)" target="_blank"><span style="font-family:arial;font-size:9.75pt">Web</span></a><span style="font-family:arial;font-size:9.75pt"> | </span><a href="http://www.stratoscale.com/blog/" style="color:rgb(17,85,204)" target="_blank"><span style="font-family:arial;font-size:9.75pt">Blog</span></a><span style="font-family:arial;font-size:9.75pt;color:rgb(108,163,214)"> | </span><a href="https://twitter.com/Stratoscale" style="color:rgb(17,85,204)" target="_blank"><span style="font-family:arial;font-size:9.75pt">Twitter</span></a><span style="font-family:arial;font-size:9.75pt;color:rgb(108,163,214)"> | <a href="https://plus.google.com/u/1/b/108421603458396133912/108421603458396133912/posts" style="color:rgb(17,85,204)" target="_blank">Google+</a> | </span><span style="font-family:arial;font-size:9.75pt"><a href="https://www.linkedin.com/company/stratoscale" style="color:rgb(17,85,204)" target="_blank">Linkedin</a></span></p></div></div></div></div></div></div></div></div></div>
</div></div></div>