cde11611d9
This change also introduces two network interfaces: * flat: Copies current neutron DHCP provider logic to work with cleaning ports; * noop: noop interface. The default value of the network_interface is None, meaning that the node will be using the default network interface. The default network interface is determined the following way: * if [DEFAULT]default_network_interface configuration option is set (the default for it is None), the specified interface becomes the default for all nodes; * if it is not set, 'flat' interface will be used if the deployment currently uses 'neutron' DHCP provider, otherwise 'noop' interface will be used. create_cleaning_ports and delete_cleaning_ports methods of the DHCP providers are still being called in case of out-of-tree DHCP providers, but this possibility will be removed completely in the next release. If the DHCP provider logic is rewritten into a custom network interface, please remove those methods from the provider, so that network interface is called instead. 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: I0c26582b6b6e9d32650ff3e2b9a3269c3c2d5454
30 lines
1.6 KiB
YAML
30 lines
1.6 KiB
YAML
---
|
|
features:
|
|
- |
|
|
Added network interface. Introduced two network interface implementations:
|
|
``flat``, which replicates the flat network behavior present previously and
|
|
``noop`` when neutron is not used, which is basically a noop interface.
|
|
The network interface is used to switch network for node during
|
|
provisioning/cleaning. Added ``enabled_network_interfaces`` option in
|
|
DEFAULT config section. This option defines a list of enabled network
|
|
interfaces on the conductor.
|
|
deprecations:
|
|
- |
|
|
``create_cleaning_ports`` and ``delete_cleaning_ports`` methods in DHCP
|
|
providers are deprecated and will be removed completely in the Ocata
|
|
release. The logic they are implementing should be moved to a custom
|
|
network interface's ``add_cleaning_network`` and
|
|
``remove_cleaning_network`` methods respectively. After that, the methods
|
|
themselves should be removed from DHCP provider so that network interface
|
|
is used instead. ``flat`` network interface does not require
|
|
``[neutron]cleaning_network_uuid`` for now so as not to break standalone
|
|
deployments, but it will be required in the Ocata release.
|
|
upgrade:
|
|
- |
|
|
``[DEFAULT]default_network_interface`` configuration option is introduced,
|
|
with empty default value. If set, the specified interface will be used as
|
|
the network interface for nodes that don't have ``network_interface`` field
|
|
set. If it is not set, the network interface is determined by looking at
|
|
the ``[dhcp]dhcp_provider`` value. If it is ``neutron`` - ``flat`` network
|
|
interface is the default, ``noop`` otherwise.
|