Open Stack

Thomas, any reason you had issues using XenServer? I don't understand your commend about HA networking? The XenAPI driver supports OpenStack's HA networking. I would like to understand what we more you would need to start using XenServer with OpenStack.

The Dell connector should work with OpenSource version of XenServer, called XCP. Although the free edition of XenServer should do all you need.

You can use the Dell storage as part of the XenServer storage manager integration in nova-volume.  Renuka is adding the support into Cinder soon, which is more likely to meet your needs, so she should be able to help you. It might be good to have a real user work with her to get the feature working how you want it.

I hope that helps,
John

From: Rob_Hirschfeld at Dell.com [mailto:Rob_Hirschfeld at Dell.com]
Sent: Sunday, July 29, 2012 5:13 AM
To: openstack-operators at lists.openstack.org
Subject: Re: [Openstack-operators] Using a SAN for nova-volume & KVM

Lorin,

Thanks for forwarding.  I am the right contact for this.

Yes - there is something we can do to help with this.  I can't do it on the list at this time so I'm contacting Jon & Thomas directly to continue the conversation.

If other people are interested in this capability, please let me know.

Rob Hirschfeld
Rob_Hirschfeld at Dell.com<mailto:Rob_Hirschfeld at Dell.com>
@zehicle

From: Lorin Hochstein [mailto:lorin at nimbisservices.com]<mailto:[mailto:lorin at nimbisservices.com]>
Sent: Saturday, July 28, 2012 10:18 PM
To: Jonathan Proulx
Cc: Thomas Vachon; OpenStack Operators; Hirschfeld, Rob; Stephen Spector
Subject: Re: [Openstack-operators] Using a SAN for nova-volume & KVM

Jon:

There are several people from Dell that are active in the OpenStack community, they're probably good points of contact to engage with Dell on this issue. Two names I know of offhand are:

- Stephen Spector
- Rob Hirschfeld

Take care,

Lorin
--
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com<https://www.nimbisservices.com/>


On Jul 28, 2012, at 9:44 PM, Jonathan Proulx <jon at jonproulx.com<mailto:jon at jonproulx.com>> wrote:

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<mailto: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<mailto: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<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20120730/b20dc02f/attachment.html>