Bug #40111
closedRGW-Swift does not support capabilities API call
0%
Description
Per swift API, the URL /info should return capabilities of the swift API but RGW does not seem to support it on this URL:
- curl http://xxxx:8080/info
<Error><Code>NoSuchBucket</Code><BucketName>info</BucketName><RequestId>tx00000000000000000a2e0-005cf529ea-1e4ad3-default</RequestId><HostId>1e4ad3-default-default</HostId></Error>
once I add the swift prefix if does report basic statistics
- curl http://xxxx:8080/swift/info {"bulk_delete":{},"container_quotas":{},"swift":{"max_file_size":5368709120,"container_listing_limit":10000,"version":"13.2.5","policies":[{"default":true,"name":"default-placement"}],"max_object_name_size":1024,"strict_cors_mode":true,"max_container_name_length":255},"tempurl":{"methods":["GET","HEAD","PUT","POST","DELETE"]},"slo":{"max_manifest_segments":1000},"account_quotas":{},"staticweb":{},"
Is it possible to support this API call ?
Updated by Matt Benjamin almost 5 years ago
Hi Bjoern,
If what you're asking for is for Swift sub-urls to appear at the root, then you can enable that by setting
rgw swift url prefix = /
in your config.
Matt
Updated by Bjoern Teipel almost 5 years ago
Thanks for the info, but wouldn't affect that also the /swift/v1 api calls ?
Updated by Matt Benjamin almost 5 years ago
It is part of the formula we use when we run tempest tests (there are other options controlling Swift auth urls, I don't know if overriding swift at root is actually relevant, though you can do it). I will ask someone to put the set of interesting options we use for tempest testing in this issue.
Matt
Updated by Matt Benjamin almost 5 years ago
- Status changed from New to In Progress
Updated by Shilpa MJ almost 5 years ago
Matt Benjamin wrote:
(shilpa, is this a doc bug?)
We do have this documented here:
http://docs.ceph.com/docs/nautilus/radosgw/config-ref/#swift-settings
Updated by Abhishek Lekshmanan almost 5 years ago
- Status changed from In Progress to Need More Info
Updated by Abhishek Lekshmanan almost 5 years ago
- Status changed from Need More Info to Resolved
Updated by Bjoern Teipel almost 5 years ago
I think the underlying question was not to run swift on / and disable S3 api more if the /info URL could be supported to allow the swift capabilities call. But I understand if that would create an conflict with other APIs