Project

General

Profile

Bug #3778

document procedure for enabling subdomain S3 api calls

Added by caleb miles about 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
No
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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.

Associated revisions

Revision 8bd306b9 (diff)
Added by John Wilkins about 11 years ago

doc: Added Subdomain section.

fixes: #3778

Signed-off-by: John Wilkins <>

History

#1 Updated by caleb miles about 11 years ago

  • Assignee set to John Wilkins

#2 Updated by caleb miles about 11 years ago

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

#3 Updated by Ian Colle about 11 years ago

Any update?

#4 Updated by Sage Weil about 11 years ago

  • Status changed from New to 12

#5 Updated by John Wilkins about 11 years ago

  • Status changed from 12 to In Progress

#6 Updated by John Wilkins about 11 years ago

  • Status changed from In Progress to Resolved

Added info for subdomain call.

Also available in: Atom PDF