[03:20] <stokachu> cory_fu: new ghost is working on xenial so far :D
[03:20] <stokachu> i want to test the 0.8.0 release and get that out the door soon too
[11:46] <yioup0x> hello!!
[11:46] <yioup0x> some services are stuck in update-status hook is this normal?
[11:46] <yioup0x> it's been some hours that they are updating
[12:20] <magicaltrout> we have the best stuff ever for OLAP over all your big data stuff coming in our 3.9 release
[12:20] <magicaltrout> just putting together an RC2 with juju datasource injection, automatic schema generation and stuff
[12:20] <magicaltrout> it'll make analytics over the big data & SQL charms really easy
[13:09] <cory_fu> stokachu: I should have mentioned, I updated the ghost charm to support changing the "release" option, so we should definitely try upgrading.  I just realized, though, it should probably retry on "checksum" change as well
[13:13] <cory_fu> stokachu: https://github.com/battlemidget/charm-layer-ghost/pull/3
[13:14] <cory_fu> :)
[13:15] <stokachu> cory_fu: merged, ill try the upgrade now
[13:18] <marcoceppi> cory_fu: ping re: https://github.com/juju-solutions/charms.reactive/issues/76
[13:19] <lazyPower> marcoceppi - is that a verbiage change to reactive as a whole?
[13:19] <marcoceppi> cory_fu: people we really confused by `status_set` and `set_state`
[13:20] <marcoceppi> givenhow close in nature they are, it aslo made it really confusing since it blurs what state, people assuemd this was a state engine in juju instead of on the unit level
[13:20] <magicaltrout> you know what
[13:20] <magicaltrout> I was going to say that exact thing the other day
[13:20] <magicaltrout> and I thought I was being pedantic ;)
[13:20] <marcoceppi> so the idea of flags as a way to distil the state without really changing meaning was proposed by mark
[13:21] <marcoceppi> here's an example of what the code could look like: https://github.com/marcoceppi/layer-vyos-proxy/blob/master/reactive/vyos_proxy.py
[13:22] <magicaltrout> +1 for something like that
[13:22] <magicaltrout> also helps in amulet and stuff where you're tying to figure out what status/state/message you're trying to extract
[13:22] <cory_fu> If we're going to change that, should we make it "flag_set" (even though I hate that order) to be consistent?
[13:23] <lazyPower> +1 to normalizing on the method signatures
[13:24] <cory_fu> (I'm not even going to bother trying to argue that we change "status_set" :p)
[13:24] <marcoceppi> cory_fu: welllllllllllllll
[13:24] <marcoceppi> I'd be okay with set_status
[13:24] <aisrael> ^^ +1
[13:24] <marcoceppi> in charms.model
[13:24] <marcoceppi> ;)
[13:25] <cory_fu> True
[13:25] <marcoceppi> with like an from charms.model import classic_names
[13:25] <marcoceppi> cory_fu: though, set_action seems odd compared to action_set
[13:25] <marcoceppi> maybe not
[13:26] <Prabakaran> Hello Team, I am facing the below issue in Juju 2.0 while uploading packages to the controller using juju attach command and also juju inline deployment command using resources. Error code : http://pastebin.ubuntu.com/18097919/
[13:26] <marcoceppi> set_action_data might be better name in general
[13:26] <Prabakaran> And also it is taking lot of time to upload into the container when the product package is of more than 1 GB. Is there any trick to increase file upload speed? And also I am wondering why it is taking long time to upload/download on the controller within the same subnet. Could somebody make me clear on this?
[13:26] <cory_fu> marcoceppi: What about charms.model.status.set() and charms.reactive.flag.set()
[13:26] <lazyPower> Prabakaran - how large is your attachment?
[13:26] <cory_fu> +1 to set_action_data
[13:26] <Prabakaran> 1.8GB
[13:26] <marcoceppi> cory_fu: possibly
[13:26] <marcoceppi> I'm still very much up in the air about charms.model
[13:27] <lazyPower> Prabakaran - ah i missed your follow up. There is a bug currently that prevents large attachments from working in the current betas
[13:27] <magicaltrout> lazyPower: thats push to controller is it the same?
[13:27] <marcoceppi> cory_fu: right now it's more like charms.model.unit.status.set()
[13:27] <stokachu> cory_fu: should we be using mariadb instead of mysql?
[13:27] <lazyPower> magicaltrout - it appears so, it ran into an IO error trying ot attach to the controller
[13:28] <marcoceppi> cory_fu: so I like charms.model.unit.set_status instead
[13:28] <lazyPower> Prabakaran - can i get you to file a bug for that? i'd like to xref with core on this issue
[13:28] <magicaltrout> ah yeah
[13:28] <magicaltrout> i didn't scroll across far enough
[13:28] <Prabakaran> ya sure
[13:28] <cory_fu> stokachu: I did my testing with mariadb, but marcoceppi has put a fair amount of work in recently to improve the mysql charm
[13:28] <magicaltrout> marcoceppi <-> work?
[13:28] <stokachu> cory_fu: ok cool
[13:29] <marcoceppi> stokachu: cory_fu: that's an overstatement, I removed and touched up the tests that were failing consistently because of bad setups
[13:29] <marcoceppi> magicaltrout: great question!
[13:29] <magicaltrout> pfft
[13:29] <marcoceppi> ;)
[13:29] <Prabakaran> and also is it possible for me to upload the file by getting into the controller...?
[13:29] <magicaltrout> i'm looking forward to a whole room of americans with similar enthusiam later this year marcoceppi
[13:29] <magicaltrout> although I might need ear plugs, or a sick bowl ;)
[13:30] <marcoceppi> magicaltrout: I'll make sure to beef up on my "English"
[13:30] <magicaltrout> hehe
[13:30] <magicaltrout> just ask kwmonroe for some tips
[13:30] <magicaltrout> he's got the english patter down to a fine art.... if you live in the early 1900's
[13:30] <marcoceppi> pip pip!
[13:33] <stokachu> cory_fu: if you get time today you could run through my conjure-up enabled ghost bundle
[13:33] <stokachu> https://gist.github.com/battlemidget/a35809531b34db683d54d8b046353d80
[13:33] <lazyPower> Prabakaran - negative. the resources feature works with gridfs in mongo, and then some internal juju bits rely on that process to complete successfully (eg: BSON ID's of the resource)
[13:33] <lazyPower> Prabakaran - so without having intimate knowledge of that, i dont think you can fake it out
[13:33] <lazyPower> stokachu - oh btw i ran the cojure scripts for kubernetes, nice work :)
[13:33] <lazyPower> *conjure
[13:34] <stokachu> lazyPower: thanks :D ive got some updates to make to the bundle  as well
[13:34] <lazyPower> nice
[13:34] <marcoceppi> cory_fu: I updated the issue, I was projecting on screen when I filed it
[13:36] <Prabakaran> k thanks <lazypower> what is the bug number for the timeout issue?
[13:36] <lazyPower> Prabakaran - I'll need you to file the bug for that :)
[13:36] <Prabakaran> can u help me on how to raise a bug?
[13:36] <lazyPower> Prabakaran - its only hit the list as far as I'm aware of. There was a thread started by  merlijin, but it was specifically in reference to jujucharms.com resources, not local resources on the controller
[13:37] <lazyPower> Prabakaran - sure, start here https://bugs.launchpad.net/juju-core/+filebug
[13:37] <lazyPower> Prabakaran - we'll need the juju version, arch, what you did, what you expected to happen, what happened, associated logs, and reproduction steps
 i am getting timeout error while submitting bug.. " Timeout error  Sorry, something just went wrong in Launchpad.  We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.  Trying again in a couple of minutes might work.  (Error ID: OOPS-4ad94ec13b63a1d16b8f1c05cd6b031b)"
[13:59] <lazyPower> Prabakaran - if you hit the back button in your browser and re-submit does it complete successfully or does it give you the same 500 error?
[14:06] <kjackal> cory_fu: do you want a help in reviewing zeppelin?
[14:07] <magicaltrout> it's a big balloon filled with gas and exploded in flames....
[14:07] <magicaltrout> much like some juju deployments! ;)
[14:07]  * magicaltrout gets his coat
[14:07] <lazyPower> alternatively, its a wicked rockstar group whos music is as timeless as... well.. a zeppelin
[14:07] <cory_fu> kjackal: Yeah, if you want to take a look at it, go ahead.
[14:07] <lazyPower> potentially made from lead even
[14:08]  * lazyPower rimshots and wanders off stage
 i tried twice still i am getting the same... i asked my teammate to raise for the same.. bug number is https://bugs.launchpad.net/juju-core/+bug/1597354
[14:10] <mup> Bug #1597354: Juju 2.0 Resource Error - cannot add resource failed to write data: read tcp : i/o timeout <juju-core:New> <https://launchpad.net/bugs/1597354>
[14:10] <lazyPower> Prabakaran - that makes me want to say it might also be on your end if your tcp connections are timing out
[14:10] <kjackal> cory_fu: cool, I am on it
[14:11] <lazyPower> Prabakaran - perhaps do some network debugging and see if you're experiencing packet loss?
[14:11] <cory_fu> kjackal: thanks
[14:11] <lazyPower> but thanks for the bug, I'll shop this with the core dev release manager to see if they've seen anything like this in testing
 i just pinged from my machine .. there is no packet loss
[14:26] <stokachu> lazyPower: who can i bug for https://bugs.launchpad.net/charms/+source/elasticsearch/+bug/1589947
[14:26] <mup> Bug #1589947: Use status-set when elasticsearch is active and ready <conjure> <elasticsearch (Juju Charms Collection):New> <https://launchpad.net/bugs/1589947>
[14:27] <lazyPower> stokachu - thats going to be fun... you'll have to set that in the middle of the ansible routine
[14:27] <stokachu> ew
[14:27] <lazyPower> yeah
[14:27] <lazyPower> :)
[14:27] <lazyPower> I considered going for a reactive rewrite but time prevented me from doing that
[14:28] <lazyPower> that and our ES charm is pretty solid right now
[14:28] <stokachu> yea
[14:28]  * lazyPower had a bag of bugs to sprinkle around :P
[14:28] <lazyPower> i can try to hammer that out today
[14:28] <lazyPower> should be pretty simple
[14:28] <stokachu> hmm i wonder, juju should just pull from agent status if workload status is undefined
[14:28] <lazyPower> i dont think thats right to just clone the agent status
[14:29] <lazyPower> i'd rather the workload status remain unknown if the author has not put any status messaging in the charm
[14:29] <lazyPower> then its pretty blatant whats happening
[14:29] <stokachu> well you dont really know whats happening as there is no messages :)
[14:32] <stokachu> lazyPower: also seeing this on aws https://paste.ubuntu.com/18101489/
[14:36] <lazyPower> stokachu which revision of ETCD is this?
[14:36] <stokachu> lazyPower: rev3
[14:36] <stokachu> kubernetes is rev5
[14:36] <lazyPower> hmm, flannel biffed it on registering the network
[14:37] <lazyPower> is the instance still up?
[14:37] <stokachu> lazyPower: yea
[14:37] <lazyPower> if so can you ssh-import-id lazypower on that node and hit me with some ip <3?
[14:37] <lazyPower> i'd like to see why that tanked, its been good in CI
[14:37] <stokachu> you want on kubernetes or etcd?
[14:38] <stokachu> or both
[14:38] <lazyPower> both would be good
[14:49] <lazyPower> resource-get
[14:49] <lazyPower> Use 'resource-get' while a hook is running to get the local path to the file for the identified resource. This file is an fs-local copy, unique to the unit for which the hook is running. It is downloaded from the controller, if necessary.
[14:49] <lazyPower> whoops
[15:08] <arosales> stokachu: I am testing the good work you and cory_fu did on ghost
[15:08] <stokachu> arosales: cool!
[15:08] <stokachu> arosales: you should also test the upgrade
[15:09] <stokachu> since it defaults to version 0.7.2 and latest is 0.8.0
[15:09] <arosales> stokachu: recommended wise I see https://jujucharms.com/ghost/precise, but I was wondering if we should reach out to hatch and confirm to promote yours for trusty and xenail
[15:10] <stokachu> yea i'd like to see the reactive charm go recommended
[15:11] <arosales> ok, I don't see hatch here atm but I'll send a mail on it.
[15:11] <arosales> stokachu: thanks
[16:14] <LiftedKilt> jcastro marcoceppi: is there a best guess eta for a final 2.0 release? (are we talking weeks or months?)
[16:14] <LiftedKilt> also - great job on beta10. It's been really smooth for me so far
[16:47] <penguinRaider> Hi, I am running juju 1.25.5-trusty-amd64. If I run a command using juju run which gets timed out, then the next command seems to be getting timed out too even with the greater threshold. I checked it on the machine side it seems both processes seem to be running and stuck http://paste.ubuntu.com/18109177/
[16:51] <bdx> openstack-charmers: how do you guys feel about setting openstack-dashboard session timeout to that of the keystone token expiration?
[16:52] <bdx> openstack-charmers: or possibly a new config "session-timeout" for openstack-dashboard
[17:06] <cargonza> bdx, you should attend the openstack irc meeting in the #ubuntu-meeting
[17:32] <bdx> cargonza: thx, on it
[17:33] <bdx> cargonza: did I miss it?
[17:34] <cargonza> bdx, yup... next week again - https://wiki.ubuntu.com/ServerTeam/OpenStackCharmsMeeting
[17:34] <bdx> awwwwweee
[17:34] <bdx> thanks
[17:34] <bdx> I'll mark my schedule
[17:34] <cargonza> cool!
[17:35] <rick_h_> stokachu: around?
[17:36] <bdx> rick_h_: hey whats up? how are cross-model-relations coming along?
[17:36] <rick_h_> bdx: :P
[17:37] <rick_h_> bdx: stop asking about juju post-2.0 we're still working on 2.0
[17:41] <bdx> rick_h_: shucks ... I was under the impression that was in the 2.0 milestone.  Last we spoke you guys were sprinting on it ... just wondering how its coming along is all
[17:42] <rick_h_> bdx: sorry, it's on the "release after 2.0" one
[17:44] <bdx> no worries
[17:44] <bdx> thanks
[17:49] <LiftedKilt> rick_h_: how is the 2.0 release coming?
[17:49] <bdx> bahaa
[17:49] <bdx> yes
[17:50] <bdx> rick_h_: go easy on him
[17:50] <LiftedKilt> Don't want to be a bother - just curious if there is any idea of a timeline - i.e. weeks vs months
[17:50] <rick_h_> LiftedKilt: weeks, just more than a couple of them :)
[17:51] <LiftedKilt> rick_h_: totally understand - there's a ton going into this release, and I'd way rather it get delayed and the bugfixes added than just rushing to get it out there before it's ready
[17:51] <LiftedKilt> any idea when gui will be beta10 compatible?
[17:54] <jrwren> LiftedKilt: more soon than soonish.
[17:55] <LiftedKilt> jrwren: haha fair enough
[17:58] <stokachu> rick_h_: heyyy
[18:21] <stokachu> conjure-up is beta10 compatible just fyi
[18:21] <stokachu> so is macumba :)
[18:24] <rick_h_> stokachu: <3
[18:26] <stokachu> rick_h_: see my email?
[18:28] <rick_h_> stokachu: yes, sorry, getting pulled into a customer issue atm so kina afk looking at that
[18:33] <stokachu> rick_h_: all good
[18:53] <junaidali> Hi everyone, I'm having an issue in one of my deployments, juju gets the ip of node as public-address. Anyone knows about this issue?
[19:31] <kwmonroe> cory_fu: i'm doing an "if is_state(db.available); do_something(db)", but i can't remember how to get the db object.  halp.
[19:32] <cory_fu> I'd recommend using @when() if at all possible.
[19:32] <cory_fu> If not possible, you have to use RelationBase.from_state('db.available')
[19:33] <cory_fu> But that will make your handler / code harder to unit test
[19:33] <cory_fu> And petevg will get mad at you
[19:33] <kwmonroe> :)
[19:34] <kwmonroe> fair enough.. i was on a kick about condensing reactive handlers so i didn't have stuff like "configure_with_db()" and "configure_without_db()", but whatevs.
[19:35] <petevg> Mocking out RelationBase.from_state isn't the worst thing, for the purposes of unit tests.
[19:35] <petevg> I'm still working out what level of mocking we want to tolerate, though.
[19:36] <kwmonroe> petevg: i don't care what cory_fu says.. you're alright in my book.
[19:36] <petevg> Aw, shucks.
[19:42] <magicaltrout> kwmonroe: https://medium.com/@ecesena/a-quick-demo-of-apache-beam-with-docker-da98b99a502a#.k8dnol49r
[19:42] <magicaltrout> good one  for you guys,  I  mentioned it before I think,  but the blog is a good demo
[19:43] <kwmonroe> yeah - neat magicaltrout.. but there goes my afternoon :/
[19:43] <magicaltrout> you're very welcome ;)
[19:48] <arosales> kwmonroe: to confirm, what were your plans for  cs:~bigdata-dev/xenial/apache-spark-79
[19:48] <arosales> kwmonroe: specifically for promulgating the s390x pieces.
[19:52] <kwmonroe> arosales: i wanted to make sure the rebuilt spark charm didn't break realtime syslog bundle, but i haven't gotten around to bundletesting it with the -dev charms.  i'll kick that off right now.
[19:52] <kwmonroe> if it looks good, i'll promulgate the xenial pieces for spark
[19:53] <arosales> kwmonroe: sounds good, thanks
[19:53] <arosales> kwmonroe: your code never has bugs right
[19:53] <kwmonroe> yeah arosales, but this has some stuff from cory in it too.
[19:54] <arosales> ah, ok
[20:02] <lazyPower> kwmonroe - so they are rocket powered bugs, with heisenbug tendencies
[20:06] <cory_fu> Sorry, I wandered off in the middle of the conversation.  Keep in mind that you can avoid duped code across handlers by calling one directly from the other.  Or by refactoring shared code up into a lib/charms/layer/foo.py library for your charm.
[20:07] <cory_fu> kwmonroe: That said, I just did the optional state plus RelationBase.from_state() approach in https://github.com/battlemidget/charm-layer-ghost/blob/master/lib/charms/ghost.py
[20:08] <cory_fu> See lines 44 and 81
[20:10] <kwmonroe> very cool cory_fu
[20:14] <narinder`> hi all  start from today i am seeing weired issue with juju where public-ip was blank with the service and deployment failed at last. But status says installation in progress.  ceilometer/0            maintenance    executing   1.25.5  2/lxc/0                                (install) Installing packages
[20:23] <bbaqar> hey guys .. is there any way to connect a bridge to a VLAN interface i have created using maas? i.e. bond0.120 -> br-mgmt
[20:33] <kwmonroe> arosales: syslog bundle looks good: http://54.67.62.114:9090/#/notebook/flume-tutorial  rev 10 is ready: https://jujucharms.com/apache-spark/
[20:35] <arosales> kwmonroe: and assuming the current promulgated version is built from https://github.com/juju-solutions/layer-apache-spark it has your latest bits in it, correct?
[20:36] <arosales> to confirm the correct charm publish workflow is:
[20:36] <arosales> charm push .
[20:36] <arosales> charm publish cs:<user>/<charm>-<rev>
[20:36] <arosales> and then a grant to all for read
[20:37] <arosales> charm grant cs:~<user>/<charm> everyone
[20:37] <arosales> My main question is the charm grant is needed or publish to the stable channel does that by default. My testing shows the grant was needed by wanted to confirm that is indeed correct
[20:37] <kwmonroe> arosales: correct in that the current promulgated version is built from that gh link.
[20:38] <arosales> https://jujucharms.com/docs/devel/authors-charm-store is my reference
[20:38] <arosales> kwmonroe: cool thanks
[20:38] <kwmonroe> arosales: ymmv if you're not explicit when you 'charm push .'.  i think by default it will stick the charm in your namespace (ie, ~kwmonroe) based on the distro you pushed from (ie, xenial).  so for spark, i was more explicit: charm push . cs:~bigdata-charmers/apache-spark
[20:39] <kwmonroe> and then it spit back a charmstore url, which is what you feed charm publish
[20:39] <kwmonroe> grant is only needed the first time
[20:39] <kwmonroe> arosales: so i just "charm publish cs:~bigdata-charmers/apache-spark-10", but didn't need to re-grant for that specific revision.
[20:40] <arosales> kwmonroe: ok I was pushing a new charm to my name space and I had to charm grant to deploy it
[20:40] <arosales> kwmonroe: I got an odd Ubuntu One login when I didn't grant, in the terminal no less
[20:40] <arosales> very odd
[20:41] <kwmonroe> arosales: i would bet if you built a new version of that charm, you could push/publish without a re-grant
[20:41] <arosales> kwmonroe: but if I wanted apache-spark in my name space
[20:41] <arosales> I would need to push/publish/grant
[20:41] <kwmonroe> right
[20:41] <arosales> ok
[20:41] <arosales> I didn't think I needed the grant
[20:41] <kwmonroe> (the first time, subsequent times would just be push/publish)
[20:41] <arosales> but  it turns out I do
[20:41] <arosales> ok
[20:42] <arosales> I'll let you return to watching the beam demo now
[20:42] <arosales> thanks for the help kwmonroe
[20:42] <kwmonroe> :)  np
[21:09] <arosales> kwmonroe: got a sec to look at some reactive bits?
[21:09] <arosales> or any other reactive gurus in here
[21:09] <arosales> http://paste.ubuntu.com/18126079/
[21:16] <cory_fu> arosales: The configure method requires a "config" param: https://github.com/marcoceppi/layer-mongodb/blob/master/lib/charms/layer/mongodb.py#L66
[21:17] <cory_fu> arosales: I'm guessing that just needs to be changed to: m.configure(config())
[21:24] <arosales> cory_fu: thanks, I'll give that a try
[21:29] <cholcombe> how do you specify the repository in juju2 like juju1? --repository=blah/blah
[21:29] <magicaltrout> just give it a path to your local charm
[21:30] <cholcombe> mskalka, ^^
[21:30] <magicaltrout> juju deploy /home/charmbuilder/charms/trusty/mynewcharm
[21:30] <cholcombe> magicaltrout, thanks
[21:31] <magicaltrout> no problem.... appears the charmers don't believe in  depreciation of stuff! ;)
[21:31] <cholcombe> lol
[21:35] <petevg> cory_fu: following up on our conversation about unit testing layered charms this morning ... I may push back and say that we really do need to build a layered charm before unit testing it; the code isn't really complete until you do so.
[21:35] <petevg> That said ...
[21:35] <petevg> Behold the horrors that I have wrought: http://paste.ubuntu.com/18127615/
[21:35] <cory_fu> Why?
[21:36] <petevg> Ask again after you read the module I linked above :-)
[21:36] <petevg> That code actually works, and it handles the issue where I want to import the "real" charms.layer.apache_bigtop_base in my test while mocking out charms.layer.options
[21:36] <petevg> *case (not issue)
[21:37] <petevg> Here's the top of my test class, to give an example of actually using it: http://paste.ubuntu.com/18127718/
[21:40] <petevg> cory_fu: I'd like to spend a little more time writing tests with the thing that I linked above, just to see how weird or messy it gets in practice. It may be cleaner to just tell people to build the charm and then run "make unit_test", though ...
[21:45] <igonl> Any good references or methods for negotiating a relation that sets up a database charm with a web application?
[21:45] <petevg> I am happy about having written something that involves a closure, hacking the sys module, and monkey patching import. I'm not sure that it's the right kind of happy, though ...
[21:45] <igonl> What's the best way to pass around the credentials?
[21:46] <igonl> I'm familiar with lifecycle hooks, but I'm new to relation hooks.
[21:51] <petevg> igonl: if you're writing a charm, you can use relation-get to fetch things like the password, which the database charm will generally generate for you. Take a look at the "database-relation-changed" from the walk-through for reference: https://jujucharms.com/docs/1.25/authors-charm-writing
[21:52] <petevg> If you're writing a layered charm, things are a little bit different. It doesn't sound like that's what you're doing, though.
[21:53] <magicaltrout> igonl: i might have something
[21:53] <igonl> Yah, that looks good. I've found relation-get and relation-set helper methods.
[21:53]  * magicaltrout greps around launchpad
[21:54] <cory_fu> petevg: https://github.com/juju-solutions/layer-apache-bigtop-base/commit/a4c1b8355c9032d0e7f577af9ecc92e25e93f9e7
[21:54] <igonl> Docs do stress that they run out of order though and to not rely on anything from those methods being there. Then something about the -relation-changed being the best place to get variables.
[21:55] <igonl> I did test the out of order bit to be true using `sleep` to change the writes to a file.
[21:55] <cory_fu> petevg: That works for me.  The pre-import of charms.layer and the create=True are both critical, though
[21:55] <igonl> I can't use Layers as it's built in python and I'm sticking with Bash-only.
[21:56] <petevg> cory_fu: Yep. I was going for something where we could generate a list of all the things that we need to mock, and pass it in all at once, rather than ending up with a cascading layer cake of "with" statements.
[21:56] <magicaltrout> igonl: http://bazaar.launchpad.net/~spicule/charms/trusty/saikuanalytics-enterprise/trunk/view/head:/hooks/mysqldb-relation-changed
[21:56] <magicaltrout> i use that to get mysql details and store them in  a file inside my charm install
[21:56] <petevg> igonl: no pressure to use layers -- I just wanted to make sure that was wasn't pointing you at bash when you were looking at Python :-)
[21:57] <igonl> magicaltrout: I like the juju log message in that script, thanks.
[21:57] <cory_fu> petevg: My point was that I think we can avoid having to mock builtins.__import__
[21:58] <igonl> I was interested in if any usage of the environment variables provided were being used in such charm conversations. $JUJU_REMOTE_UNIT
[22:01] <petevg> cory_fu: We could actually hide multiple calls to .patch in a context, so it would look something like 'with mock_modules([<some list o' modules]): import ...'  I think that mocking out __import__ is more fun, but it is probably a better idea to leave it alone.
[22:03] <cory_fu> Hrm.  It seems like removing the pre-import of charms.layer works ok after all
[22:04] <petevg> It should. I was only pre-importing it in my code because I wanted it in sys.modules.
[22:04] <cory_fu> Sometimes package namespaces work strangely
[22:04] <petevg> ... before I did my module hacking, that is.
[22:04] <cory_fu> Anyway, I have to EOD
[22:04] <petevg> Cool. I am going to do the same soon. Catch you later.
[22:04] <cory_fu> petevg: I got about 1/4 of the way through reviewing your hiera layer change.  :p
[22:05] <cory_fu> I'll finish it first thing tomorrow
[22:08] <kwmonroe> igonl: just fyi, you can write bash layers.. openjdk is an example bash charm: https://github.com/juju-solutions/layer-openjdk/blob/master/reactive/openjdk.sh
[22:10] <kwmonroe> igonl: i should note that interfaces need to be in python, but the charm layers can be in bash.
[22:10] <igonl> kwmonroe: had no idea. Must of developed the bad assumption off of what the docs showed and from the charms I browsed. Thanks.
[22:11] <plars> anyone seen a situation where the bootstrap node gets *very* high load average? We had a power outage recently, and the maas cluster I'm using came back ok but it was slow to do anything with juju
[22:11] <plars> after many failed attempts, I was finally able to ssh to the bootstrap node and it had a load avg near 500!
[22:11] <igonl> Ya'll Ill take another look at layers. They did seem like one more layer of abstraction I didn't want to deal with when learning charms.
[22:12] <plars> syslog is getting flooded with a lot of messages like this:
[22:12] <plars> Jun 29 22:12:08 limited-club mongod.37017[20063]: Wed Jun 29 22:12:08.533 [conn918] update presence.presence.pings query: { _id: "e548e092-a274-46ef-8ed7-089b1cb954d7:1467238320" } update: { $set: { slot: 1467238320 }, $inc: { alive.36: 4294967296 } } nscanned:0 idhack:1 nupdated:1 fastmodinsert:1 keyUpdates:0 locks(micros) w:116225 116ms
[22:12] <plars> (and many more, all from mongod)
[22:12] <plars> restarting juju-db brings it down for a little while, but it always creeps back up
[22:12] <igonl> kwmonroe: btw that's some clean code you wrote there.
[22:13] <kwmonroe> THANKS igonl!  see magicaltrout?  i do good things.. ^
[22:14] <magicaltrout> i never said you didn't kwmonroe
[22:14] <kwmonroe> too right magicaltrout, too right.
[22:14] <kwmonroe> chip chip cheerio
[22:14] <magicaltrout> i just defer to cory_fu when it comes to you explaining the stuff you've done :P
[22:14] <kwmonroe> lolz
[22:19] <magicaltrout> ah its still online!
[22:19] <magicaltrout> kwmonroe: http://www.whoohoo.co.uk/cockney-translator.asp
[22:19] <magicaltrout> that is more important than apache beam
[22:20] <kwmonroe> oh hairy biscuits
[22:30] <kwmonroe> hey kjackal admcleod, on the off chance you're online.. how long should a hbase perf-test take on aws?
[22:31] <kwmonroe> ha!  nm, just returned in 1300 seconds.. i guess that's how long.
[22:32] <magicaltrout> i believe what you really mean is  kjackal admcleod, on the Frank Bough chance you're online.. 'a long should a 'base perf-test take on aws?
[22:34] <kwmonroe> :)  that's exactly what i meant
[22:35] <magicaltrout> of course
[22:35] <magicaltrout> you have to bear in mind admcleod 's scottish background
[22:36] <magicaltrout> Guid day kjackal admcleod, oan th' aff chance yoo're online.. hoo lang shoods a hbase perf-test tak' oan aws?
[22:36] <magicaltrout> would be better