27fc3d0bc1
Clarifies the code in add_ports_to_network() so that it is clear that the ironic ports that are created in neutron are not necessarily all pxe-enabled. Adds more comments to describe the behaviour if non-pxe-enabled ports are created in neutron. Fixes a typo in the corresponding release note. This is a follow up to I8d0f4e28efb05af704839f3b92cb3dfd48d57940. Change-Id: I94ff18bc137401ff4cd316755408c2099bb563cb Story: 2005494
20 lines
946 B
YAML
20 lines
946 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Provides an opt-in fix to change the default port attachment behavior
|
|
for deployment and cleaning operations through a new configuration option,
|
|
``[neutron]add_all_ports``. This option causes ironic to transmit all
|
|
port information to neutron as opposed to only a single physical network
|
|
port. This enables operators to successfully operate static Port Group
|
|
configurations with Neutron ML2 drivers, where previously configuration
|
|
of networking would fail.
|
|
|
|
When these ports are configured with ``pxe_enabled`` set to ``False``,
|
|
neutron will be requested not to assign an IP address to the port. This
|
|
is to prevent additional issues that may occur depending on physical
|
|
switch configuration with static Port Group configurations.
|
|
- |
|
|
Fixes an issue during provisioning network attachment where
|
|
neutron ports were being created with the same data structure
|
|
being re-used.
|