Jeremy, Thanks for putting this together. This is very useful for getting a clear picture of where we are and where we need to go.
Just so that I understand this right, the points under 1.7.x is what we'll do for the next 1.7 release, correct? I don't think the legacy Swift api in apis/swift is currently deprecated. Also, wouldn't it be better if we deprecate the legacy swift api (api/swift) after we know that all current providers (including HPCloud) work well with the new openstack-swift provider? Just curious, why do we need separate providers for rackspace-cloudfiles-us/uk? Can't a user simply use openstack-swift and use the appropriate endpoint? I'm in for all meetings/discussions/hackathons/summit around BlobStore. -Shri On Thu, Jul 3, 2014 at 6:18 PM, Jeremy Daggett <jeremy.dagg...@rackspace.com> wrote: > Hi devs, > > Over the past couple of days, I have put some thought into the > openstack-swift roadmap. Our current goal is to promote the API in the 2.0 > release and address any outstanding issues/missing functionality between now > and the release. > > As most of you know, this project has been a WIP during the 1.7.x release > train, and will continue its evolution over the next several releases. > > Here is a brief look at where we are today, along with my current high-level > thinking for the road to 2.0: > > 1.7.x > - Introduction of "modern" Swift API > - Creation of Rackspace Cloud Files providers > - Deprecation of legacy Swift API (apis/swift) > - Deprecation of @Beta openstack-swift APIs > - Deprecation of legacy providers > - Address outstanding JIRA issues > > 1.8 > - Removal of @Beta openstack-swift APIs > - Ensure that all providers use the new API (hpcloud-objectstorage) > - Address any potential BlobStore changes > - Address outstanding JIRA issues > > 2.0 > - Promote openstack-swift API to main jclouds repo > - Promote openstack-swift based providers (rackspace-cloudfiles-us/uk) > - Remove legacy Swift APIs/providers > - Address any potential BlobStore changes > - No outstanding JIRA issues! > > We desperately need to solidify our plans around BlobStore, especially > AsyncBlobStore, during these releases as well. Several of us have discussed > what we think we need to do there, however we need to determine what needs to > be done and create a concrete plan. Many of us are here in the SF Bay Area, > so we could potentially get together for a BlobStore summit to hash it all > out. It would be great to get this done asap! > > In addition, there are around 17 outstanding JIRAs that need to be addressed, > many of which may only be related to the legacy code. I am going to start > tearing through them next week and ensure that we create JIRA issues for each > of the major tasks listed above. > > I would appreciate community feedback and perspectives on this information, > thanks! > > /jd >
