| Thanks for giving it a try. If you're ever thinking about trying it again, we (MAAS team) would be happy to help. Truth is that the problems that MAAS is trying to solve are hard, and it's taken us some time to solve them. We're spending a lot of time in this development cycle working on the robustness of the MAAS node lifecycle. MAAS 1.5 is significantly better than 1.3, and getting stronger all the time. Similarly, Juju 1.18 and 1.19 are leaps ahead of 1.13 – the local provider is now in a workable state and gets used a lot internally. We at Canonical eat our own dogfood as far as MAAS and Juju are concerned. We're using MAAS extensively in our DCs (though I don't think we use it for 100% of machines; I'm not privy to that knowledge) and the vast majority of our core services are deployed using Juju. |
There were a lot of cool working parts such as the Juju-gui and the way that nodes could be tagged for different charms. Though the way that charms deployed at the command line sometimes didn't appear in the gui vexed us.
I like the idea of MaaS on the cloud in a box. A plug and play cloud has its uses though TechOps time is at a premium and rebuilding the stack unlikely.
We ended up investing more time instead into Jenkins and gave up on the distributed computing issue by using 64 core, 512GB RAM servers.