[Bug 1653231] Re: Cinder not configured to provide telemetry to ceilometer

[Frode Nordahl]

Sounds about right. Good input on a more simplistic way to solve it.


I have these concerns for such an approach:
a) Notifications sent by cinder-volume-usage-audit will never be consumed and might at some point create trouble on the end users rabbitmq-cluster if they do not have ceilometer running.
b) The audit gathering process might put an extra toll on the cinder nodes and become a unnecessary resource drain for end users not using ceilometer.


For a):
If ceilometer is designed in such a way that the consuming agent creates the queue and not the producer, I guess the messages will not be sent/stored unless the central ceilometer agent is present. We will probably have to check for problematic and unnecessary error logging on the cinder nodes though?


For b):
I guess we will have to evaluate and measure what amount of resources this process hogs in a sizable cluster.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Juju Charms Collection.
Matching subscriptions: charm-bugs
https://bugs.launchpad.net/bugs/1653231

Title:
  Cinder not configured to provide telemetry to ceilometer

Status in cinder package in Juju Charms Collection:
  New

Bug description:
  Metrics are currently not collected for Cinder volume when using
  Ceilometer in a deployment.

  Cinder needs a few additions to its configuration file and the
  'cinder-volume-usage-audit' program needs to be run periodically on
  cinder units.

  I would suggest that this either is added to the cinder-charm and
  activated with a relation to ceilometer or by creating a new
  subordinate charm like the ceilometer-agent subordinate used for nova-
  compute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charms/+source/cinder/+bug/1653231/+subscriptions