15:00:13 #startmeeting gantt 15:00:13 Meeting started Tue Nov 11 15:00:13 2014 UTC and is due to finish in 60 minutes. The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:16 The meeting name has been set to 'gantt' 15:00:25 anyone here to talk about the scheduler? 15:01:16 hi 15:01:19 hi 15:02:19 #topic Summit recap 15:02:38 PaulMurray, I know you were there so you don't need a summary, vigneshvar were you there? 15:02:49 yes i was there 15:03:11 we can make this quick then, I had 2 main takeaways for the scheduler: 15:03:29 sure 15:03:45 1) Of the kilo imperatives the scheduler clean up is on the list (this is doubleplus good) 15:04:24 2) we have an explicit set of 8 BPs/Specs that, once implemented, everyone agrees the scheduler interfaces are sufficiently cleaned up 15:05:08 after we do 2) in Kilo we can do the actual split to Gantt in L (gantt as an optional scheduler) and the in M we can hopefully make Gantt the default 15:05:14 hi guys 15:05:32 doron_afk, hi, did you see my summit summary 15:05:33 just a quick updates, many folks are away since there's some holiday today 15:06:07 n0ano: sadly, no/ 15:06:22 doron, yeah, I wanted to have the meeting to get things back on track but not much to day. 15:06:27 OK, just to recap: 15:06:33 1) Of the kilo imperatives the scheduler clean up is on the list (this is doubleplus good) 15:06:34 2) we have an explicit set of 8 BPs/Specs that, once implemented, everyone agrees the scheduler interfaces are sufficiently cleaned up 15:06:34 after we do 2) in Kilo we can do the actual split to Gantt in L (gantt as an optional scheduler) and the in M we can hopefully make Gantt the defaul 15:06:45 * n0ano cut & paste sort of works 15:07:12 does anyone have anything else from the summit they'd like to point out? 15:07:13 This is my first time in the meeting. i was working on a different scheduler blueprint. Now since it wont be part of 8 BPs, could i contribute to one of these 15:07:30 yes. To be more specific we have the milestones here: https://etherpad.openstack.org/p/kilo-nova-milestone-targets 15:07:50 prio's here: https://etherpad.openstack.org/p/kilo-nova-priorities 15:07:51 vigneshvar, sure, any help would be appreciated 15:07:58 and scheduler indeed takes a dignified prio. 15:08:28 doron, indeed, that's why I'm cautiously optimistic that we can actually make progress (emphasis on the cautious) 15:08:46 n0ano: +1 15:09:13 to my best knowledge sbauza is reviewing current bp's. 15:09:24 mainly the ones assigned to him. 15:09:54 kind of sequing (sp) into the next topic 15:10:09 #topic scheduler BPs for Kilo 15:10:31 in the agenda email I sent out I listed the current set of 8 BPs/Specs 15:10:46 sbauza commented on that list and we're making progress 15:11:15 once jay gets back from vacation I expect we can find out who's working on what and get some progress made 15:11:35 I intend to create a wiki page to track progress on those BPs (I don't like etherpads for that) 15:11:52 I'll post an email when I have it up and we can fine tune what it looks like. 15:12:03 n0ano: quick Q; 15:12:19 should we break the bp's into smaller tasks? (is it needed) 15:12:27 just to keep track and see we make it on time. 15:12:57 or we can check with jay next week. 15:12:59 n0ano, the list is missing make-resource-tracker-use-objects 15:13:18 doron, potentially, depends upon the specific BP, the isolate DB ones are well scoped and don't need to change, we can study the others to see 15:13:27 PaulMurray, my bad, looks like I missed that 15:13:41 n0ano, I should reply to the list 15:13:53 PaulMurray, I'll be sure to include it into the wiki page and yes, replying on list would be good. 15:14:36 basically, we need to focus on those BPs and make sure we get them included in kilo, that is going to be my focus for this cycle. 15:15:07 n0ano, also something that was to make a pci stats object (s) - like the virt hardware case 15:15:16 and reviews are more than welcome to make sure we have as much progress as possible. 15:16:02 PaulMurray, we kind of punted on the PCI issue, we'll need to get the PCI people involved to clean that up properlyu 15:16:06 PaulMurray: wasn't it decided to keep it as a blob to make sure it does not block the scheduler efforts? 15:16:20 n0ano: indeed so. 15:16:27 doron, that was my understanding also 15:17:19 n0ano, doron, hm, I talked to Jay about it, I went back over the etherpads and found no decision recoreded - I thought it didn't actually get decided 15:17:33 n0ano, doron, do you remember more? 15:17:45 PaulMurray, no, I thought it got left punted 15:17:46 PaulMurray: well not in so many words, but this is what I remember mostly; 15:18:12 ie- pci folks are needed for the cleanup, and it should not block the scheduler work. 15:18:41 doron, that's what I remember and I +1 that plan 15:19:09 ok - I will follow up on that - it was my task to chase up the pci stats 15:19:35 OK, moving on... 15:19:43 #topic opens 15:19:56 anyone have anything else to talk about? 15:20:26 just a big thanks for everyone on their work last week from /me. 15:20:50 doron, NP 15:21:09 OK, I was expecting a relatively short meeting today so I'll let everyone go 15:21:18 tnx and talk to you next week (if not before) 15:21:21 bye 15:21:28 cya all. 15:21:33 since i am new, i would like to know how i can start contributing to scheduler Any pointers or any offline help. I dont want to divert the meeting 15:21:42 #endmeeting