15:01:46 #startmeeting marconi 15:01:47 Meeting started Tue Mar 18 15:01:46 2014 UTC and is due to finish in 60 minutes. The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:48 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:51 The meeting name has been set to 'marconi' 15:02:22 #topic role-call 15:02:23 o/ 15:02:23 o/ 15:02:26 o/ 15:02:28 race condition 15:02:30 o/ 15:02:31 s/role/roll 15:02:49 role: poptart distributor 15:02:49 o/ 15:02:53 o/ 15:02:57 Folks, I am new here. 15:03:02 tjanczuk: welcome! 15:03:14 * kgriffs gives tjanczuk his first pop-tart 15:03:43 alcabrera: is amit around? 15:03:49 \o 15:03:54 not at his desk, kgriffs 15:03:57 I saw him earlier 15:03:57 kk 15:04:00 My name is Tomasz Janczuk, since recently I work for HP. Previously I worked for Microsoft (12 years) and did a startup. You can find me at http://github.com/tjanczuk, http://tomasz.janczuk.org, and @tjanczuk. 15:04:06 tjanczuk: welcome! 15:04:18 o/ 15:04:20 Hi Tomasz! 15:04:32 o/ 15:04:34 node, eh? 15:04:36 I am spelunking Marconi, and will have a few questions about plans and directions if you don't mind. 15:04:43 * kgriffs likes node and their community 15:04:46 Yes, node ;) 15:05:00 tjanczuk: ok, we should have some time during open discussion 15:05:11 great, thanks 15:05:18 #link https://wiki.openstack.org/wiki/Meetings/Marconi#Agenda 15:05:24 #topic pecan evaluation 15:05:36 #link https://wiki.openstack.org/wiki/Marconi/pecan-evaluation 15:05:38 mmm, pecans 15:05:42 they are most delicious 15:05:45 so, Balaji stayed up all night to finish this 15:05:51 he is sleeping now 15:05:52 :) 15:06:01 sleeping next to me - with his eyes open! :D 15:06:05 hah. 15:06:19 balajiiyer: d00d, I thought you were in teh bed 15:06:27 * kgriffs wonders if balajiiyer is human 15:06:56 kgriffs: apparently you cant sleep through the morning if you have a toddler at home. 'daddy wake up, brush your teeth' 15:07:02 LOOOOL 15:07:20 so, first off, a GREAT BIG THANK YOU to Balaji! 15:07:38 * sriram claps 15:07:43 * alcabrera cheers 15:07:51 #info Balaji kicks a** 15:08:12 You are very welcome folks, couldnt have done without you all 15:09:36 kgriffs: can you add that link to the bp? 15:09:52 balajiiyer: sure 15:09:55 Yay! It was a good read too :) 15:10:16 That is great. Reading this now. 15:11:30 balajiiyer: can you change the bp to "implemented"? 15:11:52 kgriffs: done 15:12:05 thanks 15:12:27 w00t 15:12:40 Sweetness! 15:13:13 balajiiyer: so, it looks like if performance were equal, the decision matrix would still favor Falcon? 15:14:01 balajiiyer: I would think so. Development experience is better with Falcon while writing ReST APIs 15:14:23 kgriffs: w00t 15:14:31 balajiiyer: ok, you may want to call that out since it sounds like you are basing your recommendation mostly on perf 15:14:44 yeah doing the math, Pecan comes out at 387 if performance were equal. 15:15:44 FWIW, I've heard the same thing anecdotally from lots of people who try Falcon. 15:17:31 ok, so as Pecan as a framework continues to improve, I think we should consider re-evaluating for our 2.0 API 15:17:37 that is my proposal 15:17:44 sounds fair 15:17:46 ah 15:17:50 on that note 15:18:06 question: what can Pecan do to improve? what can Falcon do to improve? 15:18:14 what are some solid recommendations for each framework? 15:18:26 balajiiyer: maybe you could make a couple bullet lists? 15:19:27 otherwise, anyone object to posting this to the ML? 15:19:34 no objections from me 15:19:45 would we put it under [marconi] or... ? 15:20:05 hmmm 15:20:11 it has that flavor 15:20:17 since queues were used for benchmakring 15:20:19 but also 15:20:21 [wsgi] 15:20:24 seems very relevant 15:20:34 On the topic of performance, were there some performance measurements done for Marconi under different scale situations (#queues, #requests etc)? I could not find much browsing on the web. 15:20:43 Is there a [pecan] now that it's in stackforge? 15:21:27 ametts: there is 15:21:42 kgriffs: I would put it under Marconi, since this evaluation is done for 'Marconi', and I evaluated only the features that were required for Marconi 15:21:53 example: http://lists.openstack.org/pipermail/openstack-dev/2014-March/029099.html 15:22:05 iow, the evaluation is specific to marconi 15:23:31 i agree it should be in marconi 15:23:42 so as far tagging, it seems [marconi][pecan] might be the most eye-catching 15:23:45 and relevant 15:23:50 *far -> for 15:23:52 tjanczuk: we have done some, but perhaps not published them as broadly as we should have. I would welcome further work in that area. 15:24:50 #note need to do more performance tests, vary number of queues, requests, etc. and publish them 15:25:11 kgriffs: is there any data you could share? 15:25:14 tjanczuk: it may make sense to make that a Juno bp - feel free to register one 15:26:11 tjanczuk: you can ping balajiiyer and malini in #openstack-marconi after the mtg. I believe they have some tsung tests they can share that includes all the message operations. 15:26:53 at some point it may just make sense to build a complete pecan driver, and a set of benchmark tests for marconi, and have them run periodically. And deployers can then just choose between falcon or pecan themselves. 15:27:06 thanks 15:27:17 balajiiyer: ok, so can you add some bullets for recommendations to the wiki, and then post to the ML? 15:27:45 kgriffs: ok, will do 15:27:49 #action balajiiyer to post pecan eval to the ML 15:27:51 amitgandhi: seems a big effort :D 15:29:15 flwang: it is, but also periodically running benchmark tests is also a big effort. i guess its relative between just building a pecan driver or keep on benchmarking 15:30:27 we need to eventually automate our benchmarking system, much like speed.pypy.org (http://speed.pypy.org/) 15:30:32 +1 15:30:50 that's valuable, regardless of whether we choose to support new storage/transport drivers 15:30:58 +1 15:31:07 I think we may even already have a bp to do that 15:31:13 we'll triage that once Juno opens 15:31:41 cool 15:32:05 #topic ATL summit 15:32:06 #note consider automating benchmarking infra; very valuable 15:32:19 the ATL summit - coming soon! 15:32:22 yes 15:32:25 +1 15:32:34 everyone have their session proposals in? 15:33:18 if not, please do that this week 15:33:19 :) 15:33:28 I submitted one for 'Notifications', it says it is 'Unreviewed'. Who reviews and approves it? 15:33:56 kgriffs will be the guru :D 15:34:17 o kcool 15:35:48 is the hardware hacking still happening? :P 15:35:48 #link http://summit.openstack.org/ 15:35:59 technically, you have until April 20 to submit 15:36:15 I'm just trying to encourage everyone to get them in early 15:36:18 :D 15:36:30 anything else on this topic people want to bring up? 15:36:37 kgriffs: i have posted the signed messages idea 15:36:50 flwang: nice, thanks 15:37:09 cpallares: I got my led strips in, let the hardware hacking happen! :P 15:37:31 mpanetta: woooh! 15:37:57 I was going to bring them to work today, but decided against it... 15:38:20 so, I think there will be a team meet-and-greet on the evening of the 10th for folks who are in town 15:38:30 we should find a time during the week as well to go do dinner together 15:39:03 +1 15:39:08 +2 15:39:13 rock on 15:39:16 #topic Review updates to the API v1.1 spec: remove metadata, pop semantics, lazy queue create (kgriffs) 15:39:37 I think we should wait on this until next week when Flavio can be here 15:39:51 is that cool with everyone? 15:39:52 kgriffs: +1 15:40:06 +1 15:40:48 works for me 15:40:57 +1 15:40:57 +1 15:41:22 ok. Some folks had questions regarding the metadata thing, specifically. I think metadata would be fairly easy to implement with topics; we just have a different table for that and only lazy-add records if/when user sets metadata for a given topic 15:41:33 but anyway, everyone think on that and please review the current spec 15:41:49 #link https://blueprints.launchpad.net/marconi/+spec/api-v1.1 15:42:04 it doesn't have metadata endpoints right now, but I am leaning towards adding them back 15:42:51 #topic review actions from last time 15:42:58 Looks like we just had one: flaper87 to add a bug for sqla GC 15:43:03 iirc, that is done 15:43:13 anything else from last week people want to mention? 15:43:45 kgriffs: I will continue to follow up with megan_w on customer stories for ATL summit 15:43:54 thanks! 15:44:01 kgriffs: sounds good 15:44:09 in other news, I believe we finally squashed the devstack bug causing marconi-server to crash 15:44:16 w00t! 15:44:18 yay 15:44:31 kudos to mpanetta and malini! 15:44:43 thanks to mpanetta for wrapping this daemonic issue up, and malini for carrying it all the way to completion. :) 15:45:00 #topic Review Graduation BPs/Bugs 15:45:09 here is my hit list: 15:45:15 1. merge docs 15:45:24 2. get gate working with mysql backend 15:45:43 * kgriffs wonders if that is it) 15:46:26 3. fix pypy issue that is blocking #1 15:46:43 that pypy issue... :( 15:46:50 kgriffs: I think there are 3 docs patches we need to merge and most of them are ready 15:47:31 flwang: is that sphinx patch one of them? 15:47:39 kgriffs: yes 15:47:58 sphinx patch can fix the doc gate failure 15:48:35 ok, but we still have the pypy thing which seems to be unrelated 15:49:00 I need a volunteer to help track down the pypy thing 15:49:09 kgriffs: yep, it's a blocker 15:49:57 ok, if anyone has time today or tomorrow to assist, please do. Flavio has started looking at it too. 15:50:25 kgriffs: I will keep an eye on that 15:50:26 I'm looking as I can. I found a nova thread on the ML 15:50:31 http://lists.openstack.org/pipermail/openstack-dev/2014-March/029508.html 15:50:38 that relates to this pypy issue 15:50:40 flwang, alcabrera: thanks for your help! 15:50:42 it's known, thankfully 15:50:44 :) 15:51:49 paste.openstack.org/show/73701/ 15:52:01 that might help with your pypy concern 15:52:39 adrian_otto: thanks! 15:52:39 trouble is new setuptools don't install properly through pip 15:52:51 alcabrera: can you try submitting a patch with that? 15:52:51 thanks, adrian_otto. I just saw this in the launchpad bug 15:52:52 causing the sudden breakage 15:52:55 kgriffs: will do 15:53:01 #link https://bugs.launchpad.net/openstack-ci/+bug/1290562 15:53:09 #link http://paste.openstack.org/show/73701/ 15:53:48 ok folks, don't forget out graduation review is this afternoon during the TC meeting. 15:53:56 #topic open discussion 15:54:23 I was curious what the plan is rearding AMQP, STOMP, and MQTT, if any? 15:54:32 kgriffs: any outlook for the graduation? :) 15:56:53 flwang: I am going through the latest requirements now, and will post our status in #openstack-marconi soon, but I think we are looking pretty good. 15:57:14 kgriffs: cool 15:57:35 kgriffs: any chance we can talk for a few minutes at #openstack-marconi right after this meeting? 15:57:50 tjanczuk: we are looking at AMQP for Juno. It will mean allowing a driver to only support a subset of the API, and we may need to add some stuff to v1.1 or v2.0 to help with mapping the semantics. 15:58:27 tjanczuk: sure, the team is very active in our IRC channel, so feel free 15:58:56 tjanczuk: wrt STOMP and MQTT, I don't think those have been discussed yet 15:59:26 ok everyone, thanks!!!! 15:59:29 o/ 15:59:30 * kgriffs hands out pop-tarts 15:59:33 I'll gather minutes. 15:59:39 thanks man 15:59:41 #endmeeting