Open Stack

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.

On 26 November 2014 at 06:43, John Griffith <john.griffith8 at gmail.com>
wrote:

> On Mon, Nov 24, 2014 at 10:53 AM, Monty Taylor <mordred at inaugust.com>
> wrote:
> > On 11/24/2014 10:14 AM, Drew Fisher wrote:
> >>
> >>
> >> On 11/17/14 10:27 PM, Duncan Thomas wrote:
> >>> Is the new driver drop-in compatible with the old one? IF not, can
> >>> existing systems be upgraded to the new driver via some manual steps,
> or
> >>> is it basically a completely new driver with similar functionality?
> >
> > Possibly none of my business- but if the current driver is actually just
> > flat broken, then upgrading from it to the new solaris ZFS driver seems
> > unlikely to be possibly, simply because the from case is broken.
>
> Most certainly is your business as much as anybody elses, and complete
> valid point.
>
> IMO upgrade is a complete non-issue, drivers that are no longer
> maintained and obviously don't work should be marked as such in Kilo
> and probably removed as well.  Removal question etc is up to PTL and
> Core but my two cents is they're useless anyway for the most part.
>
> >
> >> The driver in san/solaris.py focuses entirely on iSCSI.  I don't think
> >> existing systems can be upgraded manually but I've never really tried.
> >> We started with a clean slate for Solaris 11 and Cinder and added local
> >> ZFS support for single-system and demo rigs along with a fibre channel
> >> and iSCSI drivers.
> >>
> >> The driver is publically viewable here:
> >>
> >>
> https://java.net/projects/solaris-userland/sources/gate/content/components/openstack/cinder/files/solaris/zfs.py
> >>
> >> Please note that this driver is based on Havana.  We know it's old and
> >> we're working to get it updated to Juno right now.  I can try to work
> >> with my team to get a blueprint filed and start working on getting it
> >> integrated into trunk.
> >>
> >> -Drew
> >>
> >> _______________________________________________
> >> OpenStack-dev mailing list
> >> OpenStack-dev at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Duncan Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141127/02ae9cce/attachment.html>