15:02:36 <garyk> #startmeeting scheduler 15:02:36 <openstack> Meeting started Tue Oct 29 15:02:36 2013 UTC and is due to finish in 60 minutes. The chair is garyk. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:40 <openstack> The meeting name has been set to 'scheduler' 15:03:01 <garyk> the schedule is out for the summit 15:03:58 <MikeSpreitzer> http://icehousedesignsummit.sched.org/ ? 15:04:24 <llu-laptop> Seems I don''t see the scheduler performance session. Boris didn't do that? 15:04:44 <garyk> http://icehousedesignsummit.sched.org/overview/type/nova#.Um_OgiSInns 15:05:03 <garyk> http://icehousedesignsummit.sched.org/event/cde73dadfd67eaae5bf98b90ba7de073 15:05:13 <garyk> rethinking scheduler design - http://icehousedesignsummit.sched.org/event/cde73dadfd67eaae5bf98b90ba7de073 15:05:29 <garyk> smartter placement for work loads - http://icehousedesignsummit.sched.org/event/57775e21d82cf716d435f02c9185db1e 15:05:43 <garyk> metrics - http://icehousedesignsummit.sched.org/event/630d65c8879935f7bc085833f47bb537 15:05:56 <garyk> instance groups api - http://icehousedesignsummit.sched.org/event/b23505a1c59fa2e9e5f94e9467b5a76a 15:06:17 <garyk> russellb has been really generous and nearly the whole of wednesday is scheduling 15:07:07 <garyk> he has also scheduled a number of unconference sessions 15:07:38 <MikeSpreitzer> glad to see it 15:07:51 <garyk> in a sec i will post the link - people can register for 10 minute slots 15:08:20 <MikeSpreitzer> Already? Or when we get there? 15:08:22 <Yathi> are there specific unconference sessions for scheduler, 15:08:24 <alaski> right. There are Nova specific unconferences so there should be a fair number of slots to bring up unscheduled topics 15:08:25 <garyk> https://etherpad.openstack.org/p/NovaIcehouseSummitUnconference 15:08:33 <Yathi> or for Nova in general 15:08:39 <russellb> feel free to sign up this week 15:08:47 <garyk> Yathi: it is specifically for Nova. 15:09:10 <russellb> and if others don't sign up, you can have more time 15:09:31 <garyk> at the moment myself and a few colleagues have registered a topic on resource tracking 15:09:43 <russellb> the one on tuesday might be better for wednesday now that scheduling sessions got moved to wednesday 15:10:34 <garyk> russellb: correct - i'll move it to weds 15:10:37 <russellb> ok 15:11:23 <garyk> the sessions are going like hot cakes :) 15:12:49 <garyk> are there any issues that we would like to discuss today? 15:14:12 <Yathi> Should we make the scheduler related unconference sessions on Wednesday as well ? I thought it will be overloaded for Wednesday hence submitted one for Tuesday 15:14:51 <garyk> Yathi: that is what russellb suggested above 15:14:59 <MikeSpreitzer> I think those of us advocating optimization approach would like it to be in the minds of those in the "rethinking" session 15:15:16 <MikeSpreitzer> but "rethinking" comes before the Wed unconference. 15:15:18 <garyk> regarding demo's there are also opnetsakc unconference sessions where you can register on the day and then get a slotted time 15:15:33 <MikeSpreitzer> 10 min also? 15:15:43 <garyk> those sessions will also be to folks who may not be on the nova track 15:15:51 <garyk> MikeSpreitzer: yes, i think so 15:16:29 <garyk> MikeSpreitzer: in the past there was a board that people could write their topics. It is a good place to show demos etc. 15:17:12 <MikeSpreitzer> Bird in the hand and all that 15:17:48 <MikeSpreitzer> OK if I sign up for a Nova unconference until I get a general one? 15:18:36 <alaski> sure, if you have a topic sign up. If you change later then someone else can use the slot 15:18:48 <MikeSpreitzer> OK, that's my plan 15:19:24 <garyk> i guess that if there is an overflow then the PTL may intervene and prioritize 15:19:52 <russellb> of unconference sign-ups? yeah, if i have to 15:20:02 <russellb> would rather just let it be open and first come first serve :) 15:20:19 <garyk> i guess that if we are having scheduling discussion on wednesday then maybe we can all get together for drinks or lunch on tuesday - put faces to names 15:20:39 <MikeSpreitzer> sounds good 15:20:46 <garyk> russellb: cool. thanks for arranging everything. 15:20:48 <Yathi> have some initial discussions and plans before the session 15:21:00 <Yathi> Tuesday get together sounds good 15:22:16 <garyk> so how about tuesday lunch? we can sync the meeting time in the morning 15:22:38 <MikeSpreitzer> Huh? Lunch time is indicated in the schedule 15:23:35 <garyk> i think 1 − 2 is free for lunch. so maybe we can meet next to the nova room at 1pm and then go and get a table together 15:23:58 <MikeSpreitzer> http://icehousedesignsummit.sched.org/ says 12:45 — 1:20 15:24:53 <garyk> so lets make it 12:50 at the nova room. 15:25:07 <MikeSpreitzer> +1 15:25:14 <garyk> that will give people a chance to attend lightening talks if they wish 15:26:12 <garyk> do we have any other topics to talk about of should we all go to planning our etherpads? 15:26:47 <Yathi> you mean etherpads for the session 15:27:00 <Yathi> sorry it is my first summit.. 15:27:05 <garyk> russellb: on question - in neutron there was talk of not having presentations but just using etherpads for the sessions. will this be the same for nova? 15:27:09 <Yathi> will need to work with you all 15:27:21 <russellb> yes, please 15:27:52 <MikeSpreitzer> Hmm, I was hoping to show templates, screen shots, etc 15:27:55 <russellb> it should be primarily discussion, and only using etherpad seems to be working best 15:28:14 <russellb> having some reference info available is ok ... but just know it's not supposed to be a presentation 15:28:31 <russellb> it's not like materials are forbidden, just not typically used in the sessions that go the best 15:28:32 <russellb> IMO 15:28:35 <MikeSpreitzer> OK. But we're debating API, so concrete examples are really good 15:28:42 <russellb> that's fine 15:28:44 <PhilD> How about always havign an Etherpad (its a great way to capture feedback, etc) - but allow a few slides to be shown if it helps illustrate a specific point 15:28:52 <russellb> yes that makes sense 15:29:41 <MikeSpreitzer> particularly if what you want to show has a URL that can go in the etherpad, I suppose 15:31:03 <garyk> at times a picture/diagram is very important as it helps capture an idea. but we also need to have the dicussion and engage one another 15:31:26 <MikeSpreitzer> right, that's the whole point 15:33:23 <Yathi> we have a few documents being written up with the ideas 15:33:35 <Yathi> they will be good reading material for the sessions 15:34:19 <garyk> Yathi: i think that we should share the ideas before and then discuss things. the etherpads whould have the links to the documents. the etherpads will later be used as part of the BP's or tracking 15:34:23 <MikeSpreitzer> Yes, I was confusing session with demo. For session, writeup beforehand is good. 15:34:58 <MikeSpreitzer> reading beforehand is even better 15:35:04 <Yathi> garyk: But what I am worried is there might be a lot of suggestions overlapping views, etc. how to coordinate 15:35:10 <Yathi> and manage on a etherpad 15:35:48 <garyk> Yathi: from past experience what has worked is a short introduction with diagrams and maybe flows and then discussion. 15:36:21 <Yathi> garyk: ok 15:37:05 <Yathi> garyk: for the Instance group API work - can I create a new blueprint - or use the old one ? we have newer model, newer apis, etc.. 15:37:59 <garyk> Yathi: i think that we can use the existing BP. I think that we just need to make sure that it is updated to contain the latest details 15:38:29 <Yathi> Ok. I will add some links there.. with the latest doc, etc 15:38:36 <garyk> Yathi: thanks! 15:39:14 <garyk> i really think that it is important that we try and get things in in the first or maximum second milestone. that is the only way we may get this through in icehouse 15:39:35 <garyk> timing is of the essence 15:41:26 <Yathi> the discussions I am seeing in the mailing list, everyone wants the whole thing to solved at once 15:41:32 <garyk> i hope that we can convey the ideas in the session that we have. this will certainly help move it forwards 15:41:35 <garyk> :) 15:41:37 <Yathi> but we should realize that we should start simple 15:41:49 <MikeSpreitzer> I am thinking in a roadmap fashion 15:41:52 <Yathi> and that is the attempt to get it started within Nova 15:41:56 <MikeSpreitzer> But I do not want to lose sight of the goal. 15:42:03 <garyk> yup, i agree with the simple. we need it to be robust so that we can build on it 15:42:25 <Yathi> agreed. 15:42:26 <garyk> MikeSpreitzer: it is a process and without stable foundations we will find it hard to get anything done. 15:42:37 <MikeSpreitzer> garyk: agreed 15:43:12 <garyk> i am hoping that we will get to speak about this all at the summit. it is the best place for people to voice their reservations and more importnatly they can express ideas which can help us achieve a common goal 15:43:38 <Yathi> at the summit, we should finalize what can be done in the icehouse time frame 15:43:46 <garyk> agreed 15:43:53 <Yathi> some of the discussions may take a few more summits to implement 15:43:58 <MikeSpreitzer> that being the primary purpose of a summit, right? 15:44:06 <garyk> correct. 15:44:30 <garyk> first we crawl, then walk and hopefully one day run 15:46:02 <garyk> for the development cycle we also need to make sure that the patches can be reviewed - that is posting one huge patch is not a good idea. we need to do small and coherent iterations that can be viewed as pieces in the puzzle... 15:46:09 <garyk> sorry for babbling on 15:46:35 <Yathi> garyk: please go on 15:46:37 <Yathi> it helps 15:46:45 <Yathi> for new comers 15:47:19 <garyk> i hope that at the summit we can break down all of the pieces, assign them to interested parties and then try and sync our work along the way. 15:47:28 <MikeSpreitzer> I think the existing Instance group work provides a model 15:47:36 <MikeSpreitzer> it was broken down into several pieces 15:47:58 <garyk> MikeSpreitzer: yup, that was the plan. hopefully we can continue with that model moving forwards 15:48:41 <Yathi> garyk: I am not able to update that blueprint. I would like to add details and change the owners 15:48:50 <garyk> one thing i think is very importnat for the community is for us to try and let everyone know where we are in the cycle of development and what is current done, being done and what needs to be done 15:49:13 <garyk> Yathi: i think russellb or a core reviewer may be able to change the owner 15:49:18 <MikeSpreitzer> good point. Seeing the whole roadmap is good, not just what's been done so far 15:49:24 <garyk> unless we get senhau to come and work with us again :) 15:49:48 <Yathi> :) 15:49:55 <Yathi> Senhua is not in our team anymore 15:50:24 <russellb> yeah 15:50:27 <MikeSpreitzer> A blueprint could include in its whiteboard a roadmap, right? 15:50:31 <Yathi> russelb: Can you please make me the drafter? and assignee, and let me edit details for this blueprint - https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension 15:50:34 <russellb> just tell me the blueprint and who to assign it to 15:50:47 <russellb> anyone on the nova-drivers launchpad team has the necessary permissions 15:51:12 <Yathi> my full name - Yathiraj Udupi if you search for it 15:51:59 <Yathi> how to join nova-drivers launchpad team ? 15:52:13 <garyk> Yathi: i think that you need to be nova core 15:52:30 <garyk> that is kind of like running the comrades marathon and finishing in a top ten place :) 15:52:54 <Yathi> garyk: I am aiming high 15:52:58 <garyk> :) 15:53:03 <Yathi> some day in the future I hope 15:53:48 <garyk> anything else to be discussed? 15:54:38 <Yathi> I guess this week will not be very productive. preparing for the summit travel, etc. and wrapping up other things 15:56:00 <garyk> ok. so looking forwards to having fruitful discussions. 15:56:02 <MikeSpreitzer> I hope we can continue some discussion in the ML for a couple more days. 15:56:15 <garyk> travel safe and see you guys on Tuesday 15:56:26 <MikeSpreitzer> be seeing you 15:56:43 <Yathi> see you all at the summit .. 15:56:49 <Yathi> signing off until then 15:56:54 <garyk> #endmeeting