Sorry I should've been a little more verbose in my previous answers.
I don't have anything implemented yet. I'm only looking at designing the
solutions. All slideware so far :-).
We develop a filesystem backed by object stores including Openstack Swift.
We'd like to work with or without Keystone.
We did load balancers in each logical region with affinity set on the
proxies per region. We use Keystone and I'm curious why you aren't but
that's not the end-all, just curious. You can control replication behavior
after storage policies are implemented (Juno or pre-Juno) but what you want
to do i
So I believe, there are largely two options:
1) DNS Magic
2) Separate endpoints for separate regions.
Thanks everyone!
On Mon, Jun 23, 2014 at 8:58 PM, Michael Gale wrote:
> One more thing, do you read:
> https://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/
>
>
>
Hello,
How are you planning to replicate data between regions? You said you
don't want container-sync.
Also Swift offers read affinity and write affinity, I believe this is setup
on the Swift proxy. The affinity settings allow the proxy servers to
restrict read and write requests to local reso
One more thing, do you read:
https://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/
On Mon, Jun 23, 2014 at 9:57 PM, Michael Gale
wrote:
> Hello,
>
>How are you planning to replicate data between regions? You said you
> don't want container-sync.
>
> Also Swift
Got it.
So what's the authentication method would you plan to have on Swift now?
Basically, you can use Geo-DNS with a single Swift endpoint CNAME record on
auth endpoint. Once the auth request be routed to nearest Swift Proxy, it
returns it's storage url for the user.
2014-06-24 11:29 GMT+08:
I don't plan to use Keystone at all.
On Mon, Jun 23, 2014 at 8:13 PM, Kuo Hugo wrote:
> Do you plan to have two keystone servers in each region or single keystone
> server for both east/west coast Swift proxy?
>
> 1. Geo-DNS + single Swift region endpoint in keystone
> 2. Geo-DNS for Keystone ser
Do you plan to have two keystone servers in each region or single keystone
server for both east/west coast Swift proxy?
1. Geo-DNS + single Swift region endpoint in keystone
2. Geo-DNS for Keystone servers and each Keystone server returns the local
Swift endpoint.
3. Let user to switch which regio
Hi,
I am trying to understand the notion of "regions" in Swift. To start
with, it's kinda confusing that the notion of "region" in Keystone is
not exactly the same as that of Swift. So I could authenticate with
Keystone, get a Swift endpoint for a region (Keystone's notion of a
region) and write/r
