ce1e88991e
This adds microversion 1.46 to allow: * returning conductor_group in the node object * specifying conductor_group in the node create API * specifying conductor_group in the node update API * allow filtering nodes by conductor_group Change-Id: I32e0333c78cfcb2d88dfd4f70f0be012dcfef407 Story: 2001795 Task: 22643
18 lines
803 B
YAML
18 lines
803 B
YAML
---
|
|
features:
|
|
- |
|
|
Conductors and nodes may be arbitrarily grouped to provide a basic level
|
|
of affinity between conductors and nodes. Conductors use the
|
|
``[conductor]/conductor_group`` configuration option to set the group
|
|
which they belong to. The same value may be set on one or more nodes
|
|
in the ``conductor_group`` field (available in API version 1.46), and
|
|
these will be matched such that only conductors with a given group will
|
|
manage nodes with the same group.
|
|
|
|
A group name may be up to 255 characters containing ``a-z``, ``0-9``,
|
|
``_``, ``-``, and ``.``. The group is case-insensitive. The default group
|
|
is the empty string (``""``).
|
|
|
|
The "node list" API endpoint (``GET /v1/nodes``) may also be filtered by
|
|
conductor group in API version 1.46.
|