/srv/irclogs.ubuntu.com/2015/01/20/#juju-dev.txt

thumperI added a constraint that a new environment should have the same provider type as the state server environment00:00
thumperwell, default00:00
thumpernot constraint00:00
jw4thumper: I've not been able to reproduce the bug 1412292 - are those errors happening consistently for you?01:37
mupBug #1412292: Intermittent test failure in ActionSuite.TestActionsWatcherEmitsInitialChanges <action> <intermittent-failure> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1412292>01:37
thumperjw4: about one time in three01:37
jw4thumper: hmm; do you have a fast machine, or a slow one - or is it PPC - or anything like that?01:38
thumpertwo year old fast i7, lots of ram and fast ssd01:38
jw4thumper: kk - I'll try picking apart the logic to see what I can find01:38
thumperok01:38
menn0thumper: Fix it, then Ship it01:59
jw4thumper: two quick questions - 1) I assume the defect report has the full output of the test run. Is that true? 2) what version of go are you using?01:59
jw4thumper: fwiw I suspect the problem is the watcher isn't getting updated in time that the two actions were removed02:00
thumpermenn0: ta02:42
thumperjw4: using what ever version is in trusty02:42
thumperjw4: I'm guessing it is a race condition02:42
thumperjw4: but I've not looked at the code02:43
thumperman...03:20
thumpergetting endorsements on linked in by folk I don't remember linking to03:20
thumperoh... he is a juju gui peep03:21
axwwallyworld_: about to send an email to fwereade for some advice on the state model, I've CC'd you in case you have ideas on it03:25
wallyworld_ok03:25
axwthe relations to units and services are feeling a bit messy03:26
* thumper finishes the apiserver httphandler before enfixorating the branch menno reviewed03:26
thumpermenn0: I have another branch that fixes the rest of the apiserver03:50
thumpermenn0: I just need to write tests for each of the api end points to exercise the additional environment03:50
menn0thumper: sweet03:52
menn0thumper: i'm deep into integrating envWorkerManager into the machine agent03:52
thumperawesome03:52
thumperI feel the pieces are slowly coming together03:52
menn0thumper: lots of awkward details to figure out03:52
thumpermenn0: yep, I know03:53
thumpermenn0: so many fiddly bits03:53
menn0thumper: e.g the singular runner03:53
thumperboo... hiss...04:15
thumperdamn05:08
thumperI bet that two line tweak might break something05:08
thumperI'm done05:14
thumperthese tests are taking ages to write05:14
thumperlaters05:14
dimiternmorning all07:05
anastasiamacdimitern: morning :) 5pm here tho07:13
dimiternanastasiamac, afternoon then :)07:13
anastasiamacdimitern: thnx for consideration :)07:14
anastasiamacdimitern: one thing i miss about Nothern hemisphere - r long dusks in summer07:14
dimiternanastasiamac, oh, they're not so long there?07:14
dimiternanastasiamac, I'd have a hard time adjusting to summer in january :)07:15
anastasiamacdimitern: with +40 and an awful humidity, u will not mistake this for winter!07:16
anastasiamacdimitern: there is no dusk :(07:16
dimiternanastasiamac, *lol*07:16
anastasiamacdimitern: one minute it's day, the next night07:16
anastasiamacdimitern: there r millions of other advantages tho :)07:16
dimiternanastasiamac, that is a bit weird07:17
anastasiamacdimitern: k... to be fair it takes about 20 minutes for day to turn to night :D07:17
dimiternanastasiamac, I bet there are, although with all the creepy crawlers in AU..07:17
anastasiamacdimitern: and don't forget flying cockroaches :P07:17
dimiternanastasiamac, oh we have those as well - nasty creatures07:18
anastasiamacdimitern: certainly very exotic07:19
wallyworld_axw: i've made some changes; i was taking some shortcuts previously to try and get it done more quickly; tests should have better coverage now07:23
dimiternwallyworld_, axw, hey guys - can one of you review this goamz PR please? https://github.com/go-amz/amz/pull/2007:24
axwwallyworld_: ok cool07:24
axwwallyworld_: looking07:24
axwdimitern: will take a look in a bit07:25
wallyworld_dimitern: i'm about to get ready for soccer, but can look when i get back if not done07:25
dimiternaxw, thank you07:25
dimiternwallyworld_, cheers07:25
dimiternwallyworld_, isn't it too hot for soccer? :)07:25
wallyworld_dimitern: inly if you're soft :-)07:26
dimiternwallyworld_, :D07:26
wallyworld_axw: i gotta dash, but i might next add some basic framework for registering storage provider types eg loop with a skeleton implementation. then the blanks can be filled in while work is done on making the loop storage available to env providers, and fallback logic implemented etc07:33
wallyworld_axw: tnks for review, i just used state in tests to get end-end tested for now, can mock out later07:33
axwwallyworld_: that SGTM07:33
axwthanks07:33
axwdimitern: reviewed07:57
dimiternaxw, ta!07:57
dimiternvoidspace, standup?10:03
voidspacedimitern: omw10:03
axwdimitern: when you're free, can you please review https://github.com/juju/names/pull/37 ?11:13
dimiternaxw, sure thing11:14
dimiternaxw, lgtm11:20
axwdimitern: do you mean vary the storage name? i.e. something other than "store"?11:20
axwthanks11:21
dimiternaxw, yeah11:21
axwdimitern: okey dokey, will do11:21
dimiternaxw, I only later read the description of what it is :)11:21
perrito666morning11:50
anastasiamacperrito666: morning...11:51
axwdimitern: another small one http://reviews.vapour.ws/r/766/12:00
dimiternaxw, ship it! :)12:02
axwdimitern: thanks12:02
perrito666bogdanteleaga: there is something wrong with http://reviews.vapour.ws/r/632/12:21
perrito666it lacks code12:21
perrito666jam2: inet problems?12:21
jam2perrito666: its been happening for a couple of days now. They "upgraded" my local router in preparation for changing something about the networking to the building, and now every 15-30min I get a SSL session negotiation failure.12:22
bogdanteleagaperrito666: hmm, it hasn't been created automatically so I tried to do it manually, apparently it didn't work12:23
bogdanteleagaperrito666: the code is on github however can I update it from the web interface?12:23
perrito666bogdanteleaga: if you did the post manually probably it worked but you need to go to reviewboard and publish it12:25
dimiternvoidspace, maas meeting?14:04
* perrito666 actually had to prepare a brew to review fwereade's branches14:07
fwereadeperrito666, oh dear, is it that bad?14:07
perrito666nope, I just checked the lenght and decided that i better prepare my brew before and not after14:08
fwereadeperrito666, good thinking :)14:08
fwereadeperrito666, if it helps, I think the test changes outweigh the code in both of them14:08
perrito666abentley: this was the failing test of the last cursed email I got http://juju-ci.vapour.ws:8080/job/win-client-deploy/1319/console that is the test right?14:12
abentleyperrito666: That looks like a problem with the machine running the test.14:13
* perrito666 stops peeking at the local newspaper before getting an ulcera14:14
natefinchMorning everybody14:26
dimiternhey natefinch!14:26
natefinchdimitern: howdy :)14:27
perrito666hey natefinch back?14:27
natefinchperrito666: back, yes14:27
natefinch05852414:27
perrito666natefinch: we wherent expecting you for a couple of weeks14:27
perrito666natefinch: tx nice pass14:28
natefinchlol14:28
natefinchjust my google authenticator number14:28
natefinchyeah, this is about when I expected to be back.... 2 weeks after the company shutdown14:28
voidspacedimitern: damn!14:39
voidspacedimitern: sorry14:39
dimiternvoidspace, :) np14:40
voidspacedimitern: just forgot :-(14:40
voidspacedimitern: I need to tattoo it to my hand or something14:40
dimiternvoidspace, *lol*14:40
dimiternvoidspace, nothing major - non-installable nodes can be tested very soon - check the minutes doc if you like14:41
sinzuinatefinch, perrito666 dimitern : I don't see any 1.21-beta5 specific issues in play in the this bug. I don't think it should block the release of 1.21-rc1 https://bugs.launchpad.net/juju-core/+bug/141087614:41
mupBug #1410876: Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a directory - Could not destroy  snapshot %s - failed to allocate a pty; Insufficent privileges to control  juju-trusty-lxc-template <lxc> <oil> <trusty> <juju-core:Incomplete> <juju-core 1.21:Incomplete> <juju-core14:41
mup1.22:Incomplete> <https://launchpad.net/bugs/1410876>14:41
voidspacedimitern: I will do, cool14:41
voidspacedimitern: sounds good14:41
dimiternsinzui, looking14:42
voidspacedimitern: we need an api to assign resources (like ip addresses) to them for non-installable nodes to be directly useful to us14:42
perrito666sinzui: I agree thumper and Í documented our findings there and it seems it is outside juju14:42
sinzuithank you perrito666 . I will try to remove the bug from rc114:43
dimiternsinzui, yep, I was just checking the code - it seems 1.21-rc1 shouldn't be affected14:52
sinzuifab14:53
wwitzel3perrito666: ping15:06
sinzuinatefinch, dimitern:do you have a moment to review this branch http://reviews.vapour.ws/r/768/15:22
natefinchsinzui: ship it!15:26
sinzuithank you natefinch15:26
jw4OCR PTAL http://reviews.vapour.ws/r/769/ - fix for bug 141229215:44
mupBug #1412292: Intermittent test failure in ActionSuite.TestActionsWatcherEmitsInitialChanges <action> <intermittent-failure> <test-failure> <juju-core:Triaged by johnweldon4> <https://launchpad.net/bugs/1412292>15:44
dimiternjw4, looking15:44
jw4dimitern: thanks15:45
dimiternjw4, if the issue is with the watcher, why not fix it there?15:46
jw4dimitern: 1) I'm not sure it's a problem with the watcher 2) making a change there would have widespread effect15:50
jw4dimitern: the issue in the watcher is that it waits up to 10 ms every time after a change to see if there are more changes before returning15:50
jw4dimitern: that's probably not bad in real life, but in the tests we were expecting it to be a bit more deterministic15:50
dimiternjw4, right, there might be an issue lurking in there, but the fix seems fine - almost ready with the review15:51
jw4dimitern: tx15:51
dimiternjw4, done15:55
jw4dimitern: ta15:55
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
voidspacejust spent about an hour trying to work out if I can get the MACAddress out of a network definition in lshw18:29
voidspaceonly to realise a few minutes ago that it's there, it's just called "serial" instead of mac address18:29
voidspaced'oh...18:29
voidspaceat least I have it18:30
hazmatis usermanagement so to be functional18:36
hazmatnevermind18:38
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
voidspaceright19:10
voidspaceg'night all19:10
voidspaceEOD19:10
=== kadams54 is now known as kadams54-away
katcowhen we create our lxc templates for cloning, we start them and then wait for them to stop. what causes them to eventually stop so cloning can continue?19:44
=== kadams54-away is now known as kadams54
natefinchkatco: not sure19:51
katcofor reference: https://github.com/juju/juju/blob/1.20/container/lxc/clonetemplate.go#L16219:52
katcotrying to dx https://bugs.launchpad.net/juju-core/+bug/134838619:52
mupBug #1348386: lxc template fails to stop <clone> <lxc> <oil> <juju-core:Fix Released by cox-katherine-e> <juju-core 1.20:Fix Released by cox-katherine-e> <https://launchpad.net/bugs/1348386>19:52
hazmatare tags supposed to leak through the api?19:56
katcohazmat: they are not19:57
hazmatcause it seems like we started off without doing that, but now their leaking all over the place19:57
hazmatactions, usermanager, etc19:57
hazmatssh key manager.. basically anything using Entities is expecting tags.19:58
hazmatparam.Entities that is19:58
katcohazmat: in the api/* packages? or apiserver/*?19:58
hazmatkatco, in apiserver19:59
katcohazmat: ah. that is designed to take tags19:59
katcohazmat: tags are OtW format, api/* is what is client-facing19:59
hazmatwell that is the exposed api19:59
katcohazmat: as i understand it anyway19:59
hazmatapi/* is an implementation of a client.. server is the api so we have a rather unfortunate situation on server that things are a mix of tags and not tags.20:00
jw4hazmat, katco as I recall from discussion w/fwereade the apiserver takes string representations of tags20:00
katcohazmat: this could be wrong, but how it was explained to me is that tags are OtW format and so as jw4 said we pass the string-representation of tags into apiserver/*20:01
jw4hazmat: there was some confusion about tags vs. string representation of tags - are you referring to the string representation or the type names.Tag ?20:01
katcohazmat: i.e.: tags are how clients communicate with the RPC server20:01
hazmatnone of the core api does (deploy/add-machine/remove-machine/add-units/remove-units/setcharm/etc), but all the things that have been added recently are using tags heavily20:02
hazmatso we now have proper mismash of different ids in the api20:02
jw4hazmat: as I recall it that is because of a shift in focus too - the intent being that all ids are internal only and string representation of tags used ubiquitously20:03
jw4hazmat: we just haven't migrated everything yet20:03
hazmator maybe its just client facade shouldn't use tags20:03
hazmatand other facades are all tag centric20:03
jw4hazmat: but I could be wrong - hoping fwereade notices and weighs in20:04
fwereadehazmat, all facades should be tag centric -- but the client ones were mostly written before tags were a thing, and many have not been (needed to be) updated yet20:04
fwereadehazmat, tags were introduced as a way to encode id and type for things like the annotations api20:04
hazmattags have been around a while, we just never exposed them through to client facade consumers20:04
hazmatfwereade, which means they were in the first release of the api really.. ie ever since gui supported juju-core20:05
fwereadehazmat, so we didn't need to ensure that every entity namespace was disjoint from every other20:05
fwereadehazmat, near enough, yes, it was specifically for annotations that we added them iirc20:05
hazmatokay.. i guess i'm going to just keep with other client impl not forcing users to care about tags, just automatically append per appropriate call20:07
hazmatthe only place there was ever a need for tag disambiguation was the annotations (and perhaps not there), i'd rather not have api consumers actually have to concern themselves with it unless by  choice.20:08
=== kadams54 is now known as kadams54-away
natefinchmorning thumper20:52
natefinchwwitzel3, ericsnow: can you guys post a review for the GCE stuff so I can get started on it?21:01
ericsnownatefinch: almost there21:02
natefinchericsnow: cool... feel free to make a PR with a big WIP on the front of it if that's helpful.21:02
aznashwanericsnow: have a moment?21:11
ericsnowaznashwan: almost :)21:11
ericsnowaznashwan: gimme a minute21:11
* thumper headdesks21:12
thumperdamn... damn... damn....21:12
katcothumper: good morning21:13
thumperI've just realised that although the tests pass, this will fail under real load21:13
thumperhi katco21:13
ericsnowaznashwan: what's up?21:17
aznashwanericsnow: i was the loonie with the systemd service management PR from Christmas Eve (namely this one: http://reviews.vapour.ws/r/671/)21:18
ericsnowaznashwan: yep :)21:19
aznashwanericsnow: the thing is it's done exactly as upstart (namely I used exec calls to systemctl for managing the services), and since have been told that a more native approach would be more favorable...21:19
aznashwanI've recently been show this package from the coreOS guys: https://github.com/coreos/go-systemd which might be exactly what we're looking for.21:21
ericsnowaznashwan: yeah, that is what we were planning on using21:21
aznashwanIt would not take too long to adapt my PR to use that, however i'm in the middle of exam season right now, and am not able to get to it sooner than this weekend21:22
aznashwanplus however much time responding to review requests and etc... would take21:23
aznashwanis that timeline ok for you guys?21:23
=== kadams54-away is now known as kadams54
ericsnowaznashwan: it depends on what we end up getting done this week with regards to systemd21:24
ericsnowaznashwan: I expect that we will already have take care of things by this weekend21:24
ericsnowaznashwan: we were planning on incorporating changes from your patch in whatever we did21:25
wwitzel3natefinch: http://reviews.vapour.ws/r/771/21:26
aznashwanericsnow: as you will, apart from changing the exec calls and (sadly) having to redo the tests, my patch is pretty much on par with the upstart one21:27
ericsnowaznashwan: cool21:27
aznashwanericsnow: are you guys also planning to do anything about how the service management system is selected in the (very) near future?21:28
ericsnowaznashwan: yeah, that will be a part of what we are working on21:29
ericsnowaznashwan: we also have to refactor various bits of upstart-specific code throughout juju core to be init-system agnostic :(21:30
aznashwanericsnow: yes, the places were services were used seemed very upstart-specific in the first place...21:31
ericsnow\me gears up for paying off some technical debt21:31
ericsnownatefinch: for fun take a look at the list of commits on that PR21:32
aznashwanericsnow: well, best of luck to you guys. as i've said, I would be more than happy to do it on Saturday of you don't get around to it by then21:32
ericsnowaznashwan: sounds great :)21:33
aznashwanericsnow: keep in touch. godspeed :D21:33
natefinchericsnow, wwitzel3: cool, looking21:34
katco/21:54
=== lazyPower is now known as lp|outy5000
menn0axw: i'm currently reviewing your charm storage PR22:15
thumpermenn0: where is the statesuite that you created?22:37
thumperstate/testing22:38
thumpernm22:38
menn0thumper: :)22:39
jw4thumper: I'm pretty sure I've fixed the watcher test - fyi :)22:40
wwitzel3ericsnow: ping23:06
ericsnowwwitzel3: present23:07
wwitzel3ericsnow: going to jump in to moonstone for a bit23:07
ericsnowk23:07
=== kadams54 is now known as kadams54-away
=== kadams54-away is now known as kadams54
=== kadams54 is now known as kadams54-away
anastasiamacthumper: super command of super command..23:47
anastasiamacthumper: for eg. juju storage pool list....23:47
anastasiamacthumper: is there a precedence?..23:47

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