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 authentication and it passes you on. I think i'm missing something here or something is not implemented right on swift support on amanda. As you can see on the previous message, the swift proxy responds with the uri of the keystone server, but amanda is not sending something right (or it is miss-configured). On Thu, Jun 20, 2013 at 2:43 PM, Jean-Louis Martineau <martin...@zmanda.com> wrote: > 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 amanda-devices > > Jean-Louis >
