On 12/14/2017 03:08 PM, Blair Bethwaite wrote:
Nice idea.
Tnx!
I definitely agree that the submission mechanism needs to support HTTP
proxies. I imagine many (most?) ceph-mgr daemons are on private
networks, and not everyone has NAT.
Yes, that's something I'll implement. Should be simple to do with Python
requests.
Wido
On 14 December 2017 at 20:24, Wido den Hollander <wido@xxxxxxxx> wrote:
Hi,
After discussing with Sage I started to work [0] on a 'brag' module for Ceph
Manager.
The intention of this module is to send (after a opt-in!) statistics about a
Ceph cluster back to the project every few days.
My intention is to include:
- fsid (as identifier)
- number of MONs
- number of OSDs
- FileStore / BlueStore
- number of pools / PGs
- data used in bytes
- data free
- number of objects,
- version(s)
A admin can also say that the report is allowed to be 'public' where you can
then visit (for example) https://brag.ceph.com/public/<fsid> and show off
your Ceph cluster.
You could then add a description and we could compile top lists about Ceph
systems.
How do people think about this? Would this be interesting?
I would try to convince most of my customers to send this information back
to the project. The more information we get, the better Ceph can become.
Wido
[0]: https://github.com/wido/ceph/commits/mgr-brag
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
