Totally makes sense. I was mainly curious whether this was simply down to features/middleware or if there were other factors. We've recently been playing with swift-ceph-backend to try and integrate discrete Ceph based object stores seamlessly into a geo-distributed Swift cluster, so that from a user perspective they get a consistent interface and the added Swift middleware goodies. Not yet sure if it's a production-able solution though, the project seems to have gone quiet.
On 5 October 2016 at 16:57, Xav Paice <[email protected]> wrote: > On Wed, 2016-10-05 at 15:42 +1100, Blair Bethwaite wrote: >> Nice! But I'm curious, why the need to migrate? > > Hmm. I want to be diplomatic since both are great for their thing. > > For us, the main reason was simply that we wanted replication of the > object storage between regions (we started the process before that was a > feature in RGW), but also being a public cloud we also wanted to be able > to bill customers for their usage, and we were finding that incredibly > difficult with Rados Gateway in comparison to Swift. > > That, and we found customers were using RGW as a backup, and that's on > the same storage back end as our Cinder and Glance - moving to a > different platform makes it separate. > > There's a few other features in Swift that aren't in RGW, and we have > customers asking for them, which really matters a lot to us. > > There's pros and cons for both, I don't regret us using RGW but it just > doesn't suit our needs right now. > -- Cheers, ~Blairo _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
