Jeremy, thank you and congratulations on completing the new openstack-swift provider and I look forward to jclouds promoting it as the preferred Swift interface in 1.8. We duplicate effort by continuing to fix bugs and add features on the legacy provider and I hope we can cease, or at least significantly reduce, these activities in 1.8.
On Fri, Jul 04, 2014 at 01:18:52AM +0000, Jeremy Daggett wrote: > - Remove legacy Swift APIs/providers Removing support for the legacy provider in 2.0 might prove too aggressive. Some private object stores provide support for older versions of the Swift API, e.g., Essex, or have unusual authentication mechanisms. Can we defer discussion of removal until the 2.0 development cycle, when we have more feedback from users against a variety of providers? In particular, Shri Javadekar might give good feedback on compatibility 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! I would like to participate in this and can help with some of the work, especially with the portable API. We need some kind of asynchronous support even without AsyncBlobStore and newer providers like Glacier raise interesting questions. When deasyncing, we should ensure that jclouds does not regress in performance on some critical operations like clearContainer and try to address some other issues like cancellation. -- Andrew Gaul http://gaul.org/
