Hello all, I recently came across the need to add cinder's volume telemetry data into a client's ceilometer environment.
I've found that there was a patch for charm-cinder that enables the cron-tick for cinder-volume-usage-audit and implemented it in a cherry-picked fashion into my current charm (as I await timing to upgrade this charm to the released version with the patch.) Many thanks to Jorge for that config feature, and this is working properly. Referenced patch here: https://git.openstack.org/cgit/openstack/charm-cinder/commit/?id=07ae3acbb49368c58b0ad3d119ff21db39fb31c2 Unfortunately, nothing in ceilometer is picking up the oslo_message_notifications on the unit where cinder is running. I went to add the ceilometer-agent-charm to the unit, but found it's only written to pick up OS and Compute telemetry data and does not include the ceilometer-agent-notification package. I found documentation hereregarding the need to start the ceilometer-agent-notifications service: https://docs.openstack.org/developer/ceilometer/install/manual.html#installing-the-notification-agent
My ultimate question for the juju-charmers is whether a new ceilometer-notifications-agent-charm should be written, or if we can extend the ceilometer-agent charm that is specifically written for Compute nodes currently to auto-detect it's parent charm from the subordinate:container relationship and configure appropriately whether that is cinder or nova-compute or some "other" parent? Or, am I missing something else entirely that should be picking up these oslo_messaging_notifications from cinder-volume-usage-audit? Thank you for your time and guidance, -Drew
signature.asc
Description: PGP signature
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
