Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-06-21 Thread Shyam Prasad N
I forgot to close loop on this. I managed to solve this problem with a config change in /etc/swift/proxy-server.conf: I needed to include the line: auth_version = 3 under [filter:s3token] On Fri, Jun 1, 2018 at 5:02 PM, Shyam Prasad N wrote: > Hi Kota, > > I tried with the changes you

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-06-01 Thread Shyam Prasad N
Hi Kota, I tried with the changes you suggested. It gives me the old error again... eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks -- http://s3server:8080 s3curl: Found the url: host=s3server; port=8080; uri=; query=; s3curl: s3server s3curl: s3server s3curl: ordinary endpoint

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-06-01 Thread Yuxin Wang
Hi Shyam, It’s like what Kota said about StringToSign. And I think the point is that the host isn't equal to one of the endpoints listed(https://github.com/scality/S3/blob/master/tests/functional/s3curl/s3curl.pl#L32

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-06-01 Thread Kota TSUYUZAKI
Hi Shyam, > s3curl: StringToSign='PUT\n\n\nFri, 01 Jun 2018 05:47:53 > +\n/s3server/testbucket' It looks like your StringToSign doesn't include correct info for your request.(e.g. resource should be only "/testbucket") See

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-06-01 Thread Shyam Prasad N
Hi Kota, Thanks for the response. When I specify the URL as http://s3server:8080/testbucket, it throws back a SignatureDoesNotMatch error. eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks --createBucket -- http://s3server:8080/testbucket s3curl: Found the url: host=s3server;

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-31 Thread Kota TSUYUZAKI
Hi Shyam, You should specify the path starts from bucket. It will be like http://20.20.20.229:8080/testBucket assuming you didn't configure virtual-hosted style. Even if your *Swift* endpoint is http://20.20.20.229:8080/v1/AUTH_dc86f7d8787b46158268bd77098b6578, swift3 doesn't require the

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-31 Thread Shyam Prasad N
Hi Yuxin, Thank you for sharing your configs. So I've managed to get past the Signature not matching error. Now the error is different. InvalidbucketName: eightkpc@objectstore1:~/s3curl$ ./s3curl.pl --debug --id=testerks --createBucket --

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-30 Thread Yuxin Wang
Hi Shyam,No problem. The output of the commands is attached.And my test cluster is on Swift v2.15.1 with Swift3 v1.12Also, here is the common process when I'm creating an S3 credential and using in s3curl. Hope it helps.1. Create a user and a project, and assign a proper role.openstack project

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-25 Thread Shyam Prasad N
Hi Yuxin, If you don't mind, can you share the output of the following commands in your running swift3 setup? openstack credential list openstack ec2 credentials list cat /etc/swift/proxy-server.conf Also, what are the access keys and secret keys that you use? I want to make sure that I'm not

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-25 Thread Shyam Prasad N
Tried that. Unfortunately same error. Is there anything I can do to troubleshoot this? On Fri, May 25, 2018 at 2:56 PM, Yuxin Wang wrote: > They can be any strings. > > Replace them with whatever you want. > > - Yuxin > > 在 2018年5月25日,14:57,Shyam Prasad N

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-25 Thread Shyam Prasad N
I'm using Queens on Ubuntu 18.04. On Fri, May 25, 2018 at 1:54 PM, John van Ommen wrote: > What release are you using? > > In 2016 I tried to get this working for a client of mine at HPE, and found > that it wouldn't work without a fair bit of hacking. Basically the

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-25 Thread Yuxin Wang
They can be any strings. Replace them with whatever you want. - Yuxin > 在 2018年5月25日,14:57,Shyam Prasad N 写道: > > Thanks. I'll try this. > But what values do I use in place of ak and sk? I want to use some command to > get those values, right? > > On Fri, May 25,

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-25 Thread John van Ommen
What release are you using? In 2016 I tried to get this working for a client of mine at HPE, and found that it wouldn't work without a fair bit of hacking. Basically the software hadn't been updated in about a year, and the newest release was incompatible with the version of OpenStack that we

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-25 Thread Shyam Prasad N
Thanks. I'll try this. But what values do I use in place of ak and sk? I want to use some command to get those values, right? On Fri, May 25, 2018 at 9:52 AM, Yuxin Wang wrote: > I created ec2 credentials using command `openstack credential create`. > > i.e. > >

Re: [Openstack] Struggling to get the s3 api interface to work with swift.

2018-05-24 Thread Kota TSUYUZAKI
Hi, Shyam > tester => { > id => 'test:tester', > key => 'testing', > }, If you are using this id/password to get your token from keystone, you should set them as access_key and secret key for your s3 client. You don't have to set any token information from keystone for