Monday, 2025-08-25

opendevreviewTakashi Kajinami proposed openstack/ceilometer master: wip: Restore SNMPInspector  https://review.opendev.org/c/openstack/ceilometer/+/95836805:08
opendevreviewMerged openstack/ceilometer master: Get more flavor attributes from libvirt metadata (if available)  https://review.opendev.org/c/openstack/ceilometer/+/94336507:27
opendevreviewTakashi Kajinami proposed openstack/ceilometer master: wip: Restore SNMPInspector  https://review.opendev.org/c/openstack/ceilometer/+/95836808:30
opendevreviewTakashi Kajinami proposed openstack/ceilometer master: wip: Restore SNMPInspector  https://review.opendev.org/c/openstack/ceilometer/+/95836808:36
jlarribatkajinam thanks for updating the commit message in https://review.opendev.org/c/openstack/ceilometer/+/958368 to reflect the rationale of reintroducing SNMP information, but this still seems strange to me08:44
jlarribatkajinam ceilometer is not meant to provide hardware metrics anymore for the compute nodes, it just provides measurements for the VMs that are running in each node08:46
tkajinamjlarriba, yeah, though again that's what watcher expects now09:13
tkajinamto measure memory usage of hosts09:13
tkajinamceilometer provides IPMI metrics so having SNMP metrics too does not really extend its scope too much. I'm just checking the amount of work we may need to restore it09:13
tkajinama lot of things have been changed in pysnmp recently09:14
jlarribaceilometer provides ipmi metrics in a different instance, the ceilometer-compute does not provide ipmi metrics09:50
jlarribai think it extends its scope, yeah. Because why provide only memory, and not cpu information about the node? or disk09:51
jlarribai think all of that is better done outside of ceilometer, with a generic agent as none of that has anything to do with openstack09:52
tkajinamtechnically you can run a dedicated instance of polling-agent to pull snmp metrics.10:14
tkajinamIt can pull cpu metrics. the wired situation in watcher using only memory metrics based on snmp is caused by incomplete implementation in nova which exposes only cpu metrics10:15
tkajinamI think that nova feature was implemented for some tricky scheduler filter which they don't want to extend anymore so adding memory metrics to nova may not be accepted10:15
tkajinamjlarriba, are you saying that we should even drop ipmi agent ?10:16
tkajinamwhich is nothing to do with openstack really10:16
jlarribatkajinam yes, it might be subject for deprecation in the future, depending on how the power monitoring open source space evolves10:37
jlarribaif users can reliably get good power consumption via a different, generic agent, I would vouch for stop maintaining ipmi as it has nothing to do with openstack, really10:38
jlarribatkajinam watcher could rely on memory metric retrieved by a different, generic monitoring agent that provides those metrics10:39
tkajinamyeah10:50
opendevreviewMerged openstack/ceilometer master: Publish image meta from notifications and pollsters (if available)  https://review.opendev.org/c/openstack/ceilometer/+/94287911:01
opendevreviewTobias Urdin proposed openstack/ceilometer master: Handle EPIPE Broken Pipe from Libvirt RPC  https://review.opendev.org/c/openstack/ceilometer/+/95803911:36

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!