MAAS doesn't offer an API to get network interfaces information for a node

[Dimiter Naydenov]

Right now Juju needs to do several API calls in order to get all the networking details for a node: networks attached to the node, connected MACs, and then parse the lshw XML output (which is fragile and doesn't cover cases where a complex networking setup is done post commissioning and hardware discovery - e.g. bonding, etc.). This works, but as mentioned in bug #1304857, Juju ideally needs a new MAAS API to return all network interfaces of a node, including the network name of the NIC, MAC(s), interface names and device indices (if possible - e.g. "eth0" has index 0, but it depends on udev rules, etc.), and (when MAAS has that info) dependencies (i.e. "eth0" is the "parent" interface of a VLAN virtual NIC "eth0.42"). I'm sure Landscape or other users of MAAS will find this information useful.

[Mark Shuttleworth (sabdfl)]

Hi folks, this should certainly have a milestone set. If we're modelling network and disks in 1.8, then we need APIs to ask about the network interfaces and disks for a given node.

[Raphaël Badin (rvb)]

Here is what 1.8 supports: listing the MACs attached to a node, listing the networks and listings the MAC attached to a network.
I'm assigning this to 1.9 because 1.9 will had support for listing not only the MACs but also the interfaces for a node.

[Blake Rouse (blake-rouse)]

MAAS does support listing of the physical attached block devices on a node in 1.8. This is exposed over the API.

maas admin node read system_id_of_node

Will return a JSON object that includes physcialblockdevice_set. That field contains a list of all physically attached block devices on that node.

[Blake Rouse (blake-rouse)]

This is now possible with:

maas admin node-interfaces read system_id_of_node