21:01:22 #startmeeting zaqar 21:01:23 Meeting started Mon Jan 11 21:01:22 2016 UTC and is due to finish in 60 minutes. The chair is flwang1. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:01:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:01:27 The meeting name has been set to 'zaqar' 21:01:36 ok, let's meet at here ;) 21:01:57 #topic roll call 21:01:59 o/ 21:02:12 \o zaqarians 21:02:18 ryansb: hey 21:02:29 ryansb: will you join the austin summit ? 21:02:34 I believe so 21:02:42 ryansb: cool 21:02:46 unless something major changes, of course 21:02:53 hopefully we can have a face to face talk :) 21:03:13 o/ 21:03:14 I'm not sure, but I have a hope 21:03:28 ok, i think just us 21:03:47 i only have 30 mins, sorry guys 21:04:01 so if you don't mind, it could be a short meeting 21:04:04 no worries - I can wrap it up after you head off 21:04:11 (assuming we have topics) 21:04:12 ryansb: awesome, thank you 21:04:18 #topic docs 21:04:34 firstly, let's give Eva-i a big congrats! 21:04:46 our config-ref patch has been merged 21:05:09 it looks like this http://docs-draft.openstack.org/05/263405/7/gate/gate-openstack-manuals-tox-doc-publish-checkbuild/24be02f//publish-docs/draft/config-reference/messaging.html 21:05:34 yes, this patch was merged https://review.openstack.org/#/c/263405/ 21:05:39 Eva-i: thank you for your effort on this work, it's really awesome 21:05:49 though Fei Long found a bug which I will fix 21:05:59 hurrah 21:06:07 yay, yay 21:06:32 and i know the developer doc patch from Eva-i has been merged as well :D 21:06:36 it's super cool 21:06:54 so the only thing about our doc is the api-ref 21:07:06 if we can make it in Mitaka, it will be fabulous 21:07:23 flwang1: I'm sorry, I haven't investigated today about current api-ref situation 21:07:30 i can't think out another word to describe that 21:07:51 Eva-i: don't say sorry, it's not really rush 21:07:57 flwang1: but my today will still last for few hours, so let's see 21:08:01 we have already made a great progress 21:08:20 we can't make it w/o your help 21:08:24 Eva-i: ^ 21:08:49 Eva-i: do you have any other things we should talk about docs? 21:08:53 flwang1: I'm not sure my help will be enough still 21:09:13 flwang1: no, now nothing about docs 21:10:08 cool 21:10:17 #topic zaqarclient 21:10:53 now all the subscriptions patch have got the lovely +2 from a gentleman, now we need another +2 from a nice lady :) 21:11:08 MD just added the claim support for v1 21:11:29 and i'm going to leverage that to get the claim support for v2 21:12:01 anything i missed? 21:12:22 ryansb: i saw your patch for pre-signed url 21:12:37 yep - adding curl formatting for that ATM 21:12:37 i will review it today, it's on my list, just FYI 21:12:44 so wait until I rev it 21:13:01 i'm really sure we can complete the client work in Mitaka 21:13:14 yeah, that'll be easy 21:13:37 yep, i'm really excited about that 21:14:10 i can even imagine the poor client support blocked how many potential users of zaqar 21:14:30 anything else? 21:14:43 #topic zaqar-ui 21:15:15 i didn't make much progress last week for the zaqar UI 21:15:30 me done nothing for zaqar-ui 21:15:54 so i'm thinking about if i can't work the anjular js work this week, i may go for the normal django way 21:16:04 any concern? guys? 21:16:12 flwang1: what are advantages of angularjs? 21:16:23 and we can upgrade when it's really ready for most of the other panels 21:16:28 projects i mean 21:16:40 not particularly - I think the value is having queues and such exposed, so angular doesn't add much 21:17:00 Eva-i: that's the preferred way for the future 21:17:07 from the front-end PoV 21:17:16 ryansb: yep, you got the key point 21:17:23 ryansb: i'm thinking the same thing 21:17:50 flwang1: okay 21:17:56 for now, what we really need is promote the service by UI, anjular js or django doesn't matter 21:18:16 ryansb: thanks for the feedback 21:18:33 ryansb: i will switch to django then 21:18:41 vkmc: ^ 21:18:48 vkmc: let me know if you have any concern 21:19:17 ok, anything else? 21:19:20 yes 21:19:36 flwang1: I know you don't want too many features in this cycle, but me and ryansb want to introduce a new feature. Though I think it's mostly a bug fix. Would you like to know what this feature is? 21:19:53 Eva-i: sure, i'm keen to know 21:21:43 flwang1: current notifications from Zaqar doesn't contain useful info: queue name and message id. The feature is to make notifications send also this info. 21:22:07 flwang1: for now notifications look like this: {'body': 'message1', 'ttl': 60} 21:22:38 let me quote ryansb 21:22:40 ryansb: 1) SNS includes ID and topic in notification http://docs.aws.amazon.com/sns/latest/dg/json-formats.html#http-notification-json 21:22:47 2) subscribers are likely to want queue information if they subscribe to multiple queues 21:22:55 3) subscribers that want to ack/delete/claim messages they are notified of will need the message ID 21:23:56 Eva-i: oh, yep, i'm aware of that. 21:24:38 flwang1: should I make a spec. The patch will not be big. Very small. 21:24:44 Eva-i: it think it's a good feature/fix 21:24:50 flwang1: while apiv2 is unstable, we can safely do it 21:25:17 api v2 is stable enough :) 21:25:39 philosophy nit: it's a strictly additive change, so even if we'd committed to "stable" in the v2 API, it would be safe to do 21:25:44 Eva-i: will the fix/feature change the api? 21:26:03 ryansb: ^ 21:26:04 flwang1: it will only add the message ID and queue name to the notification 21:26:35 ryansb: if so, it's up to you guys if you want to propose a spec 21:26:36 so the message would become {'body': 'message1', 'ttl': 60, 'queue_name': 'foobar', 'id': } 21:27:18 ryansb: given it won't change the api, and the change seems very small 21:27:30 flwang1: depends if to think about notification format as part of api. If so, the api change will be backwards compatible. ryansb proven it. 21:27:31 if no spec, pls file a RFE bug 21:27:42 flwang1: okay, i'll do it! 21:27:55 will fill a bug 21:28:31 Eva-i: given it just adds new elements for the resp, so i don't think it will break the back compatibility 21:28:39 ryansb: thoughts? 21:29:52 ok, sorry guys, i'm going to run for another meeting 21:30:03 ryansb: can you help host the rest of the meeting? 21:30:24 flwang1: okay, good bye 21:30:33 ttyl, guys 21:31:15 vkmc: are you still here? 21:31:21 I am 21:31:47 ryansb: vkmc: anything you want to discuss? 21:31:56 I can show my new bug report 21:32:22 not much... the only thing I want to highlight is that Mitaka 2 is here and we need to cut it soon :) 21:32:36 so probably all the cool features that you were chatting before are for m3 21:33:01 okay, I'll to upload binary websocket patch today 21:33:23 *I'll try 21:33:59 so we must either stop this meeting or change the topic 21:35:53 Nothing else from me 21:36:03 #topic open discussion, I suppose 21:37:51 okay, that's the bug I was talking about https://bugs.launchpad.net/python-zaqarclient/+bug/1532776 21:37:53 Launchpad bug 1532776 in Python client library for Zaqar "Invisible conflict during creation of some resources " [Undecided,New] 21:38:30 feel free to confirm it or mark as invalid or something else 21:39:35 kk 21:39:46 Anyone else? 21:40:01 Nothing... 21:40:38 oh, I read it as "anything else" 21:42:36 ok, well #endmeeting 21:42:37 err 21:42:41 #endmeeting 21:42:44 thanks all! 21:43:49 ryansb: and the meeting continues... 21:44:06 vkmc: maybe you'll be able to stop this meeting? 21:44:56 no, Fei Long can 21:45:03 #endmeeting 21:45:16 yep 21:45:41 flwang1: we need your help to stop this meeting 21:48:27 it's okay, we'll be able to use #endmeeting after 12 minutes 22:13:53 #endmeeting