c62e1bee29
This patch exposes the node's network_interface field in the REST API. It also adds restrictions on the node states in which network interface change is possible and whether the requested network interface is enabled. As a temporary solution until the driver composition work is completed, we have taken an approach that requires all API and Conductor nodes to have the same setting for enabled_network_interfaces. There are inline notes in the code indicating where we will address this in the future. Partial-bug: #1526403 Co-Authored-By: Om Kumar <om.kumar@hp.com> Co-Authored-By: Vasyl Saienko <vsaienko@mirantis.com> Co-Authored-By: Sivaramakrishna Garimella <sivaramakrishna.garimella@hp.com> Co-Authored-By: Vladyslav Drok <vdrok@mirantis.com> Co-Authored-By: Zhenguo Niu <Niu.ZGlinux@gmail.com> Change-Id: I67495196c3334f51ed034f4ca6e32a3e01a58f15
8 lines
322 B
YAML
8 lines
322 B
YAML
---
|
|
features:
|
|
- Bumped API version to 1.20. It adds API methods to work with
|
|
``network_interface`` node object field, that specifies the network
|
|
interface to use for that node. Its value must be identical and
|
|
present in the ``[DEFAULT]enabled_network_interfaces`` list option
|
|
on conductor and api nodes.
|