Feature #21073
closed
mgr: ceph/rgw: show hostnames and ports in ceph -s status output
Added by Abhishek Lekshmanan over 6 years ago.
Updated about 5 years ago.
Category:
Administration/Usability
Component(RADOS):
Manager (RADOS bits)
Description
Similar to the way we do mds and mgr statuses, we could display the rgw endpoints in ceph status as well, the information is already a part of service map and hence just requires some tweaking in the ceph status output
Similar to the way we do mds and mgr statuses, we could display the rgw endpoints in ceph status as well
Hey, Abhishek, I'm not sure whether I understand your point correctly. we do not print hostname information in `ceph -s` now. as following:
./bin/ceph -s
*** DEVELOPER MODE: setting PATH, PYTHONPATH and LD_LIBRARY_PATH ***
2017-08-24 11:04:43.586848 7fc80ffbc700 -1 WARNING: all dangerous and experimental features are enabled.
2017-08-24 11:04:43.629611 7fc80ffbc700 -1 WARNING: all dangerous and experimental features are enabled.
cluster:
id: ac475608-074f-404c-9054-45059bdf978f
health: HEALTH_OK
services:
mon: 3 daemons, quorum a,b,c
mgr: x(active)
mds: cephfs_a-1/1/1 up {0=a=up:active}, 2 up:standby
osd: 5 osds: 5 up, 5 in
rgw: 1 daemon active
data:
pools: 6 pools, 48 pgs
objects: 254 objects, 5952 bytes
usage: 499 GB used, 188 GB / 688 GB avail
pgs: 48 active+clean
The line with
rgw: 1 daemon active
should look like this
rgw: 1 daemon active, a:80/443
or
rgw: 3 daemons active, a:80/443 b:80/443 c:80/443
where "a,b,c" are the hostnames of currently active RGWs
- Assignee set to Joao Eduardo Luis
- Project changed from rgw to RADOS
- Category set to Administration/Usability
- Component(RADOS) Monitor added
- Component(RADOS) Manager (RADOS bits) added
- Component(RADOS) deleted (
Monitor)
https://github.com/ceph/ceph/pull/25540
This patch will show the service's id, but not the port. For the rgw example, the interesting port to be aware of is the frontend's, and that is service-specific enough that it would only be present in the service's metadata, and somewhat free form. We would have to be aware of how the service defines its metadata, and parse that in a way that makes sense. As such, I don't think it's trivial (or maybe even feasible) to show that at this time (and maybe not ever) -- maybe the dashboard would be more appropriate of a place to expose that sort of information.
The port info is in servicemap under frontend_config, though I agree it is specific enough and probably doesnt warrant being in the short summary, it is available in the servicemap for those needing those specifics anyway
- Status changed from New to Resolved
Also available in: Atom
PDF