Monday, 2015-11-23

*** tej has joined #openstack-zaqar00:03
*** tej has quit IRC00:35
openstackgerritFei Long Wang proposed openstack/python-zaqarclient: Add support for flavor-list  https://review.openstack.org/24850201:02
*** mdnadeem1 has joined #openstack-zaqar01:03
*** Qiming has joined #openstack-zaqar01:05
*** mdnadeem1 has quit IRC01:07
*** mdnadeem1 has joined #openstack-zaqar01:12
*** mdnadeem1 has quit IRC01:46
*** 64MAEDR3D has joined #openstack-zaqar01:53
openstackgerritFei Long Wang proposed openstack/python-zaqarclient: Add support for flavor-create  https://review.openstack.org/24850802:08
openstackgerritFei Long Wang proposed openstack/zaqar: Fix queue create failure when metadata is {}  https://review.openstack.org/24786702:22
*** 64MAEDR3D has quit IRC02:36
*** mdnadeem2 has joined #openstack-zaqar02:39
openstackgerritFei Long Wang proposed openstack/python-zaqarclient: Add support for flavor_show  https://review.openstack.org/24850902:39
*** mdnadeem2 has quit IRC02:40
*** mdnadeem2 has joined #openstack-zaqar02:58
*** mdnadeem2 has quit IRC03:01
*** mdnadeem2 has joined #openstack-zaqar03:18
*** mdnadeem2 has quit IRC03:20
*** mdnadeem1 has joined #openstack-zaqar03:39
*** mdnadeem1 has quit IRC03:39
*** achanda has joined #openstack-zaqar03:58
*** AAzza has quit IRC04:07
*** AAzza_ has joined #openstack-zaqar04:07
*** AAzza_ is now known as AAzza04:07
*** achanda has quit IRC04:10
*** mdnadeem_ has joined #openstack-zaqar04:21
*** achanda has joined #openstack-zaqar05:01
*** achanda has quit IRC05:04
*** rcernin has joined #openstack-zaqar05:36
*** rcernin has quit IRC05:42
*** wanghao has joined #openstack-zaqar06:39
*** rcernin has joined #openstack-zaqar07:07
*** openstack has joined #openstack-zaqar07:20
*** mdnadeem_ has quit IRC07:21
*** sriram has joined #openstack-zaqar08:27
*** sriram has quit IRC08:27
*** sriram has joined #openstack-zaqar08:27
*** Qiming has quit IRC09:31
*** sriram has quit IRC10:01
*** khushbu_ has joined #openstack-zaqar10:11
*** khushbu_ has quit IRC10:11
*** khushbu_ has joined #openstack-zaqar10:16
*** khushbu_ has quit IRC10:16
*** khushbu has joined #openstack-zaqar10:20
*** khushbu has quit IRC10:23
*** khushbu_ has joined #openstack-zaqar10:26
*** khushbu_ has quit IRC10:29
*** Qiming has joined #openstack-zaqar10:29
*** khushbu_ has joined #openstack-zaqar10:40
*** flaper87 has quit IRC10:46
*** flaper87 has joined #openstack-zaqar10:46
*** khushbu_ has quit IRC10:46
*** diga has joined #openstack-zaqar11:43
*** diga has quit IRC11:54
*** dmowrer has joined #openstack-zaqar12:08
*** dmowrer has quit IRC13:01
*** dmowrer has joined #openstack-zaqar13:10
*** tej has joined #openstack-zaqar13:32
vkmcEva-i, good catch!13:38
*** tej has quit IRC13:39
*** khushbu_ has joined #openstack-zaqar13:47
*** khushbu_ has quit IRC14:02
*** diga has joined #openstack-zaqar14:17
*** dmowrer has quit IRC14:17
*** dmowrer has joined #openstack-zaqar14:22
*** jasondotstar_afk is now known as jasondotstar14:33
*** sriram has joined #openstack-zaqar14:50
*** achanda has joined #openstack-zaqar14:53
Eva-ivkmc: do we have a meeting in 5 minutes?14:55
*** openstackgerrit has quit IRC15:02
*** openstackgerrit has joined #openstack-zaqar15:02
vkmcEva-i, no, it's rotating, it's at 21utc today15:07
Eva-ivkmc: okay15:07
*** dmowrer has quit IRC15:10
*** dmowrer has joined #openstack-zaqar15:13
*** mdnadeem1 has joined #openstack-zaqar15:21
*** mdnadeem1 has quit IRC15:26
*** mpanetta has joined #openstack-zaqar15:29
*** ametts has joined #openstack-zaqar15:38
*** ametts has quit IRC15:44
*** Qiming has quit IRC15:52
*** ametts has joined #openstack-zaqar15:56
*** achanda_ has joined #openstack-zaqar16:07
*** achanda has quit IRC16:08
*** rcernin has quit IRC16:08
*** amitgandhinz has joined #openstack-zaqar16:10
*** Pablo|off| has joined #openstack-zaqar16:14
*** Pablo|off| is now known as pcaruana16:15
*** diga has quit IRC16:16
*** amitgandhinz has quit IRC16:36
*** tej has joined #openstack-zaqar17:10
*** tej has quit IRC17:16
*** rcernin has joined #openstack-zaqar17:21
*** tej has joined #openstack-zaqar17:36
*** davideagnello has joined #openstack-zaqar17:39
*** achanda_ has quit IRC17:49
*** achanda has joined #openstack-zaqar18:00
*** tej has quit IRC18:00
*** achanda_ has joined #openstack-zaqar18:04
*** achanda has quit IRC18:07
*** kgriffs is now known as kgriffs|afk18:31
*** boris-42 has quit IRC18:48
*** tej has joined #openstack-zaqar19:00
*** ametts has quit IRC19:03
*** flwang has quit IRC19:13
*** flwang has joined #openstack-zaqar19:27
*** flwang1 has joined #openstack-zaqar19:45
*** vkmc is now known as vkmc-afk19:47
flwanghi guys19:49
*** tej has quit IRC20:00
*** achanda_ has quit IRC20:04
*** tej has joined #openstack-zaqar20:39
flwanganybody around?20:44
flwangwe have the weekly meeting after 15 mins, just a reminder20:44
*** ametts has joined #openstack-zaqar20:55
flwanganybody around?21:00
flwangwe're in #openstack-meeting-321:00
*** jasondotstar has quit IRC21:12
*** vipuls has quit IRC21:12
*** jasondotstar has joined #openstack-zaqar21:18
*** vipul has joined #openstack-zaqar21:19
*** sriram has quit IRC21:24
*** bradjones has quit IRC21:27
*** vkmc-afk is now known as vkmc21:27
*** ametts has quit IRC21:28
vkmcEva-i, flaper87, jasondotstar, ryansb, therve, mdnadeem21:28
vkmcmeeting!21:28
*** bradjones has joined #openstack-zaqar21:29
*** bradjones has joined #openstack-zaqar21:29
*** david-lyle has quit IRC21:31
*** tej has quit IRC21:32
*** mpanetta has quit IRC21:33
*** david-lyle has joined #openstack-zaqar21:34
*** njohnston is now known as nate_gone21:46
*** david-lyle has quit IRC21:55
flwangvkmc: do you think it's reasonable?22:01
flwangi mean the reserved attributes of queue22:01
vkmcflwang, I'm not sure wrt to the overlapping it will have with the attributes the messages have22:02
vkmcI mean22:02
*** david-lyle has joined #openstack-zaqar22:03
vkmcyou have the following attributes22:03
flwangvkmc: we don't support attributes of msg for now, IIRC22:04
vkmcdelayseconds, maximummessagesize (this one makes sense to me), messageretentionperiod (aka ttl, our messages have it), policy22:04
flwangyou mean TTL?22:04
vkmcyes22:04
flwangok22:04
*** david-lyle has quit IRC22:04
flwangyep, messages attributes will override the queue's attrs22:04
vkmcflwang, it makes sense though, if we want to set a default according to the queue22:05
vkmcif you don't specify a ttl, then it takes the ttl the queue has22:05
flwangvkmc: for example, when posting msg, if there is TTL, then user it, otherwise, use the queue's TTL22:05
vkmcand if the queue doesn't have a ttl defined, then a default is used22:05
flwangexactly22:06
vkmc+122:06
vkmcI like the idea22:06
flwangvkmc: with that way, we can reduce a little big traffic maybe :)22:06
vkmcflwang, yeah!22:07
flwangbut that's not the key part, the key part is we can have a really flexible queue22:07
flwangby adding some reserved attrs22:08
vkmcindeed22:08
vkmcand have a real use for metadata22:08
flwangvkmc: yes, for sure22:09
vkmcI think is a great idea22:10
vkmcshould we work on a spec for that? check with params make sense22:10
flwangvkmc: that's the idea in my mind recently, if you like it then i think it deserves a blueprinbt+spec22:11
flwangi'm seeing some comments from flaper87 :D22:11
*** dmowrer has quit IRC22:12
flwangvkmc: this is the architecture of ali yun, which is the biggest public cloud of China, see https://translate.google.co.nz/translate?sl=auto&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2Fblog.aliyun.com%2F1346&edit-text=&act=url22:13
vkmcflwang, let's see22:15
flwangvkmc: i have reviewed their api, very similar like the SQS, and the architecture is similar like Zaqar22:16
*** dmowrer has joined #openstack-zaqar22:16
flwangits MQS master, is like our control plane22:17
flwangso select the right 'pool'22:18
*** dmowrer has quit IRC22:20
*** rcernin has quit IRC22:20
*** dmowrer has joined #openstack-zaqar22:20
*** david-lyle has joined #openstack-zaqar22:21
flwangand we also need to implement 'dead letter queue', 'delay queue' and 'long poll'22:22
flwangand ali cloud's priority queue is also very interesting22:22
vkmcyeah :o22:24
vkmcmany things tod o22:24
*** david-lyle has quit IRC22:25
*** dmowrer has quit IRC22:25
vkmc(I'm slightly distracted, I'm doing a podcast about zaqar later today)22:26
vkmcin Spanish though22:26
vkmc:D22:26
flwangvkmc: ok, take your time22:26
flwangsounds cool :)22:27
vkmc:)22:28
flwangvkmc: yep, we have much things to do, so let's start from a blurprint :)22:29
flwangi will draft a blueprint for the reserved attributes target for m-222:29
vkmcsounds great22:31
vkmcI'll catch up with the ali yun architecture22:31
vkmcand ping you to discuss the other features22:31
vkmcmaybe with some other contribs :)22:32
flwangawesome, thank you so much22:34
flwangyou make my day :)22:34
Eva-iflwang: vkmc: hello, I didn't attend to meeting, but I read it.22:34
flwangEva-i: awesome22:34
Eva-ivkmc: flwang: I think we can move now missing contributor content from wiki to http://docs.openstack.org/developer/zaqar/, but all other things still have to reside in wiki fow now before doc team will allocate places for hosting Zaqar docs.22:38
vkmcflwang++22:38
vkmcEva-i, hey hey!22:38
vkmccool22:38
vkmc:)22:38
vkmcwe could start working on it tomorrow, split some work22:38
vkmcand start changing the docs22:38
vkmcwe can file bugs for the docs under developer/zaqar or start a new bp22:39
vkmcperhaps start a new bp makes more sense22:39
flwangvkmc: bp in zaqar?22:39
vkmcflwang, yes, the developer guide is in our code base22:40
flwangyep,  i see, just confirm22:40
vkmchttps://github.com/openstack/zaqar/tree/master/doc/source <-22:40
vkmcso we can keep track of changes that way22:40
Eva-ivkmc: so what we're gonna do in developer/zaqar? Import few things from wiki and add API ref as you wanted?22:42
vkmcEva-i, and fix the bugs you mentioned in the etherpad22:43
Eva-ivkmc: alright22:43
flwangvkmc: as for the api ref22:43
flwangthe ref we have is not the one i'm looking for22:43
flwangvkmc: Eva-i: i would like to see an api-ref like this http://developer.openstack.org/api-ref.html22:44
flwangour current api-ref is used for the zaqar developer22:44
flwangbut we do really need the api-ref for the developer who would like to leverage zaqar in their application22:45
flwangi would put a higher priority for the later :)22:45
flwangjust my 2 cents22:45
vkmc+122:45
Eva-iflwang: yes, Zaqar will need eventually it's own page in http://developer.openstack.org/api-ref.html22:45
vkmcwe need both22:45
Eva-iflwang: but also additional spec must be filled for doc team22:46
flwangEva-i: yep, i see22:46
flwangi know we don't have much bandwidht/resource to do all the them22:47
flwangjust think aloud in case you miss it22:47
Eva-iflwang: for now we can host user API ref somewhere else for example22:47
flwangEva-i: define 'user API'?22:48
Eva-iflwang: https://wiki.openstack.org/wiki/Zaqar/specs/api/v1.122:49
flwangEva-i: yep, if we have the bandwidth, we can work it out and keep it in zaqar dev doc22:50
flwangit's ok, IMHO22:50
*** tej has joined #openstack-zaqar22:50
*** tej has quit IRC22:51
Eva-iflwang: also zaqar dev docs currently have this: http://docs.openstack.org/developer/zaqar/#api-reference22:51
flwangEva-i: yep, i didn't see the other projects keeping this kind of 'api ref'22:55
Eva-iflwang: personally I don't agree with vkmc and I think it's best to keep 'user API' in wiki for now untill Zaqar will get it's place in http://developer.openstack.org/api-ref.html22:55
vkmcI said we should have it in both places22:56
vkmcnot remove it from the wiki22:56
vkmcEva-i, ^22:56
vkmcI only aimed to remove the information that is redundant and for contributors only22:57
Eva-ivkmc: why we need user API reference in both places?22:57
vkmcEva-i, because the information under developers/zaqar is the official guide for Zaqar developers22:58
vkmcand it would make sense to have everything in one place, or at least a pointer22:58
Eva-ivkmc: it would be hard to keep in sync these things. Maybe it's better to store API reference in one place and provide a link to it from another place?23:00
vkmcsure, that could work23:00
Eva-ivkmc: okay23:01
*** david-lyle has joined #openstack-zaqar23:03
*** david-lyle has quit IRC23:05
Eva-iKeystone, for example, in it's developer/keystone stores information only for contributors, not all the information contributors might need. Of course, contributors need more than that, so the second paragraph exists: http://docs.openstack.org/developer/keystone/23:12
flwanglunch time, brb23:15
*** david-lyle has joined #openstack-zaqar23:23
*** dmowrer has joined #openstack-zaqar23:25
*** david-lyle has quit IRC23:25
*** dmowrer has quit IRC23:26
*** dmowrer has joined #openstack-zaqar23:27
*** davideagnello has quit IRC23:27
*** davideagnello has joined #openstack-zaqar23:29
*** davideagnello has quit IRC23:31
*** dmowrer has quit IRC23:31
*** davideagnello has joined #openstack-zaqar23:35
*** david-lyle has joined #openstack-zaqar23:35
Eva-ivkmc: flwang: thank you for warm words for me in meetings chat23:36
*** david-lyle has quit IRC23:41
*** david-ly_ has joined #openstack-zaqar23:41
*** tej has joined #openstack-zaqar23:59

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