Is anyone else using keystone authentication with radosgw? Anyone having any luck getting the authtoken caching working?
- Darren On 8 October 2013 10:17, Darren Birkett <[email protected]> wrote: > Hi All, > > What's the best way to try and track down why this isn't working for us? > It doesn't seem that there are any other options I can provide. Lack of > (working) radosgw integration with keystone would be a huge blocker for us > being able to adopt ceph as part of our product set. > > Thanks, > Darren > > > On 7 October 2013 14:28, Darren Birkett <[email protected]> wrote: > >> Hi All, >> >> In our prior tests with 0.67.3, keystone authtoken caching was broken >> causing dreadful performance - see >> http://www.spinics.net/lists/ceph-users/msg04531.html >> >> We upgraded to release 0.67.4 as we wanted to test the apparent fix to >> authtoken caching that was included in the release notes. Unfortunately, >> we still seem to be seeing the same issues - keystone is hit for every >> single operation, causing a huge bottleneck in performance. >> >> Aside from upgrading packages and restarting all daemons, are there some >> options we are missing from the below to get things to work properly: >> >> :/etc/ceph/ceph.conf >> [client.radosgw.gateway] >> .... >> rgw_keystone_url = http://x.x.x.x:35357 >> rgw_keystone_admin_token = xxxxxxxxxxxxxxxxxxx >> rgw_keystone_accepted_roles = admin, Member >> rgw_keystone_token_cache_size = 10000 >> .... >> >> >> Thanks >> Darren >> > >
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
