[03:05] <finisherr> Can someone explain what a charm does? I'm looking at the demos and I"m seeing someone plug these apps together, but what is happening there?
[03:05] <finisherr> when you pull an app out on to the canvas and create a relationship, what is happening, are the services being configured?
[03:07] <finisherr> I guess without knowing what is actually happening, the high level interface is a little confusing
[10:25] <ashipika> \o/
[13:15] <jcastro> marcoceppi, do you plan on making the new queue live today?
[13:17] <jcastro> jose, when the orangebox gets to mhall's place I can G+ you and show you how to use it.
[13:19] <jose> jcastro: sure thing!
[13:19] <marcoceppi> jcastro: that's the plan, technically off today
[13:20] <jcastro> oh ok, nm
[13:49] <mhall119> jose: why does the box need to be at my place for you to show jose how to use it?
[13:52] <Odd_Bloke> * mhall119 looks out the window and sees jose peering in.
[13:53] <mhall119> lol
[16:13] <jcastro> aisrael, https://juju.ubuntu.com/docs/authors-charm-store.html
[16:13] <jcastro> scroll down to the reviewer tips, etc.
[16:30] <aisrael> Looks like it's moved here? https://juju.ubuntu.com/docs/reference-reviewers.html
[16:41] <jcastro> oh, right
[16:42] <jcastro> lazyPower, question, why file a bug to push to trusty? Why not just push to trusty?
[16:42] <lazyPower> jcastro: some of the precise charms simply wont make it
[16:42] <jcastro> right
[16:42] <lazyPower> so with a bug, we can track the progress of that jump from precise => trusty and give it a thorough review
[16:42] <jcastro> ah ok, ta
[16:42] <lazyPower> its kind of like completing the bits from the audit, in an ad-hoc fashion
[17:34] <lazyPower> hazmat: juju-deployer understands maas tagging?
[17:35] <jose> mhall119: I think you wanted to highlight jcastro instead of myself :P
[17:37] <lazyPower> hazmat: https://bugs.launchpad.net/charm-tools/+bug/1360374 - here's what i'm referencing re: tags
[17:37] <mup> Bug #1360374: bundle proof is unaware of MAAS tagging <Juju Charm Tools:New> <https://launchpad.net/bugs/1360374>
[18:10] <hazmat> lazyPower, yes it does
[18:11] <hazmat> lazyPower, deployer doesn't validate constraints
[18:11] <hazmat> lazyPower, thats a proof error
[18:11] <hazmat> proof doesn't understand constraints.. probably quite alot of them
[18:11] <hazmat> instance-type, maas-tags, maas-name, and probably others i'd guess
[18:12] <hazmat> deployer passes constraints through
[18:12] <hazmat> and bubbles up the juju error if juju doesn't understand them
[18:20] <lazyPower> hazmat: yeah - i filed the bug against bundle proofer - and i thought that might be whats going on is since you're shelling out you can just hand all that off
[18:20] <lazyPower> thanks for clarification hazmat
[18:22] <hazmat> np
[18:27] <jcastro> http://askubuntu.com/questions/514728/juju-deploy-issues?noredirect=1#comment697187_514728
[18:27] <jcastro> this looks to me like his file structure on disk is missing $charmname, thoughts?
[18:30] <hazmat> jcastro, he's got a hooks directory in precise
[18:30] <hazmat> jcastro, he can move that and remove the warnings
[18:30] <marcoceppi> jcastro: yea
[18:30] <jcastro> right
[18:30] <jcastro> but I am wondering if it's supposed to be
[18:30] <jcastro> /home/eduard/charms/precise/stack/hooks
[18:30] <jcastro> and not
[18:30] <jcastro> /home/eduard/charms/precise/hooks
[18:31] <hazmat> jcastro, he has both
[18:31] <jcastro> ok
[18:31] <hazmat> well maybe
[18:31] <hazmat> jcastro, he has a valid charm metadta in charms/precise/stack
[18:31] <jcastro> oh
[18:32] <jcastro> because it would error otherwise!
[18:32] <jcastro> I am wondering how you got to "he has both"
[18:32] <hazmat> the hooks dir in precise/hooks is confusing juju causing the warning.. whether he also has them in precise/stack/hooks i dunno
[18:32] <hazmat> jcastro, i don't know that for sure
[18:32] <hazmat> jcastro, in which case yes he'd neeed to move 'hooks' to under precise/stack
[18:32] <jcastro> marcoceppi: I would add that to the answer
[18:33] <jcastro> since you torpedo'ed my rep man!
[18:41] <lazyPower> jcastro: we're coming for you... one upvote at a time
[19:03] <aisrael> Is there a good template to follow for filing a bug report?
[19:05] <lazyPower> aisrael: depends on the context of the bug. Is this against a charm?
[19:05] <aisrael> juju-core. mysql is broken on local providers
[19:05] <lazyPower> this is a known bug, it has to do with a memory constraint
[19:06] <aisrael> Yeah, innodb buffer.
[19:06] <lazyPower> its being set to consume 80% of the given ram, and it totally breaks when deployed on the local provider.
[19:06] <lazyPower> afaicr a bug has been filed and marcoceppi has triaged this in the forthcoming mysql re-release
[19:09] <aisrael> https://bugs.launchpad.net/charms/+source/mysql/+bug/1294334
[19:09] <mup> Bug #1294334: mysql charm blows up on out of memory error <mysql (Juju Charms Collection):Confirmed> <https://launchpad.net/bugs/1294334>
[19:09] <aisrael> That looks like the one. It's undecided, though
[19:14] <aisrael> There's a couple bugs that are duplicates but not marked as such. Should I tag those as duplicates?
[19:24] <marcoceppi> aisrael: yeah. There's a duplicate bug link
[19:28] <jcastro> marcoceppi, I thought your rewrite fixed this?
[19:28] <aisrael> marcoceppi: ok, I marked them as dupes. It seems like just having the caveat might not be enough.
[19:35] <marcoceppi> aisrael: it's being patched
[19:35] <hazmat> marcoceppi, that zone doc is ready for review incidentally
[19:35] <marcoceppi> hazmat: ack, will take a look in a bit
[19:36] <aisrael> marcoceppi: rock on, thanks
[20:13] <mhall119> jose: yeah I did