Hi Sebastian,I'll tidy it up and raise a PR so we can track it better - apologies for not doing that to start with.As far as mgr/rook is concerned the events module is not interacting with rook or any of it's CR's at all which is why I started this off as a separate module.I like the idea of exposing native kubernetes events (POD started, initializing, crashloopbackoff) type stuff to the dashboard UI though.On Fri, Aug 2, 2019 at 8:34 PM Sebastian Wagner <swagner@suse.com> wrote:Nice one!
Could you make a proper PR out of it?
One thing came to my mind: This interacts with Rook's CephCluster CRD.
Would it make sense to move it into the mgr/rook module?
And secondly, would it make sense to display Kubernetes events[0] in the
Ceph Dashboard? I.e. we could show events for pods etc. Kiefer?
Sebastian
[0]: https://www.bluematador.com/blog/kubernetes-events-explained
Am 02.08.19 um 06:51 schrieb Paul Cuzner:
>
> Hi,
>
> I've been working on a mgr module to push some types of ceph system
> activity into the kubernetes events api, so kubernetes users get a more
> granular view of what's going on within the ceph cluster.
>
> The code is not complete, but if you're interested it's here -
> https://github.com/pcuzner/ceph/blob/add-events-mgr-module/src/pybind/mgr/k8sevents/module.py
>
>
> At this point it does the following;
>
> * ties into the log_monitor2 rados call to pick up audit and
> healthcheck messages
> * creates an hourly health heartbeat (health + capacity)
> * emits events for configuration changes
> o host add/remove
> o osd add/remove
> o pool add/remove
> o pool size and min_size changes
>
> Interested to hear if there are any other ceph 'events' that I should be
> considering
>
> Cheers,
>
> PC
>
> _______________________________________________
> Dev mailing list -- dev@ceph.io
> To unsubscribe send an email to dev-leave@ceph.io
>
--
SUSE Linux GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nürnberg)