]> git.ipfire.org Git - thirdparty/libvirt.git/commit
conf: parse/format <teaming> subelement of <interface>
authorLaine Stump <laine@redhat.com>
Wed, 22 Jan 2020 21:24:10 +0000 (16:24 -0500)
committerLaine Stump <laine@redhat.com>
Wed, 29 Jan 2020 20:33:29 +0000 (15:33 -0500)
commitfb0509d06ac57434c2edbd81ee63deb32a0e598a
tree060a6486e9f8151113d832346125078d7e365309
parentcad65f222f29dffd4e91d43b230665aca813c7a6
conf: parse/format <teaming> subelement of <interface>

The subelement <teaming> of <interface> devices is used to configure a
simple teaming association between two interfaces in a domain. Example:

  <interface type='bridge'>
    <source bridge='br0'/>
    <model type='virtio'/>
    <mac address='00:11:22:33:44:55'/>
    <alias name='ua-backup0'/>
    <teaming type='persistent'/>
  </interface>
  <interface type='hostdev'>
    <source>
      <address type='pci' bus='0x02' slot='0x10' function='0x4'/>
    </source>
    <mac address='00:11:22:33:44:55'/>
    <teaming type='transient' persistent='ua-backup0'/>
  </interface>

The interface with <teaming type='persistent'/> is assumed to always
be present, while the interface with type='transient' may be be
unplugged and later re-plugged; the persistent='blah' attribute (and
in the one currently available implementation, also the matching MAC
addresses) is what associates the two devices with each other. It is
up to the hypervisor and the guest network drivers to determine what
to do with this information.

Signed-off-by: Laine Stump <laine@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
docs/schemas/domaincommon.rng
src/conf/domain_conf.c
src/conf/domain_conf.h
tests/qemuxml2argvdata/net-virtio-teaming-network.xml [new file with mode: 0644]
tests/qemuxml2argvdata/net-virtio-teaming.xml [new file with mode: 0644]
tests/qemuxml2xmloutdata/net-virtio-teaming-network.xml [new file with mode: 0644]
tests/qemuxml2xmloutdata/net-virtio-teaming.xml [new file with mode: 0644]
tests/qemuxml2xmltest.c