[kikoreis]

Thanks for trying; here's a commentary on your points:

> * Auto-enrollment of nodes was tough to get working. > * Overlay and config management was weak and better handled by Puppet. Though Juju beans were touted as able to handle this.

If you have any detail to share on these I'd love to hear more. The first point has long been a sore point in MAAS and we're doing a lot of work this cycle to improve auto-registration and dealing with BMC hardware.

> * Juju 1.13 and maas 1.3 do not support isolated juju environments in the same maas cluster. No idea what version it is at now.

You can definitely do that now -- all you need to do is to set up separate users in MAAS and use different credentials for each of those. We've used this recently in the field for demonstrations (to take advantage of limited hardware)

> * Juju charms "local provider" is potentially very compelling but wasn't in a workable state.

This also works today (and can be used independently of MAAS) and as of 1.18 is in great shape; I'm personally supporting a few companies using it in production.