Open Stack

There is currently work going on (spearheaded by Red Hat) to make the parts of Swift that talk to storage volumes a little cleaner and more abstracted. This is benefiting Swift in general by allowing us to develop FS-specific interfaces (eg something optimized for XFS over a general POSIX FS) and benefiting Red Hat in particular by allowing them to easily integrate Swift and GlusterFS.

If you'd like to discuss this, I'd suggest joining IRC in #openstack-swift, and we can see how the current work works with what you are suggesting.

--John





On May 22, 2013, at 11:16 AM, "Pecoraro, Alex" <Alex.Pecoraro at emc.com> wrote:

> Hi all,
>  
> I wanted to get some feedback about the best way to implement support for Isilon storage clusters within Swift. I’ve taken the Swift code and hacked on it a bit to build a prototype that works with Isilon, but I don’t think that my changes would make sense to integrate into the main Swift codebase because they are very much hack-ish/prototype-ish changes and even if they weren’t they would be very specific to the needs of an Isilon device and as such probably wouldn’t make sense to someone not using an Isilon storage device in the Swift cluster.
>  
> I was thinking that perhaps the way that makes the most sense and would be easiest for us (Isilon) to maintain would be to add some type of plugin/extension capability to Swift so that portions of the functionality could be overridden. I was thinking that I could probably draw up a blueprint for this and do the work of implementing it. That’s just my thought, but I wanted to hear what the members of the list have to say concerning this.
>  
> BTW, the primary thing that I had to deal with in order to make Isilon work with Swift was the fact that each node in an Isilon cluster shares a single storage volume by virtue of the OneFS operating system that Isilon nodes run on. So, for example, I had to modify the Swift proxy server so that it doesn’t do things like simultaneously write to two nodes in the same Isilon cluster. Also, I had to modify the replicators so that they do not attempt to replicate between nodes in the Isilon cluster, etc, etc.
>  
> Isilon, as a company, feels that OpenStack has a bright future and we want to make sure that we can be a part of that, so I would appreciate any feedback you can give me concerning the best way to support Isilon and OpenStack integration for the long term.
>  
> Thanks for your time and consideration.
>  
> Alex Pecoraro
> Sr. Software Engineer
> EMC Isilon
>  
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev