What's error message you saw when you tried? Shinobu ----- Original Message ----- From: "Abhishek L" <abhishek.lekshmanan@xxxxxxxxx> To: "Robert Duncan" <Robert.Duncan@xxxxxxxx> Cc: ceph-users@xxxxxxxx Sent: Friday, September 18, 2015 12:29:20 PM Subject: Re: radosgw and keystone version 3 domains On Fri, Sep 18, 2015 at 4:38 AM, Robert Duncan <Robert.Duncan@xxxxxxxx> wrote: > > Hi > > > > It seems that radosgw cannot find users in Keystone V3 domains, that is, > > When keystone is configured for domain specific drivers radossgw cannot find the users in the keystone users table (as they are not there) > > I have a deployment in which ceph providers object block ephemeral and user storage, however any user outside of the ‘default’ sql backed domain cannot be found by radosgw. > > Has anyone seen this issue before when using ceph in openstack? Is it possible to configure radosgw to use a keystone v3 url? I'm not sure whether keystone v3 support for radosgw is there yet, particularly for the swift api. Currently keystone v2 api is supported, and due to the change in format between v2 and v3 tokens, I'm not sure whether swift apis will work with v3 yet, though keystone v3 *might* just work on the s3 interface due to the different format used. > > > Thanks, > > Rob. > > ________________________________ > > The information contained and transmitted in this e-mail is confidential information, and is intended only for the named recipient to which it is addressed. The content of this e-mail may not have been sent with the authority of National College of Ireland. Any views or opinions presented are solely those of the author and do not necessarily represent those of National College of Ireland. If the reader of this message is not the named recipient or a person responsible for delivering it to the named recipient, you are notified that the review, dissemination, distribution, transmission, printing or copying, forwarding, or any other use of this message or any part of it, including any attachments, is strictly prohibited. If you have received this communication in error, please delete the e-mail and destroy all record of this communication. Thank you for your assistance. > > ________________________________ > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |