Hi Tom,
I'm taking the easy way out for the near term. I've reconfigured Swift to use
the tempauth middleware, and am replicating the user ids and tenant ids that I
have in Keystone. This allows everyone on my project team to have a uniform
runtime configuration setup. In the meantime, I'm s
Doesn't the s3token patch by Yoshiyama san fix this for Diablo/Keystone
... http://www.debian.or.jp/~yosshy/openstack-diablo/s3token.txt ?
Regards,
Tom
On 03/28/2012 08:36 AM, Chmouel Boudjnah wrote:
Hi,
On Tue, Mar 27, 2012 at 10:32 PM, Lillie Ross-CDSR11
mailto:ross.lil...@motorolasolution
Hi,
On Tue, Mar 27, 2012 at 10:32 PM, Lillie Ross-CDSR11 <
ross.lil...@motorolasolutions.com> wrote:
> Then, if I want to use S3 binding with Swift (Diablo), I need to used the
> simpler 'swauth' middleware for authenticatoin? Just wondering.
>
Yes this is correct.
Cheers,
Chmouel.
___
Hi Chmouel,
Then, if I want to use S3 binding with Swift (Diablo), I need to used the
simpler 'swauth' middleware for authenticatoin? Just wondering.
Thanks again,
Ross
--
Ross Lillie
ross.lil...@motorolasolutions.com
On Mar 27, 2012, at 4:19 PM, Chmouel Boudjnah wrote:
> Hi Ross,
>
> O
Hi Ross,
On Tue, Mar 27, 2012 at 9:14 PM, Lillie Ross-CDSR11
wrote:
> I'm trying to get the S3 api working with Swift using Keystone
> authentication. My setup is based on the patched Diablo release using the
This wouldn't work on Diablo, you would need keystone from essex to
get this working
5 matches
Mail list logo
