Comment 15 for bug 1860743

Hi Alex,
thanks for your work.

I hit this again on Focal/Ussuri but I have one doubt:

I have a dedicated network for live migration but checking the docs, I don't see any mention of the fact that nova-cloud-controller units must have an IP on the same live migration network.

in nova-compute You can configure this in 2 ways:
1. Using a bind named "migration"
2. Using the configuration param "libvirt-migration-network"

After doing this, I see that the "clear-unit-knownhost-cache" action is trying to connect to compute nodes through the live migration network but n-c-cs don't have an IP on that network. Also, n-c-c doesn't offer any bind for this.

So, the question is:
Should we add a Bind to n-c-c? Or at least specify in the doc that when a dedicated live migration network is used on nova-compute, a constraint (space=livemigrationnet) is needed on n-c-c?

Thank you.
Regards,
Marco