Hey Whit, >From what I understand of OpenStack it depends on how you're going to configure the storage pools. If you're willing to keep the storage pool on separate dedicated hardware you could run that yourself as an unsupported config and maintain that and provide that to RSP as a storage pool and leave them responsible for the rest of the stack. We run unsupported with our team at RSP and have had good luck with it but I've also been lucky to get on good terms with my account team so they've worked to make sure I get what I'm looking for. If you're looking to have storage on the same machines that do the compute nodes they're going to be less cooperative. From what I've seen I've been able to get them to support lots of stuff that I've implemented but I've had no luck getting them to implement anything they don't support. What features are you looking at specifically from gluster for the HA environment? Have you had a chat with their openstack folks about getting that stuff from another technology? Another option is to call a rose by another name, the Red Hat Storage Server which is gluster still but packaged in Red Hat which may scare less people over there and get something moving. I'm happy to chat more about it if you like. All the best, Josh ----- Original Message ----- From: "Whit Blauvelt" <whit.gluster@xxxxxxxxxxxxx> To: "Nux!" <nux@xxxxxxxxx> Cc: gluster-users@xxxxxxxxxxx Sent: Thursday, December 5, 2013 4:03:50 PM Subject: Re: Gluster and OpenStack On Thu, Dec 05, 2013 at 08:19:04PM +0000, Nux! wrote: > I don't understand what Rackspace has to do in all this. AFAIK Cinder does > support Gluster. > http://www.gluster.org/category/glusterfs-openstack-cinder/ Rackspace Private Cloud is where they rent the dedicated hardware to the customer with OpenStack installed. Rackspace handles the OpenStack installation. Rackspace is responsible for maintaining the hardware and OpenStack. The customer is responsible for all aspects of the VMs. Since Rackspace has deep OpenStack expertise, and we don't, this makes sense. But Gluster, from Rackspace's perspective, suffers from "not invented here." So my question is whether despite all this we might wedge it into the stack - or overlay it on top - without screwing things up with all the parts with very much want Rackspace to be responsible for. Make sense? Best, Whit _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
