Comment 10 for bug 1219795

So you're saying that after I create the network, I must create/delete a port in order to "trigger" initial network creation. Once this is done, then a call to create a subnet will create the dhcp port if needed. Otherwise, the dhcp port will not be created until the first port is created.

As for the referenced commit, I think I would have rather seen a "defer" option that could be set when creating a network if desired.

As for this patch, which will allocate an existing unattached port, the problem I have is that it may use the port you're creating. I'd rather see it create the dhcp port, then create the port requested, so it's not considered when looking for unused ports. I realize the dhcp allocation is async, which makes this difficult. If you create the requested port first, is there a way to exclude it from the dhcp port selection? Problem is, if you create 2 ports, even the second may get created before the dhcp port is allocated.

Also, as I mentioned above, when the dhcp port is setup on the create port call, it's setting the device_id on the port, but not the device_owner. This works if the dhcp port is setup on the create subnet call.