Description of problem: Since the Ceph Dashboard can display network speeds of nics in the network pane for a node then we should also display configured MTU. This will help verify all nodes are configured with same MTU size, (1500 or Jumbo frames for example). Version-Release number of selected component (if applicable): 4.0
Created attachment 1514326 [details] Dashboard Hosts Grafana
Mike, RHCS 4.0 Dashboard integrates several Cephmetrics charts, but as you may see in the attached picture, there's no similar placeholder for detailed networks stats. Another question I have, given this is mostly a static setting. Does it make sense to display it into Grafana dashboard, or can it be moved somewhere else? @Federico?
I agree with the idea of putting the MTU value in the host's info page. Targeting 4.1 for delivery.
@Mike, when reviewing this for 4.1, I think this request does not fit into the dashboard concerns. Let me explain: - The goal of this is to let the user know about a sub-optimal/wrong setting and 'call for action' on that setting. - MTU is not highly valuable data to display: it's not a changing setting, and once fixed it is unlikely to change again. Based on the above, I'd suggest to move this to ceph-medic. In fact there's an upstream RFE for this (https://github.com/ceph/ceph-medic/issues/7).
(In reply to Ernesto Puerta from comment #10) > @Mike, when reviewing this for 4.1, I think this request does not fit into > the dashboard concerns. Let me explain: > - The goal of this is to let the user know about a sub-optimal/wrong setting > and 'call for action' on that setting. > - MTU is not highly valuable data to display: it's not a changing setting, > and once fixed it is unlikely to change again. > > Based on the above, I'd suggest to move this to ceph-medic. In fact there's > an upstream RFE for this (https://github.com/ceph/ceph-medic/issues/7). So why is this on 4.1? Please handle: - Close - Move to 5.x - Fix.
@Yaniv, Federico targeted this specifically at 4.1 (https://bugzilla.redhat.com/show_bug.cgi?id=1650397#c7). That's why I asked him (and Mike & Paul) for their thoughts.
(In reply to Ernesto Puerta from comment #12) > @Yaniv, Federico targeted this specifically at 4.1 That was a year+ ago... > (https://bugzilla.redhat.com/show_bug.cgi?id=1650397#c7). That's why I asked > him (and Mike & Paul) for their thoughts. BTW, a different idea would be to launch the host's Cockpit - which has all this data + configuration for this host. Anyway, I'm moving it to 5.0. We can always bring it back.
@Yaniv @Ernesto No issues with the 5.0 plan, I think ceph-medic and even an insights rule would cover the supportability aspect I was looking to address.
Thanks @Yaniv (and @Mike for the clarification)!
I think the intention of this feature was lost with all the details. The idea is to alert the user if a specific network is configured with a custom MTU and a host is mis-configured. The idea is to alert the user. If it is already part of node exporter, so a nice chunk of the work is done. We now need some integration work - understand which NIC is under which network and what is the expected MTU.
Once completed in RHCS 5, please evaluate if we can backport it to 4.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat Ceph Storage 5.0 bug fix and enhancement), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:3294