[00:32] <stokachu> are canonical employees eligible for the charm contest?
[00:58] <jcastro> stokachu: nope
[00:58] <jcastro> arosales: one way
[01:24] <arosales> jcastro, whew, may want to confirm that on the list.
[01:24] <stokachu> aw and i had some good ideas
[09:17] <cjwatson> So - after upgrading from Python juju to juju-core (by way of a general saucy upgrade, I wasn't specifically trying to upgrade), I can no longer access my existing deployment: juju status returns "error: no CA certificate in environment configuration".  How do I fix this?
[09:17] <cjwatson> (Don't say "bootstrap again".)
[09:26]  * cjwatson files https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1200878
[09:26] <_mup_> Bug #1200878: Upgrade breaks existing pyjuju deployment <regression-release> <juju-core (Ubuntu):New> <https://launchpad.net/bugs/1200878>
[11:50] <marcoceppi> cjwatson: this is a known issue. you need pyjuju to access pyjuju environments. you should be able to update-alternatives and select 0.7 for juju
[14:36] <AskUbuntu> Can I make the MAAS server Juju machine 0? | http://askubuntu.com/q/319618
[16:11] <bmullan> does juju GO have LXC support fully implemented yet?
[16:12] <cjwatson> marcoceppi: Thanks.  That seems as though it might have been worth some documentation in the package, such as a debian/NEWS file.
[16:13] <cjwatson> (I would have read such a thing; I use apt-listchanges.)
[16:15] <marcoceppi> bmullan: not yet, it's due to land soon-ish