quantail

Don't drink alcohol, Don't buy unnecessary things, Get one thing done a day.

The content seems very banal and will only serve to humanize her in the coming primaries. Super Tuesday is March 1st.

The timing is uncanny.

The different email addresses seem to contain interesting classification. HRC16, HDR22 and HRC17 are some that jumped out. HRC1 & HRC2 must of been some particularly lofty circles.

We'll bring the pony and the stick.

Apologies for positing a supposition without knowing the facts.

To be clear we are a great fan of Canonical's work and it's too easy complain about the few issues that praise them for the great work that is done every day on the Ubuntu platform.

The bleeding edge of Open Source technology is oft a perilous place to do business.

Hey, thank you for developing it!

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.

Yeah, we were psyched to use it as a private cloud deployment tool and to manage some development environments. It represented a interesting middle ground between a container like setup (docker) and a distributed computing model like Storm/Disco.

A stack was run on it, however it lacked the polish, support and flexibility required to make it a platform worth investing in.

That is not to say that we thought the idea was bad but that it was nowhere near mature enough for production last year.

Given how Tahr has rolled out, we suspect most development effort was put into the mobile platform and a close integration of MaaS with the cloud in a box.

We spent around 6 weeks trying to wrangle Juju and MaaS into a working state in August 2013. Skimming through my notes we surmised the following.

* 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.

* 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.

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

In the end we abandoned it.