Collect Bios, Memory and Processor Info from Dmidecode - follow-up

Fixes nits in the spec:
https://specs.openstack.org/openstack/ironic-inspector-specs/specs/dmidecode-reporting.html

This is a follow-up to commit 916a485782.

Change-Id: Id6dc53e7c3b166c2856520f686bcbeede1d7a730
Partial-Bug: #1635057
This commit is contained in:
Ramamani Yeleswarapu 2017-05-12 12:53:45 -07:00
parent f44e945ce6
commit 65c23ec149
1 changed files with 9 additions and 6 deletions

View File

@ -17,7 +17,7 @@ scheduling. Currently, total and physical memory size are collected.
However, more specific information about DIMMs would help deployers to However, more specific information about DIMMs would help deployers to
schedule nodes for low latency workloads. Similarly, CPU data fields such as schedule nodes for low latency workloads. Similarly, CPU data fields such as
signature and socket designation would be useful for inventory management. signature and socket designation would be useful for inventory management.
This spec proposes a collector for the **ironic-inspector** to obtain a few This spec proposes a collector for the **ironic-python-agent** to obtain a few
more key details of CPU, memory, and BIOS. more key details of CPU, memory, and BIOS.
@ -25,12 +25,12 @@ Problem description
=================== ===================
Configuring nodes for better performance is a priority from the operators Configuring nodes for better performance is a priority from the operators
point of view. The operator can specify node capabilities in a nova flavor point of view. The operator can specify node capabilities in a **nova** flavor
for a node to be selected for `scheduling`_. Collecting key CPU, memory, and for a node to be selected for `scheduling`_. Collecting key CPU, memory, and
BIOS data fields will enable operator to create flavors based on discovered BIOS data fields will enable operator to create flavors based on discovered
hardware features. hardware features.
Here is a list of the key data fields that will be of use for this purpose: Here is a list of the key data fields that might be used for this purpose:
* ``BIOS Version``: To know which firmware version is running on the host, for * ``BIOS Version``: To know which firmware version is running on the host, for
maintenance reasons. maintenance reasons.
@ -54,7 +54,7 @@ The proposed change is to implement a collector for listing the details of the
processor, memory, and BIOS in the **ironic-python-agent**'s inspector module processor, memory, and BIOS in the **ironic-python-agent**'s inspector module
using the `dmidecode utility`_ and then returning the collected data to the using the `dmidecode utility`_ and then returning the collected data to the
**ironic-inspector**. The processing done on this data in the **ironic-inspector**. The processing done on this data in the
**ironic-python-agent** is limited, to allow for the server side plugin to **ironic-python-agent** is limited, to allow for a server side plugin to
process as much or as little of the data as needed. process as much or as little of the data as needed.
.. note:: .. note::
@ -71,6 +71,9 @@ process as much or as little of the data as needed.
The format of the data collected by the new collector in The format of the data collected by the new collector in
**ironic-python-agent** looks like this:: **ironic-python-agent** looks like this::
"inventory": {
}
...
"dmi": { "dmi": {
"bios": { "bios": {
"Vendor": <vendor name>, "Vendor": <vendor name>,
@ -194,8 +197,8 @@ Deployer impact
The deployer will be able to get more data about the CPUs, DIMMs, and BIOS. The deployer will be able to get more data about the CPUs, DIMMs, and BIOS.
This information would be useful in configuring the system for better This information would be useful in configuring the system for better
performance. The deployer will provide the optional collector via performance. The deployer will enable the optional collector
the ``ipa-inspection-collectors`` kernel argument. ``dmi-decode`` via the ``ipa-inspection-collectors`` kernel argument.
Developer impact Developer impact