Wednesday, 2015-12-09

flwangEva-i: i would like to use blueprint00:02
flwangbut for this case, we don't need a spec?00:02
ryansbI think we probably need a spec, since it's APIImpact00:05
*** tej_ has joined #openstack-zaqar00:06
*** tej has joined #openstack-zaqar00:06
Eva-iryansb: websocket connection in web client opens just like this "var socket = new WebSocket('ws://localhost:9000/');", after opening connection zaqar and zaqar clients send headers inside serialized messages. There's no http, though it's better to use same names for headers as in http.00:07
flwangryansb: sorry, i'm talking about the doc question Eva-i asked00:07
Eva-iflwang: only if you want, I'm lazy to write the spec, but of course I can ;)00:09
*** tej__ has joined #openstack-zaqar00:10
flwangEva-i: personally, i don't think we really need a spec00:10
flwangif you can write a clear blueprint00:10
ryansboh, ok, then yeah never mind00:10
ryansbI've got to head off - have a good night zaqarians00:11
Eva-iryansb: me never mind?00:11
Eva-iryansb: thank you for today, good night00:11
ryansbEva-i: I mean flwang never mind about the spec for docs00:11
Eva-iryansb: okay00:11
ryansbI crossed the conversational wires00:11
*** tej_ has quit IRC00:13
*** tej has quit IRC00:13
Eva-iflwang: should I describe in the blueprint only solutions or both problems and solutions?00:13
*** tej has joined #openstack-zaqar00:13
flwangEva-i: problems and solutions if you don't want to write a spec00:19
flwangthen a detailed blueprint would be nice00:19
Eva-iflwang: alright00:20
*** tej has quit IRC00:20
Eva-iflwang: if blueprint will be too fat, we can always convert it to spec.00:20
*** tej has joined #openstack-zaqar00:20
flwangdo you think it's a huge blueprint?00:21
flwangif so, we may need to split it00:21
flwangi don't think spec and address the size issue00:21
ryansbflwang: can you review https://review.openstack.org/#/c/254926/ when you get a chance?00:22
ryansbok, now I actually have to log off - see y'all tomorrow00:22
flwangsure, see you00:24
Eva-iflwang: the blueprint will have more text than the commit message in this patch https://review.openstack.org/#/c/250582/00:24
Eva-iflwang: I don't think the blueprint should be splitted, I saw in doc team very complex blueprints.00:26
*** AAzza_ has joined #openstack-zaqar00:26
flwangEva-i: it's a good question for me. Personally, i don't want to let the spec adding more workload for you00:26
flwangbut if you think a spec can make things more clear, then go for it00:27
flwangfor document, i don't think we have a very strict rule00:27
*** AAzza has quit IRC00:30
*** AAzza has joined #openstack-zaqar00:30
*** AAzza_ has quit IRC00:32
Eva-iflwang: spec will make things more clear, because the commit message from my patch, which I want to include to blueprint text, is hard to read and it needs formatting. I believe specs exist exactly for that purpose - to format the blueprint message and add image inserts.00:36
flwangEva-i: if you're happy,then i'm happy00:37
Eva-iflwang: in my blueprint there will be no images, of course.00:37
*** tej has quit IRC00:37
*** tej__ has quit IRC00:37
Eva-iflwang: =)00:37
flwangEva-i: cool :)00:37
*** openstackstatus has quit IRC00:50
*** openstack has joined #openstack-zaqar00:53
*** itisha has quit IRC01:16
*** lei-zh1 has joined #openstack-zaqar02:01
openstackgerritEva Balycheva proposed openstack/zaqar: Make zaqar-bench use credentials from os_client_config  https://review.openstack.org/25505102:52
*** Qiming has joined #openstack-zaqar02:56
openstackgerritEva Balycheva proposed openstack/zaqar: Make zaqar-bench use credentials from os_client_config  https://review.openstack.org/25505102:56
openstackgerritEva Balycheva proposed openstack/zaqar: Make zaqar-bench use credentials from os_client_config  https://review.openstack.org/25505102:57
*** sonuk has joined #openstack-zaqar03:05
*** sonuk has left #openstack-zaqar03:10
*** dmowrer has joined #openstack-zaqar03:19
*** dmowrer has quit IRC03:24
*** flwang1 has quit IRC03:55
Eva-iflwang: ping03:58
*** lei-zh1 has quit IRC04:26
*** lei-zh1 has joined #openstack-zaqar04:44
*** lei-zh1 has quit IRC05:02
*** boris-42_ has quit IRC05:03
*** Qiming has quit IRC05:22
openstackgerritEva Balycheva proposed openstack/zaqar-specs: Support for binary data in the websocket transport  https://review.openstack.org/24925705:26
*** Qiming has joined #openstack-zaqar05:27
Eva-iflwang: I rethinked the problem of subscriptions. Such problem is hardly existing. I provided the explanation in the spec. If it's not really a problem, I can remove all mentions of this problem from thie spec.05:29
*** lei-zh1 has joined #openstack-zaqar05:31
*** dmowrer has joined #openstack-zaqar05:46
*** dmowrer has quit IRC05:51
openstackgerritOpenStack Proposal Bot proposed openstack/zaqar: Imported Translations from Zanata  https://review.openstack.org/25062106:28
*** rcernin has joined #openstack-zaqar07:20
*** flwang1 has joined #openstack-zaqar07:25
*** boris-42_ has joined #openstack-zaqar07:31
*** flwang1 has quit IRC08:00
*** flwang1 has joined #openstack-zaqar08:16
*** flwang1 has quit IRC08:49
*** flwang1 has joined #openstack-zaqar08:49
*** openstackstatus has quit IRC09:05
*** openstack has joined #openstack-zaqar09:08
*** dmowrer has joined #openstack-zaqar09:13
*** dmowrer has quit IRC09:18
*** openstackgerrit has quit IRC09:32
*** openstackgerrit has joined #openstack-zaqar09:32
*** openstackgerrit has quit IRC10:02
*** openstackgerrit has joined #openstack-zaqar10:02
*** lei-zh1 has quit IRC11:24
flwang1vkmc: flaper87: can you help review https://review.openstack.org/254926 ?11:35
openstackgerritFei Long Wang proposed openstack/zaqar-ui: Initial project creation  https://review.openstack.org/25521311:36
ryansbheyo, zaqarians11:55
vkmcheyo!11:58
ryansbvkmc: you should help fix the gate by reviewing https://review.openstack.org/#/c/254926/ :)12:05
vkmcryansb, sure thing12:06
flwang1ryansb: hi12:11
flwang1vkmc: hello12:11
flwang1vkmc: and https://review.openstack.org/#/q/status:open+project:openstack/python-zaqarclient,n,z :)12:11
flwang1i'm going to bed12:12
flwang1btw, i just created our first ui patch, see https://review.openstack.org/25521312:12
flwang1but unfortunately, i'm not a good ui guy. the patch still needs some love12:12
flwang1https://review.openstack.org/25521312:12
*** dmowrer has joined #openstack-zaqar12:16
*** dmowrer has quit IRC12:34
*** dmowrer has joined #openstack-zaqar12:34
*** boris-42_ has quit IRC12:43
*** dmowrer has quit IRC12:46
*** dmowrer has joined #openstack-zaqar12:47
*** dmowrer has quit IRC12:53
*** dmowrer has joined #openstack-zaqar12:53
*** dmowrer has quit IRC12:58
*** dmowrer_ has joined #openstack-zaqar12:58
*** dmowrer has joined #openstack-zaqar13:00
*** itxaka has joined #openstack-zaqar13:01
*** dmowrer_ has quit IRC13:03
*** dmowrer has quit IRC13:06
*** dmowrer has joined #openstack-zaqar13:07
*** dmowrer has quit IRC13:16
*** dmowrer has joined #openstack-zaqar13:18
*** dmowrer_ has joined #openstack-zaqar13:21
*** dmowrer has quit IRC13:23
Eva-ihello13:24
*** dmowrer_ has quit IRC13:36
*** dmowrer has joined #openstack-zaqar13:37
*** dmowrer has quit IRC13:41
*** dmowrer has joined #openstack-zaqar13:42
openstackgerritRob Cresswell proposed openstack/zaqar-ui: Initial project creation  https://review.openstack.org/25521313:49
openstackgerritRob Cresswell proposed openstack/zaqar-ui: Initial project creation  https://review.openstack.org/25521313:51
*** dmowrer has quit IRC13:52
*** dmowrer has joined #openstack-zaqar13:52
*** venkat_ has joined #openstack-zaqar13:54
*** dmowrer_ has joined #openstack-zaqar13:55
*** dmowrer has quit IRC13:57
*** dmowrer_ has quit IRC13:59
*** robcresswell has joined #openstack-zaqar14:00
robcresswello/ Hi folks. Just in case it wasn't seen in the Horizon chat, I've updated the UI patch to fix a couple of issues https://review.openstack.org/#/c/255213/14:00
robcresswellIt should load as expected within Horizon now. Fixed tests as well I believe.14:01
vkmcrobcresswell, \o14:06
vkmcrobcresswell, thanks for that14:06
*** sriram has joined #openstack-zaqar14:10
*** sriram has quit IRC14:11
*** sriram has joined #openstack-zaqar14:12
Eva-irobcresswell: thank you14:17
*** dmowrer has joined #openstack-zaqar14:24
*** mpanetta_ has joined #openstack-zaqar14:27
*** amitgandhinz has joined #openstack-zaqar14:29
Eva-ivkmc: can you please take a look at my updated spec https://review.openstack.org/249257 ?14:35
*** dynarro has joined #openstack-zaqar14:50
*** tej has joined #openstack-zaqar14:51
*** tej_ has joined #openstack-zaqar14:51
Eva-iCan you guys look at the second paragraph here: http://developer.openstack.org/api-ref.html ? How do you think, what status each Zaqar API have?14:56
*** venkat_ has quit IRC14:58
robcresswellEva-i, vkmc: No problem :)14:59
robcresswellPing me in #openstack-horizon if you need more help14:59
ryansbEva-i: I think we'd consider v1 deprecated, v1.1. supported, and v2 current15:03
ryansbbut definitely ask more people than just me15:03
Eva-irobcresswell: yes, sure ;)15:04
*** robcresswell has left #openstack-zaqar15:04
Eva-iryansb: okay. If v2 is current, do you think it's "stable" (we will not make any backward incompatible patches)?15:05
Eva-iryansb: I'm not sure, but I think I saw some patches for v2 API which are not backward compatible.15:07
ryansbnot sure15:07
Eva-iryansb: but maybe our next patches will be compatible. Yes, let's wait for the opinions of others.15:08
ryansbyup15:08
*** wanghao has joined #openstack-zaqar15:09
*** lei-zh1 has joined #openstack-zaqar15:12
*** Qiming has quit IRC15:45
openstackgerritRyan Brown proposed openstack/python-zaqarclient: First pass at CLI for signed URLs  https://review.openstack.org/25373116:01
*** kgriffs|afk is now known as kgriffs16:18
*** kgriffs is now known as kgriffs|afk16:27
*** Eva-i has quit IRC16:27
*** Eva-i has joined #openstack-zaqar16:29
*** amitgandhinz has quit IRC16:32
*** amitgandhinz has joined #openstack-zaqar16:33
*** dmowrer has quit IRC16:48
*** lei-zh1 has quit IRC16:55
*** dmowrer has joined #openstack-zaqar17:05
*** rcernin has quit IRC17:11
*** dynarro has quit IRC17:39
*** amitgandhinz has quit IRC17:41
*** itxaka has quit IRC17:52
*** amitgandhinz has joined #openstack-zaqar18:06
*** amitgandhinz has quit IRC18:11
*** amitgandhinz has joined #openstack-zaqar18:12
*** dmowrer has quit IRC18:32
openstackgerritEva Balycheva proposed openstack/zaqar: Make zaqar-bench use credentials from os_client_config  https://review.openstack.org/25505118:46
*** flwang1 has quit IRC18:50
*** flwang1 has joined #openstack-zaqar18:51
Eva-iHello. I'm trying to make zaqar-bench able to work with keystone authentication. For some reason it gets stuck with keystone auth. It works only when I set "skip_queue_reset = True", i.e. zaqar/bench/conductor.py:40 method doesn't execute. What can be wrong? =/18:53
Eva-iHere's my patch https://review.openstack.org/25505118:53
*** dmowrer has joined #openstack-zaqar18:54
*** flwang1 has quit IRC19:00
*** david-ly_ has joined #openstack-zaqar19:00
*** david-ly_ is now known as david-lyle_19:03
*** david-lyle has quit IRC19:03
*** david-lyle_ is now known as david-lyle19:04
openstackgerritMerged openstack/zaqar: Explicitly use asyncio protocol for websockets  https://review.openstack.org/25492619:16
*** wanghao has quit IRC19:27
*** sriram has quit IRC19:31
*** sriram has joined #openstack-zaqar19:31
*** sriram has joined #openstack-zaqar19:31
*** sriram has quit IRC19:34
*** sriram has joined #openstack-zaqar19:35
*** flwang1 has joined #openstack-zaqar19:49
*** david-lyle has quit IRC19:58
*** david-lyle has joined #openstack-zaqar19:58
*** mpanetta_ has quit IRC20:04
*** dmowrer has quit IRC20:15
*** tej_ has quit IRC20:39
*** tej has quit IRC20:39
*** dmowrer has joined #openstack-zaqar20:58
*** dmowrer has quit IRC21:03
Eva-iflwang: flwang1: ping21:39
flwangEva-i: pong21:40
Eva-iflwang: hello, I saw your comment on my zaqar-bench patch(https://review.openstack.org/251023). This patch only allows Zaqar to work with Zaqar version before november 23(because this patch was merged: https://review.openstack.org/#/c/245526/). My new upcoming patch (https://review.openstack.org/255051) will make it work with latest Zaqar version.21:41
Eva-iflwang: sorry not Zaqar, but python-zaqarclient21:42
flwangEva-i: did you mean with the first patch, benchmark still doesn't work?21:42
Eva-iflwang: yes, still doesn't work, but work with any python-zaqarclient version before november 23.21:43
Eva-i*works21:43
flwangEva-i: hmm...21:46
flwangthe title is "Fix zaqar-bench not working"21:47
flwangso is it possible to init the zaqar client as noauth21:47
Eva-iflwang: well, the title was true... and now it's not. I can change the title.21:47
Eva-iflwang: or yes, I can make zaqar-bench specify 'noauth' backend for the client.21:48
flwangthat's my point21:48
flwangi think the fix should be able to get a workable noauth benchmark, right?21:49
Eva-iflwang: okay, going to implement it right away.21:50
flwangEva-i: awesome, thanks21:50
Eva-iflwang: can you also look at the second paragraph here: http://developer.openstack.org/api-ref.html ? How do you think, what status each Zaqar API have? It's needed for API spec.21:51
Eva-i*API docs spec21:51
flwangcurrent is v221:51
flwangsupported v1.121:52
flwangas for v1, i think we haven't deprecated it21:52
flwangi will confirm with flaper8721:52
openstackgerritMerged openstack/zaqar: Remove version from setup.cfg  https://review.openstack.org/25215421:52
Eva-iSo we will not make any backward incompatible patches to API v2 anymore and can just add new features?21:52
flwangi can't get your point21:55
flwangnew feature != incompatible21:55
flwangwe can add new features to v2, but not v1.1 and v121:56
Eva-iflwang: yes, "current" means new features, but no more incompatible changes. If we're planning to make some incompatible changes, v2 should be called "experimental".21:57
Eva-iflwang: basically, I'm asking, are we planning any incompatible changes?21:58
flwangEva-i: nobody want to add incompatible changes21:58
Eva-iflwang: okay21:58
flwangbut you know, software is  a product of compromise21:59
flwangthat said, we can't guarantee 100%22:00
*** sriram has quit IRC22:00
Eva-iflwang: you mean, if we find huuuge bug, we probably will need change the API in incompatible way? I understand.22:00
flwangsince we're still evolving22:01
flwangEva-i: yep, possibly22:01
Eva-iflwang: okay22:01
flwangyou're smart, i think you can get my point22:02
Eva-iflwang: and that's what Ryan thinks: "v1 deprecated, v1.1. supported, and v2 current". You, me and Ryan think the same way about v.1.1 and v2.22:05
Eva-iflwang: I think I will omit API v1 in my API spec.22:06
flwangEva-i: i think v1 is deprecated, but i'm 100% sure, since IIRC, rackspace is still using it22:06
flwangEva-i: it's ok, you don't have to take care of v1 in your spec22:07
Eva-iflwang: also I updated my websocket spec: https://review.openstack.org/249257. I'm sorry, I decided not to do this: "maybe we can add a new reserved option for subscription to define the format". I came up with a new different solution, explained why I chosen it and added "reserved option" as alternative solution. If you will not like the new solution, I can quickly set "reserved option" as main solution. Sorry for so many messages, was just w22:15
flwangEva-i: i will take a look, i always like the good idea, not mine :)22:16
Eva-iflwang: cool22:17
*** david-lyle has quit IRC22:34
*** david-ly_ has joined #openstack-zaqar22:39
*** david-ly_ is now known as david-lyle22:45
*** boris-42_ has joined #openstack-zaqar22:59
openstackgerritEva Balycheva proposed openstack/zaqar: Fix zaqar-bench not working  https://review.openstack.org/25102323:02
*** amitgandhinz has quit IRC23:07
openstackgerritEva Balycheva proposed openstack/zaqar: Fix zaqar-bench not working  https://review.openstack.org/25102323:10
*** rcernin has joined #openstack-zaqar23:37
*** Qiming has joined #openstack-zaqar23:51
openstackgerritEva Balycheva proposed openstack/zaqar: Refactoring of docs during Mitaka cycle  https://review.openstack.org/25058223:56

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