Hello Anthony, As a support person, I disagree with the statement that `ceph status` for instant state doesn't benefit from the version being in there. I don't remember which ceph version each customer runs. Yes, it's just a `ceph versions` command away, but having it in `ceph status` would save typing when quickly examining the customer's cluster. Regarding the "which version to report" question: all of them (from all Ceph daemons), comma-separated, collapsing any duplicates, and the client version separately, if it is different. In a typical case, there will be only one value to show. On Fri, Aug 8, 2025 at 11:40 PM Anthony D'Atri <anthony.datri@gmail.com> wrote:
Hello all !
Jumping on the bandwagon concerning ceph CLI. Yes, having version(s) info will be great.
I suspect that the common uses of `ceph status` for instant state usually don't benefit from the version being in there, which would clutter the output. Note that `ceph status -f json-pretty` *does* include this info, and indeed during an upgrade, or in e.g. an rgw hotfix situation, what single value would be reported?
Consider also: would you report the version of ceps-common that provides the `ceph` CLI command on the invoking host? Or what `ceph versions` reports, which could be different?
Also, I wish we have an option, like the `-w` but different : just
showing ceph
status (-s) continuously, with refresh.
That sounds a lot like Grafana ;)
A bit like what I use, but integrated, and perhaps better : I actually
use
`watch ceph -s` a lot.
Indeed this has been a go-to for years.
Regards, -- Gilles
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- Alexander Patrakov