[05:53] <junaidali> is there a command that can get the current focused model?
[05:54] <junaidali> ah, got it. I missed the show-model command
[07:42] <kjackal> good morning juju world!
[11:23] <rick_h> junaidali: yes, and if you list-models or just models the current one should have a * on it
[11:33] <anrah> Quick question about update-status hook
[11:33] <anrah> It seems when using reactive charms it runs all reactive decorators what are available then?
[11:34] <anrah> can I somehow avoid this?
[11:42] <kjackal> anrah: yes, supose you have a method that should be run only once. inside that method you should do something like set_state('method.called') and you should decorate that method with "when_not('method.called')"
[11:47] <anrah> so I can use decorators inside methods?
[11:57] <kjackal> anrah: you can declare states inside your methods. Then you can guard aganst these states with the appropriate decorators
[11:57] <kjackal> let me find an example
[11:58] <kjackal> anrah: https://github.com/juju-solutions/bigtop/blob/master/bigtop-packages/src/charm/mahout/layer-mahout/reactive/mahout.py#L23
[11:58] <kjackal> here we make sure mahout is installed only once
[11:58] <anrah> yep
[11:59] <anrah> that is familiar
[11:59] <anrah> Problem right now is that I use layers and somerelation.connected part gets executed multiple times
[13:59] <jcastro> rick_h: I have to hit the road late next week, but perhaps we should do an office hours before then?
[14:04] <rick_h> jcastro: on the calendar tomorrow
[14:05] <jcastro> rick_h: did I miss an announcement on a list?
[14:06] <rick_h> jcastro: was going to today
[14:06] <rick_h> jcastro: on my todo to chat with you about it but been in calls today
[14:06] <rick_h> jcastro: started updating the doc with a script
[14:07] <jcastro> yeah I have calls all day
[14:07] <jcastro> ok so you just want me to rally my folks and we'll talk about whatever?
[14:07] <rick_h> jcastro: yea, but have some topics I want to walk through
[14:07] <jcastro> ack I see them
[14:18] <rick_h> jcastro: so yea, I wanted to see what else you wanted to add.
[14:18] <rick_h> jcastro: and see if anyone wants to join
[14:18] <rick_h> jcastro: and that's on the calendar for tomorrow, are you able to send an email or should I?
[14:21] <jcastro> go for it
[14:21] <jcastro> I'll add content to your notes
[14:22] <rick_h> jcastro: k, ty
[14:22] <jcastro> kwmonroe: any new hotness from BD I should include?
[14:28] <rick_h> jcastro: is there any sort of HO link/etc we can put into the email? How's that working these days?
[14:28] <jcastro> hmm, let me think
[14:28]  * rick_h recalls you chatting with someone that it's not hangout on air any more but more a public youtube thingy?
[14:29] <jcastro> yeah they changed it
[14:29] <jcastro> https://www.youtube.com/my_live_events as the juju users
[14:30] <jcastro> I'll add it now
[14:30] <rick_h> ah, gotcha
[14:32] <jcastro> oh man, this is actually way better
[14:33] <jcastro> https://www.youtube.com/watch?v=wo23ZXwa8ZU is the URL for tomorrow
[14:33] <jcastro> that's handy
[14:33] <jcastro> it doesn't let me select a hangout though unless I go live, so I guess we'll get that URL before we start
[14:34] <jcastro> rick_h: oh nice bonus, it announced the upcoming office hours in my subscription feed as "Upcoming" with the time and date, that's really awesome.
[14:34] <rick_h> jcastro: sweet
[14:36] <jcastro> rick_h: the bottom of your mail encourage people to just subscribe to the YT channel, then from now on they'll get a notification when we go live
[14:36] <jcastro> that's an easy way to get caught up to date without too much overhead, for people who want to keep up but not necessarily participate.
[14:37] <rick_h> jcastro: k, is there any hint on how folks can join the HO?
[14:37] <jcastro> not afaict, what we usually do is fire it off early and then put the URL here
[14:37] <rick_h> jcastro: so just tell them "a hangout link will be made available in #juju or something?
[14:37] <jcastro> right
[14:37] <rick_h> k
[14:37] <jcastro> that's exactly what we do
[14:39] <jcastro> rick_h: it has a setting for hangouts, and then it has another setting for custom encoders
[14:40] <jcastro> that means we could each OBS into one stream, we should experiment with that in the future, that's how the pros do the multi-stream deals
[14:40] <rick_h> jcastro: any feedback let me know: https://pastebin.canonical.com/172188/
[14:40] <jcastro> lgtm, I did rename the session to The Juju Show though
[14:40] <jcastro> sounds cooler
[14:41] <rick_h> hah ok
[14:42] <rick_h> jcastro: k, sent
[14:43] <rick_h> jcastro: let me know of any other topics you want to toss up and see you tomorrow for it?
[14:43] <jcastro> yeah I'll add more post-daily call, I need to round up some status from folks
[14:43] <rick_h> jcastro: rgr ty
[16:10] <arosales> marcoceppi: hello
[16:13] <marcoceppi> o/
[16:13] <arosales> marcoceppi: if you have some time could you merge (if appropriate) and push updates to nagios from the following MPs
[16:13] <arosales> https://code.launchpad.net/~majduk/charms/trusty/nagios/branch/+merge/304492
[16:13] <arosales> https://code.launchpad.net/~dbuliga/charms/trusty/nagios/nagios/+merge/288614
[16:13] <arosales> I think petevg has reviewed the later
[16:14]  * wxl is sad there's no juju snap
[16:14] <magicaltrout> eh?
[16:15] <wxl> i was going to set up a quick vm to test a little wordpress thingy. idea was get ubuntu snappy core in a vm which happens almost immediately, and then install the juju snap so i could grab the wordpress charm. but no such snap exists.
[16:16] <magicaltrout> balloons: jcastro
[16:16] <petevg> wxl: I believe there is a juju snap, though it's still under development: `snap install juju --beta --devmode`
[16:16] <balloons> wxl, there is, it's just in the beta channel
[16:17] <wxl> amd64 only tho yeah?
[16:17] <balloons> right, it's in beta because it requires devmode still
[16:17] <balloons> nope, all supported arches
[16:17] <wxl> yeah weird i can't find it
[16:17] <balloons> snap find won't find it.. just install
[16:17] <wxl> no i mean i tried to install it and it says it can't find it
[16:18] <wxl> this is an i386 core fwiw
[16:18] <balloons> i386 is not a supported arch
[16:18] <wxl> not supported by juju?
[16:18] <arosales> jcastro: to confirm juju office hours is tomorrow, correct?
[16:18] <balloons> wxl, correct
[16:18] <wxl> ah, k
[16:18] <wxl> thanks :)
[16:19] <balloons> wxl, :-) Can you not use the amd64 client?
[16:19] <wxl> probably. unfortunately i've been hobbling along on this i386 install that i've sort of multiarched to amd64 but it's a real pain dealing with all the apps. just been too lazy to do a new install
[16:20] <wxl> so i'll see :) thanks for the help guys
[16:20] <wxl> and gals :)
[16:21] <magicaltrout> i386? makes me feel old
[16:24] <rick_h> arosales: yes, tomorrow
[16:27] <marcoceppi> arosales: well there's larger problems there
[16:27] <marcoceppi> those rely on ingestion
[16:30] <jcastro> arosales: yep
[16:50] <wxl> reading through https://jujucharms.com/docs/stable/getting-started
[16:50] <wxl> is bootstrap a necessity regardless of whether or not you're using lxd?
[16:52] <wxl> seems that the lxd snap is in devmode too
[16:52] <wxl> s/dev/mode/beta/
[16:55] <wxl> unfortunately it doesn't seem to add the lxd group
[16:58] <jcastro> Using the snapped juju with the snapped lxd doesn't work yet
[16:58] <jcastro> It's on their roadmap though last time I checked
[16:58] <jcastro> ideally you'd get the entire thing from snaps and be good to go
[16:59] <wxl> jcastro: but tl;dr juju does require lxd, no?
[16:59] <magicaltrout> no
[16:59] <magicaltrout> unless you want to use lxd ;)
[16:59] <wxl> oh
[16:59] <wxl> ok well i don't give a hoot about that. :)
[16:59] <magicaltrout> bootstrap will just launch a controller node on your given cloud
[16:59] <magicaltrout> or lxd provide
[16:59] <magicaltrout> r
[16:59] <jcastro> oh, if you don't care about that then you can just use it to deploy to AWS or whatever
[17:00] <magicaltrout> so you do need to bootstrap but its not lxd specific
[17:00] <jcastro> `juju bootstrap aws/us-east-2` for example
[17:00] <wxl> oic well given that i'm running off of a cloud image in virtualbox, i guess i do need it XD
[17:00] <wxl> s/cloud/snappy-core/
[17:05] <jrwren> wxl: it should work VERY well on a cloud image in virtualbox, but I don't use snaps for anything.
[17:07] <wxl> jrwren: yeah i'm aiming for "quickest way to a local wordpress install" and right now the issue is apparently that the snaps need work still.
[17:11] <jrwren> wxl: which snaps?
[17:11] <wxl> jrwren: specifically the issue is with the lxd snap, which admittedly in beta, but it doesn't add the lxd group and there's no easy way to do that in snappy's locked down environment
[17:12] <jrwren> wxl: is there a reason to use the lxd snap and not deb package? apt install lxd works very well for me.
[17:13] <wxl> jrwren: well snappy core relies entirely on snaps. the reaosn i want to use snappy core is i can download an image and have it running in minutes, versus going through a whole install.
[17:13] <wxl> jrwren: realize this is an "ideal world" kind of thing. it's not a complaint about juju or snappy. development just hasn't got ther eyet
[17:13] <jrwren> wxl: oh! I missed the snappy core part. I only saw the "reading through https://jujucharms.com/docs/stable/getting-started"
[17:14] <wxl> jrwren: yeah sorry for the confusion. i'm an odd case for sure :)
[17:15] <arosales> jcastro: rick_h thanks. If possible I would like to talk about review queue and charm testing
[17:16] <arosales> marcoceppi: re nagios and dep on ingestion, sorry I didn't parse that
[17:17] <marcoceppi> arosales: it's a ~charmers charm, it's not been taken over by anyone
[17:17] <marcoceppi> and we can't just update the store, its a charm that relied on ingestion that no one has taken over
[17:19] <arosales> marcoceppi: ah, but your listed as a maintainer
[17:19] <arosales> I thought we pushed fixes to this already....
[17:19] <marcoceppi> i guess I could just move this to my name on charmstore
[17:19] <marcoceppi> though I'm really no longer the maintainer
[17:20] <arosales> Well I normally ping maintainers to do this
[17:20] <marcoceppi> arosales: maintainers in the yaml file really means nothing
[17:20] <marcoceppi> it's the person that matinained it at one point in time
[17:20] <marcoceppi> it's really about the owner in the charm store now
[17:20] <arosales> It's the best we have thus far to mark a maintainer
[17:21] <marcoceppi> arosales: but I'm telling you, I've not been maintaining it
[17:21] <arosales> marcoceppi: in any case if you would no longer like to maintain could you email the list?
[17:21] <marcoceppi> it's essentially, unmaintained
[17:21] <arosales> Gotcha
[17:22] <arosales> We have some contributions on it so I'll ping ~charmers to merge and push for now
[17:22] <marcoceppi> arosales: you're missing the point
[17:22] <marcoceppi> we can merge it sure
[17:22] <marcoceppi> but it'll never get into the store
[17:23] <arosales> Sorry, I do understand
[17:23] <arosales> We need to land the fix in LP
[17:23] <marcoceppi> but that fixes nothing in the store
[17:23] <arosales> And the push that code to the store
[17:23] <marcoceppi> the second half needs a maintainer
[17:23] <petevg> bcsaller, cory_fu: Do either of you mind if I push a new build of python-libjuju to matrix's wheelhouse?
[17:23] <marcoceppi> someone other than ~charmers, and I'm not an active maintainer
[17:23] <arosales> Sorry me typing on a phone atm
[17:24] <arosales> marcoceppi: ok, could we
[17:24] <arosales> start by you emailing the list looking for a maintainer?
[17:25] <marcoceppi> sure
[17:25] <arosales> Perhaps there is someone untested in maintaining
[17:25] <arosales> marcoceppi: thanks
[17:25] <magicaltrout> i'm interested in maintaining it
[17:25] <arosales> Untested = interested
[17:25] <magicaltrout> because i use it and i know of a couple of other issues that I've patched
[17:25] <arosales> Looks
[17:26] <arosales> Like we have a winner :-)
[17:26] <arosales> marcoceppi: ^ petevg ^
[17:26] <marcoceppi> magicaltrout: if you want to create a public repos *somewhere* I'll merge these two things, convert it to git and hand it over
[17:27] <arosales> marcoceppi: magicaltrout thanks!
[17:27] <magicaltrout> marcoceppi: i can just push the code to github then?
[17:27] <marcoceppi> magicaltrout: as the *previous* maintainer, yes
[17:29] <marcoceppi> magicaltrout: if you set up a repo, I'll push over the latest code
[17:31] <magicaltrout> https://github.com/buggtb/nagios-charm
[17:31] <magicaltrout> shove it in there marcoceppi
[17:34] <marcoceppi> magicaltrout: what email address do you want to use as maintainer?
[17:39] <magicaltrout> tom@spicule.co.uk please marcoceppi
[17:40] <marcoceppi> magicaltrout: cool
[17:44] <marcoceppi> magicaltrout: okay, pushed
[17:45] <marcoceppi> magicaltrout: if you want to push that to the store, I'll move the promulgated name to you
[17:47] <cory_fu> petevg: Nope
[17:48] <petevg> cory_fu: you referencing my comment on the hadoop-processing issue? Or is it just a general "nope"?
[17:49] <petevg> cory_fu: oh, right. You're answering my question. I had forgotten that I had asked it :-)
[17:49] <cory_fu> petevg: :)
[17:50] <petevg> cory_fu, bcsaller: Pushed an updated python-libjuju .whl to matrix master. Please pull and rebase if you want to deploy fancy bundles :-)
[17:53] <bcsaller> petevg: thanks
[19:00] <kwmonroe> lazyPower: mbruzek:  matt's note said charmbox:devel was going away.  can we keep it and build a jujubox:devel that pulls from ppa:juju/devel?  it'd be nice to have a juju/charmbox with 2.1-betaX
[19:02] <mbruzek> kwmonroe: make a pull request if you want that and we will review
[19:03] <lazyPower> kwmonroe: we're kind of booked with what we're supporting already. Matts suggestion is what i would recommend, that if you can contribute the Dockerfile and a minimal test (See matts latest pr) we could reasonably get that in and accounted for in the automation.
[19:12] <magicaltrout> sorry marcoceppi https://jujucharms.com/u/spicule/nagios-charm
[19:12] <magicaltrout> done
[19:14] <marcoceppi> magicaltrout: can you push it as jujucharms.com/u/spicule/nagios ?
[19:19] <magicaltrout> boo
[19:19] <magicaltrout> yeah
[19:19] <magicaltrout> dunno why i did that :)
[19:20] <magicaltrout> done
[19:23] <magicaltrout> whats the charm grant command to revoke access?
[19:29] <marcoceppi> magicaltrout: revoke
[19:32] <magicaltrout> ah up a level i was still looking in the grant menu
[19:41] <marcoceppi> magicaltrout: done
[19:46] <magicaltrout> joy
[20:17] <kwmonroe> lazyPower: mbruzek:  local build looks good with 2.1-beta1.  here's a pr to bring devel inline with master (plus a couple commits to add ppa:juju/devel).  this will affect cwrbox, so you may want to hold off until https://github.com/seman/cwrbox/pull/2 is merged.
[20:17] <kwmonroe> https://github.com/juju-solutions/jujubox/pull/28
[20:17] <lazyPower> nice
[20:17] <lazyPower> thanks kwmonroe
[20:18] <kwmonroe> np.. nice job on travis integration!
[20:19] <lazyPower> thats all matt :0
[20:33] <cory_fu> bcsaller: So, I'm using async for the charm archive download and all, but I can't figure out a way to extract the zip in an async way.  Also, fetching the archive URL involves a non-async call to the charm store API, which we have seen hit a 10s timeout in tests.  I guess my only option on those is run_in_executor?
[20:59] <tvansteenburgh> cory_fu: that's what i would do (for both)
[21:48] <lazyPower> marcoceppi: Cynerva: ryebot: - https://k8s-gubernator.appspot.com/build/canonical-kubernetes-tests/logs/e2e-node/1122_17:10:48.000    despite the fact we're not officially merged, with some url hax, we're totally in the dashboard :P
[21:49] <ryebot> lazyPower: Sweet!
[22:06] <pcdummy> What are the minimum specs needed for Juju? (To try it out) ?
[22:12] <marcoceppi> pcdummy: if you're using the lxd provider,  4 cores and 8gb ram
[22:12] <marcoceppi> otherwise, a cloud provider
[22:19] <pcdummy> marcoceppi: thanks
[22:19] <pcdummy> Will install Juju the coming days and give it a try.
[22:20] <marcoceppi> pcdummy: cool, if you need cloud credentials, sign up for the developer program: https://developer.juju.solutions
[22:21] <pcdummy> marcoceppi: juju will give me something like that: https://drawstack.github.io/qxjoint/ ? :)
[22:23] <pcdummy> marcoceppi: that was a fun project i was working on (should be a interface for LXD in conjunction with saltstack).
[22:25] <lazyPower> pcdummy: correct, however juju is application centric view in the GUI instead of machine/container centric.
[22:25] <marcoceppi> pcdummy: it will give you something...similar
[22:37] <pcdummy> NICE
[22:37] <pcdummy> I'll give it certainly a try.
[23:14] <pcdummy> juju has no live migration of containers?
[23:15] <rick_h> pcdummy: no, it does not currently
[23:17] <pcdummy> So downtimes on maintenance of the host, if the app isn't scaleable/loadbalanced/whatever.