Support sending per driver sensors to a metering system

Registered by Jim Mankovich on 2014-10-08

The current conductor send_sensor _data interface only supports sending IPMI specific sensor metrics to ceilometer. This blueprint is for updating the conductor to support sending arbitrary hardware metrics from sources other than IPMI. Platform hardware metrics are available from per vendor sources other than IPMI and support for vendor specific metrics should be supported by the conductor. The conductor currently defines a generic hardware sensor format and calls a per management driver callout to acquire the sensors, but it currently assumes that the sensors it receives are from IPMI and that only sensors of type Temperature, Fan, Voltage, and Current are valid.

Blueprint information

Status:
Started
Approver:
aeva black
Priority:
Low
Drafter:
Jim Mankovich
Direction:
Approved
Assignee:
Jim Mankovich
Definition:
Approved
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Jim Rollenhagen on 2015-10-12

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/support-per-driver-sensor-meters,n,z

Addressed by: https://review.openstack.org/130074
    Support per driver sensor meters

NobodyCam: 03/04/15 - poked ceilometer folks via IRC and ML. starting to get eyes on the spec we are dependent upon ( https://review.openstack.org/#/c/130359 ). Ceilometer asked if code could be pushed up for their review. I would also request the same for the remaining Ironic spec's, if there is code please push up as sip until the spec land, this will help ensure the code can land in K.

Some initial feed back from Ceilometer folk:
  20:48 | gordc > NobodyCam: just an fyi, from ironic pov, i don't think there's any issue with the proposed notification format. the questions are more on how/what to consume on ceilometers end
  20:50 | NobodyCam > gordc: awesome :)
  20:51 | gordc > NobodyCam: you can create messages using pycadf (to build a standardised format with a list of proposed metrics) if ironic needs a format for payload.
  20:51 | gordc > NobodyCam: but i won't lie. it's a massively biased opinion.lol
  20:51 | NobodyCam > :)
  20:51 | gordc > http://docs.openstack.org/developer/pycadf/event_concept.html -- on the off chance you are interested.

03.05.2015: Based on conversation I am dropping this our of K3 ~BadCub~

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.