Comment 6 for bug 1808062

@slaweq, spawning VMs in the correct Neutron AZ is important, and in the use case I wanted to use this I would be using Nova Host Aggregates to separate compute nodes by Nova AZ.

I would expect that if an operator had set up Neutron AZs, but had not set up Nova AZs to match, that the Nova scheduler would attempt to bind a port to a random hypervisor, and that would fail if the network were not available to that compute node.

In any case, I think it is acceptable to require associating a Nova AZ on a host aggregate group when dividing the deployment into multiple Neutron AZs.