libvirt/tests/interfaceschemadata/bridge-no-address.xml

<interface type='bridge' name='br0'>
  <start mode='onboot'/>
  <mtu size='1500'/>
  <bridge stp='off'>
    <interface type='ethernet' name='eth0'>
      <link speed='1000' state='up'/>
      <mac address='ab:bb:cc:dd:ee:ff'/>
    </interface>
    <interface type='ethernet' name='eth1'>
    </interface>
  </bridge>
</interface>
Add netcf XML schemas and test data * docs/schemas/interface.rng: schemas for the interface XML files directly imported from netcf-0.1.0 * tests/interfaceschemadata/*.xml: set of test files from netcf-0.1.0 changed to use single quote instead of double quote 2009-07-15 17:37:20 +00:00			`<interface type='bridge' name='br0'>`
			`<start mode='onboot'/>`
			`<mtu size='1500'/>`
			`<bridge stp='off'>`
			`<interface type='ethernet' name='eth0'>`
virInterface: Expose link state & speed Currently it is not possible to determine the speed of an interface and whether a link is actually detected from the API. Orchestrating platforms want to be able to determine when the link has failed and where multiple speeds may be available which one the interface is actually connected at. This commit introduces an extension to our interface XML (without implementation to interface driver backends): <interface type='ethernet' name='eth0'> <start mode='none'/> <mac address='aa:bb:cc:dd:ee:ff'/> <link speed='1000' state='up'/> <mtu size='1492'/> ... </interface> Where @speed is negotiated link speed in Mbits per second, and state is the current NIC state (can be one of the following: "unknown", "notpresent", "down", "lowerlayerdown","testing", "dormant", "up"). Signed-off-by: Michal Privoznik <mprivozn@redhat.com> 2014-05-07 12:21:35 +00:00			`<link speed='1000' state='up'/>`
interface: clean up virInterfaceDefDevFormat This modifies the formatting function of virInterface to be a proper mirror of the parse function, including the addition of a "parentIfType" arg so that we can decide whether or not it is appropriate to emit the elements that are only in toplevel interfaces, as well as the <link> element (which isn't allowed for bridge interfaces). Since the restructuring of the code necessarily changes the order of some of the elements, some test case data had to be updated. 2014-06-19 09:58:56 +00:00			`<mac address='ab:bb:cc:dd:ee:ff'/>`
Add netcf XML schemas and test data * docs/schemas/interface.rng: schemas for the interface XML files directly imported from netcf-0.1.0 * tests/interfaceschemadata/*.xml: set of test files from netcf-0.1.0 changed to use single quote instead of double quote 2009-07-15 17:37:20 +00:00			`</interface>`
Update interface.rng and xml test files to match netcf 0.1.5 The RNG now supports IPv6 and bonds attached to bridges, along with some other minor tweaks. All test files from netcf have been copied to the test directory and added to the xml2xml and schema tests (and they all pass, of course ;-) 2010-01-02 01:40:26 +00:00			`<interface type='ethernet' name='eth1'>`
			`</interface>`
Add netcf XML schemas and test data * docs/schemas/interface.rng: schemas for the interface XML files directly imported from netcf-0.1.0 * tests/interfaceschemadata/*.xml: set of test files from netcf-0.1.0 changed to use single quote instead of double quote 2009-07-15 17:37:20 +00:00			`</bridge>`
			`</interface>`