0ce5cdb7c8
This patch modifies current attributes matching from a single name-value->node hit to a best-match score. Also using an UUID as the attributes table primary key to allow exposing attributes in API later (bug 1525231). Change-Id: I205e31652b21b9e030b9530149e533b29c52a387 Closes-Bug: 1651719 Partial-Bug: 1525231
18 lines
584 B
YAML
18 lines
584 B
YAML
---
|
|
features:
|
|
- |
|
|
Looking up nodes during introspection or discovery now supports multiple
|
|
attributes matching. For example, two nodes can use the same ``bmc_address``
|
|
and still can be distinguished by MAC addresses.
|
|
upgrade:
|
|
- |
|
|
Uniqueness of a node ``bmc_address`` isn't enforced any more.
|
|
- |
|
|
The primary key of the ``attributes`` table is relaxed from the
|
|
``attributes.name, attributes.value`` column pair to a new column
|
|
``attributes.uuid``.
|
|
fixes:
|
|
- |
|
|
Introspection fails on nodes with the same IPMI address but different IPMI
|
|
ports.
|