[ceph-users] Re: Attention: Documentation - mon states and names

2024-06-15 Thread Zac Dover
https://github.com/ceph/ceph/pull/58057 represents the beginning of a response to issue II (Ceph command-presentation convention standardization) in Joel's email above. I plan to add angle brackets (or something like them) in the near future. I think it might be worth putting down here in

[ceph-users] Re: Attention: Documentation - mon states and names

2024-06-11 Thread Anthony D'Atri
Custom names were never really 100% implemented, and I would not be surprised if they don't work in Reef. > On Jun 11, 2024, at 14:02, Joel Davidow wrote: > > Zac, > > Thanks for your super-fast response and action on this. Those four items > are great and the corresponding email as

[ceph-users] Re: Attention: Documentation - mon states and names

2024-06-11 Thread Joel Davidow
Zac, Thanks for your super-fast response and action on this. Those four items are great and the corresponding email as reformatted looks good. Jana's point about cluster names is a good one. The deprecation of custom cluster names, which appears to have started in octopus per

[ceph-users] Re: Attention: Documentation - mon states and names

2024-06-11 Thread Janne Johansson
> Note the difference of convention in ceph command presentation. In > https://docs.ceph.com/en/latest/rados/troubleshooting/troubleshooting-mon/#understanding-mon-status, > mon.X uses X to represent the portion of the command to be replaced by the > operator with a specific value. However, that

[ceph-users] Re: Attention: Documentation - mon states and names

2024-06-10 Thread Zac Dover
Joel, Thank you for this message. This is a model of what in a perfect world user communication with upstream documentation could be. I identify four things in your message that I can work on immediately: 1. leader/peon documentation improvement 2. Ceph command-presentation convention