Thursday, 2013-02-14

*** djohnstone has quit IRC00:01
*** amyt has quit IRC00:05
*** grapex has quit IRC00:30
*** amyt has joined #openstack-meeting-alt01:00
*** cloudchimp has quit IRC01:08
*** amyt has quit IRC01:15
*** rnirmal has quit IRC01:18
*** sacharya has joined #openstack-meeting-alt01:22
*** kaganos has quit IRC01:33
*** cloudchimp has joined #openstack-meeting-alt01:45
*** bdpayne has quit IRC01:47
*** amyt has joined #openstack-meeting-alt02:43
*** amyt has quit IRC02:45
*** amyt has joined #openstack-meeting-alt02:45
*** cloudchimp has quit IRC02:55
*** esp has joined #openstack-meeting-alt03:43
*** esp has left #openstack-meeting-alt04:09
*** grapex has joined #openstack-meeting-alt04:39
*** esp has joined #openstack-meeting-alt04:50
*** esp has left #openstack-meeting-alt04:53
*** grapex has quit IRC05:11
*** sacharya has quit IRC05:51
*** esp has joined #openstack-meeting-alt07:31
*** esp has quit IRC07:38
*** esp has joined #openstack-meeting-alt08:04
*** esp has quit IRC08:11
*** esp has joined #openstack-meeting-alt08:38
*** esp has quit IRC08:48
*** esp has joined #openstack-meeting-alt09:13
*** esp has quit IRC09:24
*** esp has joined #openstack-meeting-alt09:50
*** esp has quit IRC10:00
*** sacharya has joined #openstack-meeting-alt14:27
*** sacharya has quit IRC14:50
*** amyt has quit IRC14:53
*** jcru has joined #openstack-meeting-alt14:57
*** amyt has joined #openstack-meeting-alt15:01
*** cloudchimp has joined #openstack-meeting-alt15:03
*** amyt has quit IRC15:05
*** amyt has joined #openstack-meeting-alt15:28
*** rnirmal has joined #openstack-meeting-alt15:36
*** jcru is now known as jcru|away15:45
*** cp16net is now known as cp16net|away15:48
*** imsplitbit has joined #openstack-meeting-alt15:50
*** jcru|away is now known as jcru15:59
*** sacharya has joined #openstack-meeting-alt16:00
*** bdpayne has joined #openstack-meeting-alt16:25
*** cp16net|away is now known as cp16net16:33
*** bdpayne has quit IRC16:39
*** grapex has joined #openstack-meeting-alt16:43
*** jcru is now known as jcru|away17:04
*** bdpayne has joined #openstack-meeting-alt17:09
*** jcru|away is now known as jcru17:10
*** cp16net is now known as cp16net|away17:40
*** esp has joined #openstack-meeting-alt17:55
*** esp has left #openstack-meeting-alt17:59
*** jcru has quit IRC18:03
*** esp has joined #openstack-meeting-alt18:04
*** cp16net|away is now known as cp16net18:10
*** imsplitbit has quit IRC18:29
*** kgriffs has joined #openstack-meeting-alt18:37
*** cppcabrera has joined #openstack-meeting-alt18:43
*** edsrzf has joined #openstack-meeting-alt18:47
*** esp has quit IRC18:58
*** esp has joined #openstack-meeting-alt19:00
*** carimura has joined #openstack-meeting-alt19:01
*** cp16net is now known as cp16net|away19:04
kgriffs#startmeeting marconi19:05
openstackMeeting started Thu Feb 14 19:05:02 2013 UTC.  The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot.19:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:05
*** openstack changes topic to " (Meeting topic: marconi)"19:05
openstackThe meeting name has been set to 'marconi'19:05
kgriffsHey folks19:05
kgriffslet's get this party started19:05
kgriffs#topic Review actions from last time19:05
*** openstack changes topic to "Review actions from last time (Meeting topic: marconi)"19:05
kgriffsSo, did anyone learn about PATCH support in major web servers?19:05
kgriffsI'm not seeing wkharold in the room19:06
*** ametts-atl has joined #openstack-meeting-alt19:06
*** flaper87 has joined #openstack-meeting-alt19:06
*** treeder has joined #openstack-meeting-alt19:06
cppcabrerawkharold left this link last time: http://weblog.rubyonrails.org/2012/2/25/edge-rails-patch-is-the-new-primary-http-method-for-updates/19:06
cppcabrera"Yes, it should. I have personally tried Apache, nginx, Phusion Passenger, Unicorn, Thin, and WEBrick. They all understood PATCH requests out of the box." - from the link, Feb. 25, 201219:07
kgriffsrock on19:07
kgriffssounds like we are good on that front, then19:07
flaper87₥e got here a bit late19:08
*** cp16net|away is now known as cp16net19:08
flaper87and forgot to use the / in the last message19:08
kgriffs#note PATCH is well-supported in servers, client libs TBD19:08
flaper87^^19:08
cppcabreraYou haven't missed much. We just started. :)19:08
flaper87cool19:08
kgriffsI'd be surprised if we had issues with any of the common HTTP client libs.19:09
flaper87kgriffs: requests supports all that19:09
kgriffssweet. I <3 Requests19:09
* flaper87 loves it too19:09
kgriffshttpie is pretty awesome too19:10
kgriffsanyway...19:10
flaper87so, what were we discussing?19:11
kgriffs#topic API - Post Messages19:12
*** openstack changes topic to "API - Post Messages (Meeting topic: marconi)"19:12
kgriffshttps://etherpad.openstack.org/queuing-api19:12
kgriffsso, last time we left off talking about what the body of a message should be19:12
kgriffsAs long as it is valid JSON and within some max size (say, 64K), I think we should allow it.19:13
kgriffsAny objections?19:14
* kgriffs watches a tumbleweed roll by19:15
cppcabreraSounds good to me. The max size sounds like a good parameter to leave to configuration time.19:15
flaper87no19:15
flaper87no objections, I mean19:15
treeder+119:15
kgriffs#agreed Allow arbitrary bodies, as long as it is valid JSON and under a certain size.19:16
treedercppcabrera: i think the restrictions have to be set19:16
treederas part of the api19:16
kgriffsOK. Max size?19:16
treeder+1 on 64k19:16
ametts-atlNow that we've confirmed PATCH is widely supported, is there anything we need to re-review from last week?19:17
flaper8764kb sounds reasonable19:17
cppcabrera+1 on 64KB, as well.19:17
kgriffsso, that's about 16K messages per GB19:18
kgriffsIf clients max out the size19:19
kgriffsseems like most messages would be a lot smaller19:19
*** SlickNik has left #openstack-meeting-alt19:19
kgriffs#agreed Specify max message size as part of the API, make it 64 KiB19:20
kgriffsOK, so one more thing on this before we move on...19:20
kgriffsWhen a client posts a message, the server decorates it with some metadata, such as an ID.19:22
*** imsplitbit has joined #openstack-meeting-alt19:22
kgriffsso, nesting the "body" element in the post document mirrors the nested structure of the message when it is retrieved19:23
kgriffsWe could get rid of the nesting for POSTs, but I'm not sure how much it matters either way.19:23
kgriffsActually, maybe we should, because the way the spec is written now would imply that a client could include, e.g., "id" if they wanted, but the server should generate that IMHO.19:25
cppcabreraI think eliminating the nesting would be cool to avoid having to do something like: msg['body']['content'] vs. msg['content'] from a json parsing POV.19:25
kgriffsAny objections to hoisting "body" up one level.19:25
kgriffs(in the POST)19:25
cppcabreraNo.19:25
kgriffslet me edit the etherpad19:25
treederlooking...19:25
flaper87mmh19:26
*** vipul is now known as vipul|away19:27
treederAre you saying just post the content directly with no wrapper?19:27
kgriffsalmost. The only wrapper is an array.19:27
treederoh, i see19:28
treedermy only concern is it doesn't leave much room for improvement19:28
*** cp16net is now known as cp16net|away19:28
treedercan't add new features or anything to the messages19:29
kgriffsOr we could say, it has to be an array of objects19:29
kgriffsgood point19:29
treederand i'm a big fan of future proofing api's19:29
kgriffs+119:29
flaper87I think it, as it's in the wiki, is good19:30
*** vipul|away is now known as vipul19:30
*** rnirmal has quit IRC19:30
kgriffs#agreed We say it is an array of these objects and we can even have a JSON schema that we validate against, and technically this is a different media type that what you get back from a GET.19:31
*** cp16net|away is now known as cp16net19:31
flaper87one thin, tho19:31
flaper87thing19:31
kgriffsshoot19:31
flaper87in that example, what does event and backupId mean?19:31
flaper87just random parameters used for the example?19:32
kgriffscorrect19:32
*** cp16net is now known as cp16net|away19:32
kgriffscould be anything that's valid JSON19:32
flaper87we should maybe create some context around those examples19:32
flaper87ok19:32
flaper87what I wanted to be sure is that those paremeteres werent part of a, lets say, header for that body19:33
kgriffsyeah, this spec isn't great documentation; I imagine we'll have something a lot friendlier for devs to reference.19:33
flaper87like content-length or whatsoever19:33
kgriffsoic19:33
flaper87because, imho, that wouldn't be consistent with having a "body" key in the root dict19:33
kgriffsyep19:34
kgriffsOK, so anything else for posting messages?19:35
*** kaganos has joined #openstack-meeting-alt19:35
flaper87nopoe19:37
kgriffs#topic API - Get Messages19:37
flaper87arg19:37
*** openstack changes topic to "API - Get Messages (Meeting topic: marconi)"19:37
kgriffsquestion, comments, rude remarks? ;)19:38
kgriffsOne thing that probably isn't clear is why marker is decoupled from message IDs.19:39
kgriffsThe reason is that it provides more options for storage implementations19:39
kgriffsWe can chat about it more in a future meeting, when we start talking storage drivers.19:40
cppcabrera+1 for the decoupling effort.19:41
kgriffsOf course, marker may be a message ID, but client's shouldn't know any better.19:41
treederwhy the userAgent in response?19:41
kgriffsis it helpful to know what client sent the message?19:42
treederhmm, not sure19:42
treederalso, href is sort of redundant in the message19:43
flaper87mmh, don't think that's useful19:43
kgriffsActually, if we add message signing eventually, it would be necessary to know who signed it to look up the public key19:43
cppcabreraHmmm.. what if the user-agent was just embedded in a message? Leave it up the application to generate it and include it?19:44
kgriffsHow about taking out userAgent for now and adding it back later if needed?19:44
cppcabreraSounds good to me.19:44
treeder+119:45
flaper87+119:45
flaper87makes more sense19:45
kgriffs#agreed Drop userAgent in message header, revisit later if needed19:45
ametts-atlIs there a potential race condition between getting messages and claiming them?  Would you typically get first, then claim, or vice-versa?  Do we need an option to do both in one operation?19:45
flaper87lets try not to overthink from the beggining19:45
kgriffsYou would claim first19:45
flaper87we're doing a good job so far19:45
kgriffsclaim actually returns a list of affected messages19:46
*** kaganos has quit IRC19:46
kgriffsdoing a regular GET would be more for pub-sub or an auditor19:46
treederGet Messages and Claim should be pretty much the same functionality, but claim "claims" them right?19:47
ametts-atlDoes claim include the message content, or just the ids?19:47
kgriffsSame as GET, you get the whole enchilada19:48
ametts-atlgotcha - ok19:48
flaper87lol @ enchilada19:48
* kgriffs missed lunch today19:48
treederhehe19:48
flaper87that explains everything19:48
flaper87:P19:48
treederI think that should be part of the spec19:48
kgriffsso, let's finish up with GET19:49
flaper87treeder: enchilada ?19:49
flaper87:P19:49
treederya19:49
treeder;)19:49
treederre: href: seems redundant?19:49
cppcabreraenchilada - cloud queuing for those that missed the free lunch.19:49
treederhaha19:50
flaper87hehe19:50
kgriffsSo, I'm OK with dropping the per-message href, assuming the URI template for getting a single message is defined somewhere, maybe in a home document.19:51
*** cp16net|away is now known as cp16net19:51
treederyou have Get a Specific Message endpoint19:52
kgriffsyes19:52
treederuser already has queue name and message id, so easy to make that href19:52
kgriffsyep19:52
kgriffsAny RESTafarians in the room who object?19:52
kgriffs#agreed Drop per-message href field19:53
kgriffsAnything else for "Get Messages"?19:54
flaper87nope19:54
treedernope19:54
kgriffsmoving on...19:54
kgriffsthis will be our last topic for today.19:55
kgriffs#topic API - Claim Messages19:55
*** openstack changes topic to "API - Claim Messages (Meeting topic: marconi)"19:55
flaper87so, basically the claim is a patch with a clain action in it19:58
flaper87op*19:58
kgriffsright, the client patches x messages with a "claim" and the server filters any messages that already have a claim.19:59
flaper87seems to make sense20:01
kgriffsAs long as all workers use this method rather than GET, it works.20:01
kgriffsOf course, an auditor or debugger or whatever could use GET to watch things go by20:01
*** vipul is now known as vipul|away20:02
kgriffswell, looks like we are out of time. You guys want to sleep on this one and pick up the discussion next week?20:02
kgriffsmaybe go have some enchiladas…20:03
cppcabreraAny new action items? We've still got the three pending on Trello.20:03
flaper87kgriffs: yeap, I'd like to think a bit more on it20:03
flaper87and also, should complete my zmq part (I was out of office)20:03
treederya, sounds good20:03
treederi'm getting hungry. ;)20:03
kgriffsoic20:03
*** rnirmal has joined #openstack-meeting-alt20:04
flaper87treeder: if kgriffs missed his lunch you should do the same20:04
* flaper87 runs away20:04
flaper87hehe20:04
kgriffsflaper87: I'd appreciate your thoughts on how to abstract out the protocol in the implementation (make it pluggable). Maybe could be it's own blueprint.20:04
kgriffswhat was the trello link again?20:05
treederhttps://trello.com/board/openstack-marconi/511403287d138cd6200078e020:05
flaper87kgriffs: sure, I've that queued, sorry I didn't make it for this meeting20:05
*** vipul|away is now known as vipul20:07
kgriffsno worries, man. Really appreciate your help. Also, it would be cool if you could help me start brainstorming about storage drivers.20:07
kgriffs(specifically, what backend is a good first target)20:07
flaper87kgriffs: yep, we could make that in a new wiki page20:07
flaper87kgriffs: my first thought is mongodb20:07
flaper87but we can dig that a bit more20:08
kgriffsSure thing.20:08
kgriffsI'll schedule it for a future meeting.20:08
flaper87+120:08
kgriffsOK guys, let's wrap it up.20:09
kgriffsnext week, same time, same bat-channel. If we can get enough done, we can go back to twice a month chats.20:10
*** dhellmann has joined #openstack-meeting-alt20:10
kgriffs#endmeeting20:10
*** openstack changes topic to "OpenStack meetings (alternate) || Development in #openstack-dev || Help in #openstack"20:10
openstackMeeting ended Thu Feb 14 20:10:30 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-14-19.05.html20:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-14-19.05.txt20:10
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-02-14-19.05.log.html20:10
flaper87kgriffs: cool20:11
flaper87thanks guys20:11
flaper87++ for everyone20:11
cppcabreraTake care, everyone. :)20:11
kgriffstchuss20:11
*** cppcabrera has left #openstack-meeting-alt20:11
*** ametts-atl has left #openstack-meeting-alt20:11
*** treeder has quit IRC20:13
*** kgriffs has left #openstack-meeting-alt20:16
*** flaper87 has left #openstack-meeting-alt20:16
*** bdpayne has quit IRC20:17
*** bdpayne has joined #openstack-meeting-alt20:18
*** vipul is now known as vipul|away20:32
*** carimura has quit IRC20:33
*** esp has left #openstack-meeting-alt20:34
*** vipul|away is now known as vipul20:38
*** kaganos has joined #openstack-meeting-alt21:12
*** cp16net is now known as cp16net|away21:14
*** cp16net|away is now known as cp16net21:31
*** vipul is now known as vipul|away21:38
*** vipul|away is now known as vipul21:39
*** tsygrl has quit IRC21:52
*** rnirmal has quit IRC21:57
*** vipul is now known as vipul|away22:11
*** dhellmann has quit IRC22:12
*** vipul|away is now known as vipul22:18
*** cloudchimp has quit IRC22:29
*** rnirmal has joined #openstack-meeting-alt22:30
*** imsplitbit has quit IRC22:31
*** edsrzf has quit IRC23:05
*** grapex has quit IRC23:06
*** edsrzf has joined #openstack-meeting-alt23:15
*** cloudchimp has joined #openstack-meeting-alt23:24
*** sacharya has quit IRC23:29

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!