[00:19] <jose> hey ValDuare
[08:12] <raywang> hello juju team, how can I disable the DEBUG info from "juju debug-log", and just leave INFO from the output? :)
[15:33] <cory_fu> Hrm.  My install hook (running under amulet on LXC) seems to be hanging on "ldconfig deferred processing now taking place" and just sits there with no apparent activity going on.
[15:33] <cory_fu> Any suggestions on how to figure out what's going on, or should I just jack up the timeout and hope for the best?
[15:37] <cory_fu> arosales, perhaps?
[15:38] <arosales> cory_fu, hello
[15:38] <cory_fu> Was hoping you might have some advice on my question.  :-)
[15:39] <marcoceppi> cory_fu: what are you installing?
[15:39] <arosales> ldconfig . . . .
[15:39] <cory_fu> Running the deploy test on my allura charm.  The allura unit hangs and times out during the install hook
[15:40] <arosales> cory_fu, got a pointer to your amulet test and pastbin to your tests?
[15:41] <cory_fu> Actually, it doesn't even seem like it's getting into the hook at all.  I'll put my log file up
[15:45] <cory_fu> http://pastebin.ubuntu.com/7250318/
[15:47] <cory_fu> So I'm wrong, it is getting into the install hook
[15:47] <marcoceppi> cory_fu: yeah, it' hanging on openjdk install
[15:49] <cory_fu> Why would that happen, and can I fix it?
[15:51] <marcoceppi> no idea, and that's entirely up to you
[15:51] <cory_fu> Bah.  :-p
[18:17] <arosales> as a quick test to get a charm running on a more recent kernel I tried
[18:17] <arosales> http://paste.ubuntu.com/7250984/
[18:18] <arosales> ideally it would be nice to have a config option to specify this, but what do folks think about rebooting in the install hook. Is there a better place?
[18:18] <arosales> The tested ok for me, but wanted to see if any other folks had any better suggestions on where a are boot should be.
[18:37] <lazyPower> arosales: It makes sense that since its a predependency. the last step of the install hook should be that reboot so we ensure everything else has been run.
[18:38] <lazyPower> eg: i wouldn't want my  node to reboot everytime config-change runs, as at that point we can assume the node has already joined a cluster of the service. +1 from me on the current implementation
[18:39] <arosales> lazyPower, thanks or the feedback. I did add that as the last command in the install hook
[19:13] <kirkland> I have a bundle, which currently references a bunch of cs: charms
[19:14] <kirkland> I need to switch all of those cs: to local: charms
[19:14] <kirkland> I have copies of all of the charms locally
[19:14] <kirkland> what else do I need to do, to tell the bundle where my local copy of the charm store, is located?
[19:15] <kirkland> marcoceppi: jcastro: ^
[19:16] <marcoceppi> kirkland: set JUJU_REPOSITORY before running the bundle
[19:18] <kirkland> marcoceppi: export JUJU_REPOSITORY=/srv/charmstore/
[19:18] <kirkland> marcoceppi: and then change cs: to local: ?
[19:19] <marcoceppi> kirkland: change charm: cs:... to just charm: <charm>
[19:20] <kirkland> marcoceppi: so charm: "cs:precise/mysql-29" becomes ... what?
[19:20] <marcoceppi> kirkland: charm: mysql
[19:20]  * marcoceppi checks
[19:21] <marcoceppi> yeah, that should do it
[20:32] <jose> lazyPower: if you're up for some reviewing, I pushed a new fix for the owncloud charm
[21:27] <jose> guys, what should I do if I want to be the maintainer of a charm?
[22:20] <ghartmann> I haven't found it yet, but do we an ipython notebook juju charm ?
[22:24] <ghartmann> do you think that this would be worth working on ?