Re: [ovirt-users] separate ovirtmgmt from glusterfs traffic

Hi Tibor, On 13/11/14 13:41, Demeter Tibor wrote: This generally sounds like a good plan, but note that QoS on the host-level will only become available in oVirt 3.6 (it might become available soon on master, if you're feeling lucky...). VM-level QoS (available since 3.3) won't help you with "administrative" traffic (i.e. traffic that isn't going into / coming out of the VMs themselves). If the switch allows this VLAN to reach all hosts, there shouldn't be a problem; since oVirt 3.4 the VLAN tagging should "propagate" to all active hosts. However, see my comment below concerning "VM network". I'm not knowledgeable about gluster specifics, but let's see if I can help. What's the current situation with the gluster network, is it already VLAN-tagged? If it is and you're not moving it to another interface on the hosts, I *think* things should be fine. This means that a bridge is created for this network on hosts. If VMs don't use this network (i.e. virtual interfaces are assigned profiles of ovirtmgmt), you can make it non-VM (with no VLAN tagging) and have it assigned to the same host interface as VLAN-tagged networks (I would say this is less risky than VLAN-tagging ovirtmgmt).