Description of problem:
When creating a new gluster volume the default interface used for gluster traffic is the ovirtmgmt though threre are other interfaces available. This causes network saturation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create a new gluster volume in a glusterfs domain
2.you can choose only the ovirtmgmt ip from the drop down menu when adding bricks
Only ovirtmgmt interface is used for gluster traffic creating a bottleneck and render hosts unreachable during heavy disk workloads (like importing a vm)
Been able to choose among all interfaces of the hosts.
One more thing is that this is causing the cluster to be unusable as it keeps bringing hosts down in engine when I try to import a vm (it uses a lot of bandwith). There's a way to change this after the volume is created by using gluster commands, but I think it should be done straight at creation time within webadmin and else, have the posibility of changing it after the volume is active (someone could get new interfaces after having the volume in production).
*** Bug 1177778 has been marked as a duplicate of this bug. ***
Should this be on MODIFIED?
Tested with 184.108.40.206-1.el7.centos + gluster 3.7.5
Following are the observations,
1. I could create a separate logical network for gluster
2. I could assign a role gluster for that network
3. Volume created use this network
Based on the above marking this bug as verified