No it is not working. I think it means an http proxy, not a swift
proxy. It is trying to connect to S3_HOST through the PROXY, that it
is not the case.
s3cmd for example don't need the keystone server. You just connect to
the swift proxy, the swift proxy asks the the auth server (keystone)
for aut
On 06/19/2013 10:37 PM, Schlacta, Christ wrote:
Is it possible, or even better, supported to use .7z instead of .tar
for the backup archive format? I know .7z gets incredible compression
rates and provides the archive layer functionality as well, and
includes an encryption mechanism as well.
On 06/20/2013 07:27 AM, Stratos Zolotas wrote:
It seems that something is "confusing" the authentication.
My setup has the Swift proxy and the Keystone authentication service
on different servers.
Do you tried to set S3-HOST to the keystone server?
and/or set the PROXY device-property?
man am
It seems that something is "confusing" the authentication.
My setup has the Swift proxy and the Keystone authentication service
on different servers.
Now i have this error:
$ amlabel DailySet1 DailySet1-1 slot 1
Reading label...
Error reading volume label: s3_open2 failed: This server could not
Quoting Debra S Baddorf :
The fix I just sent is much more elegant than I originally mentioned.
I'm actually using the provided (symbol or variable) to set the user
back to the proper client login (ie the non prived user) that you
specified
in your setup configuration files and/or compi
