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