Marco,
The replication *inside* Swift is not intended to move data between two
different Swift instances -- it's an internal data repair and rebalance
mechanism.
However, there is a different mechanism, called container-to-container
synchronization that might be what you are looking for. It
Thanks Donagh,
I will take a look to the ontainer-to-container synchronization to understand
if it fits with my scenario.
Cheers,
Marco
On Thu, Mar 13, 2014 at 03:28:03PM +, McCabe, Donagh wrote:
Marco,
The replication *inside* Swift is not intended to move data between two
different
You may be interested by this project as well :
https://github.com/stackforge/swiftsync
you would need to replicate your keystone in both way via mysql replication
or something like this (and have endpoint url changed as well obviously
there).
Chmouel
On Thu, Mar 13, 2014 at 5:25 PM, Marco
Hi Chmouel,
using this approach should I need to have the same users in both keystone?
Is there any way to map user A from cloud X to user B in cloud Y?
Our clouds have different users and replicates the keystone could have
some problems, not only technical.
Cheers,
Marco
On Thu, Mar 13, 2014
