Comment 2 for bug 1452922

But doing so could be not enough unless we do as well:
* glance images traffic, cinder volumes ISCSI traffic, ceph osd2node and so on storages related traffic shouldn't pass through the management network.
* we should move all of these types of traffic to one of the storage networks we have, or introduce more.
* ideally, Fuel should support only deployments with storage networks separated to physical interfaces. QoS is not a panacea, AFAIK, it may drop packets raising re-transmission rates, and in the cases there is no CPU power for processing IRQ, results might be very sad and lead to storage degradation.