IP's are not checked for address conflict

[Nickita Zaporozhets]

Both VIP's - mgmt and public may already be used. Network checker will not show any conflicts or problems. This may lead to deployment fail or issues on a deployed cloud, which will be really hard to debug in some cases - this may look like strange OCF failures or so on.

[Oleksiy Molchanov (omolchanov)]

Python team, please advise.

[Dima Shulyak (dshulyak)]

I think this is not only about VIPs, it is more generic, as a part of network verification we dont check for any intersection between already used IPs in environment and IPs that will be assigned by nailgun.

This is not a trivial change, and requires design.

1. This distributed verification needs to be added to nailgun/astute/mco/net_check subsystems of fuel
2. We are already doing some configuration for public network on bootstrap nodes to check repos, but it needs to be extended with configuration for management, and what about others?
3. After intersection will be found - it needs to be stored in nailgun, probably as IPAddr object that isnt assigned to any node or cluster.

[Alexander Kislitsky (akislitsky)]

We passed SCF in 8.0. Moving the bug to 9.0.