[14:28] <FunnyLookinHat> Can juju-core handle LXC local deployments?  I'm getting a error: environment "sample" has an unknown provider type "local" when doing juju bootstrap
[14:28] <pavel> which version of juju?
[14:29] <FunnyLookinHat> launchpad trunk for juju-core :D
[14:30] <pavel> I think here is your answer http://askubuntu.com/questions/309508/sample-lxc-has-an-unknown-provider-type-local-error-when-bootstrapping
[14:31] <pavel>  In order to use LXC as a provider you will need to use Juju .7. The way we're currently doing this is you can install juju along with juju-core and use alternatives to switch back and forth:
[14:31] <FunnyLookinHat> Ah
[15:09] <marcoceppi> FunnyLookinHat: Local provider in juju-core is scheduled to land this cycle
[15:10] <FunnyLookinHat> marcoceppi, right on - I can test with 0.7 in the meantime  :)
[15:10] <FunnyLookinHat> Curious - when does this current cycle go "stable" ?
[15:11] <marcoceppi> FunnyLookinHat: I haven't the slightest idea, I know they've got another release ready to go soon and there's talks of publishing a juju-core release every 2 weeks, but as for when juju-core goes 2.0 (stable) that's still dependant on when features land, etc
[15:12] <FunnyLookinHat> marcoceppi, Ah ok thanks :)
[15:25] <jcastro> hey evilnickveitch
[15:25] <jcastro> http://blog.smartbear.com/careers/13-things-people-hate-about-your-open-source-docs/
[15:25] <jcastro> thankfully we already are avoiding most of them
[15:25] <evilnickveitch> cool, thanks!
[15:28] <evilnickveitch> jcastro, i think we are avoiding all of them, apart from not shipping the docs with the software
[15:28] <evilnickveitch> which we could do if we wanted
[15:28] <marcoceppi> evilnickveitch: which we should do to make thumper happy*
[15:28]  * marcoceppi squints at juju help
[15:29] <evilnickveitch> marcoceppi, I think we should. There are various other bits that need tidying up
[15:29] <evilnickveitch> man pages for example
[15:29] <marcoceppi> yeah, but it should be pretty easy go html -> whatever-format-they-want
[15:30] <evilnickveitch> marcoceppi, indeed - that is the genius of whomever it was that decided the docs should be written in HTML
[15:31] <marcoceppi> Easy, you might pull a muscle patting yourself on the back that hard ;)
[15:31] <evilnickveitch> :)
[15:32] <marcoceppi> really <3 the new docs. evilnickveitch I'll have a merge request for the redirects against the juju-core branch by my eod as it looks like most of the pages are there now (and I'll be out next week)
[15:33] <evilnickveitch> marcoceppi, okay, that's great, I'll try and pick it up later
[15:34] <arosales> evilnickveitch, I have an RT open to get the docs deployed as you may have seen. But with that I listed no deps. Thus, could you work to get the navigation settled and then drop the jade ?
[15:34] <evilnickveitch> arosales - sure, I have been working on that, should be sorted by Monday :)
[15:35] <arosales> evilnickveitch, thanks.  Could you update the RT with that, you should be on cc.
[15:35] <evilnickveitch> yeah, i see it, will do
[15:36] <arosales> evilnickveitch, thanks.
[15:36] <arosales> marcoceppi, I am also checking where the redirects should live (you are also on cc).
[15:36] <marcoceppi> arosales: ack, I'm going to stick them in the repo for now, incase that's becomes a blocker next week
[15:37] <arosales> marcoceppi, ok sounds good. IS can also move them where appropriate if they are in the repo too
[15:50] <pavel> jcastro, hello
[15:51] <jcastro> hi!
[15:54] <pavel> ./msh jcastro we have a kickoff on a tuesday only
[15:54] <pavel> but can we schedule another one about requirements on a monday?
[15:55] <arosales> pavel, hello
[15:55] <pavel> sry, I fucked up with those irc commands )
[15:56] <jcastro> yeah the problem is m_3's availability
[15:56] <jcastro> pavel: but if you guys are around now maybe we can set something up?
[15:56] <arosales> pavel, no worries.  what jcastro said
[15:56] <pavel> yes, we can
[15:57] <jcastro> was concerned by the time m_3 got off the phone on the call he is now that you guys would be in bed.
[15:57] <arosales> m_3, and I are in meeting for another hour
[15:58] <pavel> I see
[15:58] <arosales> pavel, is 17:00 UTC to late for you?
[15:58] <pavel> it's ok for me
[15:58] <pavel> Jorge, can we have a small hangout just for me to clarify some points?
[15:59] <arosales> pavel, I'll set up a quick google hangout for 17:00 with jcastro and m_3
[15:59] <pavel> today?
[15:59] <arosales> correct
[15:59] <arosales> in 1 hour
[15:59] <arosales> given it is not too late for you
[15:59] <pavel> it will work perfectly for me
[16:00]  * arosales doesn't want it to disrupt you friday evening though :-)
[16:01] <pavel> friday night is long  :)
[16:02] <jcastro> I like how you roll
[16:56] <FunnyLookinHat> What's the command to see the bash as I'm deploying a charm ?
[17:04] <marcoceppi> FunnyLookinHat: debug-log ?
[17:05] <FunnyLookinHat> marcoceppi, duh.  thx.  :D
[17:05] <FunnyLookinHat> I was looking at juju-debug and just realized that's how you SEND something
[17:05] <marcoceppi> Personally, I prefer to juju ssh <service>/<unit>; tail -f /var/lib/juju/units/*/charm.log; but I'm just old fashioned
[17:12] <paraglade> has anyone tried to get the following to work using just charms and no manual config: kibana + elasticserach + logstash indexer + redis + logstash agent
[17:12] <paraglade> I seem to be hitting a wall with the redis part
[20:49] <FunnyLookinHat> Ah geez - how do I send a message to the log from within a hook again? ( bash hook, that is )  juju-log message ?
[20:50] <FunnyLookinHat> Doesn't seem to want to play nice...  :-P
[20:50] <FunnyLookinHat> Oh I just missed it...