Comment 6 for bug 1832526

It is already possible to assign different physical networks to different compute nodes. This model might work for the edge networks as described (assuming that we expect the end user to set them up with appropriate address ranges if they're bridged to other networks, but that is the standing assumption for any provider network today). Basically, each edge would have a different physical network.

If we went that way, the problem is that, as you come to run a network, the nova boot fails with an error because of the port bind if the anticipated physnet is not present. Scheduling is supposed to be the gate to determine that the VM would run on the selected host, but scheduling today does not take account of available physical networks on a host.

This is not intended to solve inter-edge connectivity, which is out of scope and which is clearly ruled out in the implementation by having separate physnets per location (which says, in API terms, the locations are not interconnected).