Ceph » mgr » Dashboard

I was told that the Beast frontend supports "port=" as well as "endpoint=", so maybe the fix is simpler than I thought?

One further point. Though I am by far not an expert on RGW/Beast, my understanding is that the "endpoint" configuration line that is being parsed by this regex could potentially be quite complicated - even with multiple endpoints.

In that light, would it make sense to mention these possible complications in the documentation? I.e. instead of the unequivocal statement

"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."

it could be more careful and say something like:

"In a typical default configuration with a single RGW endpoint, this is all you have to do to get the Object Gateway management functionality working. The dashboard will try to automatically determine the host and port of the Object Gateway by parsing the relevant line in ceph.conf."

The civetweb interface has supported multiple ports and optional host or ssl for a while now.

So, for instance,
rgw_frontends = civetweb port=80+443s ssl_certificate=/etc/ceph/private/keyandcert.pem

Last I checked, ceph-ansible wasn't very good about this, but it also wasn't very good about ssl either.

Nathan Cutler wrote:

One further point. Though I am by far not an expert on RGW/Beast, my understanding is that the "endpoint" configuration line that is being parsed by this regex could potentially be quite complicated - even with multiple endpoints.

In that light, would it make sense to mention these possible complications in the documentation? I.e. instead of the unequivocal statement

"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."

it could be more careful and say something like:

"In a typical default configuration with a single RGW endpoint, this is all you have to do to get the Object Gateway management functionality working. The dashboard will try to automatically determine the host and port of the Object Gateway by parsing the relevant line in ceph.conf."

Sounds good to me, except for the last part - the dashboard actually obtains this information from the service map, not ceph.conf. I'll update the documentation accordingly, until we have found a more generic solution for this.

Lenz Grimmer wrote:

Nathan Cutler wrote:

One further point. Though I am by far not an expert on RGW/Beast, my understanding is that the "endpoint" configuration line that is being parsed by this regex could potentially be quite complicated - even with multiple endpoints.

In that light, would it make sense to mention these possible complications in the documentation? I.e. instead of the unequivocal statement

"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."

it could be more careful and say something like:

"In a typical default configuration with a single RGW endpoint, this is all you have to do to get the Object Gateway management functionality working. The dashboard will try to automatically determine the host and port of the Object Gateway by parsing the relevant line in ceph.conf."

Sounds good to me, except for the last part - the dashboard actually obtains this information from the service map, not ceph.conf. I'll update the documentation accordingly, until we have found a more generic solution for this.

Docs pull request: https://github.com/ceph/ceph/pull/27581 - please review.

In general, when enhancing the autodetection, we should ensure that it also supports IPv6 addresses

so with beast port=<> would bind to both ipv4 and v6, endpoint binds to the ip:port combination which can be v4 or v6

with civetweb port=<> would bind to a v4 port if it is just a number. It can also be a ip:port combo in which case both v4 and v6 endpoints are supported

See https://docs.ceph.com/docs/master/radosgw/frontends/#id1 for some additional info