21:00:38 #startmeeting nova 21:00:38 well, depends on horizontal or vertical split 21:00:39 Meeting started Thu Mar 27 21:00:38 2014 UTC and is due to finish in 60 minutes. The chair is russellb. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:43 The meeting name has been set to 'nova' 21:00:48 hello! who's here? 21:00:51 hi 21:00:52 I am 21:00:52 lo 21:00:53 o/ 21:00:53 hi 21:00:53 o/ 21:00:55 o/ 21:01:00 . 21:01:00 o/ 21:01:02 hi 21:01:12 #link https://wiki.openstack.org/wiki/Meetings/Nova 21:01:22 #topic icehouse-rc1 21:01:28 \o 21:01:36 goal is to release icehouse-rc1 by end of week (tomorrow) 21:01:39 so let's see how we're doing 21:01:46 #link https://launchpad.net/nova/+milestone/icehouse-rc1 21:02:04 4 bugs left to go, so let's go through them one by one 21:02:12 https://bugs.launchpad.net/bugs/1296913 21:02:13 Launchpad bug 1296913 in nova "GroupAntiAffinityFilter scheduler hint no longer works" [High,Confirmed] 21:02:17 This one is on me 21:02:28 and i have a fix running unit tests locally at the moment 21:02:32 will post once they finish 21:02:54 could use reviews once the fixes are up 21:03:06 https://bugs.launchpad.net/bugs/1112912 21:03:12 Launchpad bug 1112912 in nova "get_firewall_required should use VIF parameter from neutron" [High,In progress] 21:03:14 another one that came up this week 21:03:16 fix is in the gate 21:03:46 https://bugs.launchpad.net/bugs/1295381 21:03:47 Launchpad bug 1295381 in nova "VMware: resize operates on orig VM and not clone" [High,In progress] 21:03:52 what's the status on this one? 21:04:01 * jogo walks in late 21:04:02 * russellb hasn't looked today 21:04:19 * hartsocks walks in late as well 21:04:20 that one has been reviewed and updated today 21:04:26 im checking on it just a sec 21:04:36 tjones: OK thanks 21:04:40 kinda troubling that that one is still evolving this late 21:04:48 since it's not a small fix 21:05:04 jenkins has not voted on the latest version for some reasn 21:05:11 minesweeper is dead today due to an upgrade from grizz to havana 21:05:13 check zuul? 21:05:28 tjones: so we're not going to get a minesweeper read on this one? 21:05:38 since this bug is in only 1 virt dirver for one operation, is it still a blocker for RC1? 21:05:50 dansmith: im hoping we will. arosen is working like mad on it 21:05:50 I would like to see it make RC1 of course 21:06:16 jogo: maybe we hold this for later rcs once we get a minesweeper read? 21:06:20 tjones: how bad would it be if it misses rc1? 21:06:41 i don't want to *plan* on an rc2 ... but based on history, seems quite likely 21:06:43 we had a good run yesterday with minimal changes today. it would mean resize basically is broken 21:06:54 it resizes the wrong vm disk 21:07:06 tjones: this can always be one of the first backports to stable/havana if needed. 21:07:18 jogo: stable/icehouse? 21:07:22 yeah 21:07:24 heh, right 21:07:25 tjones: derp yes 21:07:45 so you guys think we should block until minesweeper can run on it? 21:07:51 I think we should 21:07:57 yeah .. 21:08:20 ok i will let you know as soon as it gets running. it will be the 1st patch in 21:08:25 I think the risk to DB migrations from this patch is very minimal 21:08:26 tjones: perfect 21:08:37 but I am all for being cautious 21:08:41 so should I untarget it? 21:08:46 dansmith: no leave it 21:08:49 let's plan on it going in 21:08:55 but if it's the last bug standing, then we can untarget 21:08:57 okay 21:09:00 russellb: ++ 21:09:18 tjones: be sure to make noise once it gets a run 21:09:27 russellb will do 21:09:50 https://bugs.launchpad.net/bugs/1240922 21:09:51 Launchpad bug 1240922 in nova "VM don't resume after detaching volume" [Medium,In progress] 21:10:01 status on this one? 21:11:04 that's on ndipanov, but i bet he's sleeping :) 21:12:03 that one has a patch, https://review.openstack.org/#/c/83505/ 21:12:08 needs review 21:12:37 i just +2d it 21:12:39 seems reasonable to me 21:13:30 also, the instance group fixes ... https://review.openstack.org/83588 https://review.openstack.org/83589 https://review.openstack.org/83590 21:13:37 +Aed 21:13:41 jogo: thanks! 21:13:57 any more issues related to icehouse-rc1? 21:14:09 looks like we're on target to be able to do rc1 tomorrow, so that's great 21:14:29 really appreciate everyone's help keeping this bug list under control 21:14:30 http://old-wiki.openstack.org/rc/ 21:14:34 \o/ 21:14:39 a pretty clean burndown line 21:14:49 tjones: and thanks for your work on bug wrangling! 21:15:07 russellb: my pleasure - i love bossing people around ;-) 21:15:12 hehe 21:15:26 #topic bugs 21:15:33 tjones: any other bug talk for today? 21:15:54 nothing critical - let me check the untagged real quick 21:16:02 OK 21:16:17 it changes quickly. i'll let you know if i see anything 21:16:29 OK 21:16:38 melwitt: anything on the novaclient bug queue today? 21:17:00 dims had a novaclient patch for an ipv6 parsing bug 21:17:05 don't know if it's critical 21:18:09 russellb: nothing looks new but I need to go through it more 21:18:16 melwitt: ok all good thanks! 21:18:18 #topic blueprints 21:18:25 #link http://lists.openstack.org/pipermail/openstack-dev/2014-March/030576.html 21:18:31 the mail above discusses the updated blueprint plan for Juno 21:18:43 the summary is that we've added a git repo so we can use gerrit for doing review of specs 21:19:01 we've been working quickly to get this ready for when Juno opens (as early as tomorrow) 21:19:14 the email above has links to the repo's README and the template we've been building to base specs on 21:19:26 any comments/questions/concerns on this updated process? 21:19:40 russellb: how far off are we from doc generation and gating 21:19:50 jogo: nothing done there yet AFAIK 21:19:56 it's a spinx project now at least 21:20:00 sphinx. 21:20:01 and do we have a domain we can publish too? 21:20:05 nova.openstack.org/? 21:20:09 no idea 21:20:17 Has there been any test runs? 21:20:17 git.openstack.org :-p 21:20:24 jogo: publishing the sphinx job really isn't critical 21:20:26 leifz: test runs in what sense? 21:20:33 sdague: that's how i feel too 21:20:41 the entry point is blueprints.launchpad.net 21:20:44 Somebody run their blueprint through? 21:20:48 sdague: well we want to make sure the blueprints are easy to read 21:20:51 leifz: not yet 21:20:58 jogo: blueprints.launchpad.net 21:21:02 we've been blocking doing real reviews on specs while we work out the template 21:21:15 github will render the files i bet 21:21:24 Sure thing. :-) 21:21:24 yeh, valid rst will render 21:21:35 https://github.com/openstack/nova-specs/blob/master/specs/template.rst 21:21:37 one issue with the current template: 21:21:48 when someone fills it out, it will be hard to see if they skipped any sections 21:21:55 jogo: i was thinking about that 21:21:56 being they will just delete the stuff 21:22:04 I liked the idea of rst comments 21:22:07 for now i'm thinking have the template open in another tab as you go through and read it 21:22:25 all the rst comments might be really annoying/distracting when trying to read it in gerrit 21:23:03 before we open the propsals up I think we should try this with a single propsal 21:23:10 so we can work out any kinks 21:23:17 russellb: that may work 21:23:21 OK 21:23:28 mikal: may have one 21:23:38 could file a pretty simple "backportable DB migrations" blueprint 21:23:40 jogo, could have a test that fails if a section has less than x words and does not start with "None." 21:23:42 i can volunteer spawn refactor ;-) 21:23:45 that's something we know we want to approve 21:23:49 i mean for hartsocks 21:23:51 so we can get it through quickly 21:23:55 I was planning on writing the spawn refactor proposal. 21:24:21 I was planning on posting something on that as soon as you folks were ready I meant to say. 21:24:28 I was thinking https://review.openstack.org/#/c/80865/ 21:24:33 I have another question: when we switch to the new system, when does a BP go into launchpad? 21:24:40 mikal already claimed 'first' 21:24:47 mspreitz: it's basically the same process in launchpad as before 21:24:49 Heh 21:24:56 * jogo waves at mikal 21:25:02 the addition is that the "link to spec" on the blueprint has to point to a review in gerrit 21:25:10 instead of a wiki page, google doc, or nothing 21:25:10 So a BP goes into both places at the start? 21:25:14 yeah 21:25:16 that make sense? 21:25:23 it's basically standardizing on where specs go 21:25:28 got it 21:25:28 I need to tweak mine to match the new template but I could do that today to one of them if we wanted a test case 21:25:31 and reviewing them through gerrit 21:25:43 that could be stated explicitly in the intro to the new system 21:25:48 if we block everything on one BP, i want to pick the simplest one possible to expedite it 21:25:58 makes sense 21:26:16 I have to go now. Bye 21:26:18 why block everything? especially reviews? 21:26:33 devoid: jogo was interested in a trial run 21:26:55 i think the juno equivalent of https://blueprints.launchpad.net/nova/+spec/backportable-db-migrations-icehouse would be quick and easy though 21:27:18 that has to be the first db migration merge anyway 21:27:32 russellb: that works 21:27:35 k 21:27:41 i can write that up tomorrow 21:27:48 once rc1 is sorted 21:27:56 anything else on the blueprint plans? 21:28:41 I'll just need help walking through the new procedure when it comes time to propose the spawn-refactor stuff. 21:28:53 hartsocks: yep, np 21:28:57 #topic open discussion 21:29:00 I'm sure a number of other folks will be in the same place. 21:29:03 https://bugs.launchpad.net/openstack-ci/+bug/1282629 21:29:04 Launchpad bug 1282629 in openstack-ci "Log #openstack-nova in Eavesdrop" [Medium,Incomplete] 21:29:15 if you have an opinion on whether #openstack-nova should be logged or not, please comment on that bug 21:29:30 most channels are logged. i don't really like it, but happy to do whatever most people want 21:29:34 just vote on the bug 21:30:07 russellb, yea, and I've switched my opinion on it. but there were +1's there and I don't want to close it for them. 21:30:28 a vote of -1 is fine too if that's how you feel 21:30:29 whichever 21:31:14 * dansmith just voted 21:31:18 russellb: do you know any method to search the log easily? I think a lot of discussion happens on IRC, so it will be helpful if some tools to dig out information from the log. 21:31:29 google if it's logged 21:32:00 * hartsocks voting -1 on logging 21:32:01 russellb: thanks. 21:32:08 * geekinutah votes -1 21:32:14 im fine with not logging - i have a proxy 21:32:18 yiang5_1: I suspect a lot of people just use irc loggers like znc and then just use grep 21:32:59 any other topics for today? 21:33:04 how many -1 votes does it take? :) 21:33:05 cyeoh_half: thanks for information. I will check what's znc :) 21:33:06 getting close to opening juno! 21:33:23 as it was likely my question in irc yesterday that brings that topic up .. 21:33:32 yjiang5_1: it's pretty simple but i can help if you need it 21:33:59 tjones: really thanks and will turn to you if need any help. 21:34:00 I also log... but if it isn't not a logged channel I prefer to make sure I only refer to old info for personal use 21:34:42 It's radically different to keep channel logs for your own use than it is to expose the channel logs to a web crawler. 21:34:53 yes 21:35:47 yep. 21:36:11 hartsocks: yea I think this only comes up because lots of people new to IRC, can't stay connected all the time and dont know about irc proxies 21:36:25 so we could just point people to them when they ask about logging 21:36:42 Or write up a "how to irc" wiki page 21:36:51 I've deliberately avoided building a proxy for myself. I can't possibly keep track of everything. I might change my mind late, however. 21:37:17 znc rocks 21:37:27 hartsocks: depends on what timezone you're in. For some people it's really necessary 21:37:31 +1 for znc! 21:37:36 cool. 21:38:03 anything else? otherwise we can close up early 21:39:42 +1 for early! 21:39:47 k :) 21:39:49 thanks everyone! 21:39:53 #endmeeting