Whether you want to build the software, run it, grow the community or just learn more about it, there will be content, workshops and design sessions for you to attend at the OpenStack Summit, Oct 15-18 in San Diego. Stick around Friday for the first OpenStack service day, a 1/2 day beach cleanup.
This journey began when I began thinking about some pain points with Swift in general. One of the issues being that there is a view that Swift should be the point of abstraction for other storage systems to be used. This has lead to some code that I feel doesn't belong in Swift proper. Other's have taken the approach of creating a compatibility layer on top of their storage system. I don't think either of these are sustainable long term.
Since the beginning of Openstack, there has not been a clear definition of what Openstack CORE means. In this talk I would like to present a clear definition of what Openstack CORE should be, and how that applies to Swift, and possibly other projects.
I will also present one option of how Swift could be split apart into two projects. One that would be part of openstack core that would provide the APIs and required bits to be a point of abstraction for object storage in Openstack with pluggable back ends. The other would pull the actual implementation of Swift into a separate project that would include a driver for Openstack object storage.