neutron/releasenotes/notes/modify-dhcp-behavior-based-on-network-auto-schedule-1ea5e74fd5bb560c.yaml
Reedip 139b496ef9 Dont schedule Network, respecting network_auto_schedule config
Currently, if dhcp mapping from a network is removed, it is reassigned
to the network. This is because of the Network Scheduler's schedule
function, which considers balancing the networks with the agents, whether
enable_dhcp is set on its subnets or not. It does not take into account
the network_auto_schedule config option. This is particularly disturbing
when considering backends which have their provide their own DHCP.

With this patch, if network_auto_schedule is set to False, networks wont
be automatically scheduled to DHCP Agents. If DHCP is to be mapped to a
network, it can be mapped using the CLI itself.

While it may seem that this change is breaking what is already working,
but as mentioned earlier, if there are network backends which provide DHCP
support themselves, they wont need the automatic mapping, which the term
"network_auto_schedule" actually stands for.

Closes-Bug: #1647421
Change-Id: If1a6a2a174d0f737415efa2abce518722316a77b
2019-11-26 01:55:03 +00:00

15 lines
710 B
YAML

---
fixes:
- |
Neutron currently does not fully respect the network-auto-schedule
configuration option. If the network-auto-schedule option is set to
False, the network -
a) Is still scheduled on the DHCP agent when it is created
b) Is scheduled on a new DHCP agent if the old DHCP mapping is removed
by the user/admin.
It is especially necessary where the Network Backends provide DHCP
directly. This has been fixed now and if the network-auto-schedule
is set to False in the config file, networks would not be automatically
scheduled to the DHCP Agents. If mapping/scheduling is required, it can
be done manually or by setting the network-auto-schedule to True.