Something wrong with my certificates and Keystone, cause changing to
self-signed certificates everything is working.
On Tue, Feb 10, 2015 at 8:52 PM, Gui Maluf wrote:
> http://paste.openstack.org/show/171017/
>
> On Tue, Feb 10, 2015 at 8:33 PM, Kris G. Lindgren
> wrote:
>
&
http://paste.openstack.org/show/171017/
On Tue, Feb 10, 2015 at 8:33 PM, Kris G. Lindgren
wrote:
> Can you post your haproxy config file?
>
>
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy, LLC.
>
>
> From:
hey guy,
my production environment is down for two days and I can't fixit.
I had 3 keystone+swiftproxy nodes, balanced with DNS-RR and endpoints
pointing to DNS; keystone running on 5000/35357 and swift on 443, both with
self-signed certificate and native ssl;
Then I've changed the swiftproxy to
Exactly. This is a big issue. I'm wondering how globally distributed handle
this type of issue. How storages replicate between two countrys, like
Brazil and China, in a secure manner?
On Wed, Oct 15, 2014 at 3:06 PM, Pete Zaitcev wrote:
> On Wed, 17 Sep 2014 15:16:22 -0300
> Gui M
ote:
> Hi,
>
> The objects are replicated using rsync. You can use rsync via SSH tunnels.
>
> rsync -az /file/path user@host:/dest/path
>
> Does that answer your question?
> --
> Y
>
> On 17 September 2014 18:16, Gui Maluf wrote:
>
>> I've a glo
I've a globally distributed swift infrastructure with many nodes in
different zones across the my whole country. In order to replicate a/c/o,
data travels through Internet so replicas goes to it place.
Replicas are copied between storage nodes and swift presume all storage
nodes are running in a s
