All third party OS' are deployed with the latest LTS ephemeral image or the one that is default for commissioning.
There are multiple reasons why we always deploy a Ubuntu based OS' with the same ephemeral image. Examples:
1. If you deploy 'Trusty' with Xenial ephemeral on a hardware for which Trusty's default kernel does not include support for, then the deployment process will succeed, but the deployed machine won't work.
2. Similarly, if you deploy 'Zesty' with a Xenial ephemeral image, on a machine for which Xenial doesn't have drivers for, then the deployment process will fail altogether.
That said, I did a bit more digging and I need to correct my previous statement. MAAS/cloud-init/curtin do not support configuring 'components' nor 'sources' for the Ubuntu mirrors:
@Tom,
All third party OS' are deployed with the latest LTS ephemeral image or the one that is default for commissioning.
There are multiple reasons why we always deploy a Ubuntu based OS' with the same ephemeral image. Examples:
1. If you deploy 'Trusty' with Xenial ephemeral on a hardware for which Trusty's default kernel does not include support for, then the deployment process will succeed, but the deployed machine won't work.
2. Similarly, if you deploy 'Zesty' with a Xenial ephemeral image, on a machine for which Xenial doesn't have drivers for, then the deployment process will fail altogether.
That said, I did a bit more digging and I need to correct my previous statement. MAAS/cloud- init/curtin do not support configuring 'components' nor 'sources' for the Ubuntu mirrors:
* components = main, restricted, universe, multiverse
* source = deb-src
Configuring pockets for the Ubuntu mirrors is supported though.
* pockets = *-updates, *-security, *-backports
Changing this as a wishlist.