Here you go:
vdsClient -s 0 setupNetworks 
networks='{rhevm:{bonding:bond2,bootproto:dhcp,bridged:True}}' 
bondings='{bond2:{nics:eth1+eth2}}'

----- Original Message -----
From: "Sandro Bonazzola" <sbona...@redhat.com>
To: "VDSM Project Development" <vdsm-devel@lists.fedorahosted.org>
Sent: Thursday, August 22, 2013 9:44:06 AM
Subject: [vdsm] vdsClient networking (addNetwork with existing bond)

Hi,
I'm trying to fix https://bugzilla.redhat.com/999577 which in short is
failing to create bridge specifying a bond interface as nic using vdsClient.

The failing command line is:

'/usr/bin/vdsClient', '-s', 'localhost', 'addNetwork', 'bridge=rhevm', 'vlan=', 
'bond=',
'nics=bond2', 'force=False', 'bridged=True', 'BOOTPROTO=dhcp', 'ONBOOT=yes', 
'blockingdhcp=true'

I suppose that 'nics=bond2' and 'bond=' are wrong.
I'm searching for a man page or something like that for understanding how to 
prepare the command line without success.

http://www.ovirt.org/VdsClient is outdated and says anything about networking.

I've seen in http://www.ovirt.org/Vdsm_Network that using a bond should be 
supported but for the supported topologies
there are no command line examples.

For:

bridge1 ----------- bond --- nic1
                        \
                         -- nic2

I suppose that the command line should have 'bond=bond' 'nics=nic1,nic2' is 
this right?
If the bond already exists is it enough specifying 'bond=bond', 'nics=' ?



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel

Reply via email to