Re: [Openstack-operators] Rados Gateway to Swift migration
ah. ok. we were going to start looking into getting some metrics too, but hadn't yet. We're infernalis now, and going to jewel soon. Theres a huge difference between jewel and hammer. So maybe its better now... The whole single namespace for all tenants thing is supposed to be fixed in jewel too. which has bitten us on multiple occasions. Thanks, Kevin From: Xav Paice [xavpa...@gmail.com] Sent: Wednesday, October 05, 2016 12:39 PM To: Fox, Kevin M Cc: George Mihaiescu; OpenStack Operators Subject: Re: [Openstack-operators] Rados Gateway to Swift migration On Wed, 2016-10-05 at 19:29 +, Fox, Kevin M wrote: > Did you try it with jewel? If not, what version? > >From Emperor up to Hammer, haven't upgraded since then. I see that there's a number of significant changes, some of the limitations we were finding to be a problem may be gone now. > Thanks, > Kevin > > From: Xav Paice [xavpa...@gmail.com] > Sent: Wednesday, October 05, 2016 12:12 PM > To: George Mihaiescu > Cc: OpenStack Operators > Subject: Re: [Openstack-operators] Rados Gateway to Swift migration > > On Wed, 2016-10-05 at 07:19 -0400, George Mihaiescu wrote: > > Hi Xav, > > > > We are trying to get usage metrics for radosgw as well for internal cost > > recovery. Can you please share how far you got in that process and what it > > was missing? > > > > To be honest, we didn't get very far and that's one of the reasons for > using Swift instead. There were limitations with permissions that we > found very difficult to get around, without having a data collection > user added to each and every project. > > > Thank you, > > George > > > > > On Oct 5, 2016, at 1:57 AM, Xav Paice 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. > > > > > > > > > ___ > > > OpenStack-operators mailing list > > > OpenStack-operators@lists.openstack.org > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
On Wed, 2016-10-05 at 19:29 +, Fox, Kevin M wrote: > Did you try it with jewel? If not, what version? > >From Emperor up to Hammer, haven't upgraded since then. I see that there's a number of significant changes, some of the limitations we were finding to be a problem may be gone now. > Thanks, > Kevin > > From: Xav Paice [xavpa...@gmail.com] > Sent: Wednesday, October 05, 2016 12:12 PM > To: George Mihaiescu > Cc: OpenStack Operators > Subject: Re: [Openstack-operators] Rados Gateway to Swift migration > > On Wed, 2016-10-05 at 07:19 -0400, George Mihaiescu wrote: > > Hi Xav, > > > > We are trying to get usage metrics for radosgw as well for internal cost > > recovery. Can you please share how far you got in that process and what it > > was missing? > > > > To be honest, we didn't get very far and that's one of the reasons for > using Swift instead. There were limitations with permissions that we > found very difficult to get around, without having a data collection > user added to each and every project. > > > Thank you, > > George > > > > > On Oct 5, 2016, at 1:57 AM, Xav Paice 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. > > > > > > > > > ___ > > > OpenStack-operators mailing list > > > OpenStack-operators@lists.openstack.org > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
Did you try it with jewel? If not, what version? Thanks, Kevin From: Xav Paice [xavpa...@gmail.com] Sent: Wednesday, October 05, 2016 12:12 PM To: George Mihaiescu Cc: OpenStack Operators Subject: Re: [Openstack-operators] Rados Gateway to Swift migration On Wed, 2016-10-05 at 07:19 -0400, George Mihaiescu wrote: > Hi Xav, > > We are trying to get usage metrics for radosgw as well for internal cost > recovery. Can you please share how far you got in that process and what it > was missing? > To be honest, we didn't get very far and that's one of the reasons for using Swift instead. There were limitations with permissions that we found very difficult to get around, without having a data collection user added to each and every project. > Thank you, > George > > > On Oct 5, 2016, at 1:57 AM, Xav Paice 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. > > > > > > ___ > > OpenStack-operators mailing list > > OpenStack-operators@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
On Wed, 2016-10-05 at 07:19 -0400, George Mihaiescu wrote: > Hi Xav, > > We are trying to get usage metrics for radosgw as well for internal cost > recovery. Can you please share how far you got in that process and what it > was missing? > To be honest, we didn't get very far and that's one of the reasons for using Swift instead. There were limitations with permissions that we found very difficult to get around, without having a data collection user added to each and every project. > Thank you, > George > > > On Oct 5, 2016, at 1:57 AM, Xav Paice 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. > > > > > > ___ > > OpenStack-operators mailing list > > OpenStack-operators@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
Hi Xav, We are trying to get usage metrics for radosgw as well for internal cost recovery. Can you please share how far you got in that process and what it was missing? Thank you, George > On Oct 5, 2016, at 1:57 AM, Xav Paice 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. > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
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 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 OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
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. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
Nice! But I'm curious, why the need to migrate?
On 5 October 2016 at 13:29, Xav Paice wrote:
> On Wed, 2016-10-05 at 13:28 +1300, Xav Paice wrote:
>> On Tue, 2016-10-04 at 17:48 -0600, Curtis wrote:
>> > Maybe you have someone on staff who loves writing lua (for haproxy)? :)
>> >
>>
>> Well, maybe not that far, but yeah we're now thinking down that route.
>> If we get there, I'll quickly write something up about it. Many thanks
>> for the suggestion :)
>>
>
> OK, that wasn't as hard as I thought it would be. Thanks Curtis!
>
> Haproxy config snippet, in case anyone else has the same need (note, not
> in production, only rudimentary testing, and slightly sanitized for a
> mailing list):
>
> frontend objectstore
> bind :::8843 ssl crt host.crt.pem ca-file ca.pem no-sslv3
> mode http
> acl rgw_customer path_beg -m sub -f /some/list/of/rgw-folks
> use_backend rgw00 if rgw_customer
> default_backend swift-pxy00
>
> backend rgw00
> balance roundrobin
> mode http
> http-request set-path /%[path,regsub(/v1/AUTH_.{32},swift/v1)]
> server rgw1 10.0.0.111:8443 check ca-file ca.pem crt host.crt.pem ssl
> server rgw2 10.0.0.230:8443 check ca-file ca.pem crt host.crt.pem ssl
>
> backend swift-pxy00
> balance roundrobin
> mode http
> option httpchk HEAD /healthcheck HTTP/1.0
> option forwardfor
> option http-server-close
> timeout http-keep-alive 500
> server opxy1 10.0.0.123:8843 check ca-file ca.pem crt host.crt.pem ssl
>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
--
Cheers,
~Blairo
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
On Wed, 2016-10-05 at 13:28 +1300, Xav Paice wrote:
> On Tue, 2016-10-04 at 17:48 -0600, Curtis wrote:
> > Maybe you have someone on staff who loves writing lua (for haproxy)? :)
> >
>
> Well, maybe not that far, but yeah we're now thinking down that route.
> If we get there, I'll quickly write something up about it. Many thanks
> for the suggestion :)
>
OK, that wasn't as hard as I thought it would be. Thanks Curtis!
Haproxy config snippet, in case anyone else has the same need (note, not
in production, only rudimentary testing, and slightly sanitized for a
mailing list):
frontend objectstore
bind :::8843 ssl crt host.crt.pem ca-file ca.pem no-sslv3
mode http
acl rgw_customer path_beg -m sub -f /some/list/of/rgw-folks
use_backend rgw00 if rgw_customer
default_backend swift-pxy00
backend rgw00
balance roundrobin
mode http
http-request set-path /%[path,regsub(/v1/AUTH_.{32},swift/v1)]
server rgw1 10.0.0.111:8443 check ca-file ca.pem crt host.crt.pem ssl
server rgw2 10.0.0.230:8443 check ca-file ca.pem crt host.crt.pem ssl
backend swift-pxy00
balance roundrobin
mode http
option httpchk HEAD /healthcheck HTTP/1.0
option forwardfor
option http-server-close
timeout http-keep-alive 500
server opxy1 10.0.0.123:8843 check ca-file ca.pem crt host.crt.pem ssl
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
On Tue, 2016-10-04 at 17:48 -0600, Curtis wrote: > Maybe you have someone on staff who loves writing lua (for haproxy)? :) > Well, maybe not that far, but yeah we're now thinking down that route. If we get there, I'll quickly write something up about it. Many thanks for the suggestion :) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
On Tue, Oct 4, 2016 at 3:45 PM, Xav Paice wrote: > On Tue, 2016-10-04 at 07:18 -0600, Curtis wrote: >> On Mon, Oct 3, 2016 at 3:31 PM, Xav Paice wrote: >> > Hi, >> > >> > We're in the process of migrating our object storage from Rados Gateway >> > to Swift, and I was wondering if anyone has experiences with the data >> > migration steps from one to the other? >> > >> > In particular, we're currently copying each object and container one by >> > one, but the process of inspecting each and every object is incredibly >> > slow. The logic we have is kind of rsync-like, so we can repeat and >> > iterate until it's close, but the final go-live cutover will still take >> > many hours to complete. Ideas on how to get over that would be very >> > much appreciated! >> >> Could you load balance to on backend or another based on whether or >> not the account has been migrated yet? I haven't thought that through >> completely... >> > > That would be the preferable situation, migrating one customer at a > time, but we couldn't figure out how to achieve that goal without > writing some kind of middleware/proxy type of thing, or being clever > with haproxy. We may yet have to go down that route, but I'm hoping > not! Maybe you have someone on staff who loves writing lua (for haproxy)? :) > > >> Thanks, >> Curtis. >> >> > >> > Many thanks >> > >> > >> > ___ >> > OpenStack-operators mailing list >> > OpenStack-operators@lists.openstack.org >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> >> > > -- Blog: serverascode.com ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
On Tue, 2016-10-04 at 21:56 +, Fox, Kevin M wrote: > OpenStack really needs a way to have a control api for selecting a swift > "flavor", and letting you have multiple swift endpoints within, so swift the > software, radowgw, and vendor endpoints can all co'exist. > Just thinking about it, we use haproxy and the url for requests does include the project id, so we might be able to regex the requests and direct to the appropriate backend. It could make for complex support issues in the meantime, but a much smoother migration. > Kevin > > From: Xav Paice [xavpa...@gmail.com] > Sent: Tuesday, October 04, 2016 2:45 PM > To: Curtis > Cc: OpenStack Operators > Subject: Re: [Openstack-operators] Rados Gateway to Swift migration > > On Tue, 2016-10-04 at 07:18 -0600, Curtis wrote: > > On Mon, Oct 3, 2016 at 3:31 PM, Xav Paice wrote: > > > Hi, > > > > > > We're in the process of migrating our object storage from Rados Gateway > > > to Swift, and I was wondering if anyone has experiences with the data > > > migration steps from one to the other? > > > > > > In particular, we're currently copying each object and container one by > > > one, but the process of inspecting each and every object is incredibly > > > slow. The logic we have is kind of rsync-like, so we can repeat and > > > iterate until it's close, but the final go-live cutover will still take > > > many hours to complete. Ideas on how to get over that would be very > > > much appreciated! > > > > Could you load balance to on backend or another based on whether or > > not the account has been migrated yet? I haven't thought that through > > completely... > > > > That would be the preferable situation, migrating one customer at a > time, but we couldn't figure out how to achieve that goal without > writing some kind of middleware/proxy type of thing, or being clever > with haproxy. We may yet have to go down that route, but I'm hoping > not! > > > > Thanks, > > Curtis. > > > > > > > > Many thanks > > > > > > > > > ___ > > > OpenStack-operators mailing list > > > OpenStack-operators@lists.openstack.org > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > > > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
OpenStack really needs a way to have a control api for selecting a swift "flavor", and letting you have multiple swift endpoints within, so swift the software, radowgw, and vendor endpoints can all co'exist. Kevin From: Xav Paice [xavpa...@gmail.com] Sent: Tuesday, October 04, 2016 2:45 PM To: Curtis Cc: OpenStack Operators Subject: Re: [Openstack-operators] Rados Gateway to Swift migration On Tue, 2016-10-04 at 07:18 -0600, Curtis wrote: > On Mon, Oct 3, 2016 at 3:31 PM, Xav Paice wrote: > > Hi, > > > > We're in the process of migrating our object storage from Rados Gateway > > to Swift, and I was wondering if anyone has experiences with the data > > migration steps from one to the other? > > > > In particular, we're currently copying each object and container one by > > one, but the process of inspecting each and every object is incredibly > > slow. The logic we have is kind of rsync-like, so we can repeat and > > iterate until it's close, but the final go-live cutover will still take > > many hours to complete. Ideas on how to get over that would be very > > much appreciated! > > Could you load balance to on backend or another based on whether or > not the account has been migrated yet? I haven't thought that through > completely... > That would be the preferable situation, migrating one customer at a time, but we couldn't figure out how to achieve that goal without writing some kind of middleware/proxy type of thing, or being clever with haproxy. We may yet have to go down that route, but I'm hoping not! > Thanks, > Curtis. > > > > > Many thanks > > > > > > ___ > > OpenStack-operators mailing list > > OpenStack-operators@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
On Tue, 2016-10-04 at 07:18 -0600, Curtis wrote: > On Mon, Oct 3, 2016 at 3:31 PM, Xav Paice wrote: > > Hi, > > > > We're in the process of migrating our object storage from Rados Gateway > > to Swift, and I was wondering if anyone has experiences with the data > > migration steps from one to the other? > > > > In particular, we're currently copying each object and container one by > > one, but the process of inspecting each and every object is incredibly > > slow. The logic we have is kind of rsync-like, so we can repeat and > > iterate until it's close, but the final go-live cutover will still take > > many hours to complete. Ideas on how to get over that would be very > > much appreciated! > > Could you load balance to on backend or another based on whether or > not the account has been migrated yet? I haven't thought that through > completely... > That would be the preferable situation, migrating one customer at a time, but we couldn't figure out how to achieve that goal without writing some kind of middleware/proxy type of thing, or being clever with haproxy. We may yet have to go down that route, but I'm hoping not! > Thanks, > Curtis. > > > > > Many thanks > > > > > > ___ > > OpenStack-operators mailing list > > OpenStack-operators@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Rados Gateway to Swift migration
On Mon, Oct 3, 2016 at 3:31 PM, Xav Paice wrote: > Hi, > > We're in the process of migrating our object storage from Rados Gateway > to Swift, and I was wondering if anyone has experiences with the data > migration steps from one to the other? > > In particular, we're currently copying each object and container one by > one, but the process of inspecting each and every object is incredibly > slow. The logic we have is kind of rsync-like, so we can repeat and > iterate until it's close, but the final go-live cutover will still take > many hours to complete. Ideas on how to get over that would be very > much appreciated! Could you load balance to on backend or another based on whether or not the account has been migrated yet? I haven't thought that through completely... Thanks, Curtis. > > Many thanks > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Blog: serverascode.com ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Rados Gateway to Swift migration
Hi, We're in the process of migrating our object storage from Rados Gateway to Swift, and I was wondering if anyone has experiences with the data migration steps from one to the other? In particular, we're currently copying each object and container one by one, but the process of inspecting each and every object is incredibly slow. The logic we have is kind of rsync-like, so we can repeat and iterate until it's close, but the final go-live cutover will still take many hours to complete. Ideas on how to get over that would be very much appreciated! Many thanks ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
