Cool pod feature! Looks very promising.
If I compose a new VM in a libvirt-based pod, everything works, but the VM gets a virtual network interface that is connected to the default virtual network, which is pretty useless (behind NAT).
If I create a VM by hand using virt-manager, I can choose a network source for the NIC, and in addition to the virtual network 'default', I can choose to connect to a host device using macvtap in bridged mode. This is actually useful (the node can be reached from outside the vm host).
It would be great if at a minimum, the default network source could be specified as a property of the pod itself, so that newly composed machines had a functional default network setup.
MAAS version: 2.2.0 (bzr6054-0ubuntu1~16.04.1)
Oh, I should mention that one of the problems with the current behavior is that while the VM host has a network interface on a VLAN managed by MAAS, since the newly composed VM gets a network interface on the useless default virtual network, it's not on that VLAN, and thus cannot PXE boot from the rack controller.
I realize I could add a rack controller VM to each and every such VM host to solve this issue (at the expense of using up resources better used for other VMs), but that still wouldn't solve the problem that the newly composed VM is not reachable from the outside world because it's behind the default virtual network's NAT.