21:00:28 #startmeeting nova 21:00:29 Meeting started Thu Dec 6 21:00:28 2012 UTC. The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:32 The meeting name has been set to 'nova' 21:00:40 Greetings, all. 21:00:43 who's around 21:00:44 <- here, with really bad bug stats, fair warning. 21:00:58 hi 21:01:00 here, but sick. 21:01:02 hey 21:01:09 comstud: bummer, sorry :( 21:01:14 #link http://wiki.openstack.org/Meetings/Nova 21:01:25 ya, sux.. i'm out of town too 21:01:32 #topic project updates 21:01:34 Ahoy! 21:01:35 <- here 21:01:41 comstud: let's hit cells first 21:01:56 ok 21:01:56 comstud: what's the latest on cells 21:02:13 so close to done, but.. i've done nothing but slept the last 2 days :) 21:02:21 yeah, priorities :) 21:02:26 i mean, done reworking 21:02:31 but it's looking much better to me 21:02:42 great 21:02:51 grizzly-2 is January 10th, i think we should aim for that 21:02:55 tests might be a pain to re-work 21:03:01 still a good amount of time, but holidays will eat some of that 21:03:06 yea 21:03:10 i'm not going anywhere 21:03:13 but i might not get reviews 21:03:15 :) 21:03:26 heh, i'm not going anywhere either, but technically i'll be off 21:03:30 i can review anyway 21:03:45 so dedicated 21:03:54 I'll be around too, not that I've reviewed much cells stuff. The 3,500 line one scares me. 21:03:59 and they don't have christmas in the southern hemisphere, so mikal can review too 21:04:05 :P 21:04:21 the 3500 line one may be more lines when i'm done here 21:04:23 is that because the trees don't stand upside down well? 21:04:23 but easier to follow 21:04:27 not sure, haven't diffed it yet 21:04:38 but hey, that one started out at 4500 i think 21:04:45 comstud: cool, i saw you have a lot of reviews on later patches 21:04:46 dansmith: don't make me kangaroo you up the billabong 21:04:49 some approved already, which is kind of odd 21:04:51 yeah 21:04:54 haha yeah 21:05:00 not sure how you can approve something that depends on something you didn't review :) 21:05:10 mikal: heh, you all have kangaroos as pets, right? 21:05:18 i wasn't going to complain about it 21:05:19 so next week updated patches perhaps? if you're feeling better? 21:05:25 comstud: heh, i wouldn't either.. 21:05:27 yeah 21:05:35 ok, cool, anything else you want to discuss? 21:05:55 nothing on my mind other than baremetal has caused a lot of pain :) 21:05:58 bugs 21:06:04 aw 21:06:06 but that's just a comment. 21:06:12 that's the other big project we've been hitting in this meeting 21:06:16 yeah 21:06:23 continue on 21:06:24 anyone care to comment on the status there? 21:06:25 i'm good 21:06:33 I'm afraid to go near baremetal because most of them have one green check 21:06:33 comstud: what kind of bugs have hit you? 21:06:39 so we know what to watch out for better 21:07:26 in the context of cells, or you mean in general? 21:07:43 i remember a resource tracker issue, delaying setting 'node' until after resources were claimed 21:08:38 oookay. :) 21:09:13 so couple other specific projects ... 21:09:18 boot from volume improvements 21:09:24 russellb: reisze stuff and resource tracker stuff 21:09:29 comstud: ah ok 21:09:29 both might hav been resource tracker 21:09:33 basically... 21:09:36 has to do with adding of 'node' 21:09:38 sorry :) 21:09:39 to compute_nodes 21:09:41 right 21:10:01 so boot from volume ... https://blueprints.launchpad.net/nova/+spec/improve-boot-from-volume 21:10:04 #link https://blueprints.launchpad.net/nova/+spec/improve-boot-from-volume 21:10:10 nikola wanted to discuss it, but i don't see him here 21:10:20 probably because his first big patch has been merged since asking for it to be on the agenda 21:10:25 but i think there is still more work planned there 21:10:33 so, if you're interested take a look and respond to the ML thread about it 21:10:40 merge and flee 21:10:46 heh 21:10:52 (that's what i'm going to do when cells lands) 21:10:59 alexpilotti requested discussing get-password (vishy's branch) 21:10:59 drive-by patching? 21:11:02 yeah 21:11:06 but since vishy is out today, let's push it to next week 21:11:12 fine 21:11:34 or you can always post to the ML in the meantime 21:11:43 lots of stuff in progress on https://launchpad.net/nova/+milestone/grizzly-2 21:12:06 only 2 not started 21:12:11 1 is a lie, because i started it this week 21:12:22 i think the block device handling one may still be looking for a volunteer 21:12:32 so, take a look if you're not busy enough already :) 21:12:57 #topic nova bugs 21:13:12 #link http://webnumbr.com/untouched-nova-bugs 21:13:15 27 21:13:19 http://www.stillhq.com/openstack/nova/triage-20121207.txt 21:13:19 about where we've been hovering 21:13:35 * russellb awards mikal with the nova-bugs gold star of the week 21:13:37 ah come on, I triaged 2! 21:13:39 hurrah mikal 21:13:46 LOL 21:13:49 before making the tragic mistaking of fixing one :) 21:13:50 markmc: bug in the script! 21:13:52 it's rigged! 21:13:55 which ended the triaging session 21:13:56 There are a bunch of bugs I haven't had a chance to get to 21:14:08 heh 21:14:11 russellb: I have something for grizzly-2 I think, 21:14:15 russellb: its on github! Fix it! 21:14:27 dansmith: ok one sec 21:14:34 russellb: would it be okay if we have a blueprint for removing all direct db calls from manager? presumably to be complete around then... 21:14:45 man. I feel like a slacker. 21:14:55 dansmith: oh, um ... yeah, as a child blueprint under no-db-compute? 21:14:59 dansmith: that makes sense. 21:15:13 dansmith: that's going to be tight, but a good goal, and we better make it if we want to finish by grizzly-3 ... 21:15:16 russellb: just trying to have enough steps in the process so we can point to public blueprints to show status 21:15:18 on the bugs topic, https://bugs.launchpad.net/nova/+bug/1079687 is the last thing which is blocking tempest gate on nova. And given that a nova bug that tempest would have caught slipped in last week, it would be nice to get more eyes on it. 21:15:19 Launchpad bug 1079687 in nova "Flaky failures of instances to reach BUILD and ACTIVE states" [Undecided,New] 21:15:25 dansmith: good idea, file away 21:15:29 russellb: okay, thanks 21:15:34 dansmith: and link me so i can press buttons 21:16:02 i hate "flaky" bugs, heh 21:16:21 yes, agreed 21:16:32 russellb: do I need to do something to make it a proper child? 21:16:39 it appears nova has to be a very specific kind of slow to trigger it 21:16:39 no-db-virt never got to be related in that way 21:16:54 dansmith: there is a dependencies section somewhere ... down lower on the page once it's filed I think 21:16:59 okay 21:17:14 may have to be done from no-db-compute? i can't remember 21:17:55 #help need eyes on this bug, the last thing blocking the tempest gate on nova - https://bugs.launchpad.net/nova/+bug/1079687 21:17:56 Launchpad bug 1079687 in nova "Flaky failures of instances to reach BUILD and ACTIVE states" [Undecided,New] 21:18:12 https://blueprints.launchpad.net/nova/+spec/no-db-compute-manager 21:18:28 dansmith: thanks, i'll get it in grizzly-2 after meeting 21:18:44 russellb: I think you need to edit the deps on no-db-compute, because I can edit deps for the one I filed, but not the main one 21:18:49 russellb: and if you do, can you add no-db-virt as well? 21:18:53 sdague: let's push through remaining discussion, and if there's time left we can group-analyze the bug some :) 21:19:01 dansmith: ack, fine with me 21:19:06 I'm fine with that 21:19:07 thanks 21:19:08 anything else on bugs? 21:19:30 bug day next week? 21:19:34 squashing day 21:19:40 That sounds like a good idea 21:19:43 dang, I was hoping for a bug-writing day 21:19:46 yeah, i like that 21:20:00 I think ttx is organizing one 21:20:01 sure, we're due for one 21:20:23 markmc: oh? ok great ... yeah, we've got a bunch we can work through 21:20:44 i'm seeing good legit stuff every time i go triage some 21:20:49 http://eavesdrop.openstack.org/meetings/project/2012/project.2012-12-04-21.02.html 21:20:56 #info Doc Bug day December 6, Regular Bug day December 13 21:21:00 #link Doc Bug day December 6, Regular Bug day December 13 21:21:06 #undo 21:21:11 #link http://eavesdrop.openstack.org/meetings/project/2012/project.2012-12-04-21.02.html 21:21:35 nice, so we can check out our progress in the next nova meeting :) 21:22:13 so everyone put it on your calendar to block out unnecessary meetings :) 21:22:19 and mikal will be asleep while the rest of us are working, so someone might beat him 21:22:35 Heh 21:23:03 so, as usual, if everyone could triage something this week, that'd be a great help 21:23:07 still not enough names on the bug triage reports 21:23:21 especially important this week if we're going to squash next thursday 21:23:29 the better the bug list, the more productive we can be 21:23:52 and with that ... 21:23:53 yes sir 21:23:53 #topic open discussion 21:24:41 open discussion until we have nothing left, and then whoever wants to stick around, we can spend some time trying to troubleshoot this tempest gate blocker 21:25:21 awesome. 21:25:33 everyone is happy! 21:25:36 what is the tempest gate blocker? 21:25:37 welllll 21:26:02 I'm not. Python-keystoneclient ruined my day. 21:26:04 dprince: sdague brought up this bug earlier, said it was the last bug blocking being able to gate on the whole tempest suite - https://bugs.launchpad.net/nova/+bug/1079687 21:26:06 Launchpad bug 1079687 in nova "Flaky failures of instances to reach BUILD and ACTIVE states" [Undecided,New] 21:26:08 aw 21:26:26 i don't understand 'to reach BUILD' part of that 21:26:31 instances are created in BUILD state. 21:26:54 dprince: it's a race in tempest which gets triggered by exactly how slow the ci nodes are about 15% of the time 21:27:23 sdague: I run similar tests on the hour on bare metal and get fairly consistent results. 21:27:28 sdague: passes. 21:27:50 davidkranz has been running hourly gate jobs on ci, and it fails about 15% of the time 21:27:51 sdague: How do we know this isn't some sort of IO bound... public cloud type failure? 21:28:22 dprince: we don't, however, we can't light the gate on CI if it isn't repeatable on CI 21:28:35 sdague: I'm happy to take a closer look at it offline. 21:29:11 cool 21:29:23 thanks dprince 21:29:59 Yep. Sunil might also be able to help look into this as well (I'll point it out to him here shortly) 21:30:51 well, sounds like we have some eyes on it then ... 21:31:10 anything else before we #endmeeting? 21:31:37 do it! 21:31:40 anyone want to shamelessly plug their review of choice? 21:32:03 oh mtreinish's coverage patch should get a review 21:32:05 what about ones we don't like? 21:32:15 dprince: that's fair too 21:32:26 #link https://review.openstack.org/#/c/14468/ 21:32:30 plug for review 21:32:31 dprince: you can have on the record that you really don't like something :) 21:32:47 now I'm curious... 21:32:48 ah yes, that's a good one 21:32:59 sdague: thanks for the plug 21:33:09 too fast 21:33:12 I'll stay quiet... :) for now. 21:33:19 dprince: oh come onnnn 21:33:22 stir the pot 21:33:24 dprince: plug for -2 ? 21:33:41 dprince: come on, I wanna see if it's the same one I'm thinking of :) 21:34:03 shhhh. 21:34:10 it is a secret 21:34:16 heh, ok.. 21:34:31 I'd also plug clarb's testr - https://review.openstack.org/#/c/15078/ 21:34:42 which is close, he might have the last fix in a different review now 21:34:43 sdague: you've had enough 21:34:55 hey, I like running the unit tests in 42 seconds 21:35:13 sdague: +1 21:35:31 i'm very happy about that ... 21:35:34 the time part anyway 21:35:37 i don't like that our clients do caching and use keyring by default. 21:35:44 it's extremely annoying and has bitten me a number of times. 21:36:06 (just noticing some of dprince's patches to fix that somewhat for keystoneclient) 21:36:27 actually, specifically other eyes on this one - https://review.openstack.org/#/c/17639/ which is the fix, would be good 21:36:33 then the testr one should pass 21:36:43 was trying to find a patch of dprince's to pick on 21:36:46 but can't find one :-/ 21:36:55 :) 21:37:00 hold on... I'l give them to you: 21:37:05 https://review.openstack.org/#/c/17630/ 21:37:11 https://review.openstack.org/#/c/17634/ 21:37:27 oh no, i found those 21:37:28 And... FTR that is why python-keystoneclient ruined my day. 21:37:30 i meant i can't pick on them 21:37:40 because i agree 21:39:15 i want novaclient to have cache/keyring off by default. 21:39:16 alright, well guess we're wrapped up 21:39:18 :-/ 21:39:20 or not 21:39:33 it's not important 21:39:47 comstud: propose it and see what happens? :) 21:39:55 hehe ya 21:40:26 we can continue ranting over in -nova :) 21:40:29 thanks for coming all 21:40:31 #endmeeting