Comment 0 for bug 1588481

The current Fuel documentation contains very strange recommendation according network architecture:
https://docs.mirantis.com/openstack/fuel/fuel-8.0/mos-planning-guide.html#plan-the-network

First of all I would change our recommendation regarding Management network and recommend to use separate NIC or unite with Admin network, since any other traffic might seriously impact management traffic which can lead to instability of cloud (RabbitMQ, Pacemaker, MySQL clustering and etc)

So, our recommendation should look like:
- Admin
  * Should be untagged
  * >= 1G
  * Might be united with other networks
  * Ensure no DHCP services are interfering on this segment
- Management
  * Must be separated (except Admin, might be united with Admin)
  * >= 10G
  * Bonding is recommended
- Private
  * Depends on purpose of the cloud
  * If it is not critical might be united with Private net
  * >= 10G (Depends on cluster size, 1G - for small and test clouds)
  * Bonding is recommended
  * Separate NIC is recommended
- Public
  * Depends on purpose of the cloud
  * If it is not critical might be united with Private net
  * >= 10G (Depends on cluster size, 1G - for small and internal clouds)
  * Bonding is recommended
  * Separate NIC is recommended
- Storage
  * Should be separate
  * >= 10G
  * Bonding is strongly recommended
  * CEPH should have one more separate NIC for replication

If current configuration is not satisfied to our recommendations to generate a warning with risks description and confirmation whether the user is ready to take these risks.