21:01:27 #startmeeting nova 21:01:28 Meeting started Thu Jan 3 21:01:27 2013 UTC. The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:31 The meeting name has been set to 'nova' 21:01:50 #link http://wiki.openstack.org/Meetings/Nova 21:02:00 #link https://launchpad.net/nova/+milestone/grizzly-2 21:02:29 the only thing i had in mind for today was to take a look at grizzly-2 status 21:02:35 scheduld for a week from today 21:02:48 all features should be merged by Tuesday, Jan 8th to make grizzly-2 21:03:08 well, as much as I'd like, I'm sure that no-db-compute-manager won't quite make it 21:03:14 blueprint status shows us pretty far behind the goal 21:03:19 close, but not all merged by then 21:03:27 dansmith: ok, if you're sure let's bump it 21:03:37 i think our goal right now should be to make it realistic 21:03:39 okay 21:03:48 baremetal is very close right now (even though it's not on that list) 21:03:49 figure out what needs a push to get over the line, and push stuff out that isn't going to make it 21:04:00 devananda: it's not *looks* 21:04:04 xenapi config drive is close, I just need to get my hardware setup so I can test it 21:04:08 what is it on grizzly-3? 21:04:15 ok let's go one by one here ... 21:04:17 devananda: it is on the list 21:04:26 from the top! 21:04:27 unless General Baremetal is different 21:04:34 xenapi-volume-drivers 21:04:40 is Mate Lakat here? on IRC? 21:04:52 some refactoring patches went in, but not the core stuff it seems like 21:04:55 no clue on status 21:05:00 russellb: ah, sorry. it _is_ there, under the words "bare-metal". my search for "baremetal" didn't find it :) 21:05:12 devananda: k, cool 21:05:38 #note need an update on the status of xenapi-volume-drivers blueprint 21:05:46 next ... no-db-compute-manager 21:05:58 dansmith: i went looking for your patches from yesterday, they all merged? 21:06:05 russellb: uh, no 21:06:14 :/ 21:06:18 hi 21:06:19 https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/no-db-compute-manager,n,z 21:06:21 then i got distracted by cells 21:06:23 #chair vishy 21:06:24 Current chairs: russellb vishy 21:06:26 and: https://review.openstack.org/#/c/18849/ 21:06:40 dansmith: oops, ok, will review asap then. 21:06:49 dansmith: do those patches complete the blueprint? 21:06:49 thanks 21:07:04 no, but after those, only 12 calls remain to be moved/refactored 21:07:14 (sorry I'm late) 21:07:26 vishy: it's ok, we'll keep you ;) 21:07:40 vishy: i was just thinking we'd go through grizzly-2 blueprints 21:07:48 dansmith: want to keep pushing and see if we can pull it off? 21:08:05 move it at last minute if needed ... 21:08:11 russellb: by tuesday? I don't think it's realistic, but I can certainly try 21:08:24 k, no worries 21:08:29 you've made awesome progress 21:08:30 I mean, there's no penalty for moving at the last minute, so why not? :) 21:08:35 right. 21:08:44 vishy: you know anything about xenapi-volume-drivers? 21:09:04 it's marked as high priority, but i don't know the status other than seeing some refactoring patches come through 21:10:28 ok, on to cells ... 21:10:40 i saw that comstud updated his patches yesterday, i'm in the middle of reviewing the first one 21:11:06 my gut feeling is that it's unlikely to make grizzly-2 21:11:21 whoops 21:11:23 I just pinged comstud to let him know he's being discussed 21:11:25 Heh 21:11:28 nope 21:11:30 on a call 21:11:32 russellb: I thought they were done 21:11:45 i'm done 21:11:46 i need reviews 21:11:56 i had a test to add for rpc driver for 'add main cells code' 21:11:59 but that's it 21:12:00 comstud: *nod* will have review up by end of day 21:12:31 I can take a look at that main code review today too 21:12:35 vishy: last patch on the xenapi-volume-drivers blueprint expired back in early november 21:12:36 * dansmith takes a screenshot of comstud saying cells are "done" 21:12:41 lol 21:12:42 seems dead 21:13:22 i'm not sure what to do with blueprints that die like that ... 21:13:31 russellb: it didn't seem like that one was key 21:13:36 yeah agreed 21:13:39 russellb: I thought it was just a refactor / cleanup 21:13:56 so, drop priority and untarget? 21:14:19 dansmith: note that I said that "i'm done" not that "cells is done" 21:14:29 ;) 21:14:35 comstud: i took it as you meant you were done with the phone call 21:14:37 comstud: heh :) 21:14:41 oh 21:14:42 haha 21:14:57 i'm multitasking 21:15:04 teehee :) 21:15:11 there's a test failure for one of the later branches 21:15:21 and I have a fix for that to push up along with rpc driver tests 21:15:54 comstud: I also have a small rpc sanitization change because of cells which will hopefully land in oslo today. 21:16:27 comstud: well thanks for updating. i'll hold off on comments until i post the review so we don't dominate this meeting 21:16:39 yes, plz gimme feedback 21:16:52 will do by end of day 21:16:56 ty 21:17:05 next bp ... nova-v2-api-audit, assigned to sdague 21:17:28 yeh, I think we can call that done on friday, maurosr was finishing off a few things 21:17:31 the audit part sounded very close the other day 21:17:33 russellb: in fact I'm on this one 21:17:36 awesome 21:17:39 as we talked earlier today, I'm working to get all the things that fit as api-v2 fix and will not break any api done until tomorrow, and the other part of that work will be addressed on api-v3 bp which is target to grizzly-3 (api-v3 complements v2 audit work) 21:17:41 should it be reassigned? 21:17:50 russellb: probably 21:17:56 ok, launchpad username? 21:18:01 russellb: maurosr 21:18:16 k done 21:18:34 alexpilotti: around? 21:18:43 russellb: sure 21:18:52 you have a high priority grizzly-2 targeted blueprint for hyper-v testing improvements 21:18:56 any progress there? 21:18:59 russellb: yep 21:19:17 russellb: the good news is that the deaded pickled files are gone 21:19:33 ahem, *dreaded 21:19:33 * russellb waits for the bad news 21:19:47 russellb: no bad news :-) 21:19:52 oh, yay. 21:19:57 I'm fixing up the latest tests now 21:19:58 so what's the timeline for code going up 21:20:16 I'd like to discuss with you the new design, maybe in -dev or -nova 21:20:25 russellb: tonight 21:20:41 ok sure, let's talk in -nova after meeting with whoever is interested 21:20:50 the idea is that now instead of generating pickle files we emit python code 21:21:13 this should make everybody happy IMO 21:21:20 may need to reserve judgement until there's a patch up :) 21:21:30 think you could post a WIP? 21:21:37 that would make it easier to talk about 21:21:47 that's why I wanted to send the code for review before starting the discussion 21:21:52 ok 21:22:01 well ping when ready to discuss then 21:22:14 russellb: sure 21:22:42 alaski: ping 21:22:46 next blueprint is instance-actions 21:22:51 russellb: pong 21:22:54 looks like it's all marked WIP right now 21:23:05 alaski: just looking for a general update on instance-actions 21:23:35 started a decently large rework based on belliott's comments. Then got distracted by work and holidays. SHould have t new reviews up in the next few days 21:23:55 ok, so should be bumped to grizzly-3 then 21:24:00 (deadline for merging is Tuesday) 21:24:12 yes. Definitely wo't all be in by then 21:24:18 kthx 21:24:48 very cool feature though, looking forward to it 21:25:02 next bp is version-rpc-messages, assigned to me 21:25:10 the main oslo patch went in today 21:25:26 seems a lot of people are, trying to make sure it doesn't disapoint :) 21:25:29 there's another patch for enabling the rpc message envelope for notifications 21:25:47 so once that gets in, i'll get it synced to nova, should be fine for grizzly-2 21:26:20 next up is aggregate-based-availability-zones 21:26:23 jog0: around? 21:26:33 yup 21:26:33 looks like you have it done and just need reviews last i checked 21:27:03 https://review.openstack.org/#/q/topic:bp/aggregate-based-availability-zones,n,z 21:27:07 thats correct. This changes some default behaviors so extra reviews would be apprecated 21:27:18 it's got a +2 from vishy 21:27:33 anyone want to volunteer to do another review on this in the next couple days? 21:28:08 or will someone volunteer, even if you don't want to? :) 21:28:49 russellb, I'll look at it tomorrow morning 21:28:57 dripton: cool, thanks 21:29:31 i'm not core, but I can take a look too 21:30:01 cool, well having you guys review and leave a +1 gives others more confidence to push it through, so it's very helpful 21:30:14 Its a good way to end up as core too 21:30:16 (and lots of that is required to eventually get on -core IMO) 21:30:18 mikal: that :) 21:30:41 jog0: feel free to pester as we get closer to tuesday to get it over the hump 21:30:42 onward 21:30:52 russellb: kk 21:30:57 so, that was all the high priority blueprints, on to the medium ones 21:31:16 db-unique-keys, assigned to boris pavlovic 21:31:21 he here? 21:31:36 dripton devananda jog0 ... any of you know status? 21:31:40 it's just marked as Started 21:31:43 Boris told me he was working on it before the holidays. 21:31:58 It might conflict with my db-archiving bp so we need to coordinate a bit 21:32:07 https://review.openstack.org/#/q/topic:bp/db-unique-keys,n,z 21:32:24 i think he's been circling the problem, so to speak, with other (related) reviews lately 21:33:22 k, so seems likely to get bumped 21:33:28 yea 21:33:38 think it should just be moved now? 21:33:58 if stuff isn't in review, or very close to it, seems unlikely to be merged by Tuesday 21:34:17 yep, let's bump it 21:34:17 makes sense to move it. He can ask to move it back. 21:34:36 k done 21:34:49 next, scope-config-opts, by markmc 21:34:58 he's not here, but he has pushed a bunch of patches through on this 21:35:49 i'll try to ping him tomorrow on it 21:36:13 next, entrypoints-plugins 21:36:16 i haven't been watching this closely 21:36:50 that looks pretty stalled 21:36:56 mordred: think entrypoints-plugins for nova has a chance for nova grizzly-2 (by Tuesday) ? 21:37:34 the review that mordred put out there hasn't been updated in a while, and it also needs some test magic to not make the unit tests take 3x the duration :) 21:37:49 ah ok, so that part hasn't been resolved yet, i wasn't sure 21:38:16 yeah, let's bump it ... 21:39:01 poor grizzly-2 is getting a shocking dose of reality 21:39:24 well, that's it for medium blueprints. 21:39:33 the rest are low ... 5 of which say "needs code review" 21:39:47 so those are good candidates for looking at and seeing if we can get them in quickly 21:39:57 if you look and it seems stalled, ping me and we can update the blueprint status accordingly 21:40:34 alexpilotti: you've got a low blueprint for hyper-v resize 21:40:39 what's the status on that 21:41:04 russellb: WIP, can we move it to G-3? 21:41:11 sure can, thank you 21:41:29 russellb: tx! 21:41:42 * russellb assumes the one still marked "Not started' can be bumped too ... 21:42:37 is Lance Bragstad here? 21:42:49 i'm looking at powervm-compute-enhancements 21:43:06 the blueprint seems overly generic 21:43:26 i'm not sure how you'd call it done 21:43:56 sdague: dansmith: is this something you guys could help chase and put some scope on? 21:43:57 russellb: he's coming 21:44:04 cool thanks 21:44:17 russellb: yeah, but if he can show up here soon, it'd be good to get a quick read on it 21:44:22 lbragstad: hello! 21:44:34 lbragstad: we're looking at the powervm-compute-enhancements blueprint 21:44:40 it's targeted at grizzly-2, which is next week 21:44:45 russellb: hey, sorry I missed earlier 21:44:58 so i just wanted to check in on the status and see what you felt like is left to do before it can be marked as completed 21:44:58 russellb: ok 21:45:33 https://blueprints.launchpad.net/nova/+spec/powervm-compute-enhancements 21:46:18 russellb, sdague: I should re-look - I believe we put the magic into stevedore that we need for the test speed issue 21:46:26 but bumping is probably a good idea 21:46:38 russellb: doing some checking right now 21:46:40 russellb: oh, G-2, knowing the little I do about what they're planning, I'm sure that G-2 is no longer a reasonable target 21:46:41 mordred: cool, thanks 21:46:49 I think the only question is whether G-3 even is 21:46:55 lbragstad: would you agree? 21:47:01 well the way the blueprint is worded, it's open ended 21:47:09 it just seems to be a placeholder for whatever gets done in grizzly 21:47:25 would be nice to reword it with some specific scope in mind, for whatever is realistic for grizzly 21:47:31 and then any additional plans can come as later blueprints 21:47:34 make sense? 21:47:39 russellb: yeah, well, maybe they could seal it off and call it something reasonable for G-2, but I think it was supposed to hold the place for some more changes that don't seem to be done yet 21:47:54 ok 21:48:05 lbragstad: can you rename the blueprint to something specific, and put words in there to make it well-defined? 21:48:14 that would be great 21:48:19 dansmith: sure that sounds good 21:48:31 and then let me know whether whatever it is changed to is complete in grizzly-2 or needs to be bumped to grizzly-3 21:48:33 something more specific for grizzly-2? 21:48:35 lbragstad: and with that, tell us (soon) if it still makes sense for G-2 or if it should be moved to G-3 21:49:13 lbragstad: I'm guessing that even the snapshot stuff you've got in the fire right now might be at risk for being merged by tuesday, right? 21:49:34 dansmith: I just uploaded a new patch set for that 21:49:42 russellb: we can move on and I can continue offline with lbragstad if you want 21:49:50 lbragstad: right. 21:49:56 great, just ping me with any needed blueprint updates once you're ready 21:49:59 thanks guys! 21:50:08 okie 21:50:11 devananda: do I see your name on this openvz-driver blueprint? 21:50:17 russellb: thanks for the heads up! 21:50:18 https://blueprints.launchpad.net/nova/+spec/openvz-driver 21:50:21 russellb: at one time i was working on it, yes 21:50:21 lbragstad: np 21:50:40 devananda: ok cool ... any idea where it's at? definitely doesn't seem to have a chance at grizzly-2 21:51:02 russellb: i moved away from openvz shortly before grizzly summit, and haven't heard about any progress on it since :( 21:51:24 ok ... 21:51:32 well ... i'm just going to pull it out of grizzly completely then 21:51:38 and if something magically shows up, neat 21:51:57 last i heard, hub_cap and dsalinas were still using it internally 21:52:17 well, i'll move it to grizzly-3 for now 21:52:20 we'll see ... 21:52:23 k 21:52:34 thanks 21:53:10 https://launchpad.net/nova/+milestone/grizzly-2 21:53:15 in a bit better shape now 21:53:23 everything not implemented is either ready for review, or very close to it 21:54:00 any other blueprint discussion? otherwise we'll use the last few minutes for open discussion 21:54:04 baremetal? :) 21:54:19 ah sure 21:54:38 i skipped over it since it was set as ready to be reviewed, but definitely worth bringing up anyway 21:54:42 there's basically 3 components of it (and 3 reivews) that need to be approved before that BP can be marked as done 21:55:09 in as much as those will provide a working framework for additional baremetal features to be implemented on 21:55:33 that's all :) 21:56:32 cool ... been getting reviews? 21:56:37 * russellb can't claim to have helped 21:57:09 mostly from sdague and mikal, yes. lots of patches merged earlier this week 21:57:15 https://blueprints.launchpad.net/nova/+spec/get-password could use reviews 21:57:29 my old branch was approved but it had no api sample tests 21:57:50 i added them and in the process realized i needed one other change which is in a new patch 21:59:57 vishy: should the bp be updated to needs code review? 22:00:04 just did 22:00:05 :) 22:00:08 nice 22:00:26 well i guess we're about out of time ... 22:00:51 lots of reviews needed, so let's get back to it! 22:01:03 Review all the things! 22:01:10 yes! 22:01:24 thanks everyone 22:01:27 #endmeeting