20:07:04 #startmeeting 20:07:04 been busy, so orchestration was back burner till essex RC 20:07:05 Meeting started Thu Mar 22 20:07:04 2012 UTC. The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:07:06 Useful Commands: #action #agreed #help #info #idea #link #topic. 20:07:34 understand, I've kind of been in holding mode thinking that we'll do most of the work at the essex summit 20:07:40 #topic meeting time 20:08:28 Given Thierry's email let's just definitively say that the Orchestration meeing is at 20:00UTC irrespective of daylight savings time 20:09:56 agreed. Updated wiki to that effect,to avoid confusion 20:10:27 sounds good 20:10:37 Main other agenda item is the summit, and what we should accomplish before then. 20:10:45 #agreed meeting time is 20:00UTC 20:10:56 Is orchestration listed as a session topic yet ? 20:11:12 #topic Orchestration summit topic 20:11:21 sorry guys 20:11:25 u am ack 20:11:37 i'm back 20:11:50 sriramhere, np, did you see what we've talked over so far? 20:11:59 I submitted a session proposal 20:12:01 yes 20:12:05 sriramhere: ack :-) 20:12:17 excellent, have you heard any confirmation on that? 20:13:01 not yet. 20:13:18 OK, we'll keep and eye on that and try and make sure it happens 20:13:19 i wanted to briefly talk abt what i had in my mind while submitting the proposal, and what more we can do before the summit 20:13:34 i submitted under Brainstorm - 20:13:57 brainstorm sounds appropriate 20:14:13 mainly to hash out the gaps in the previous blueprints (if at all) and why orchestration slipped out of Essex (so that we can address that) 20:14:44 also, if we can make more progress on blueprint, that d be good. 20:15:08 i also would have liked a presentation session - if we have more clarity on the design. 20:15:35 currently, we have bunch of alternatives talked about, but we need to get to the next step 20:16:00 not sure we have a full idea for a presentation yet, the multiple alternatives would indicate the brainstorm is really what's required 20:16:18 do we have the alternatives written down anywhere? 20:16:44 yes, they are under http://wiki.openstack.org/NovaOrchestrationSpecForFolsom 20:17:42 biggest issue is weaving this all into the cells and resource caching changes. That will probably impact the design. 20:18:55 so where are the resource caching changes being documented, we'll need to know that to do things right 20:19:05 Also, session proposal made me submit new blueprint - which uses the above wiki as spec placeholder 20:19:43 bp itself (derived mostly from previous bp) is at https://blueprints.launchpad.net/nova/+spec/nova-orchestration 20:19:50 would need to look at capacity cache changes. 20:20:19 what i found on the cache changes is old. let me get the link 20:20:26 it would be good if someone can update it 20:21:10 http://wiki.openstack.org/EssexSchedulerImprovements - is this correct? 20:22:16 All of this is why I suspect we're somewhat stalled until the summit - the orchestration idea is valide, but there have been significant changes in essex 20:22:29 mainly scalability, and the referece I'm using is the code 20:22:52 also, I need to jump off shortly. 20:23:08 Can we post an agenda for next week so we can be more productive ? 20:23:44 mikeyp, sure, that's a good idea, that'll give us some time to think about things a little. 20:24:21 mikeyp - would you be able to document something about the cache? 20:25:05 I can dig up the existing documentation and get references on it 20:25:09 gr8 20:25:13 I'm thinking the agenda for next week is `Orchestration and resource cache - read the linked blueprints and come prepared'. 20:25:21 ok 20:25:43 sounds like a plan 20:26:14 #action mikeyp - provide references to docs on resource cache 20:26:34 #action n0ano - post agenda for next week's meeting 20:27:04 #action n0ano sriramhere - read the blueprints mikeyp publishes and come prepared for discussion. 20:27:29 so I'm thinking we're good for today (all the work is next week), anything else before we close? 20:27:37 nothing from me. 20:27:41 also, can we do skype or some voice call for more active disccusions? 20:28:07 other than that, nothing from me 20:28:09 thats possible 20:28:33 note we don't know who will be there, there could be others trying to attend the IRC channel 20:28:47 lets convene here, and take it from there 20:29:05 OK, talk to you then 20:29:14 thanks! 20:29:44 #endmeeting