Comment 1 for bug 1052339

In a case of bonded interface, current behavior of MAAS is really problematic. Bonded interfaces can change hardware address on reboots and of course when NIC fail.

I came up with a 'concept'/workaround that links a node (and all its NICs) with an IP. So, after commissioning, I run this script, which collects IP addresses and creates a entries for dhcp template. It's not ideal, I know, but it might provide an angle to resolve this problem. If MAAS could inform maas-dhcp about the changes and generate dhcpd.conf on the fly, that would be awesome. 'maas.json' file is output of 'maas-cli maas nodes list'. Ideally, script would pull directly from MAAS, instead of reading the file (I was kind of short on time).

I think this could easily be transformed to a setup where specific NICs would be linked to specific Network or whatever is the idea in the end.