21:00:34 #startmeeting nova 21:00:35 Meeting started Thu Jul 11 21:00:34 2013 UTC. The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:38 The meeting name has been set to 'nova' 21:00:42 hello, everyone 21:00:44 who's here? 21:00:49 \o 21:00:50 hi 21:00:52 * johnthetubaguy waves 21:00:53 hi 21:00:54 o/ 21:00:55 o/ 21:00:55 o/ 21:00:56 Morning 21:00:57 heyo 21:01:06 #link http://wiki.openstack.org/Meetings/Nova 21:01:13 #topic havana-2 21:01:19 havana-2 release is next week 21:01:20 o/ 21:01:29 merge deadline is EOD Tuesday, July 16 21:01:42 I've already deferred a *bunch* of stuff to havana-3 that didn't look like it could make it 21:01:47 let's review the list of what's left 21:01:56 #link https://launchpad.net/nova/+milestone/havana-2 21:02:00 \o/ 21:02:12 first up, let's cover v3 API work 21:02:14 cyeoh: hi! 21:02:25 heh ok. 21:02:28 a lot has merged in the last week 21:02:31 \o 21:02:36 so we have about 40 or so extensions merged so far 21:02:46 around 15-20 more to go 21:03:05 I don't think all will make it in - merge conflicts and also we need a newer version of stevedore for 1 of them 21:03:07 ok, so of these blueprints, are any that aren't marked as Implemented feasible for h2? 21:03:19 but they should all flow in not long after 21:04:05 as in, which ones should we go ahead and set for havana-3? 21:04:17 sorry just doing a quick check 21:04:21 i guess about all of them 21:04:26 except maybe "convert core API" ? 21:04:30 https://blueprints.launchpad.net/nova/+spec/v3-api-core-as-extensions might actually be done 21:04:37 there is one more to go and that's it 21:04:37 nice 21:04:44 ok, so let's keep that one in h2 21:04:45 and move the rest 21:04:57 can you update them? 21:05:07 yea the rest are all pretty much dependent on all the extensions being merged before considered done 21:05:09 ok, will do 21:05:12 yeah makes sense 21:05:15 really nice progress though 21:05:32 anything else on v3 API you'd like to discuss? 21:05:36 thx - have had lots of help getting them merged - thank you to all who have pushed them through with all the merge conflicts... 21:05:49 nothing else on v3 API. 21:05:52 sure np, and now you're on the hook to help push the ones through that others write :) 21:05:59 :-) 21:06:08 k 21:06:19 alaski: query-scheduler 21:06:34 alaski: looks like some core bits are in, but not the part where we change the main instance boot code path to use it 21:06:44 Right. 21:06:51 From a dependency standpoint it's not in the way 21:07:03 but there's a little more to do, which probably won't make h-2 21:07:21 ok, wanted to clarify that part was in scope for this blueprint 21:07:22 sounds like it is 21:07:25 and won't make it 21:07:27 so defer to h-3? 21:07:46 yep. That part turned out to be more nuanced than I had hoped. 21:08:12 cool, there are often dragons when you go trying to redo something that has been there for ages :) 21:08:35 dansmith: compute-api-objects 21:08:46 dansmith: have a chance for h-2? 21:08:46 russellb: not gonna make h2, 21:08:50 ack, will defer 21:08:53 comstud: disagree? 21:09:03 no 21:09:15 I wish it were different, but, it ain't. 21:09:16 Too many methods left 21:09:29 boris-42: db-api-tests 21:09:37 boris-42: looks really close to done 21:10:25 according to status on the blueprint, only a few spots left to cover, and 2/3 have patches up for review 21:10:36 so we'll leave this on for h-2 and hope we can get it done by the deadline 21:10:38 boris-42: sound good? 21:10:46 boris may be asleep. :-) 21:11:11 boris-42 would ask everyone to please review those patches. 21:11:28 Heh, so many db reviews 21:11:44 next is cross-service-request-id 21:11:47 anyone know status of that one? 21:12:15 has 3 +2s and a -2 21:12:18 i blocked one of the pacthes for it 21:12:32 because it exposed the cross serive id in a way that any user could set any value for it 21:12:39 and tht would get passed all over the place 21:12:45 kinda defeats the point, IMO 21:13:03 i really like the concept, just not that it's exposed in that way 21:13:18 yeah, seems like users should have no ability to impact 21:13:21 and no knowledge of 21:13:25 right 21:13:27 just an admin thing 21:13:42 ok, well, if it's blocked by a fundamental design issue, i'm deferring it 21:14:00 seems fair 21:14:36 alaski: shelve-instance 21:14:46 just needs review? 21:15:04 yes. two need rebase once the first is in, but everythings up 21:15:50 ok cool 21:15:55 need help reviewing that one then! 21:16:09 Vek has eliminate-clear-passwords-from-cells-table 21:16:13 I think that one is close to ready 21:16:22 i had a problem with the data migration, but we've talked about it and he should have it updated soon 21:16:26 alaski: will take a closer look tomorrow 21:16:34 johnthetubaguy: awesome thanks! 21:16:38 johnthetubaguy: thanks. 21:16:55 next is ec2-error-codes 21:16:59 don't think the author is around 21:17:13 I -2'd that one, because it looked like it needed to be broken up a bunch, but that was after a quick review 21:17:22 he basically asked me to reconsider, and I haven't had a chance yet 21:17:27 so I would appreciate a 2nd opinion 21:17:35 link? 21:17:56 https://review.openstack.org/#/c/28330/ 21:18:11 probably need to give him guidance on how to break it up, that was going to be my response when i get back to it 21:18:19 unless someone else looks and tells me they agree with him that it's fine as-is 21:18:47 I'll have a look when we're done 21:18:52 ok cool thanks 21:19:02 yeah i think that definitely needs to be broken up... 21:19:10 at first glance it looks huge 21:19:11 mrodden: ok, feedback appreciated on the review then 21:19:18 russellb I am here 21:19:21 ok last medium one is from johnthetubaguy 21:19:32 ah, its in review 21:19:38 xenapi large ephemeral disks 21:19:43 so just need review? 21:19:49 got almost approved, just added an extra log 21:19:51 yeah 21:20:04 ok cool, so hopefully we can knock that out in the next few days. 21:20:12 hopefully 21:20:22 the rest still on the list are Low priority ones, anyone around that wants to talk about them? 21:20:44 Low priority ones aren't worried about quite as much from a release management perspective, just nice to haves 21:20:56 if you have time to help review stuff, please focus on the > Low priority stuff first 21:21:26 boris-42: i was reviewing blueprints, covered db-api-tests, looks like there's a good chance we can have it completed for h-2, correct? 21:21:36 yes correct 21:21:45 I will force guys to finish tomorrow all patches 21:21:57 boris-42: that sounds... concerning 21:21:59 if instance_* tests will be merged 21:22:09 then there is just a little bit work 21:22:24 I think we will finish before you wake up-) 21:22:34 mikal: lol, the forcing part? 21:22:38 BTW, anyone know why http://status.openstack.org/reviews/ is not refreshing, maybe I need to check my email? 21:22:50 russellb: yeah, I imagine a drum being beaten at the back of the room or something 21:23:08 mikal: i imagine boris-42 as a russian mob boss 21:23:23 "you WILL finish these patches.... or else" 21:23:41 johnthetubaguy: i do not ... i would ask in -infra. i haven't seen any email about it 21:24:09 =)) 21:24:12 lol 21:24:28 russellb: yeah, I should head over there 21:24:31 ok 21:24:34 so last comment before we move on 21:24:39 user-locale-api is still waiting for reviews, but it also has a prereq. that I am waiting to be merged in oslo, which is actually +2CR right now just waiting for an approval to throw it to Zuul for merge 21:24:55 mrodden: ok, will leave it on the list for now then 21:25:02 so ... havana-3 is going to be insane 21:25:04 https://launchpad.net/nova/+milestone/havana-3 21:25:14 pci passthrough .... 21:25:18 ouch 21:25:24 if you want your stuff to actually land, PLEASE have it up for review as early as possible 21:25:26 it makes m cry 21:25:47 because if even half of that gets implemented, that's going to be pushing our review bandwidth 21:26:07 it also means prioritizing reviews is very important, so we focus on getting the most important stuff in 21:26:11 there are 2 implementations my and Inetels based on my patch 21:26:14 DB patch 21:26:32 that should be rewritten in unified models way 21:26:42 your db patch should be rewritten? 21:26:50 yes, please use the unified-objects stuff 21:27:02 speaking of which, we need to start blocking patches that should be using those, but aren't 21:27:10 basically, creating new DB models and then exposing them to the rest of the code 21:27:14 absolutely agree 21:27:14 needs to be done using the new way. 21:27:30 but this patch is much more older then unified models=) 21:27:38 so it use old way=) 21:27:42 i -2'd another that is in the same situation 21:27:51 but we really can't afford going backwards on this effort 21:28:07 I agree 21:28:09 it's critical for one of the highest priority efforts we have - the long road to solid support for live rolling upgrades 21:28:16 I agree lol=) 21:28:28 same for v3 things, all changes to both apis? 21:28:28 saying it so everyone else understands too 21:28:28 We will help also with this stuff in I cycle 21:28:37 Yea, I kinda crapped all over boris's reviews, unfortunately. 21:28:43 johnthetubaguy: that's a good point ... we should probably start forcing v3 versions as well 21:29:06 +1 on v3 21:29:07 comstud it's ok 21:29:08 yeah, makes sense, for the same reasons 21:29:13 cool 21:29:15 yes, definitely for v3 21:29:31 alright, onward 21:29:33 ok I have to sleep+) 21:29:33 #topic bugs 21:29:38 any particular bugs we need to discuss 21:29:41 boris-42: ok thanks! 21:30:00 67 new bugs, a little more than i'd like 21:30:11 russellb do you need some help?) 21:30:15 with bugs?) 21:30:20 boris-42: with bug triage, always 21:30:22 and fixing them :) 21:30:36 https://wiki.openstack.org/wiki/Nova/BugTriage 21:30:40 russelb ok I add some rule about fixing bugs=) 21:30:53 minimum 1 bug / week 21:30:56 lol 21:30:59 sounds ok to me 21:31:02 for each developer=) 21:31:05 I started triaging - feel free to yell at me if I confirmed anything I shouldn't have. :-) 21:31:08 Fixing bugs you created yourself doesn't count 21:31:18 dripton ok=) 21:31:38 dription I will say them=) 21:31:41 lol 21:31:52 if anyone comes across High/Critical bugs while triaging, it would be good to bring them up here 21:31:55 dripton: that vastly limits the bugs I can fix for credit :( 21:31:58 i want to sure at least those get some attention .. 21:32:33 russellb I would like to merge all models vs migrations syncs in H2 21:32:47 boris-42: ok, we can try. 21:32:55 let's just to sub-teams 21:32:57 it could produce some unexpected bugs in psql and mysql 21:32:57 #topic sub-team reports 21:33:08 anyone around to give a report? 21:33:12 devananda: ? 21:33:13 yeah 21:33:16 Ok see you later=) 21:33:20 scheduler 21:33:23 o/ 21:33:25 \o/ but not that much to report on 21:33:38 devananda: wanna go first? 21:33:44 sure 21:33:45 (Ironic / baremetal driver) 21:34:08 not much to report on. working on the API service for ironic, definitely not going to be ready for h3 in a comparable-to-baremetal way 21:34:25 devananda: i went ahead and deferred the deprecate-baremetal blueprint to post-havana 21:34:38 the tripleo side of baremetal is moving alogn well, but i dont think a lot has changed with the baremetal driver itself 21:34:57 yeah, saw the proposal to make an official program for it 21:34:59 cool stuff. 21:35:05 ironic is still waiting for the image utils to move out of nova and into glanceclient 21:35:24 once that lands in glanceclient, i think GheRivero will be able to propose a DRY-it-up patch to nova and cinder 21:35:27 but that wont be a functional change 21:35:55 that's probably it for the nova side of our work latey 21:36:36 [eol] 21:36:39 ok cool thanks! 21:36:46 johnthetubaguy: you're up, for xenapi! 21:36:51 cool 21:37:03 so not a lot of news really 21:37:20 you need reviews on your h-2 blueprint :-) 21:37:25 some work towards getting XenAPI gated, but not visible progress 21:37:34 oh yeah? didn't know about that 21:37:35 +1 for reviews on that blueprint :) 21:37:46 that's cool to hear actually. 21:37:53 a few h-3 blueprints might get pushed out 21:38:02 johnthetubaguy: btw, did you see my email a week or two ago about "compute driver criteria" ? 21:38:10 yeah, Citrix guys have most of the tempest tests going 21:38:16 devananda: you too, since it affects baremetal ^^ 21:38:25 russellb: I did, but I should re-read it and check it again! 21:38:31 xenapi is already in the clear since it's running in smokestack 21:38:46 hm, nope :( /me goes and looks 21:38:46 :) 21:38:47 baremetal needs to have something going in the next 9 months ... but I believe that's being worked on 21:38:56 devananda: no worries, easy to miss stuff on the ML ... 21:39:12 russellb: tl;dr - we need a smokestack-like test rig, yes? 21:39:14 devananda: basically i want all virt drivers being tested against changes, even if just providing info like smokestack does 21:39:17 yes 21:39:29 russellb: perfect. already talked at length with folks about this, and yea, it's being worked on 21:39:30 and i proposed a Icehouse release deadline basically 21:39:34 perfect 21:39:35 ++ 21:39:54 and on that note ... 21:39:58 hartsocks: hi! 21:39:59 so, Citrix guys are going to updated their blueprints soon, maybe dropping some from h-3 21:40:08 I am all done now though 21:40:11 johnthetubaguy: ok cool, let me know and i'll update them 21:40:13 johnthetubaguy: thanks! 21:40:22 okay. 21:40:23 russellb: thanks, will do 21:40:24 hartsocks: updates? also, did you see that email i'm referencing? 21:40:35 So on VMwareAPI team... 21:40:38 email? 21:40:45 "Compute driver criteria" i think 21:40:55 tl;dr ... are you guys working on some sort of CI integration? 21:40:57 Doesn't ring a bell. 21:41:02 Yes. 21:41:06 ok, then you're safe 21:41:11 i'd like to see it by Icehouse 21:41:23 I was going to mention I heard back from a group working on 'tempest' for vmwareapi stuff 21:41:25 which is a good ways out, so shouldn't be a big deal if you're looking into it already 21:41:36 I'm not going to forecast when they'll have that up 21:41:45 but at some point in the future, i'm going to start to push removing things we're not testing :-) 21:41:55 that's what the openstack-dev ML post was about 21:42:00 kind of a first warning shot about it 21:42:01 Okay. 21:42:22 I will feel much better when we get our test coverage up higher. 21:42:26 * russellb nods 21:42:36 I went around to the H2 blueprint holders... 21:42:41 looked them deep in the eyes... 21:42:44 and asked... 21:42:52 Are you really really going to make H2? 21:42:55 i may have already deferred some/most/all of them ... 21:43:03 if they didn't look like they could make it 21:43:03 Yeah. 21:43:13 if you feel otherwise, let me know 21:43:41 We're close but H2 is too close and a lot of our contributors are traveling in the next couple weeks. 21:43:49 ack 21:44:02 anything else going on? 21:44:04 It looks like H2 will be all about bug fixes for us. 21:44:23 That's the big new. 21:44:28 s/new/news/ 21:44:39 end. 21:44:52 cool, thanks! 21:45:01 n0ano: scheduling! 21:45:23 like others, not too much this week, we talked about two patches going around... 21:45:50 code refactoring - e.g. moving common scheduler & cinder code to oslo, concensus was that's a good idea.. 21:46:08 +1 21:46:13 there is some already in oslo 21:46:16 that nova needs to get updated to use 21:46:24 common filter and weight infrastructure 21:46:30 other was volume affinity filter - concensus there was this was more likely a weighting function rather than a filter 21:46:34 was put there when cinder was doing its filter scheduler 21:46:43 n0ano: ok i was going to ask about that 21:46:55 i'm fine with the weight, but the more i thought about it, the more I'm -2 on the filter as proposed 21:46:58 https://review.openstack.org/#/c/29343/ for reference 21:47:20 indeed, we pretty much agreed with you on that, didn't see any compelling use cases for a filter 21:47:27 ok 21:47:36 that's about it 21:47:39 ok thanks! 21:47:56 harlowja: hi! 21:48:02 howday! 21:48:05 sup? 21:48:44 so just getting the relase of taskflow ready, shaping up, few more items being worked on, then hopefully can start plugging it in for H3 into cinder at least to start 21:48:55 just mostly chugging away on making that initial release possible 21:49:10 chug chug 21:49:14 cool, well thanks for the update, any other details you want to share? 21:49:21 nothing much yet :) 21:49:53 k, thanks! 21:49:57 #topic open discussion 21:50:06 10 minutes left if anyone wants to chat about ... anything! 21:50:33 jenkins is busy. 21:50:38 87 patches total under test right now 21:50:40 30 in the gate. 21:50:46 (across all projects) 21:51:18 other random interesting number ... in nova we've had 3597 code reviews done by 176 people in the last 30 days. 21:51:26 I'm back. Any feedback on patches: https://review.openstack.org/#/c/32040/ and https://review.openstack.org/#/c/32503/ would be nice. 21:51:41 They are related to the cold-migrations-to-conductor bp. 21:52:03 timello_: on my list for tomorrow, a review day for me tomorrow I feel 21:52:14 russellb is there a jenkins monitor that can be used to see how busy it is? 21:52:15 i'll be out of town for over a week 21:52:18 johnthetubaguy: awesome, I appreciate. 21:52:21 johnthetubaguy: cool, appreciate that 21:52:25 with limited online-ness 21:52:37 comstud: ah yes, thanks for the reminder / heads up 21:52:41 comstud: safe travels to you sir 21:52:44 ty 21:53:11 harlowja: there are a couple of things you can use ... one is http://status.openstack.org/zuul/ 21:53:16 hey guys i had a quick question about imagebackend caching 21:53:29 any reasons why were create it per flavor ? 21:53:33 harlowja: the other is https://github.com/kk7ds/openstack-gerrit-dashboard/ 21:53:36 s/were/we/ 21:53:43 harlowja: which is just a command line thingy, but it's pretty awesome. 21:53:49 coolness 21:53:51 russellb: JUST a command line thingy? 21:53:53 mikal: ^ ? 21:53:57 dansmith: hehe 21:54:01 like bash is JUST a command line thingy? 21:54:05 yes. 21:54:10 mkay :) 21:54:18 russellb: curse you 21:54:30 is it using ncurses? 21:54:39 :) 21:54:39 Chinmay_: IIRC, and it might have changed, we cache the glance image, and then the post resize image 21:54:51 Chinmay_: we do that to avoid doing the resize over and over 21:54:58 * johnthetubaguy quietly runs away to bed... 21:55:29 mikal : ok thanks 21:56:40 harlowja: no 21:56:47 harlowja: print! 21:57:08 russellb: I hit that review 21:57:12 the ec2 madness one 21:57:34 dansmith: cool 21:58:08 dansmith: ok so hopefully that's enough to convince him to split it up 21:58:08 russellb hmmm might have to hook in curses :-p 21:58:38 harlowja: yeah 21:58:47 are we done here? :) 21:58:51 yep! 21:58:55 thanks everyone! 21:58:57 #endmeeting