14:00:14 <n0ano> #startmeeting nova_scheduler
14:00:15 <openstack> Meeting started Mon Jul  6 14:00:14 2015 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:19 <openstack> The meeting name has been set to 'nova_scheduler'
14:00:24 <n0ano> anyone here to talk about the scheduler?
14:00:34 <alex_xu> o/
14:00:59 * alex_xu found the meeting is changed to better time~
14:01:02 <n0ano> lxsli, now's your chance :-)
14:01:05 <lxsli> Scheduler 2: scheduler rides again
14:01:49 <n0ano> alex_xu, glad at least one person likes the new time (a little early for me but I can handle it).
14:02:29 <alex_xu> n0ano: heh, how the vote out without person glad
14:02:38 <jaypipes> mornin.
14:02:55 <bauzas> \o
14:03:33 * bauzas is also happy to see the meeting earlier :)
14:03:55 * n0ano is a little bleary eyed but NP
14:03:57 <bauzas> it just means that US people will be just awake, so we can try to bypass them \o/
14:04:18 <bauzas> ha
14:04:29 <n0ano> OK, let's start, hopefully edleafe & Paul will catch up
14:04:39 <n0ano> #topic liberty specs
14:04:53 <bauzas> n0ano: PaulMurray didn't make a promise about that one
14:05:05 <lxsli> PaulMurray won't make it
14:05:18 <lxsli> He asked me to mention his compute node patch has finally landed, woot
14:05:29 <n0ano> lxsli, that's excellent news
14:06:14 <n0ano> looking at the priority tracking page looks like 179224 (migration) is the only one not approved, is that on track?
14:06:55 <n0ano> my bad, that one and the request spec object are still not striked out
14:07:12 <bauzas> n0ano: the spec is a priority one
14:07:28 <bauzas> n0ano: as the freeze is only for non-prio specs, we don't have to be afraid of it
14:08:00 <bauzas> n0ano: jaypipes liked it, I hope to see a bit more sponsors by the next days once the non-prio specs are freezed
14:08:15 <n0ano> looks like there's recent comments on this and no -1's so hopefully it's get +2 soon
14:08:24 <bauzas> n0ano: but for the moment, I leave all the reviewers looking at non-prio ones
14:08:55 <bauzas> about the reqspec implementation, well, it deserves reviews
14:09:12 <lxsli> bauzas: I had a look, few small comments but generally +1
14:09:23 <bauzas> lxsli: coolness
14:09:40 <bauzas> so, re the patch series the left things are:
14:09:49 <bauzas> 1/ fix the unittests for the WIP patch on filters
14:10:09 <bauzas> 2/ change the sched RPC API and provide a method using a ReqSpec object
14:10:34 <bauzas> 3/ change the conductor to hydrate the Spec there instead of using build_req_spec()
14:10:51 <bauzas> so, good progress, I hope to put it all done by EOW
14:10:58 <bauzas> and then, review time
14:11:08 <bauzas> and iteration and upload dance
14:11:32 <n0ano> so sounds good, you don't need any help on this do you (I have people that are available)
14:12:17 <bauzas> n0ano: nope, no neede
14:12:20 <bauzas> need
14:12:40 <bauzas> n0ano: tbh, it's a huge change
14:12:56 <n0ano> bauzas, NP (I'm one of the few people in my company that don't think 9 women can make a baby in 1 month)
14:13:20 <bauzas> he
14:13:51 * bauzas takes the opportunity to thank SublimeText and Ctrl-D
14:14:02 <n0ano> sounds to me like the specs are well in hand so, unles someone has an issue, let's move on
14:14:22 <n0ano> #topic Nova mid-cycle meetup
14:14:43 <n0ano> the sprint is in 2 weeks, have we thought about scheduler issues we want to bring up there?
14:15:56 <n0ano> the only one I can think of is splitting the scheduler out, we should have the APIs well defined by Liberty so we should seriously think about what needs to be done for the split in M
14:15:56 <bauzas> I should hassle johnthetubaguy with an expected agenda so I could see where I could lurk
14:16:18 <n0ano> bauzas, I checked the etherpad for it today and it's currently completely empty
14:16:45 <n0ano> looks like no one has thought about the meetup yet.
14:16:53 <bauzas> n0ano: I'm not that worried, but I will appreciate any attempt to clear that out for remote attendees :p
14:16:56 <jaypipes> n0ano: I'd like to discuss how we model flavor and image metadata during the launch request. not sure that's a real scheduler-related thing. kinda.
14:17:07 <bauzas> jaypipes: I like this
14:17:28 <n0ano> jaypipes, not a bad idea, certainly related to scheduling but probably more a Nova API issue
14:17:30 <bauzas> jaypipes: we have many "need an owner/plan" including the AZs stuff
14:17:45 <bauzas> jaypipes: I would appreciate any think tank by the midcycle time about those stuff
14:18:21 <jaypipes> bauzas: I was hoping tdurakov could own the AZ stuff. but I agree with you we need to discuss it.
14:18:32 <bauzas> jaypipes: yeah, I know your spec
14:18:45 <bauzas> jaypipes: what I would like to see is some agreement by the midcycle
14:18:50 <bauzas> - even if I'm not here :(
14:19:00 <bauzas> I mean, there
14:19:06 <jaypipes> bauzas: sure, agreed. it's on my list.
14:19:14 <lxsli> n0ano: +1 to flavor being / becoming a Nova API issue
14:19:37 <bauzas> jaypipes: the hints definition is also not yet agreed
14:19:57 <bauzas> jaypipes: I mean, the hints taxonomy
14:20:09 <jaypipes> bauzas: what do you refer to?
14:20:13 <bauzas> I remember alaski having concerns about that
14:20:22 <bauzas> jaypipes: sec, giving you the mail thread
14:20:33 <n0ano> bauzas, do we need to address the persistance of hints, I seem to remember someone working on that in the past
14:20:41 <alex_xu> alaski: prefer not use json-schema validae the hints
14:21:08 <bauzas> jaypipes: that's pretty related to how someone is describing something like a flavor or image, but to the difference it's for end-users
14:21:21 <bauzas> n0ano: that's not exactly the problem
14:21:26 <alaski> I'm fine with validation of existing hints, as long as additionalProperties is True
14:21:28 <bauzas> n0ano: we don't disagree persisting the hints
14:21:40 <n0ano> bauzas, no but I think persisting the hints needs to be done
14:21:51 <bauzas> n0ano: that's planned :)
14:22:01 <bauzas> n0ano: there is no problem with that
14:22:04 <alaski> well, I'm not totally fine with it.  but am growing less adamant over time
14:22:25 <bauzas> sec, a mail thread is better than me trying to explain
14:22:48 <bauzas> #link http://lists.openstack.org/pipermail/openstack-dev/2015-June/067996.html
14:22:58 <jaypipes> alaski: could you be more specific on what you're not totally fine with? I'm having a had time understanding precisely what we are talking about here.
14:23:11 <jaypipes> ahhhhhhhhhhhhhhhh
14:23:12 <bauzas> alaski: like I said, some grey area is still there, that's not only about API validation
14:23:14 <alaski> it's in the mail bauzas linked
14:23:22 <jaypipes> alaski: I owe you a respond on that thread. sorry man :(
14:23:28 <alaski> np
14:23:34 <bauzas> jaypipes: I owe that too :(
14:24:23 <bauzas> so, yeah, something like AZs, hints, flavor/image definitions and reviewing sprint for the ReqSpec would be awesome
14:24:32 <n0ano> #action all to cogitate on and reply to alaski mail thread on hints
14:25:31 <n0ano> bauzas, good, I'll update the etherpad with those to begin with (maybe I can get a first post :-)
14:25:34 * edleafe just woke up after 3 hours of sleep
14:26:11 <n0ano> edleafe, that's what you get for agreeing to this time :-)
14:26:22 <bauzas> jaypipes: like I said previously, even if not attending the midcycle, I'll be set on Rochester TZ
14:26:30 <jaypipes> kk
14:26:49 <bauzas> jaypipes: so it means it will be possible to do some sprint for the ReqSpec if necessary
14:26:54 <edleafe> n0ano: no, that's what I get for flying the red-eye home from holiday :)
14:27:09 <n0ano> edleafe, ouch
14:27:57 <n0ano> OK, let's think about the mid-cycle and talk again about it next week, the sprint is only 2 weeks away
14:28:13 <n0ano> #topic opens
14:28:18 <n0ano> anything new from anyone?
14:28:59 * johnthetubaguy notes the need for some kind of remote co-ordination with bauzas
14:29:16 <bauzas> johnthetubaguy: don't worry, I'll be online
14:29:35 <bauzas> johnthetubaguy: so, provided some help can be done, I'll be there
14:29:43 <n0ano> johnthetubaguy, will there be a possibility of a google hangout with video at the meetup?
14:29:48 <johnthetubaguy> as a heads up, I have been thinking about a few totally remote follow ups post the mid-cycle if we need those
14:30:11 <johnthetubaguy> n0ano: we hope so, although the room logistics don't sound perfect for that kind of thing
14:30:35 <n0ano> johnthetubaguy, believe me, I understand, we'll just have to do the best we can
14:31:13 <johnthetubaguy> n0ano: +1
14:31:27 <n0ano> anything else?
14:31:31 <bauzas> n0ano: I'm already pretty silent during the summits, I actually just need to hear :)
14:31:59 <bauzas> n0ano: if I hear something that I dislike, I can hassle you guys directly in IRC
14:32:00 <bauzas> :p
14:32:07 <bauzas> johnthetubaguy: ^
14:32:07 <n0ano> silent? are we talking about the same bauzas I know :-)
14:32:30 <bauzas> hah
14:32:45 <bauzas> don't make me wrong, I can talk about cheese for like one hour
14:33:00 <n0ano> better cheese than wine
14:33:09 * bauzas thinks he's seriously diverting
14:33:17 <n0ano> indeed
14:33:18 <lxsli> gotta run o/
14:33:19 <johnthetubaguy> bauzas: I have a better IRC client now, so that should be possible
14:33:31 <n0ano> OK, I think we're done for today, talk again next week
14:33:34 <n0ano> tnx everyone
14:33:35 <bauzas> ++
14:33:40 <n0ano> #endmeeting