Bug Fixes¶

• Fix an issue where IPE fails if the node does not havenode_name set

Upgrade Notes¶

• Python 2.7 support has been dropped. Last release ofironic-prometheus-exporter to support Python 2.7 is OpenStack Train.The minimum version of Python now supported by ironic-prometheus-exporteris Python 3.6.

Bug Fixes¶

• Fixes the bug in the redfish parser that would raiseDuplicated timeseries in CollectorRegistry: {‘metric_name’} when ametric have more that one value and different values for the labels.

• Fixes the value forinstance_uuid field when the value isNone in allparsers, we will use the same value ofnode_uuid ininstance_uuid.

New Features¶

• Adds support for handling Redfish-originated metrics alongsideIPMI ones.

• Adds a Flask Application that can accept requests under/metrics.The response to requests havetext/plain type and the content is alwaysthe aggregation of all files stored in[oslo_messaging_notifications]/location in theironic.conf.To run the application you can use any Web Server Gateway and set theapplication toironic_prometheus_exporter.app.wsgi:application.

• Adds the initial support to parse ipmi metrics based on the followingpayloads:Management,Temperature,System,Current,Version,Memory,Power,Watchdog2 andFan.The metrics are generated in a format that is valid to be consumed byPrometheus by using theprometheus client.

• Adds support to add a description for each ipmi metric.

• Adds a metric calledbaremetal_last_payload_timestamp_seconds that can beused in Prometheus to query if a baremetal node stopped sending informationfor a period of time.

• Adds support to parse the ipmi metrics based on theVoltage payload.

• Adds two newoslo_messaging_notifications drivers:

  • prometheus_exporter: the sensor data of each baremetal node istransformed into Prometheus metrics when possible and stored in a file.

  • file_exporter: stores the raw sensor data of each baremetal node ina file. It can be used to see how is the format of the data for aspecific driver before creating the parser for it.

  To use any of the driver it’s necessary to update theironic.conf withthe following configurations:

  [conductor]send_sensor_data=true[oslo_messaging_notifications]driver= <driver>transport_url=fake://location= <absolute path for directory>

  The files created by the drivers will always contain the latestinformation about the node.