Re: [ceph-users] radowsg keystone integration in mitaka

2016-10-17 Thread Andrew Woodward
Some config hints here, if you convert your config, you have to unset the admin_token and change the api version to 3, then you can specify the keystone user, password, domain, tenant, etc. You can see what we do for puppet-ceph [1] if you need a refrence [1] https://github.com/openstack/puppet-ce

Re: [ceph-users] radowsg keystone integration in mitaka

2016-10-15 Thread Logan V.
The ability to use Keystone v3 and authtokens in lieu of admin token was added in jewel. The release notes state it but unfortunately the Jewel docs don't reflect it, so you'll need to visit http://docs.ceph.com/ docs/master/radosgw/keystone/ to find the configuration information. When I tested th

[ceph-users] radowsg keystone integration in mitaka

2016-10-14 Thread Jonathan Proulx
Hi All, Recently upgraded from Kilo->Mitaka on my OpenStack deploy and now radowsgw nodes (jewel) are unable to validate keystone tokens. Initially I though it was because radowsgw relies on admin_token (which is a a bad idea, but ...) and that's now deperecated. I verified the token was still