fix sphinx errors with incorrect backticks
In these cases two backticks must be used instead of one. Change-Id: I4b09f296c5fa1cd2740f34efa9561522eec2d4e9 Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
This commit is contained in:
@@ -44,13 +44,13 @@ Example of configuration
|
||||
- ``Yes``
|
||||
* - sensor_data
|
||||
- interval
|
||||
- 600 (`default`)
|
||||
- 600 (``default``)
|
||||
- Seconds between conductor sending sensor data message via the
|
||||
notification bus.
|
||||
- No
|
||||
* - sensor_data
|
||||
- enable_for_undeployed_nodes
|
||||
- false (`default`)
|
||||
- false (``default``)
|
||||
- When set to true, the conductor will collect sensor
|
||||
information from all nodes when sensor data collection is
|
||||
enabled via the ``send_sensor_data`` setting.
|
||||
|
||||
@@ -35,10 +35,10 @@ on RDO, it can also be installed using `bifrost`_.
|
||||
$ pip install entry_point_inspector --user <user>
|
||||
$ epi group show oslo.messaging.notify.drivers
|
||||
|
||||
- Output in case of a successful installation: `prometheus_exporter` is listed
|
||||
in the `Name` column and the `Error` column should be empty.
|
||||
- Output in case of an unsuccessful installation: `prometheus_exporter` is
|
||||
listed in the `Name` column and the `Error` column will have more
|
||||
- Output in case of a successful installation: ``prometheus_exporter`` is
|
||||
listed in the ``Name`` column and the ``Error`` column should be empty.
|
||||
- Output in case of an unsuccessful installation: ``prometheus_exporter`` is
|
||||
listed in the ``Name`` column and the ``Error`` column will have more
|
||||
information.
|
||||
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
Limitations
|
||||
===========
|
||||
|
||||
* The only hardware types that have support for sensor data are `ipmi` and
|
||||
`redfish` (If a new hardware type adds support we need to add a parser for
|
||||
* The only hardware types that have support for sensor data are ``ipmi`` and
|
||||
``redfish`` (If a new hardware type adds support we need to add a parser for
|
||||
it).
|
||||
* We can only deal with `Gauge metrics
|
||||
<https://prometheus.io/docs/practices/instrumentation/#counter-vs-gauge-summary-vs-histogram>`_.
|
||||
|
||||
Reference in New Issue
Block a user