19:10:44 #startmeeting marconi 19:10:45 Meeting started Thu May 23 19:10:44 2013 UTC. The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:10:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:10:48 The meeting name has been set to 'marconi' 19:10:53 #topic bugs 19:11:07 #link https://bugs.launchpad.net/marconi 19:11:31 so, Flavio and I have started chipping away at some of these 19:11:44 malini: anything in this list you would like to highlight? 19:12:26 I was thinking we could just prioritize the undecided real quick 19:13:13 so, sorting by number ,descending 19:13:39 random 404's - would you say that's high or critical? 19:14:01 high as in - when will it be fixed? 19:14:31 I'd say, how important it is to get this done for a "beta" release 19:14:56 It is important to get this one fixed 19:15:24 seems like this one is a blocker for load testing 19:15:27 The 404s spike up when the number of users is large 19:15:30 yes 19:15:49 I have been able to repro thos only with tsung 19:15:52 ok, but it isn't like a hole in our feature implementation, like some of the others 19:16:04 how about "high" for priority? 19:16:09 works for me 19:16:37 next 19:16:38 https://bugs.launchpad.net/marconi/+bug/1177979 19:16:49 #link https://bugs.launchpad.net/marconi/+bug/1177979 19:17:00 I think medium is OK here 19:17:07 yeap 19:17:13 * kgriffs does that 19:17:33 #link https://bugs.launchpad.net/marconi/+bug/1177976 19:17:41 same here, methinks 19:18:06 ditto for the next 19:18:11 tht got me thinking- so max msg size per request will be 4kb 8 50 ? 19:18:17 #link https://bugs.launchpad.net/marconi/+bug/1177971 19:18:24 ** 4kb * 50 ? 19:18:36 max request body, you mean? 19:18:44 yes.. 19:18:49 guess it'll have to be 19:18:53 that's right, plus a little overhead 19:18:57 ok 19:19:21 for 2000 simultaneous requests, that comes out to be around 400 MB 19:19:35 ok 19:20:38 if we up that limit, to 64K then we definitely need to support streaming deserialization of the JSON (right now everything is buffered since we just use json.read) 19:20:43 (BTW) 19:21:11 #link https://bugs.launchpad.net/marconi/+bug/1177952 19:21:15 medium on that as well 19:21:34 yeap 19:21:38 although some of these things have security consequences. 19:21:59 I'm not saying we don't need to get them done for the gold release, just trying to see where to focus for a beta 19:22:20 OK, so I'll set input validation bugs to medium 19:22:26 none of these are show stoppers 19:22:54 Oh, here's one 19:22:55 https://bugs.launchpad.net/marconi/+bug/1165102 19:23:12 tht one could be a high 19:23:22 we better get that done for beta since it's spec'd in the API 19:23:31 agreed 19:23:52 is there a blueprint for modifying the syntax to using query param instead? 19:23:54 * kgriffs looking 19:24:33 I guess that just falls under v1-api 19:24:47 so, anyone have an objection to changing this: 19:25:13 not me 19:25:49 cool 19:25:55 so it would look something like: 19:26:20 myqueue/messages?ids=[95109,142358,1243098] 19:26:50 is OK? 19:27:08 are we also going to change how the location is returned when we post multiple messages? 19:27:20 yes 19:27:26 cool 19:27:28 it would have to follow suit 19:28:19 #agreed change get list of specific messages URL to put IDs in a query string param, vs. as the resource name in the path 19:28:45 OK, all set with bugs? 19:28:52 #link https://bugs.launchpad.net/marconi 19:28:58 yes 19:29:10 #topic QA cluster 19:29:22 oz_akan: I can haz updatez? 19:29:34 sure 19:30:06 new test environment is almost ready, except marconi configuration which we will do after the meeting with Malini 19:30:21 OK 19:30:23 excellent 19:30:27 one thought 19:30:29 so we have web and mongodb configuration under Salt and I will soon create a git repo for that 19:30:42 OK 19:30:47 where will that repo live? 19:30:50 I am working on documenting it 19:30:58 that is a question, I would ask to you 19:31:13 mordred: ping 19:31:29 mordred: ^^^ 19:32:20 I'm not sure. I think of it as a reference for deploying, but other people might want to do it in chef or puppet 19:33:11 hey vkmc_ 19:33:26 sure, salt is in python so I think it will be adapted by openstack sooner or later 19:33:41 oz_akan - maybe ask in #openstack-infra ? 19:33:44 hey kgriffs! 19:33:45 I think infrastructure people are even open to port all puppet to salt 19:33:52 yes I asked yesterrday 19:33:54 there is a ci-salt repo in stackforge..But hasnt been updated in a while 19:33:55 oic 19:34:38 i mean, you can ask whether this repo should live under stackforge or just under rackspace org or something 19:35:08 wow, I didn't realize salt was taking over the world. :D 19:35:25 hey, if that happens, you can contribute to updating etherpad.openstack.org 19:35:29 (nudge nudge, wink wink) 19:35:54 ok, so that's great you've made so much progress 19:36:02 I can't wait to have a real cluster to hammer. :D 19:36:36 at that point, we should also give out the info to the community so they can try it out, write non-python client libs, etc. 19:37:16 yes 19:37:17 #oz_akan to send out a not to dev list inviting people to pummel our QA/reference deployment 19:37:27 let me try that again 19:37:39 to send out a not to dev list inviting people to pummel our QA/reference deployment 19:37:41 I am working on a document about it 19:37:42 crap 19:37:53 #action oz_akan to send out a not to dev list inviting people to pummel our QA/reference deployment 19:37:59 oz_akan: perfect. 19:38:08 ok 19:38:13 one more thing I thought of earlier today 19:38:31 it would be great to have hardening in there already if not done already 19:39:32 not done yet 19:39:37 could be a subsequent release of the salt states 19:39:39 it is more like having the service up 19:39:42 sure 19:39:47 that is the point 19:39:49 sounds like a plan 19:40:02 can you also add HAVAGE to that 19:40:03 ? 19:40:19 what is HAVAGE? 19:40:33 http://www.issihosts.com/haveged/ 19:41:01 virtualized guests generally have poor entropy 19:41:05 so they need a little help 19:41:27 ok you need this package to be installed? 19:41:29 * kgriffs trying to get used to using the meetbot commands 19:41:31 #link http://www.issihosts.com/haveged/ 19:41:47 correct 19:42:10 I think it can contribute entropy to /dev/urandom - not sure if that happens by default 19:44:07 kgriffs: pong 19:44:36 mordred: hey, oz_akan was wondering where his salt scripts for Marconi should live. I'll let him explain. :) 19:44:50 ah - gotcha 19:45:06 I think at the moment they would make sense to put into a stackforge project 19:45:32 "marconi-salt" would be a good repo name 19:46:03 or we could have it as a folder under marconi 19:46:25 but that might slow down things 19:48:09 if it goes in stackforge does it get wired up to gerrit & friends? 19:50:28 oz_akan: can you follow up with mordred? 19:50:36 (we need to move on) 19:50:54 #action oz_akan to find a home for marconi-salt 19:50:59 kgriffs: ok 19:51:20 one more thing on the topic of security. Do you have some hardening guides handy? 19:51:46 I've referenced NSA before, but didn't see RHEL 6 yet. 19:51:48 #link http://www.issihosts.com/haveged/ 19:52:01 guess, pasted wrong link 19:52:02 sorry 19:52:04 wrong link 19:52:10 #link http://serverfault.com/questions/368055/anything-close-to-an-nsa-guide-for-securing-rhel-6 19:53:23 anyway, something to keep on your radar 19:53:29 moving right along... 19:53:33 kgriffs: this is kind of at the very end of my todo list, next I want to create Malini's benchmarking environment 19:53:38 ok got that 19:53:51 makes sense 19:55:01 looking at the agenda, we'll skip down to polling modes, since the others I'd like to get flaper87's thoughts on and he couldn't make it 19:55:11 #topic • BP: https://blueprints.launchpad.net/python-marconiclient/+spec/polling-modes in the client 19:55:24 #link https://blueprints.launchpad.net/python-marconiclient/+spec/polling-modes 19:55:33 vkmc_: thoughts? 19:56:26 I guess this is assuming there is a blocking/greenlet-aware polling loop 19:57:56 * kgriffs watches a tumbleweed roll by 19:59:28 kgriffs, not much I can suggest now, I'm from my phone just to keep up with the meeting :) 19:59:36 no worries 19:59:56 just mostly wanted to raise awareness of that, since it is something we want to promote 20:00:06 OK, we are out of time folks 20:00:09 parting thoughts? 20:00:29 bye bye :) 20:00:39 ok, thanks everyone 20:00:52 next week, same bat-time, same bat-channel. 20:00:59 #endmeeting