<div dir="ltr">The question about upgrade was purely to see if it had been thought about - I agree that the code is sufficiently broken that it is certainly not necessary, and quite possibly impossible - I just wondered if I was right in that analysis.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 26 November 2014 at 06:43, John Griffith <span dir="ltr"><<a href="mailto:john.griffith8@gmail.com" target="_blank">john.griffith8@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Nov 24, 2014 at 10:53 AM, Monty Taylor <<a href="mailto:mordred@inaugust.com">mordred@inaugust.com</a>> wrote:<br>
> On 11/24/2014 10:14 AM, Drew Fisher wrote:<br>
>><br>
>><br>
>> On 11/17/14 10:27 PM, Duncan Thomas wrote:<br>
>>> Is the new driver drop-in compatible with the old one? IF not, can<br>
>>> existing systems be upgraded to the new driver via some manual steps, or<br>
>>> is it basically a completely new driver with similar functionality?<br>
><br>
> Possibly none of my business- but if the current driver is actually just<br>
> flat broken, then upgrading from it to the new solaris ZFS driver seems<br>
> unlikely to be possibly, simply because the from case is broken.<br>
<br>
</span>Most certainly is your business as much as anybody elses, and complete<br>
valid point.<br>
<br>
IMO upgrade is a complete non-issue, drivers that are no longer<br>
maintained and obviously don't work should be marked as such in Kilo<br>
and probably removed as well. Removal question etc is up to PTL and<br>
Core but my two cents is they're useless anyway for the most part.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
>> The driver in san/solaris.py focuses entirely on iSCSI. I don't think<br>
>> existing systems can be upgraded manually but I've never really tried.<br>
>> We started with a clean slate for Solaris 11 and Cinder and added local<br>
>> ZFS support for single-system and demo rigs along with a fibre channel<br>
>> and iSCSI drivers.<br>
>><br>
>> The driver is publically viewable here:<br>
>><br>
>> <a href="https://java.net/projects/solaris-userland/sources/gate/content/components/openstack/cinder/files/solaris/zfs.py" target="_blank">https://java.net/projects/solaris-userland/sources/gate/content/components/openstack/cinder/files/solaris/zfs.py</a><br>
>><br>
>> Please note that this driver is based on Havana. We know it's old and<br>
>> we're working to get it updated to Juno right now. I can try to work<br>
>> with my team to get a blueprint filed and start working on getting it<br>
>> integrated into trunk.<br>
>><br>
>> -Drew<br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Duncan Thomas</div>
</div>