Comment 14 for bug 1806390

Hi @Yang, can You give us link to Your PoC patch?

Also Your proposal from one of above comments is:

> - Do not modify current DHCP agent behaviors like notifier side API. It does not harm migration logic.
> - Do not change the DHCP HA concept and L2 agent at all.
> - Just add a distributed flag for DHCP agent. And add host filtering logic the handler side RPC (get_active_network_info, get_network_info) only when the DHCP agent is distributed.

So if I will have DHCP HA (e.g. network should be on at least 3 dhcp agents), how You will select hosts on which information about port will be stored?

> - Operators have little bit new concept of distributed DHCP which the agent is only for ports within a local hypervisor.

What about API https://developer.openstack.org/api-ref/network/v2/#dhcp-agent-scheduler ? What it will report in case of this "distributed" flag set to True?

I think that this is quite complex issue and probably some spec would be useful to discuss and address such cases there.