14:04:05 #startmeeting nova_scheduler 14:04:06 Meeting started Mon Mar 14 14:04:05 2016 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:04:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:04:09 The meeting name has been set to 'nova_scheduler' 14:04:15 mornooning 14:04:25 moooooo 14:04:40 evening 14:04:41 so, while we wait US folks because those are forgetting the daylight shift... 14:05:33 anyway, we can start and people can read logs 14:06:08 #topic features (those we like but don't approve yet) 14:06:50 #info Nova still on FeatureFreeze with RC1 planned this week 14:06:57 johnthetubaguy: correct ^ ? 14:07:09 I mean for the RC1 stuff 14:07:10 +1 14:07:19 I have a doubt, lemme check 14:07:53 yeah, http://releases.openstack.org/mitaka/schedule.html 14:07:56 RC1 this week 14:08:06 so that means we should open newton soon ? 14:08:18 after RC1 is cut 14:09:01 I take that as a yes :D 14:09:29 silence means approval :) 14:09:49 so, folks, nothing to raise for feature-related changes, just a general comment : prepare your patch series, those should be reviewable soon :) 14:10:21 moving on ? 14:11:03 bauzas: yeah please continue 14:11:15 not_bauzas : okay, fair enough 14:11:21 does it mean I should resubmit the spec to open https://review.openstack.org/#/c/262938/ again? 14:12:01 * cdent appreciates bauzas' effort 14:12:16 Yingxin: indeed, all approved specs require another approval for Newton but that should be a fast-approve 14:12:27 Yingxin: ie. only one core +2/+W 14:12:45 Yingxin: one *nova-specs* core tbp 14:13:03 bauzas: get it 14:13:22 Yingxin: that will be the top prio for the pre-summit period, reviewing all pending specs to approve 14:13:39 Yingxin: and ideally, merge things which were close to be, but missed the deadline 14:14:24 Yingxin: just keep in mind that cores are still chasing regression bugs for the RC period until we deliver Mitaka 14:14:37 so we'll not be full steam ahead 14:15:00 anyway, moving on 14:15:20 #topic bugs (those we don't like but we need to fix soon) 14:15:34 so, 14:15:56 I was reviewing bugs at the end of last week, tagged scheduler and found many of them were not actionable 14:16:01 either because they are too old 14:16:13 or because the debate associated with the issue has tailed off into nothing 14:16:23 I'd much prefer to see bugs like that die in a fire than cloud up the radar 14:16:30 +++++ 14:16:58 cdent: just leave a very gentle comment asking those to be reproduced against master, and put them Incomplete 14:17:26 there are another two bug fixes in https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking 14:17:30 * cdent will endeavor to do so 14:18:13 Yingxin: scheduler-related ? 14:18:16 but I thought they are not so urgent to be merged in Mitaka 14:18:21 bauzas: yes 14:18:23 Yingxin: I don't see those 14:18:34 oh, in the sched section 14:18:41 https://review.openstack.org/#/c/290302/ 14:18:51 https://review.openstack.org/#/c/292362/ 14:18:55 Yingxin: so that's a good point 14:19:05 Yingxin: I suspect those aren't regressions, right? 14:19:15 bauzas: yes 14:19:37 Yingxin: so in general we prefer to leave the mitaka-rc-potential tag for regression bugs 14:20:06 Yingxin: that doesn't mean we can't land those bugfixes, just that they won't have the same priority as for regression bugs 14:20:15 Yingxin: but I can certainly take a look on both :) 14:20:30 bauzas: thanks :) 14:21:06 Yingxin: TBC, once we cut RC1, those bugfixes won't be in Mitaka 14:21:17 if we merge those after the RC1 tag 14:21:27 because we branch Mitaka right after RC1 14:22:09 Yingxin: so, if you'd like to get them for Mitaka and those are Newton, you'll have to tag the bug report as mitaka-stable-potential (once RC1 is cut this week) 14:22:14 Yingxin: gotcha ? 14:22:38 bauzas: yup, need to read carefully 14:23:26 Yingxin: it's just a matter of knowing what to land and when :) 14:23:34 but we can discuss that later offline 14:23:46 so they are mitaka-stable-potential if they are not so urgent to fix in mitaka? 14:23:58 Yingxin: only if you consider them valuable for mitaka 14:24:07 Yingxin: per the stable policy 14:24:36 Yingxin: I'm just trying to explain that those 2 bugfixes can be merged before or after RC1 this week 14:24:50 bauzas: ok 14:25:04 Yingxin: but depending whether it will be before or after the RC1 tag, they will respectively be either in Mitaka or in Newton, gotcha ? 14:25:25 bauzas: gotcha 14:25:35 ok, moving on, unless someone shouts no 14:25:37 now 14:27:37 #topic open discussion 14:27:46 folks, the mic is yours 14:28:12 I already made my moan, I've got nothing else. 14:29:07 nothing really I have in mind this time 14:29:24 nothing else, too 14:29:37 honestly, I don't see necessary to discuss about Summit talks 14:29:50 or rather design sessions 14:30:26 johnthetubaguy: I know you're leaving off your ring, but do you plan to open an etherpad for newton design session proposals ? 14:30:30 hey, so can I help answer questions for you cdent? 14:30:36 I just did that actually 14:30:43 #link https://etherpad.openstack.org/p/newton-nova-summit-ideas 14:30:43 awesomeness 14:30:47 about to send an ML note 14:30:51 heh 14:30:52 meant to do it last week, oops 14:31:00 * bauzas is bluetooth-paired on johnthetubaguy 14:31:25 lemme annonce that unofficially :) 14:31:30 johnthetubaguy: questions about the bugs I was moaning about? It's more of a cultural complaint than specific issues with specific bugs (although that too) 14:31:51 #info Austin design session proposals can be shared in https://etherpad.openstack.org/p/newton-nova-summit-ideas more to come in a ML thread 14:31:51 cdent: so you can kill all those that don't seem actionable, as I understand it 14:32:29 cdent: our historic issue is lack of attention, markus_z is starting to get progress there again 14:32:45 roger that 14:32:57 (american roger that, not british) 14:33:00 TBH, we are not the most aggresive project for abandoning bugs, so we can certainly be a little bit more concerned 14:33:14 cdent: I think part of the issue is not everyone agreeing how to kill them 14:33:27 cdent: ack! 14:33:31 From what I can tell I don't have all the options available to me. 14:33:52 cdent: have you joined the bug triage group, and read the triage guide? 14:34:15 I've read the triage guide, but I'm not aware of joining a group. 14:34:28 * cdent can't keep track of his own actions 14:34:41 cdent: see line three: https://wiki.openstack.org/wiki/Nova/BugTriage 14:35:19 cdent: honestly, we might want to get rid of that group, it just seems to be causing problems 14:35:20 thanks, done 14:36:05 permissive forgiveness rather than membership does seem to be the zeitgeist these days 14:36:34 cdent: for some reason, we are doing both 14:36:41 * bauzas googles 14:37:03 i.e. permissive membership (makes up new term) 14:37:31 how very british, it's kind of like how you buy a membership to a health club but still need to pay every time you go 14:37:41 * cdent boggles 14:37:54 * bauzas thanks Wikipedia 14:38:48 anyway, that does sound a tool problem with launchpad 14:39:05 * bauzas likes opening scars and putting salt on those 14:40:08 I think we're done, yeah? 14:40:12 I hope so 14:40:38 20 mins for getting a membership for health club 14:40:54 ++ folks 14:41:00 #endmeeting