Open Stack

It does look like nova/volume/san.py could be extended to use the
EqlCliExec.py utility from the Equallogic SDK, unfortunately all the
pieces of the SDK are full of this copyright:

Copyright (C) 2009 by Dell, Inc.

All rights reserved.  This software may not be copied, disclosed,
transferred, or used except in accordance with a license granted
by Dell, Inc.  This software embodies proprietary information
and trade secrets of Dell, Inc

So unless we can talk Dell into being more sane with licensing, full
and proper integration with OpenStack is unlikely.

-Jon

On Sat, Jul 28, 2012 at 6:35 PM, Jonathan Proulx <jon at jonproulx.com> wrote:
> Hi Tom,
>
> Hopefully someone has a better answer for you as I'm still relatively
> new to OpenStack myself, but I looked into this a little while ago
> because I too have an Equalogic SAN and KVM hypervisors.  The
> Equalogic connector in that equation is provided by XenServer not
> OpenStack (in fact I think but am less sure that it isn't even part of
> the opensource xen).
>
> Since I'm running a research system I can take some risks and have
> decided to go this Ceph for my storage needs, if I were in your HA
> needing shoes I'd look at how much coding was required to hook
> Equalogic's API (which exists but I haven't looked at in years) into
> the nova-volume service, you could be someone's hero, but I don't
> think there's any current work toward this.
>
> I'd be happy to be told I'm wrong about that...
>
> -Jon
>
> On Fri, Jul 27, 2012 at 3:13 PM, Thomas Vachon <vachon at sessionm.com> wrote:
>> Hi All,
>>
>> We are architecting our system for KVM (as it is the best hypervisor for
>> your money for HA networking) and a SAN for HA nova-volumes.  The only
>> reference to being able to use a SAN is with XenServer as the hypervisor.  I
>> have no problem giving a server permission to create luns (or pre-creating
>> them if I have to) for now.  I want to make sure I can point all the stuff
>> to the SAN instead of doing some half-hearted attempt by using a box as a
>> proxy.
>>
>> Our san is an EQL so iSCSI is easy.  Also, we run our "san" net on a
>> separate 10Gbe set of interfaces (all the servers have connectivity into the
>> SAN layer).
>>
>> Any thoughts?
>>
>> --
>> Thomas Vachon
>> Principal Operations Architect
>> session M
>>
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>