Bug #39252
Updated by Lenz Grimmer about 5 years ago
The documentation at http://docs.ceph.com/docs/master/mgr/dashboard/#enabling-the-object-gateway-management-frontend currently makes an unequivocal statement: statment: "This is all you have to do to get the Object Gateway management functionality working. The host and port of the Object Gateway are determined automatically." However, with the advent of Beast this is no longer the case. In the "RGW always uses civetweb" paradigm, the RGW port could be determined automatically using a regex that matches @port={}@, "port={}", like so: <pre> match = re.search(r'port=(.*:)?(\d+)(s)?', config) </pre> But nowadays, assuming the dashboard should also support Beast, that regex is broken because Beast has different semantics for specifying the RGW endpoint. For example, the relevant line in @ceph.conf@ ceph.conf might look like this: <pre> rgw frontends = "beast endpoint=[::]:80" </pre> I'm not sure what the "correct" regex should be. Should it support both Civetweb and Beast, or just one or the other? Should it support both IPv4 and IPv6? (My thanks to Ricardo Marques for helping gather the above information.)