Gianluca Cecchi wrote:
Hello,
I remember in the past that could be a problem to have high usage of
ovirtmgmt network because engine sometimes detects hosts as
unresponsive.
And it should this the reason about bandwith limitation on vm
migration, until dedicated network for it has been released.
SO the question is : what about ovirtmgmt network for gluster
replication when gluster domain is provided by ovirt nodes?
I suppose it could be a problem too, couldn't it?
In case I have a dedicated network for gluster for the nodes, how can
i configure it?
Can I configure in this case Gluster storage domain from ovirt engine
or does it require to be on this network too?
No, it doesn't. I have a setup where the two gluster servers are using
10G and ovirtmgmt is 1G. We use split-dns but the poor mens variety.
The engine server (mgmt01) sees both gluster servers on its own network
(192.168.x.x) but the gluster servers itself have host entries for the
same hostnames in the 172.19.x.x range, same holds for the vmhosts. What
happens is that you add the storage servers by fqdn and the gluster peer
probe commands resolve to the 10G network and all storage traffic is
confined to this network. So managment commands arrive on the 192
network and the actual work is done on the storage network.
Hope that I haven't confused you beyond hope:-)
Joop