[13:40] <mbruzek> Good morning Juju.  Question.  Where does the bash function ch_get_file live?
[13:41] <mbruzek> marcoceppi ^ ?
[13:42] <marcoceppi> mbruzek: that's a name I've not heard in a long long time
[13:42] <mbruzek> One of the lesser used charms is failing to find this function, I vaguely remember it.
[13:43] <mbruzek> It uses wget and checks the hash value.
[13:43] <marcoceppi> http://i.imgur.com/YO0lXro.gif
[13:43] <mbruzek> marcoceppi, the charm liferay is FAILING to find it actually.
[13:43] <marcoceppi> mbruzek: yeah, that's charmhelpers 1.0
[13:44] <marcoceppi> the charm will likely need to add a PPA to continue to function on precise
[13:44] <mbruzek> Does it no longer exist in the latest CH version?
[13:45] <marcoceppi> no
[13:46] <marcoceppi> current charmhelpers is only python
[13:46] <marcoceppi> atm
[13:46] <marcoceppi> this is when charmhelpers lived in charmtools
[13:46] <marcoceppi> pre charm-tool 1.0.0
[13:46] <mbruzek> Well it looks like it tries to install charm-helper-sh which can not be found.
[13:46] <marcoceppi> right
[13:46] <marcoceppi> the charm needs a ppa
[13:47] <mbruzek> Add a ppa or change the code to use wget?
[13:47] <marcoceppi> https://launchpad.net/~charmers/+archive/ubuntu/charm-helpers
[13:47] <marcoceppi> add a ppa, this also does the verification
[13:47] <marcoceppi> will only work on precise
[13:47] <marcoceppi> the ppa is to enable those older charm to continue working
[13:47] <mbruzek> Ok thanks.
[13:51] <jcastro> marcoceppi, is today new queue day?
[13:51] <marcoceppi> jcastro: open your eyes and seeee
[13:52] <jcastro> I still see the old queue
[13:52] <lazyPower> JoshStrobl: I do actually, i'll send it to you in a pm.
[13:52] <jcastro> oh, should I get the gui guys to fix the URL?
[13:52] <marcoceppi> jcastro: well, yeah
[13:52] <marcoceppi> jcastro: http://review.juju.solutions/
[13:53] <marcoceppi> jcastro: but not right now
[13:53] <marcoceppi> there's still things to be sorted in new rev queue
[13:53] <marcoceppi> well
[13:53] <marcoceppi> do what you think is right
[13:53] <jcastro> well, we're the only ones who use the link
[13:53] <jcastro> so let's go all in
[13:53] <marcoceppi> sounds good to me
[14:02] <lazyPower> marcoceppi: looks sharp man! Nice work on applying the design bits
[14:30] <jcastro> heya lazyPower
[14:30] <jcastro> did we ever get logstash on trusty? I can't seem to find it
[14:30] <lazyPower> it needed tests
[14:30] <lazyPower> and i was having a big issue with amulet / sentries blocking the tests
[14:30] <jcastro> ack
[14:30] <lazyPower> but baseline - is no, its not in trusty yet.
[14:30] <jcastro> which is the most current one
[14:30] <jcastro> logstash-agent or logstash-indexer?
[14:35] <jcastro> lazyPower, ^
[14:35] <lazyPower> https://code.launchpad.net/~lazypower/charms/trusty/logstash/trunk
[14:36] <lazyPower> this is a port of the indexer, feature 2 landing would be adding the agent - its a unified deliverable now
[14:36] <lazyPower> ready for the kickass part? this woudl also include kibana with feature 2
[14:36] <lazyPower> *an up to date kibana
[14:36] <jcastro> ok I'll just link to your personal branch then
[14:37] <jcastro> it's a subordinate right?
[14:39] <lazyPower> Nope. its a stand alone charm
[14:39] <lazyPower> ahhh so the agent would need to be a sub. ok - i follow where you're going with this.
[14:39] <jcastro> I think one of the old ones was a sub
[14:40] <lazyPower> yeah, the agent would have been a sub.
[14:41] <lazyPower> bummer I wasn't thinking about that, but upgrading the sub will be fairly straight forward with the work that went into the agent.
[14:41] <lazyPower> s/into the agent/into the indexer/
[16:36] <kwmonroe> mbruzek, have you come across any charms with source behind a "free registration" wall?
[16:37] <kwmonroe> i'm charming db2 express -- there's an older version in the partners ppa (which is super easy), but the latest version isn't very programatically accessible from ibm.com.
[16:38] <mbruzek> kwmonroe no I have not but I could take a look
[16:39] <kwmonroe> so i think the options are either update the partners ppa, or stash the tar.gz someplace more accessible (assuming the fine print says that's ok)
[16:39] <mbruzek> kwmonroe, could you get the required info (I suspect email, name,etc) and send an HTTP PUT ?
[16:39] <mbruzek> kwmonroe, can you link me to the wall?
[16:40] <kwmonroe> mbruzek, here's the wall:  https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-db2expressc&S_PKG=dllinux64
[16:42] <mbruzek> kwmonroe, this one looks particularly hard with the user having to register.
[16:43] <kwmonroe> yeah mbruzek - i'll take a look at the form behind "proceed without an ibmid" and see if i can PUT it.
[16:44] <kwmonroe> but even so, that seems a fragile way to get the source :/
[16:44] <mbruzek> kmonroe talk with arosales about getting it added to the partner ppa
[16:44] <mbruzek> kwmonroe, that is likely the path of least resistance.
[16:47] <kwmonroe> ack mbruzek - thx
[16:48] <arosales> kwmonroe: adding to the partner PPA I think is a longer term solution that we should take a look at. For that we just need to go through the ubuntu dev process
[16:48] <arosales> kwmonroe: ther other is putting the DB2 binary local to the charm
[16:48] <arosales> kwmonroe: you need to have an EULA in the charm and a config set for the charm user to accept. mbruzek did this for the websphere liberty lite charm.
[16:49] <arosales> kwmonroe: and the third option is building a .deb on lp in a custom PPA
[16:50] <arosales> kwmonroe: putting the binary locally may be your fastest option with an EULA config set
[16:50] <arosales> in parrallel we can work on updating the partner ppa
[16:50] <arosales> locally to the charm that is.
[16:50] <kwmonroe> gotcha arosales - thanks for the options.. i'm gonna put my legal cap on and make sure this is "free to deploy" like the marketing flyer says.
[16:50] <arosales> kwmonroe: ping mbruzek and check out what he did for the websphere liberty charm
[16:51] <mbruzek> arosales, IIRC the websphere charm downloaded the code, but yeah there was an "accept-ibm-license" configuration option in there.
[16:51] <arosales> mbruzek: ya and I think the "accept-ibm-license" portion is the part kwmonroe is intersted in.
[16:52] <arosales> mbruzek: given kwmonroe puts the db2 binary locally to the charm for now.
[16:53] <kwmonroe> yeah, i'll take a look at liberty and bug mbruzek
[19:57] <JoshStrobl> hey marcoceppi, loving the new review queue! great work man!
[20:00] <hatch> is there a way to force destroy a machine on a local deployment? 1.20.6-trusty-amd64
[20:01] <hatch> it appears to be stuck in pending
[20:04] <hatch> help says to use --force but using it says that it's not defined
[20:04] <hatch> oh well, hulk smashing :)
[20:05]  * arosales geting some review queue time in.
[20:05] <arosales> marcoceppi +1 JoshStrobl's comments on the review queue
[20:06] <arosales> hatch: is there a service on the machine?
[20:06] <marcoceppi> hatch: use terminate-machine with force
[20:06] <marcoceppi> should work
[20:06] <hatch> arosales: nope it was just hangin out in pending
[20:06] <hatch> marcoceppi: ok I'll remember that for next time
[20:07] <marcoceppi> destroy-unit and service don't have a force
[20:08] <arosales> JoshStrobl taking a look at https://github.com/juju/docs/pull/156 now
[20:08] <arosales> mbruzek: ^
[20:08] <mbruzek> I will take a look
[20:09] <arosales> mbruzek: you already commented. This is in regards to the Charm Review Process doc
[20:13] <JoshStrobl> arosales, warming up some food now, will review after :P
[20:15] <JoshStrobl> back
[20:15] <JoshStrobl> arosales, oh, I misread
[20:15] <arosales> JoshStrobl: no action from you atm. I was just stating I was going to review
[20:15] <JoshStrobl> arosales, I thought you said "take a look"
[20:15] <JoshStrobl> fail :D
[20:16] <arosales> ah. My IRC grammer is horrible so I thought it may have been that
[20:16] <arosales> and my message was kind of vague
[20:16] <JoshStrobl> arosales, no no, I just misread, thats all
[20:16] <arosales> in any case taking a look now
[20:16] <JoshStrobl> seriously my fault
[20:16] <JoshStrobl> alrighty
[20:17] <jose> marcoceppi: congratulations on the new revq, looks awesome!
[20:19] <JoshStrobl> mbruzek, sorry I haven't gotten around to working on the reference-reviewers doc yet, been busy with failing tests on some unrelated stuff today. will get around to it tomorrow morning and have something for you to review then.
[20:20] <hatch> marcoceppi:  just fyi - I somehow ended up in the same state and terminate worked thanks
[20:20] <mbruzek> No worries JoshStrobl I am up to my ears in work too.
[20:20] <JoshStrobl> mbruzek, yea I imagine a lot of crunching even before the sprint!
[20:21]  * mbruzek nods
[20:26] <JoshStrobl> arosales, going to be afk to help the wife clean our newly rescued old cat, just fyi
[20:27] <arosales>  JoshStrobl: ack, I'll post comment in the git pull request
[20:40] <jcastro> marcoceppi, bah crap
[20:40] <jcastro> we forgot something, where to report bugs on the new queue
[20:41] <jcastro> want them on issues?
[21:31] <JoshStrobl> arosales, has the storm ended? my email is finally quiet :P
[21:31] <JoshStrobl> arosales, writing a lengthy response via the comment section in GH ;)
[21:32] <marcoceppi> jcastro:  on gh
[21:33] <arosales> JoshStrobl: storm ended :-)
[21:33] <JoshStrobl> \o/
[21:33] <JoshStrobl> Thanks for all the great feedback.
[21:36] <arosales> JoshStrobl: np. I errored on being more verbose hopeully you filter mail ;-)
[21:36] <JoshStrobl> arosales, yea, it all goes to a Juju folder in Thunderbird :P