In maas_vm_host, it would be useful to have the ability to define deploy_params as is the case for maas_instance; this would allow for example to enable hardware sync.
The use case is that vlan networks might be added post-deployment and it would be useful to have a view on these from MAAS.
Another use case is the ability to provider cloud-init userdata in order to customize the LXD configuration e.g. provide a zfs storage pool, rather than use the dir based default one.
In maas_vm_host, it would be useful to have the ability to define
deploy_params
as is the case for maas_instance; this would allow for example to enable hardware sync.The use case is that vlan networks might be added post-deployment and it would be useful to have a view on these from MAAS. Another use case is the ability to provider cloud-init userdata in order to customize the LXD configuration e.g. provide a zfs storage pool, rather than use the dir based default one.