cinder and ceilometer metrics architecture question

[James Page]

Hi Drew

On Wed, 8 Mar 2017 at 16:03 Drew Freiberger <drew.freiberger at canonical.com>
wrote:
[...]

> 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 here
> regarding 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?


The ceilometer charm should be running the ceilometer-agent-notifications
service, consuming notification messages from services via the RabbitMQ
message bus.

No additional charm should be required, the existing charms should be doing
the right things already.

Cheers

James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20170308/7a25e578/attachment.html>