Bug #3778
closed
document procedure for enabling subdomain S3 api calls
Added by caleb miles over 11 years ago.
Updated over 11 years ago.
Description
The process for setting up a server that handles subdomain API requests is not documented. If possible we should add on instructions in the five-minute quick start so that the default calling method of tools like boto can be used.
- Assignee set to John Wilkins
The documentation should note that the
rgw dns name = {hostname}
option must be set in the
[client.radosgw.gateway]
section of the ceph.conf file, alternatively this option may be set under the [global] setting. We should also perhaps suggest the installation of dnsmasq on clients interacting with the gateway that wish to use the
{bucketname}.{hostname}
location which can be accomplished by setting
address=/{hostname}/{host-ip-address}
listen-address={client-loopback-ip}
along with adding {client-loopback-ip} as the first dns nameserver on client machines
- Status changed from New to 12
- Status changed from 12 to In Progress
- Status changed from In Progress to Resolved
Added info for subdomain call.
Also available in: Atom
PDF