[00:26] <lazyPower> I just noticed that it became possible to remove a subordinate relation *hattip* ty for that gents
[00:44] <rick_h_> lazyPower: coolio
[00:45] <lazyPower> rick_h_: i'm probably lagging behind in the features landing in gui. Hows things on your side o the fence?
[00:46] <rick_h_> lazyPower: going well, antonio pointed out a giant bug today but docs now update and http://juju.ubuntu.com/ is a cool new place now :) 
[00:46] <lazyPower> rick_h_: intredasting. are you aware that the /docs still links to the old docs?
[00:47] <lazyPower> (it auto completed.... maybe i'm being picky)
[00:47] <lazyPower> but i dig that its all redirecting to jujucharms.com now, thats groovy baybeh
[00:55] <rick_h_> lazyPower: the docs should be redirected as well
[00:55] <lazyPower> might be caching on my side
[00:55] <rick_h_> so have to bring that up I guess
[00:55] <lazyPower> i seem to find all those fun "you had something cached" issues
[00:56] <rick_h_> naw, it's just they just did it today so missed something there
[00:58] <rick_h_> rt replied to
[00:58] <rick_h_> so hopefully fixed up tomorrow
[12:19] <dimitern> hey guys
[12:20] <dimitern> someone familiar with quickstart can perhaps tell me were there any changes needed after the fix for bug 1420403 landed in juju-core (1.21, 1.22, and trunk)
[12:20] <mup> Bug #1420403: juju-quickstart: bad API server response: 'NoneType' object is not iterable <api> <ci> <network> <regression> <juju-core:Fix Released by frankban>
[12:20] <mup> <juju-core 1.21:Fix Released by frankban> <juju-core 1.22:Fix Committed by frankban> <juju-quickstart:Invalid by frankban> <https://launchpad.net/bugs/1420403>
[12:21] <frankban> dimitern: no, no changes required on the client side
[12:22] <dimitern> frankban, that's what I remember as well - is quickstart using lp:python-jujuclient internally?
[12:22] <frankban> dimitern: it is
[12:23] <dimitern> frankban, and the client also didn't need to change right?
[12:28] <dimitern> frankban, I doesn't seem like jujuclient changed since before the fix - just looking at the code
[12:28] <frankban> dimitern: correct
[12:29] <dimitern> frankban, thanks!
[12:29] <frankban> dimitern: was the fix released?
[12:29] <dimitern> frankban, well, 1.21.3 is released, which includes the fix, but jamespage today reported this bug 1425435
[12:29] <mup> Bug #1425435: juju-deployer/jujuclient incompatibility with 1.21.3 <api> <network> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1425435>
[12:31] <frankban> dimitern: I still get "Ports":null with 1.22-beta3
[12:32] <dimitern> frankban, that's expected - 1.22-beta3 was released before the fix
[12:33] <dimitern> frankban, hmm.. actually according to the changelog it should have the fix
[12:34] <dimitern> frankban, something's wrong here.. I'll investigate more
[12:37] <dimitern> frankban, ah, I see the problem - 1.22-beta3 includes my original fix for bug 1418433 which you then improved as part of fixing bug 1420403
[12:37] <mup> Bug #1418433: unit ports not populated by API megawatcher <api> <regression> <juju-core:Fix Released by dimitern> <juju-core 1.21:Fix Released by dimitern> <juju-core 1.22:Fix Released by dimitern> <juju-gui:Invalid> <https://launchpad.net/bugs/1418433>
[12:37] <mup> Bug #1420403: juju-quickstart: bad API server response: 'NoneType' object is not iterable <api> <ci> <network> <regression> <juju-core:Fix Released by frankban>
[12:37] <mup> <juju-core 1.21:Fix Released by frankban> <juju-core 1.22:Fix Committed by frankban> <juju-quickstart:Invalid by frankban> <https://launchpad.net/bugs/1420403>
[12:40] <frankban> dimitern: so we don't have a release with the subsequent fix?
[12:44] <dimitern> frankban, 1.21.3 should have both, but apparently there's still a problem
[12:44] <dimitern> frankban, can you do a quick test with 1.21.1 from the stable juju ppa?
[12:48] <dimitern> frankban, sorry, I meant 1.21.3, not 1.21.1
[12:48] <dimitern> (the latest available)
[13:06] <frankban> dimitern: doing it now
[13:29] <frankban> dimitern: it works with 1.21.3-utopic-amd64 from the stable PPA
[13:30] <dimitern> frankban, great! thanks for confirming
[13:30] <frankban> dimitern: so new release landed in stable but not in devel?
[13:31] <dimitern> frankban, that's one possibility, another one that's bugging me is the issue might be still there if you upgrade from 1.21.1 to 1.21.3 - I'm testing this now
[13:32] <frankban> dimitern: it wasn't working on my local machine with a fresh environment using the latest devel version, so I presume devel does not have the fix
[13:33] <dimitern> frankban, oh, that's weird, but easier to check - cheers, I'll look into the devel ppa
[13:34] <frankban> dimitern: ty
[14:07] <jcastro> hey rick_h_
[14:07] <jcastro> have we talked about CIing all the bundles on that page on a regular basis?
[14:07] <jcastro> we as in us collectively, not you you. :)
[14:10] <rick_h_> jcastro: it's brought up. There's the bundletester stuff and charm testing is supposed to look at bundles once the charm stuff is good, but I've no idea where that's at to be honest
[14:10] <jcastro> yeah also we have another problem
[14:11] <jcastro> bundles and all that jazz will work fine in AWS/Azure, etc.
[14:11] <jcastro> then you go onsite with an OB and boom
[14:11] <rick_h_> boom because? 
[14:12] <jcastro> whatever issue is local that we can't reproduce in a cloud, for example this weekend we had a squid problem on an OB
[14:12] <jcastro> and it didn't matter if the bundle worked or not, the entire thing needed to be hand held
[14:12] <jcastro> I guess I am just saying that just testing bundles in the public cloud isn't good enough
[14:13] <rick_h_> jcastro: ok, good to know. We can look into doing some OB testing on things. I know they've set some up over a company vpn and maybe we can get some time to figure out what's up and correct it if it's a regular isue. 
[14:14] <rick_h_> hatch: ping when you're in, frankban brought up a good point on the promulgated bundles and that the id there is just the bundle name. 
[14:38] <hatch> rick_h_: that's not a problem though is it?
[14:38] <hatch> and good morning :)
[14:38] <rick_h_> hatch: no, not a problem just wanted you to make sure you kept that in mind during dev/qa
[14:38] <rick_h_> hatch: as we only talked about u/xxxxx/name urls yesterday
[14:39] <hatch> yeah, this is what I came up with https://gist.github.com/hatched/3613d21af62ca9c221ed
[14:39] <hatch> I think that it'll work for all different formats
[14:40] <rick_h_> hatch: cool will QA that then. I'll work to bring up a storefront/gui together and test out the 'add to demo' and the commands across a bunch of bundles once we're ready
[14:41] <hatch> sounds good - I'm just writing the GUI tests right now for this then I'll be hopping on the storefront
[14:41] <rick_h_> ty
[15:54] <hatch> rick_h_: the GUI PR is up https://github.com/juju/juju-gui/pull/697
[17:38] <hatch> uiteam could I get a review on https://github.com/juju/juju-gui/pull/697 thx
[17:38] <rick_h_> hatch: looking
[17:38] <hatch> thanks
[17:38] <rick_h_> two cancelled calls in a row ftw! :)
[17:39] <hatch> haha less walking though
[17:49] <frankban> dimitern: any news on the Ports problem?
[17:53] <dimitern> frankban, not really - I've investigated thoroughly, couldn't reproduce it and reported my comments in bug 1425435
[17:53] <mup> Bug #1425435: juju-deployer/jujuclient incompatibility with 1.21.3 <api> <network> <oil> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1425435>
[18:07] <frankban> dimitern: ack, ty
[18:52] <hatch> great talk lazyPower 
[18:53] <lazyPower> Thanks hatch :)
[18:54] <hatch> lazyPower: do you find people understand the ansible charms better than bash ones?
[18:54] <hatch> I would have assumed a bash/python charm would be easier to grok
[18:57] <lazyPower> hatch: Ansible is really well documented and gives you a lot of batteries out of the box in terms of idempotency, and logic structures
[18:57] <hatch> is it the 'popular' one now? vs chef and whatnot
[18:57] <lazyPower> i'm trying to campaign to get ppl using proper config management rather than spawning these behemoth toolbox libraries (like we have in charmhelpers) where cm tools have already solved this problem.
[18:58] <lazyPower> eh, its a bit of preference, yaml is easier to learn than ruby + DSL's for chef/puppet - but puppet is still hands down the 800lb gorilla in the room
[19:00] <hatch> ahh
[21:25] <lazyPower> hatch: do you know if rick_h_ is still around?
[21:26] <hatch> lazyPower: your guess is as good as mine :) 
[21:27] <hatch> if he is I'm sure he'll poke his head in now that you have dinged
[21:27] <lazyPower> ok, just curious if he had an emergency to run out for
[21:27] <lazyPower> well i feel bad now, i've dinged him in 3 places :(
[21:27] <lazyPower> my name is going to be synonymous with a curse word before long...
[21:27] <hatch> lol
[21:27] <lazyPower> man.. chuck that.
[21:27] <hatch> nah you have a long way to go yet
[21:27] <lazyPower> thats the chuckest thing i've heard all day
[21:29] <hatch> Makyo: you able to do a qa on my PR?
[21:30] <Makyo> hatch, sure, I'm spinning my wheels as it is
[21:30] <hatch> break time! :)
[21:31] <Makyo> Got the PR number off the top of your head?
[21:32] <hatch> https://github.com/juju/juju-gui/pull/697
[21:32] <hatch> one better :)
[21:32] <Makyo> Thanks
[21:38] <Makyo> hatch, LGTM (though maybe in the future, we want the "Location:" link in the header might need to be update din the future)
[21:38] <hatch> Makyo: yeah tbh I have no idea what the purpose of that is anymore
[21:39] <hatch> it's always been a thorn for me
[21:39] <Makyo> I think it made more sense in an earlier iteration.
[21:39] <Makyo> Oh well, something for another time.
[21:39] <rick_h_> lazyPower: yes, was on the phone doing manager stuff for a bit :P
[21:40] <lazyPower> yeah sorry about the ping crazyness :( 
[21:41] <rick_h_> grr, this sysdeps thing is not working for me here
[21:42] <rick_h_> ah crap, vivid lxc container FML
[21:42] <rick_h_> hatch: have no QA for you atm, have to start over sorry
[21:42] <rick_h_> and uploading GB of stuff for lazyPower is making this brutal
[21:42] <hatch> :) np Makyo is on it
[21:42] <rick_h_> hatch: please get QA from gui from someone else
[21:43] <rick_h_> ty Makyo 
[21:43] <lazyPower> GIVE ME ALL YOUR BANDWIDTH MWAHAHA
[21:43] <lazyPower> rick_h_: if its a better option - just hit me with what you're working on now, the others can wait until an overnight xfer
[21:44] <rick_h_> lazyPower: np, Makyo has my back and I'm going to feed the dog/etc and just let the bandwidth go
[21:44] <lazyPower> 10-4
[21:44] <rick_h_> should see the sharepoint iso showing up now 
[21:44] <rick_h_> and then you'll have to wait forever on my upstream to pull it from guimaas
[21:44] <rick_h_> run that overnight heh
[21:44] <lazyPower> i feel like we've reverted to 90's style transfer of files....
[21:44] <lazyPower> like, xdcc
[21:44] <lazyPower> fxp
[21:44] <hatch> haha
[21:44] <lazyPower> all pre bt options
[21:45] <hatch> eff tee pee
[21:45] <hatch> ess eff tee pee 
[21:45] <hatch> :)
[21:45] <lazyPower> hatch: pleb - distribution hubs used server => server transfers :P
[21:45] <hatch> haha
[21:46] <lazyPower> i'm not going to say how i know this... but it might be from the scene... http://www.welcometothescene.com/
[22:00] <huwshimi> Morning
[22:00] <rick_h_> morning huwshimi 
[22:01] <rick_h_> lazyPower: ok, best of luck downloading now 
[22:01] <lazyPower> ta rick_h_, cheers!
[22:06] <Makyo> hatch, the more I think about it, the more we might want to escalate the Location link, since it's no longer the same as the deploy link.
[22:06] <Makyo> hatch, I mean before the design stuff in the pipeline.
[22:06] <hatch> Makyo: I always thought it was supposed to be the bzr location
[22:07] <hatch> morning huwshimi 
[22:08] <Makyo> hatch, used to be that the charmstore URL ("cs:") was what you could dump into quickstart.  Now that they've diverged, I think it should be one or the other - quickstart or bzr.
[22:08] <hatch> Makyo: well both charms and bundles have the location so probably should be bzr
[22:08] <hatch> since you can't use qs for charms
[22:09] <Makyo> hatch, sure.  I think in that case, that we should promote the deploy tab (or the information)
[22:09] <Makyo> Just deemphasize the basket.
[22:11] <Makyo> Just a thought, not actionable.
[22:12] <hatch> bundles have the cs: and charms have lp:
[22:12] <hatch> lol
[22:12] <hatch> oy
[22:12] <Makyo> Yeah, and some of the future stuff is a unification of styles toward first class bundles, just thinking about iterative approaches.