It would be nice to have the xml output for commissioning in a more human readable format, such as yaml. This would make the output information more human readable. Here is an example of what we could have:
Current xml (example):
<node id="network" claimed="true" class="network" handle="PCI:0000:00:03.0">
<description>Ethernet interface</description>
<product>Virtio network device</product>
<vendor>Red Hat, Inc</vendor>
<physid>3</physid>
<businfo>pci@0000:00:03.0</businfo>
<logicalname>eth0</logicalname>
<version>00</version>
<serial>52:54:00:35:65:8d</serial>
<width units="bits">32</width>
<clock units="Hz">33000000</clock>
<configuration>
<setting id="broadcast" value="yes" />
<setting id="driver" value="virtio_net" />
<setting id="driverversion" value="1.0.0" />
<setting id="ip" value="10.17.17.103" />
<setting id="latency" value="0" />
<setting id="link" value="yes" />
<setting id="multicast" value="yes" />
</configuration>
<capabilities>
<capability id="msix" >MSI-X</capability>
<capability id="bus_master" >bus mastering</capability>
<capability id="cap_list" >PCI capabilities listing</capability>
<capability id="rom" >extension ROM</capability>
<capability id="ethernet" />
<capability id="physical" >Physical interface</capability>
</capabilities>
<resources>
<resource type="irq" value="10" />
<resource type="ioport" value="c060(size=32)" />
<resource type="memory" value="febd5000-febd5fff" />
<resource type="memory" value="feb80000-febbffff" />
</resources>
</node>
Current yaml (example):
- node:
- id: network
- claimed: true
- class: network
- handle: PCI:0000:00:03.0
- description:
Ethernet interface
- product:
Virtio network device
- vendor:
Red Hat, Inc
- physid:
3
- businfo:
pci@0000:00:03.0
- logicalname:
eth0
- version:
00
- serial:
52:54:00:35:65:8d
- width:
- units: bits
32
- clock:
- units: Hz
33000000
- configuration:
- setting:
- id: broadcast
- value: yes
- setting:
- id: driver
- value: virtio_net
- setting:
- id: driverversion
- value: 1.0.0
- setting:
- id: ip
- value: 10.17.17.103
- setting:
- id: latency
- value: 0
- setting:
- id: link
- value: yes
- setting:
- id: multicast
- value: yes
- capabilities:
- capability:
- id: msix
MSI-X
- capability:
- id: bus_master
bus mastering
- capability:
- id: cap_list
PCI capabilities listing
- capability:
- id: rom
extension ROM
- capability:
- id: ethernet
- capability:
- id: physical
Physical interface
- resources:
- resource:
- type: irq
- value: 10
- resource:
- type: ioport
- value: c060(size=32)
- resource:
- type: memory
- value: febd5000-febd5fff
- resource:
- type: memory
- value: feb80000-febbffff
There is a reason to show the XML: so that people can write XPath expressions to match it for use with "auto" tags. If you show YAML by default you need to provide a way to see the raw XML too.
Perhaps there is a half-way house, which is to use a JavaScript colourisation library to make the XML prettier and easier to read.