[00:01] <_mup_> juju/hook-alias-expansion-redux r471 committed by kapil.thangavelu@canonical.com [00:01] <_mup_> report signal that caused hook to terminate [00:04] jcastro: How do you guys monitor the queue of charms that need to be reviewed ? [00:05] jcastro: If you add me to whatever notification method is in place, I can be more responsive. Right now, I just look at the Charm needed bugs and go from there but, there is also what almost happened today .. I almost started reviewing a charm that SpamapS was working on ... [00:05] jcastro: I guess a bit more structure on the process would help ( at least me ) working through this in a more efficient manner without stepping on any "toes" :) [00:08] negronjl: I just look at all the bugs tagged 'new-charm' periodically [00:08] negronjl: I tend to only really look hard at the New/Confirmed/Triaged ones [00:08] tho from time to time I will click through to the Incomplete/In Progress ones and see if somebody forgot to change the status [00:09] SpamapS: Do you assign the bug to yourself when you are reviewing ? How do I know that you are not already working on it ? Do you comment on the bug ? [00:11] negronjl: I don't, I think its fine if 2 people review the same charm. [00:12] negronjl: but to that end, its probably a good idea. :) [00:13] SpamapS: ok .. I think we could either comment on the bug or assign it to ourselves while reviewing ( probably both ) so we know that there may be someone already looking at it and we could ask/coordinate better. [00:13] negronjl: thus far I haven't seen much duplication, but yes, that sounds like a good plan [00:15] negronjl: ahh, your distcc was "Fix Committed" .. I should add that to the bug statuses that I dig further into [00:16] SpamapS: What's the norm for when you get a charm done .... I thought fix committed would be appropriate ... [00:19] negronjl: I actually think you're right. [00:19] negronjl: I just was focusing on Confirmed/Triaged/New [00:50] negronjl: distcc reviewed [01:18] SpamapS: cool .... I can promulgate it then [01:19] SpamapS: spoke too soon ... I'll read the review and check things out [01:48] negronjl: sorry, I had a redbull right before I reviewed it ;) [01:48] SpamapS: no worries ... I'll work on it [01:48] negronjl: like I said, the only thing you actually really need to fix is the hostname -f's [01:48] negronjl: the other stuff is just me nit picking you to death [01:48] SpamapS: nah .. I'll fix it all ... do it right or don't do it ;) [06:05] m_3, new charm runner uploaded w/ fix for snapshot [08:12] Hi [08:12] How can I run the juju hooks within the instances ? [08:12] root@root-local-drupal6-0:/var/lib/juju/units/drupal6-0/charm/hooks# ./db-relation-changed [08:12] usage: unit-get [-h] [-o OUTPUT] [-s SOCKET] [--client-id CLIENT_ID] [08:12] [--format FORMAT] [--log-file FILE] [08:12] [--log-level CRITICAL|DEBUG|INFO|ERROR|WARNING] [08:12] setting_name [08:12] No JUJU_AGENT_SOCKET/-s option found [08:41] basil_kurian_: thats under discussion right now actually. :) [08:41] basil_kurian_: because of the way hooks work, you need to run them in the context of joining/changing relations right now.. but that will change. [08:42] Is there any other way by which i can mannually run such scripts to debug it ? [08:43] How can I get logs of such scripts , when we issue an add-relation command ? [08:45] SpamapS: Is there way to see logs of such scripts , when we issue an add-relation command ? [08:49] basil_kurian_: if you want to just test developing on them, you can use 'debug-hooks' [08:50] basil_kurian_: debug-hooks will ssh to the node, and pop up a window in screen whenever a hook is supposed to be executed [08:50] basil_kurian_: so you can then run the hook over and over in the right context, and edit it all you want. :) [08:50] a byobu window , right ? [08:50] right [08:51] how can i run the scripts ? goto that directory and then ./ ?? [08:51] I have used it to write an entire charm before.. :) [08:51] oh [08:51] you'll be in the charm root already [08:51] ./ will work ? [08:51] you should stay there, some charms expect CWD == $CHARM_DIR [08:51] hooks/scriptname [08:51] oh , let me try [08:55] It is not working :( [08:55] please see this http://pastebin.ubuntu.com/866367/ [08:57] basil_kurian_: that looks like two separate things [08:57] basil_kurian_: when you ran 'debug-hooks', did it start a byobu session? [08:58] yes , it did [08:58] see the change in hostname [09:01] Sorry I got disconnected [09:02] basil_kurian_: odd [09:02] I tried several times ;( [09:03] basil_kurian_: I'd expect JUJU_AGENT_SOCKET to be set [09:03] basil_kurian_: can you pastebin 'env | grep JUJU' ? [09:03] on virtual instance , right ? [09:03] yes [09:04] root@root-local-drupal6-0:~# env | grep JUJU [09:04] root@root-local-drupal6-0:~# [09:04] no output [09:05] basil_kurian_: weird! [09:05] any file to source ? [09:05] basil_kurian_: you're inside the byobu window, and no JUJU_ .. [09:05] basil_kurian_: no it should be set [09:05] basil_kurian_: what version of juju ? [09:05] also , pleaseee the putput of pwd [09:06] basil_kurian_: dpkg -l juju would show you [09:06] root@root-local-drupal6-0:~# dpkg -l | grep juju [09:06] ii juju 0.5+bzr467-1juju2~oneiric1 next generation service orchestration system [09:07] ran that on virtual instance [09:09] basil_kurian_: ok, so this sounds like a bug. I have not tried debug-hooks on the local provider, so its possible its broken somehow. [09:09] I 'm running it on LXC containers [09:10] basil_kurian_: well past my bed time.. so I'll leave you with that. :-/ for a log, btw, you can run 'juju debug-log' to get all the logs except for the 'install' hook. [09:10] ok [09:10] bye , thanks for the help [10:00] o/ [10:01] I hope I can learn to create a charm and enter the contest [10:55] <_mup_> Bug #945505 was filed: Use ipAddress instead of dnsName now that txaws supports it < https://launchpad.net/bugs/945505 > [15:39] mightbereptar: WELCOME! [15:39] mightbereptar: we hope you can learn as well. :) [19:24] SpamapS, there's a default tmux session there thats not associated to hooks where basil was [19:24] the hook sessions pop as a new windows in the session [19:24] but it sounds like he was in the default window which is not executing a hook [21:05] <_mup_> Bug #945862 was filed: Support for AWS "spot" instances < https://launchpad.net/bugs/945862 > [23:49] jcastro: so 2nd and 3ed winner at charm contest both equally gets 100$ gift voucher?