Re: [ceph-users] Rados Gateway and keystone

: CHEVALIER Ghislain IMT/OLPS Envoyé : lundi 13 avril 2015 16:17 À : ceph-users Objet : RE: [ceph-users] Rados Gateway and keystone Hi all, Coming back to that issue. I successfully used keystone users for the rados gateway and the swift API but I still don't understand how it can work

Re: [ceph-users] Rados Gateway and keystone

Envoyé : lundi 13 avril 2015 16:17 À : ceph-users Objet : RE: [ceph-users] Rados Gateway and keystone Hi all, Coming back to that issue. I successfully used keystone users for the rados gateway and the swift API but I still don't understand how it can work with S3 API and i.e. S3 users

Re: [ceph-users] Rados Gateway and keystone

 : RE: [ceph-users] Rados Gateway and keystone Hi all, Coming back to that issue. I successfully used keystone users for the rados gateway and the swift API but I still don't understand how it can work with S3 API and i.e. S3 users (AccessKey/SecretKey) I found a swift3 initiative but I think

Re: [ceph-users] Rados Gateway and keystone

] De la part de ghislain.cheval...@orange.com Envoyé : jeudi 16 avril 2015 13:14 À : ceph-users Objet : Re: [ceph-users] Rados Gateway and keystone Hi, I finally configure a cloudberry profile by setting what seems to be the right endpoint for object storage according to the openstack environment

Re: [ceph-users] Rados Gateway and keystone

:24 À : ceph-users Objet : RE: [ceph-users] Rados Gateway and keystone Hi, Coming back to that issue. My endpoint wasn’t right set up. I changed it to myrgw:myport (rgwow:8080) in the cloudberry profile or in the curl request and I got a 403 error due to a potential bad role returned by keystone

Re: [ceph-users] Rados Gateway and keystone

manage the keystone configuration, I will have to submit this issue to the administrator. Best regards De : CHEVALIER Ghislain IMT/OLPS Envoyé : mercredi 6 mai 2015 11:48 À : ceph-users Objet : RE: [ceph-users] Rados Gateway and keystone Addendum In the keystone log, I got 2015-05-06 11:42:24.594

Re: [ceph-users] Rados Gateway and keystone

-users Objet : Re: [ceph-users] Rados Gateway and keystone Hi, Despite the creation of ec2 credentials which provides an accesskey and a secretkey for a user, it’s always impossible to connect using S3 (Forbidden/Access denied). All is right using swift (create container, list container, get

Re: [ceph-users] Rados Gateway and keystone

15 avril 2015 13:16 À : Erik McCormick Cc : ceph-users Objet : Re: [ceph-users] Rados Gateway and keystone Thanks a lot That helps. De : Erik McCormick [mailto:emccorm...@cirrusseven.com] Envoyé : lundi 13 avril 2015 18:32 À : CHEVALIER Ghislain IMT/OLPS Cc : ceph-users Objet : Re: [ceph-users

Re: [ceph-users] Rados Gateway and keystone

Thanks a lot That helps. De : Erik McCormick [mailto:emccorm...@cirrusseven.com] Envoyé : lundi 13 avril 2015 18:32 À : CHEVALIER Ghislain IMT/OLPS Cc : ceph-users Objet : Re: [ceph-users] Rados Gateway and keystone I haven't really used the S3 stuff much, but the credentials should

Re: [ceph-users] Rados Gateway and keystone

Hi all, Coming back to that issue. I successfully used keystone users for the rados gateway and the swift API but I still don't understand how it can work with S3 API and i.e. S3 users (AccessKey/SecretKey) I found a swift3 initiative but I think It's only compliant in a pure OpenStack swift

Re: [ceph-users] Rados Gateway and keystone

I haven't really used the S3 stuff much, but the credentials should be in keystone already. If you're in horizon, you can download them under Access and Security-API Access. Using the CLI you can use the openstack client like openstack credential list | show | create | delete | set or with the