/srv/irclogs.ubuntu.com/2015/02/25/#juju-gui.txt

lazyPowerI just noticed that it became possible to remove a subordinate relation *hattip* ty for that gents00:26
rick_h_lazyPower: coolio00:44
lazyPowerrick_h_: i'm probably lagging behind in the features landing in gui. Hows things on your side o the fence?00:45
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
lazyPowerrick_h_: intredasting. are you aware that the /docs still links to the old docs?00:46
lazyPower(it auto completed.... maybe i'm being picky)00:47
lazyPowerbut i dig that its all redirecting to jujucharms.com now, thats groovy baybeh00:47
rick_h_lazyPower: the docs should be redirected as well00:55
lazyPowermight be caching on my side00:55
rick_h_so have to bring that up I guess00:55
lazyPoweri seem to find all those fun "you had something cached" issues00:55
rick_h_naw, it's just they just did it today so missed something there00:56
rick_h_rt replied to00:58
rick_h_so hopefully fixed up tomorrow00:58
=== TheRealMue is now known as TheMue
=== johnweldon is now known as jw4|afk
=== urulama_ is now known as urulama
=== jw4|afk is now known as johnweldon
dimiternhey guys12:19
dimiternsomeone 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
mupBug #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:20
frankbandimitern: no, no changes required on the client side12:21
dimiternfrankban, that's what I remember as well - is quickstart using lp:python-jujuclient internally?12:22
frankbandimitern: it is12:22
dimiternfrankban, and the client also didn't need to change right?12:23
dimiternfrankban, I doesn't seem like jujuclient changed since before the fix - just looking at the code12:28
frankbandimitern: correct12:28
dimiternfrankban, thanks!12:29
frankbandimitern: was the fix released?12:29
dimiternfrankban, well, 1.21.3 is released, which includes the fix, but jamespage today reported this bug 142543512:29
mupBug #1425435: juju-deployer/jujuclient incompatibility with 1.21.3 <api> <network> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1425435>12:29
frankbandimitern: I still get "Ports":null with 1.22-beta312:31
dimiternfrankban, that's expected - 1.22-beta3 was released before the fix12:32
dimiternfrankban, hmm.. actually according to the changelog it should have the fix12:33
dimiternfrankban, something's wrong here.. I'll investigate more12:34
dimiternfrankban, ah, I see the problem - 1.22-beta3 includes my original fix for bug 1418433 which you then improved as part of fixing bug 142040312:37
mupBug #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
mupBug #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:37
frankbandimitern: so we don't have a release with the subsequent fix?12:40
dimiternfrankban, 1.21.3 should have both, but apparently there's still a problem12:44
dimiternfrankban, can you do a quick test with 1.21.1 from the stable juju ppa?12:44
dimiternfrankban, sorry, I meant 1.21.3, not 1.21.112:48
dimitern(the latest available)12:48
frankbandimitern: doing it now13:06
frankbandimitern: it works with 1.21.3-utopic-amd64 from the stable PPA13:29
dimiternfrankban, great! thanks for confirming13:30
frankbandimitern: so new release landed in stable but not in devel?13:30
dimiternfrankban, 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 now13:31
frankbandimitern: 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 fix13:32
dimiternfrankban, oh, that's weird, but easier to check - cheers, I'll look into the devel ppa13:33
frankbandimitern: ty13:34
=== kadams54-away is now known as kadams54
jcastrohey rick_h_14:07
jcastrohave we talked about CIing all the bundles on that page on a regular basis?14:07
jcastrowe as in us collectively, not you you. :)14:07
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 honest14:10
jcastroyeah also we have another problem14:10
jcastrobundles and all that jazz will work fine in AWS/Azure, etc.14:11
jcastrothen you go onsite with an OB and boom14:11
rick_h_boom because? 14:11
jcastrowhatever issue is local that we can't reproduce in a cloud, for example this weekend we had a squid problem on an OB14:12
jcastroand it didn't matter if the bundle worked or not, the entire thing needed to be hand held14:12
jcastroI guess I am just saying that just testing bundles in the public cloud isn't good enough14:12
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:13
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:14
hatchrick_h_: that's not a problem though is it?14:38
hatchand good morning :)14:38
rick_h_hatch: no, not a problem just wanted you to make sure you kept that in mind during dev/qa14:38
rick_h_hatch: as we only talked about u/xxxxx/name urls yesterday14:38
hatchyeah, this is what I came up with https://gist.github.com/hatched/3613d21af62ca9c221ed14:39
hatchI think that it'll work for all different formats14:39
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 ready14:40
hatchsounds good - I'm just writing the GUI tests right now for this then I'll be hopping on the storefront14:41
rick_h_ty14:41
hatchrick_h_: the GUI PR is up https://github.com/juju/juju-gui/pull/69715:54
hatchuiteam could I get a review on https://github.com/juju/juju-gui/pull/697 thx17:38
rick_h_hatch: looking17:38
hatchthanks17:38
rick_h_two cancelled calls in a row ftw! :)17:38
hatchhaha less walking though17:39
frankbandimitern: any news on the Ports problem?17:49
dimiternfrankban, not really - I've investigated thoroughly, couldn't reproduce it and reported my comments in bug 142543517:53
mupBug #1425435: juju-deployer/jujuclient incompatibility with 1.21.3 <api> <network> <oil> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1425435>17:53
frankbandimitern: ack, ty18:07
=== kadams54 is now known as kadams54-away
hatchgreat talk lazyPower 18:52
lazyPowerThanks hatch :)18:53
hatchlazyPower: do you find people understand the ansible charms better than bash ones?18:54
hatchI would have assumed a bash/python charm would be easier to grok18:54
lazyPowerhatch: Ansible is really well documented and gives you a lot of batteries out of the box in terms of idempotency, and logic structures18:57
hatchis it the 'popular' one now? vs chef and whatnot18:57
lazyPoweri'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:57
lazyPowereh, 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 room18:58
=== kadams54-away is now known as kadams54
hatchahh19:00
=== jcw4 is now known as jw4
lazyPowerhatch: do you know if rick_h_ is still around?21:25
hatchlazyPower: your guess is as good as mine :) 21:26
hatchif he is I'm sure he'll poke his head in now that you have dinged21:27
lazyPowerok, just curious if he had an emergency to run out for21:27
lazyPowerwell i feel bad now, i've dinged him in 3 places :(21:27
lazyPowermy name is going to be synonymous with a curse word before long...21:27
hatchlol21:27
lazyPowerman.. chuck that.21:27
hatchnah you have a long way to go yet21:27
lazyPowerthats the chuckest thing i've heard all day21:27
hatchMakyo: you able to do a qa on my PR?21:29
Makyohatch, sure, I'm spinning my wheels as it is21:30
hatchbreak time! :)21:30
MakyoGot the PR number off the top of your head?21:31
hatchhttps://github.com/juju/juju-gui/pull/69721:32
hatchone better :)21:32
MakyoThanks21:32
Makyohatch, LGTM (though maybe in the future, we want the "Location:" link in the header might need to be update din the future)21:38
hatchMakyo: yeah tbh I have no idea what the purpose of that is anymore21:38
hatchit's always been a thorn for me21:39
MakyoI think it made more sense in an earlier iteration.21:39
MakyoOh well, something for another time.21:39
rick_h_lazyPower: yes, was on the phone doing manager stuff for a bit :P21:39
lazyPoweryeah sorry about the ping crazyness :( 21:40
rick_h_grr, this sysdeps thing is not working for me here21:41
rick_h_ah crap, vivid lxc container FML21:42
rick_h_hatch: have no QA for you atm, have to start over sorry21:42
rick_h_and uploading GB of stuff for lazyPower is making this brutal21:42
hatch:) np Makyo is on it21:42
rick_h_hatch: please get QA from gui from someone else21:42
rick_h_ty Makyo 21:43
lazyPowerGIVE ME ALL YOUR BANDWIDTH MWAHAHA21:43
lazyPowerrick_h_: if its a better option - just hit me with what you're working on now, the others can wait until an overnight xfer21:43
rick_h_lazyPower: np, Makyo has my back and I'm going to feed the dog/etc and just let the bandwidth go21:44
lazyPower10-421: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 guimaas21:44
rick_h_run that overnight heh21:44
lazyPoweri feel like we've reverted to 90's style transfer of files....21:44
lazyPowerlike, xdcc21:44
lazyPowerfxp21:44
hatchhaha21:44
lazyPowerall pre bt options21:44
hatcheff tee pee21:45
hatchess eff tee pee 21:45
hatch:)21:45
lazyPowerhatch: pleb - distribution hubs used server => server transfers :P21:45
hatchhaha21:45
lazyPoweri'm not going to say how i know this... but it might be from the scene... http://www.welcometothescene.com/21:46
huwshimiMorning22:00
rick_h_morning huwshimi 22:00
rick_h_lazyPower: ok, best of luck downloading now 22:01
lazyPowerta rick_h_, cheers!22:01
Makyohatch, 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
Makyohatch, I mean before the design stuff in the pipeline.22:06
hatchMakyo: I always thought it was supposed to be the bzr location22:06
hatchmorning huwshimi 22:07
Makyohatch, 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
hatchMakyo: well both charms and bundles have the location so probably should be bzr22:08
hatchsince you can't use qs for charms22:08
Makyohatch, sure.  I think in that case, that we should promote the deploy tab (or the information)22:09
MakyoJust deemphasize the basket.22:09
MakyoJust a thought, not actionable.22:11
hatchbundles have the cs: and charms have lp:22:12
hatchlol22:12
hatchoy22:12
MakyoYeah, and some of the future stuff is a unification of styles toward first class bundles, just thinking about iterative approaches.22:12
=== kadams54 is now known as kadams54-away

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!