On Tue, 14 May 2019 11:08:55 +0200
Valentin Bajrami <valentin.bajrami(a)target-holding.nl> wrote:
Hi Dominik and thanks for the quick reply. Purely the load balancing
for
LACP support and the low overhead. Since teamd is probably going to be
the future I wanted to have oVirt using it. Furthermore, teamd is much
more flexible to extend, add new interfaces, change priorities and you
name it.
It would be great if teamd support was added in the upcoming oVirt
releases. I've seen there is an RFE for the same question I asked here.
Thanks Valentin for your nice explanation.
Would you comment this on the RFE
Bug 1351510 - [RFE] Support using Team devices instead of bond devices
or may I copy your text there?
Thanks
On 5/13/19 9:26 PM, Dominik Holler wrote:
> On Mon, 13 May 2019 15:30:11 +0200
> Valentin Bajrami <valentin.bajrami(a)target-holding.nl> wrote:
>
>> Hello guys,
>>
>> Next week, I'm planning to deploy ovirt-node 4.3 on a few hosts. I've
>> been running bonds for the past years but I'd like to know if teaming
>> (teamd) is also supported with this version.
>>
> No, unfortunately not.
> May I ask why you want to use teaming instead of bonding?
>
>
>> My current package version(s):
>>
>> OS Version: | RHEL - 7 - 6.1810.2.el7.centos
>> OS Description: | oVirt Node 4.3.1
>> Kernel Version: | 3.10.0 - 957.5.1.el7.x86_64
>> KVM Version: | 2.12.0 - 18.el7_6.3.1
>> LIBVIRT Version: | libvirt-4.5.0-10.el7_6.4
>> VDSM Version: | vdsm-4.30.9-1.el7
>> SPICE Version: | 0.14.0 - 6.el7_6.1
>> GlusterFS Version: | glusterfs-5.3-2.el7
>> CEPH Version: | librbd1-10.2.5-4.el7
>> Open vSwitch Version: | openvswitch-2.10.1-3.el7
>> Kernel Features: | PTI: 1, IBRS: 0, RETP: 1
>> VNC Encryption: | Disabled
>>
>> Is anyone running teamd on this version ?
>>
>> Thanks in advance
>>