21:02:14 #startmeeting 21:02:15 Meeting started Tue Sep 21 21:02:14 2010 UTC. The chair is dendrobates. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:02:16 Useful Commands: #action #agreed #help #info #idea #link #topic. 21:02:24 The agenda is here: 21:02:31 #link http://wiki.openstack.org/Meetings 21:02:54 sirp1: just in time. 21:02:58 #topic Glance Status 21:03:29 so, ill start by giving a quick background in case you guys aren't familar 21:04:04 glance is the overarching project for two components: the a) caching image proxy (nicknamed Teller) and b) the image registry (nicknamed Parallax) 21:04:31 o/ 21:05:36 right now not much exists for either; a minimal framework to get started was just merged in (still needs gundlach's recomendations taken into account) 21:05:50 and _0x44 is working on the Swift Backend 21:06:41 sirp1: is it reasonable to expect Glance for Austin? Could additional resources be useful to you? 21:06:59 no work started yet on parallax, but for the austin release that should be pretty trivial, we just need to expose a registry (possibly backed using the ORM merge from nova) and exposed through a wsgi we service 21:07:14 FF == 9 days 21:07:30 for the record. 21:07:41 jaypipes: additional resources would be much appreciated as im pretty swamped on RS internal stuff right now (and for the forseesable future) 21:08:39 sirp1: I'm about 70% complete on the NoSQL driver for the new datastore backend. Should be finished tomorrow. I can help. 21:09:04 jaypipes: awesome. 21:09:06 jaypipes: excellent 21:09:21 I know that chmouel was looking for something as well. 21:09:27 maybe he can help. 21:09:36 sirp1: I'll work with you offline on some reasonable blueprints to get done by Austin for Glance. 21:09:41 the goals of glance for austin were pretty modest, so i think we could still get it in, but more resources will be needed 21:09:47 k 21:09:56 jaypipes: good deal 21:10:13 #done glance update 21:10:16 ok, I think that covers that 21:10:28 #topic Blueprint status 21:10:39 I would like each person who is assigned a blueprint to give us a quick update. 21:10:45 We will be doing this in every future release meeting. 21:10:55 The object is to know status, not put you on the spot. 21:11:00 link to blueprint list? 21:11:01 If the status has not changed since the last meeting feel free just to say, "no change" 21:11:18 https://blueprints.launchpad.net/nova ? 21:11:20 Here is the list: 21:11:29 #link https://blueprints.launchpad.net/nova/austin 21:11:41 ah, that one is better 21:11:49 dendrobates: it is likely that we will have to drop large file support for the austin release in swift 21:11:54 In the future I will make sure to include swift. 21:11:58 #info jaypipes 70% complete on https://blueprints.launchpad.net/nova/+spec/austin-nosql-datastore-adapter 21:11:59 Hm... It seems completed blueprints vanish off that list. 21:12:00 i can go next, since openstack-api is second. it's assigned to todd but i think i kind of took it over 21:12:12 creiht: ok, good to know. 21:12:30 dendrobates: otherwise everything else on swift is on track 21:12:35 #info getting worried about api. getting EC2 off of Tornado took way longer than expected, mostly due to merge headaches. 21:13:01 it's off now, but all of Servers remains to be done, and cerberus has been too swamped w/ RS stuff to attack that yet 21:13:16 if anybody (eday?) would like to split Servers up w/ me & cerberus it would be great 21:13:28 eday: how about it? 21:13:43 <_cerberus_> There is *some* progress on the servers API, but not as much as I'd like. 21:13:46 * gundlach wasn't clear: "all of Servers remains" means that the RS API /servers endpoint doesn't exist yet 21:13:53 dendrobates, gundlach: Yeah, I'm helping with some API cleanup right now, and can help with those other bits 21:14:16 I may be able to grab some of it. I've never done REST API's before, though. 21:14:29 gundlach: with the extra help, is API at risk? 21:14:49 soren, the frontend can be taken care of -- it's the mapping of e.g. reboot() function to whatever the backned bits of Nova are required to actually reboot -- that kind of thing 21:15:07 dendrobates: lemme pass that to cerberus, since he has a better feeling for the scope of servers. cerberus? 21:15:12 pvo: any chance of freeing up RS resources to push toward FF? 21:15:13 you had mentioned changes-since maybe needing to drop? 21:15:25 gundlach: That part I feel pretty confident about. 21:15:33 dendrobates: I'm working on that right now 21:15:50 soren: great, then potentially let's add you to the 4-way meeting where cerberus eday you and i split up tasks :) 21:15:54 gundlach, soren, _cerberus_: I'm guessing between the four of us we can crank it out pretty quickly 21:15:55 cererus isn't here 21:16:05 there he is 21:16:05 <_cerberus_> eday: Most likely 21:16:33 _cerberus_: with the extra help, is the API at risk in your opinion? anything you think will still need to be dropped? 21:16:35 soren: what is the status of your 25 other blueprints, do you have time? 21:16:47 <_cerberus_> I don't believe anything is necessarily at risk, no 21:16:48 dendrobates: Done. 21:16:53 dendrobates: So yes. 21:16:54 :) 21:16:56 <_cerberus_> We've made good progress so far 21:17:06 <_cerberus_> Extra help is always appreciated 21:17:08 cool. i'll email you/soren/eday to start talking about splitting up tasks 21:17:13 dendrobates: Well, the last three are still awaiting review, but otherwise done. 21:17:27 are any of the anso guys here? 21:17:28 dendrobates: Last three branches, that is. Not blueprints, obviously. 21:17:50 OK, so some action items out of this? grr, that sounds so very Deloitte and Touche. 21:18:09 dendrobates: no, I pinged vishy to join us on the main chan. 21:18:19 #action soren to be added to gundlach's 4way 21:18:30 hmm, that doesn't sounds quite right ;) 21:18:37 It doesn't, no. 21:18:45 * gundlach pointedly ignores the innuendo 21:18:45 And now it's recorded for eternity. 21:19:01 #action jaypipes, sirp1 tackle blueprints for Austin's Glance. Split up between 2. 21:19:12 Oh, well. I'm sure there's worse stuff out there about me. 21:19:15 #action gundlach to FU w/ cerberus eday soren to get tasks split up 21:19:56 the anso guys sent some update privately that I have not had time to summarize 21:20:23 due to an extended debate with swardley on twitter :( 21:20:44 I will send, or get them to send updates to the list. 21:20:55 in the future, if you cannot attend, please send me a quick status by email 21:20:56 dendrobates: be a lover, not a fighter. ;) 21:21:13 Also, it would be very helpful if you would go into launchpad and update the status, before each meeting, if necessary 21:21:36 jaypipes: it is very difficult to argue in 140 char 21:21:54 dendrobates: :) 21:21:57 #topic Bexar Design Summit prep 21:22:06 At the upcoming design summit we will be discussing and specing out work for two 3 month releases. 21:22:24 dendrobates: I sent out a reminder to update blueprints/bugs to the ML. Would be best if you did that on Mondays I think. 21:22:25 I need everyone to be thinking of what they want in openstack in ~April 2011. 21:22:50 jaypipes: I know. It's on my list 21:22:59 We need blueprints created for each feature so we can schedule sessions to discuss them. 21:22:59 sparkycollier, spectorclan: any update on summit stuff? 21:23:10 We are trying to document the process. 21:23:16 #link http://wiki.openstack.org/Process 21:23:24 jaypipes: ther will be soon 21:23:26 dendrobates: I'm happy to put blueprints together. 21:23:39 jaypipes: i am meeting with folks on Thursday to finalize much of plan external to agenda 21:23:49 We will be doing this summit differently than the first one. The sessions will be smaller and more technical. 21:23:56 spectorclan: ++ cool. 21:23:59 We will have multiple sessions running simultaneously. 21:24:13 So you will need to pick the ones that interest you. Launchpad will let you register interest in a blueprint or make yourself mandatory. 21:24:13 #agreed 21:24:15 jaypipes: party just for developers Thursday night is a go! 21:24:21 spectorclan: :) 21:24:24 :( 21:24:30 * soren leaves Thursday morning 21:24:33 It will be very helpful if you make use of this, it will help us schedule the sessions. 21:24:44 soren: we do have a party first night for everyone 21:24:45 soren: then just get drunk on the plane. :P 21:24:48 soren: has too many weddings to attend 21:24:58 I'll get drunk Wednesday night. You can all watch. 21:25:03 We need to have a basic idea of what we will be producing over the next six months. 21:25:14 soren: been there done that 21:25:14 It is not necessary to target a specific release yet, we can prioritize the list after the summit discussions. 21:25:21 zul: :) 21:25:27 Blueprints are not limited to features, we can have tracks to discuss community, governance, documentation, process. 21:25:43 Basically anything we need to talk about as a group. 21:25:52 ++ 21:25:56 any questions? 21:26:31 ok 21:26:43 this may be our first quick meeting 21:26:46 hey all: sorry i'm late 21:26:57 np 21:27:03 we had a mandatory building emergency meeting 21:27:08 vishy: no worries. 21:27:27 can you give us updates on the anso blueprints? 21:27:31 vishy: I thought you guys lived on the international space station? :P 21:27:52 #topic Blueprint II 21:28:10 or the ones you are working on, at least? 21:28:31 are any at risk for not making feature freeze? 21:29:21 vishy: ? 21:29:38 reevacuated 21:30:07 so vishy is only listed on the orm refactor which is done. 21:30:21 We'll move on. 21:30:35 #topic Feature freeze 21:30:42 dendrobates: did you see anything about the other anso blueprints? 21:30:56 I only saw rescue, guest agent and ajaxterm 21:31:05 dendrobates: i can update 21:31:08 there were some emails today 21:31:17 I didn't know if you saw anything for migrations and snapshots 21:31:19 #topic Blueprint II 21:31:19 anotherjesse is nearby 21:31:39 nothing pushed for migrations and snapshotting yet 21:31:40 pvo I did, but did not read completely yet. 21:32:01 thannks vishy 21:32:41 vishy: does it look like migrations and snapshotting will make it by FF? 21:32:56 dendrobates: yes that is the plan 21:33:28 ok 21:33:33 #topic Feature freeze 21:33:44 Feature freeze is coming up quick. Just 9 days away and counting. 21:33:54 Please don't wait to merge your code until then. The more time we have for review the better. 21:34:23 By next Tuesday, if I haven't seen any merge request, do not be surprised to find your blueprint retargeted to the next release. 21:34:23 could you define feature freeze for me again vs post-freeze-bug-fixing? 21:34:32 yes 21:34:50 the features have to be merged, but can be buggy 21:34:54 e.g. if some aspect of servers is stubbed out but not complete, does that get axed? 21:35:00 bugs will be fixed and testing will be done 21:35:04 after FF 21:35:19 we will have a final freeze close to the release 21:35:21 ok so in good faith we should assume FF represents code that is finished. we may find bugs, but we shouldn't *know* about missing functionality. 21:35:54 yes, but soren has experience getting around freezes, so I'd talk to him. 21:36:00 heh ok 21:36:04 hopefully we won't need to :) 21:36:44 it depends, if a blueprint is marked as essential, we might consider pushing the date if we can;t complete it. 21:36:46 Heheh :) 21:36:51 * soren whistles innocently 21:36:53 the release date that is 21:37:00 , but that would be major. 21:37:10 kthx 21:37:26 If you have any questions or concerns please contact me. 21:37:47 any other release questions? 21:38:11 #topic Meeting time 21:38:21 Anyone want to complain? 21:38:28 nope. 21:38:45 * zul looks around for ninjas 21:38:46 dendrobates:is this a fixed time every week? 21:38:51 yes 21:38:57 unless it isn;t 21:39:00 I wouldn't mind if it were a bit earlier, but it's ok. 21:39:02 good over here 21:39:21 spectorclan: we will reconsider it as necessary 21:39:21 my wife and my kid wouldnt mind if it was a bit earlier as well 21:39:34 it's a good time for us in Tokyo 21:39:54 any earlier would be pretty rough 21:40:01 #topic any other business? 21:40:11 anything anyone wants to talk about? 21:40:22 this is the first time we have finished early 21:40:33 lets not make it the last time :) 21:40:52 I will always try 21:41:07 5 21:41:08 4 21:41:09 3 21:41:10 2 21:41:11 1 21:41:16 #endmeeting