Thursday, 2015-10-22

*** Qiming has quit IRC00:00
*** JAHoagie has quit IRC00:17
mdnadeemvkmc: Good morning :)00:20
vkmcmdnadeem, morning!00:20
mdnadeemvkmc: Have you seen the patch?00:21
vkmcmdnadeem, I did! looks very good00:22
vkmcchanging it for v2 seems right... and I think its backportable to v1.100:22
vkmccould you remove the .idea files? and then we can push it fwd00:22
vkmcthanks for working on it00:22
vkmc:D00:22
mdnadeemvkmc: Yah , i just remove it asap.00:23
mdnadeemvkmc: is v1.1 is release version?00:23
*** inteq has joined #openstack-zaqar00:23
*** kgriffs is now known as kgriffs|afk00:24
*** achanda has joined #openstack-zaqar00:26
mdnadeemvkmc : ^^??00:35
*** kgriffs|afk is now known as kgriffs00:37
*** kgriffs is now known as kgriffs|afk00:46
vkmcmdnadeem, v1.1 is the prior version to v200:50
vkmcfor the api00:50
mdnadeemvkmc: hehe, thanks any way i want to know if v1.1 is released version? . As per my knowledge we have to check backward compatibility with released version only00:52
vkmcmdnadeem, it is yes :)00:53
vkmcv1 is freezed... v1.1 not yet00:53
vkmcI think it won't do any harm00:53
vkmcbuuuuuut00:53
vkmcjust in case00:53
vkmcI'd like to discuss this with the rest of the team00:53
mdnadeemvkmc : Thanks, however i can not understand , what you mean by backportable to v1.1, is this mean i can do changes for v1.1 also?00:55
*** kgriffs|afk is now known as kgriffs01:03
*** Qiming has joined #openstack-zaqar01:08
Eva-ivkmc: if changes will be made to v1.1 API, then client code for v1.1 API will not be compatible anymore.01:09
mdnadeemvkmc: ^^ , i too feel so01:10
Eva-ivkmc: people who wrote programs for v1.1 API might get errors there were not expecting01:10
Eva-i*they were not expecting01:11
Eva-iSo even if v1.1 contained the bug, people already adapted to this bug, they have found some workaround01:12
*** kgriffs is now known as kgriffs|afk01:12
Eva-iAnd changing v.1.1 API which is called now stable will make these people sad01:13
Eva-iOr v.1.1 is still considered as unstable?01:14
vkmcnot for this change01:14
vkmcthis change performs a control over name collisions01:14
vkmcits not a change in the api01:14
Eva-iThis change affects responses the API provides.01:17
mdnadeemvkmc: yes, like before create command on duplicate pool name response to 201 and now it response to 40001:18
vkmcsure01:19
vkmcbut the development for v1.1 is not ended yet01:19
vkmcthat's why I'm thinking maybe its something we could add01:20
mdnadeemvkmc: oh if v1.1 is not freese yet, then we do changes , ahh cool :)01:20
Eva-iSomeone might expect 201 responses now in such cases, but suddenly zaqar will give 400 responses.01:20
mdnadeem*freeze01:20
vkmcEva-i, that's correct01:20
vkmcyou are right about it, this change changes the api01:21
mdnadeemEva-i: v1.1 is not release yet, so such changes could be possible01:22
Eva-iFor some reason I thought v1.1 is stable, but in wiki I see that only v1.0 is released01:22
Eva-iSo maybe it will be okay to change v.1.101:22
Eva-ibut it's strange a bit. Why to work on v.2.0 API when v1.1 is not yet finished01:24
vkmcyeah, that's why I'm confused01:25
vkmc:D01:25
vkmcI'll ask the PTL later about this01:25
mdnadeemI think wiki has very old data, it is not updated ye,  may be v1.1 is released01:26
mdnadeemvkmc: Please confirm us after asking to PTL :)01:26
vkmcsure, I'll ask here on the channel so you get noticed as well01:27
mdnadeemcool, :)01:27
mdnadeemAfter getting confirmation, i will work on for v1.101:28
vkmcgreat, thanks for that01:28
*** achanda has quit IRC01:30
vkmcEva-i, how are you doing with your application?01:31
Eva-ivkmc: I still haven't registered in outreachy01:31
Eva-ivkmc: today I'll update my website with "about" info and links to some of my projects. So my application will be fuller with this info01:33
Eva-ivkmc: it's time to make an application?01:35
*** akanksha_ has quit IRC01:38
vkmcEva-i, nope, the deadline is November 2nd01:39
vkmcbut I ask just in case you need help with something01:40
vkmcbtw01:40
vkmcisn't super late for you?01:40
vkmcit's late for me so... I guess...01:40
Eva-iI was about to make application about 25 october01:41
Eva-iSo in case if I will stuck with something, there will be some time01:41
vkmcsure01:42
Eva-iIt's not superlate for me01:42
vkmc4.40 am?01:42
Eva-iI just got up two hours ago.01:42
Eva-iyes, 04.42 AM01:42
vkmco.o01:42
Eva-iI decided to gradually shift my sleeping regime. In two days I'll be sleeping like a normal person.01:43
vkmchaha01:43
vkmcwhatever fits you, is ok01:43
vkmcmake sure to get enough sleep though :)01:44
Eva-iI just thought I miss the sun and so decided to fix my sleeping regime to catch more of it.01:44
vkmc:D that makes sense01:44
Eva-ivkmc: yes, sure. I feel great.01:44
*** achanda has joined #openstack-zaqar01:51
*** boris-42 has joined #openstack-zaqar02:08
openstackgerritMD NADEEM proposed openstack/zaqar: Create api through PoolNameExist exception for duplicate pool name  https://review.openstack.org/23800602:14
*** achanda has quit IRC02:17
*** khushbu_ has joined #openstack-zaqar03:14
*** achanda has joined #openstack-zaqar03:17
*** achanda has quit IRC03:25
*** khushbu_ has quit IRC03:34
*** khushbu has joined #openstack-zaqar03:36
*** achanda has joined #openstack-zaqar03:56
*** khushbu has quit IRC04:19
*** khushbu_ has joined #openstack-zaqar04:23
openstackgerritMD NADEEM proposed openstack/zaqar: Create api should throw PoolNameExist exception for duplicate pool name  https://review.openstack.org/23800604:26
*** pt_15 has quit IRC04:28
*** itisha has quit IRC04:31
*** khushbu_ has quit IRC04:52
*** csoukup has joined #openstack-zaqar05:08
*** khushbu_ has joined #openstack-zaqar05:31
*** khushbu_ has quit IRC05:59
*** csoukup has quit IRC06:01
*** khushbu_ has joined #openstack-zaqar06:02
*** khushbu_ has quit IRC06:33
*** JAHoagie has joined #openstack-zaqar06:34
*** khushbu_ has joined #openstack-zaqar06:34
*** khushbu_ has quit IRC06:38
*** khushbu_ has joined #openstack-zaqar06:39
*** khushbu_ has quit IRC06:53
mdnadeemflaper87: Hello, Please add me on wechat, my wechat ID: mdnadeem9207:03
openstackgerritZhiQiang Fan proposed openstack/zaqar: Use oslo_config new type PortOpt for port options  https://review.openstack.org/23838607:03
flaper87mdnadeem: erm, mmh, lemme find the right way to say this without you hatting me: We decided last night to stop using wechat because it has several security holes. :( Feel free to email me your number and I'll create a whatsapp group07:07
mdnadeemflaper87: I had install wechat last night :). but its cool to join on whatsup, i will mail you my number. Thanks07:13
*** achanda has quit IRC07:13
mdnadeemflaper87: can you confirm , if zaqar API v1.1 is freeze or under development ?07:17
flaper87mdnadeem: it's frozen07:23
flaper87mdnadeem: v1.1 is supported, v2 is current07:23
mdnadeemflaper87: ohk, Thanks07:27
mdnadeemvkmc: Eva-i : ^^07:27
openstackgerritMD NADEEM proposed openstack/zaqar: Flavor create api should throw FlavorNameExist exception for duplicate Flavor name  https://review.openstack.org/23839607:43
openstackgerritMD NADEEM proposed openstack/zaqar: Flavor create api should throw FlavorNameExist exception for duplicate Flavor name  https://review.openstack.org/23839607:47
*** khushbu_ has joined #openstack-zaqar08:04
*** achanda has joined #openstack-zaqar08:12
*** khushbu_ has quit IRC08:24
mdnadeemtherve: hi08:24
therveHello08:24
mdnadeemI am try to run websocket.test_queue  test, however tox skip test cases08:26
mdnadeemmay be i am doing something wrong, Please have a look : http://paste.openstack.org/show/477103/08:27
*** khushbu_ has joined #openstack-zaqar08:27
mdnadeemtherve: may be i have to test them on integration mode08:29
thervemdnadeem, Yeah, try tox -eintegration instead08:31
mdnadeem*trying08:32
mdnadeemtherve: working Thanks :)08:34
therveNo problem!08:35
thervemdnadeem, That's instended. I wanted to make sure the integration builder fails properly08:43
Eva-imdnadeem: hehe =) I added info about API v1.1 stability as a task to documentation refactoring etherpad.08:43
mdnadeemtherve: ohk , got it. Thanks :)08:43
mdnadeemEva-i: cool, :)08:44
*** akanksha_ has joined #openstack-zaqar08:45
mdnadeemEva-i: flaper87 has confirm that v1.1 is freeze now as you already seen in log .08:46
mdnadeemEva-i: I think we need  work on documentation part also, many information is missing there, so there is need to update it with right content.08:51
*** exploreshaifali has joined #openstack-zaqar08:55
Eva-imdnadeem: yes, refactoring is coming. That's why such etherpad exists.08:56
mdnadeemshare me the link08:57
exploreshaifalimdnadeem, Eva-i Hello!08:57
*** csoukup has joined #openstack-zaqar08:57
Eva-iexploreshaifali: hellow08:57
mdnadeemexploreshaifali, Hellooooooooo08:57
exploreshaifali:D08:58
exploreshaifalihow are you?08:58
mdnadeemexploreshaifali, mast, you say08:58
exploreshaifaliall well :)08:58
exploreshaifalihow we register a queue to pool? You people were playing with them, I remember, so might you can answer08:58
exploreshaifaliI have a queue with name q1 let say and a pool with p108:59
mdnadeemi was sleeping that time,08:59
exploreshaifalinow if I want q1 to register to p1, what to do?08:59
mdnadeemi check log very late in the morning08:59
Eva-imdnadeem: here's the link, but if I'm not mistaken, vkmc said that it's intended to be edited during Mitaka summit. Maybe it's wrong that I'm adding info to it. https://etherpad.openstack.org/p/zaqar-mitaka-docs08:59
mdnadeemexploreshaifali, we can link a q1 to a pool group,09:00
Eva-iexploreshaifali: as I know, it's impossible to link queque to a particular pool09:01
exploreshaifaliokay! and what to do to register a queue to pool group09:01
*** openstackgerrit has quit IRC09:01
*** csoukup has quit IRC09:01
exploreshaifalilet say we have group g1 which have pools, p1, p2, p309:01
*** openstackgerrit has joined #openstack-zaqar09:02
mdnadeemyou have to create a flavor that should link to g109:02
exploreshaifalifist thing, dose these three pools can have different flavors?09:02
mdnadeemflavor should attached to a group ,09:03
mdnadeemwe can create multiple flavor on a group09:04
exploreshaifalimdnadeem, this is as per v2 ?09:05
mdnadeemwhile creating a queue you should pass a flavor name, so here is the mapping , q1-->f1, f1-->g1, g1-->{p1,p2,p3}09:05
mdnadeemso q1 can be link to any of the pool, depending on pool weight09:06
mdnadeemyes09:06
mdnadeemlet me check, if it is same on v1.1 or not09:06
exploreshaifalimdnadeem, please can you link me to v2 doc?09:10
exploreshaifalihttps://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1 is for v1.109:11
Eva-iexploreshaifali: v2 doc do not exists09:11
mdnadeemI guess there is no doc for v209:11
Eva-i*do not exist09:12
exploreshaifalimdnadeem, so in v1.1 while creating  flavor we can give a list of pools09:12
exploreshaifalithat will link to that flavor09:12
*** achanda has quit IRC09:12
exploreshaifaliflavors are not attached with group, as per v1.109:12
mdnadeemexploreshaifali, no09:12
mdnadeemwe give a pool group name, while creating a flavor09:13
mdnadeemyes, that need to be corrected09:13
mdnadeemthere are lots of thing that we should update in v1.1 page,09:13
mdnadeemi and Eva-i have just talk about it.09:14
exploreshaifalioh! okay.... This thing was creating confusion to me109:14
exploreshaifaliGreat!09:14
mdnadeemyes, every one get confused09:14
mdnadeemby refering v1.1 doc09:14
exploreshaifaliThanks people, mdnadeem Eva-i :)09:14
exploreshaifalihahha09:14
exploreshaifalithat is full on flaper87's fault09:14
exploreshaifali:P09:14
mdnadeemnp, :)09:14
exploreshaifaliflaper is not here atm, so can blame him09:16
exploreshaifali:P09:16
mdnadeemhe can check log later, :)09:17
Eva-imdnadeem: take a look at this change https://review.openstack.org/#/c/220876/409:17
Eva-imdnadeem: I think it modifies v1.1 API, which is prohibited09:18
mdnadeemEva-i: yah, i had seen it before.09:18
mdnadeemEva-i: Regarding this i need to talk with flawng,09:19
exploreshaifalimdnadeem, its a trend here, to blame those who are not present ;)09:20
exploreshaifalino body mind it!09:20
exploreshaifalibtw tht patch link that Eva-i gave clearly specify that we need to make changes in v1.1 doc09:21
mdnadeemSo you will get blamed most, as most of the time you are not present here. lolz09:21
exploreshaifalihaha09:22
mdnadeemyes, we must update it. may be after summit i will do that09:22
exploreshaifaliI will not mind it, at least you people will remember me09:22
exploreshaifali:D09:22
mdnadeemexploreshaifali,  always :)09:22
exploreshaifaliyes after summit discussion on docs, we will do.09:22
exploreshaifali:)09:22
Eva-iflaper87: I think this patch changes v1.1 API which is stable. Is it okay? https://review.openstack.org/#/c/220876/409:23
mdnadeemEva-i: good question , flaper87 is now away, may be he response lately :)09:25
Eva-imdnadeem: yeah, maybe09:25
mdnadeemexploreshaifali, Eva-i , leaving for the home, see you tomorrow :)09:26
exploreshaifalimdnadeem, see you :)09:29
*** JAHoagie has quit IRC09:33
*** khushbu_ has quit IRC09:37
*** khushbu_ has joined #openstack-zaqar09:40
*** khushbu_ has quit IRC09:46
*** openstackgerrit has quit IRC09:46
*** openstackgerrit has joined #openstack-zaqar09:47
*** achanda has joined #openstack-zaqar10:04
*** Qiming has quit IRC10:16
*** achanda has quit IRC10:42
*** achanda has joined #openstack-zaqar10:43
*** achanda has quit IRC10:45
*** Qiming has joined #openstack-zaqar11:10
*** khushbu_ has joined #openstack-zaqar11:34
*** exploreshaifali has quit IRC11:40
*** achanda has joined #openstack-zaqar11:46
*** achanda has quit IRC11:51
flaper87Eva-i: yeah, v1.1 shouldn't be changed11:55
flaper87actually, none11:55
flaper87v2 needs to keep backwards compatibility11:56
*** khushbu_ has quit IRC11:56
Eva-iflaper87: do you mean v2 needs to support all old API features and behave exactly like old API when using these features?12:28
Eva-iflaper87: what if old API contains a bug?12:29
Eva-iflaper87: this bug should be kept?12:31
*** khushbu has joined #openstack-zaqar12:31
vkmcwe should document that v1.1 is stable12:41
vkmcand I don't see why we shouldn't change v212:42
vkmcIMO we should fix that12:42
Eva-imaybe full backwards compatibility is not worth keeping same behavior, keeping old bugs12:47
*** akanksha_ has quit IRC12:48
Eva-iflaper87: but okay, if you say so12:49
*** njohnston is now known as nate_gone12:53
*** exploreshaifali has joined #openstack-zaqar12:59
Eva-iI heard about semantic versioning. When semantic versioning is used, it's okay to change API when program's major version number changes.13:04
vkmcyeah13:06
vkmcthat's a good point13:06
*** sriram has joined #openstack-zaqar13:06
Eva-ibut I don't know if zaqar is using this versioning scheme13:06
*** kgriffs|afk is now known as kgriffs13:24
*** nate_gone is now known as njohnston13:25
*** JAHoagie has joined #openstack-zaqar13:27
Eva-iAnd my last argument will be: backwards compatibility is already broken13:28
*** JAHoagie has quit IRC13:28
*** JAHoagie has joined #openstack-zaqar13:29
Eva-iexample: https://wiki.openstack.org/wiki/Zaqar/specs/api/v1#Post_Message.28s.29 https://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1#Post_Message.28s.2913:29
*** kgriffs is now known as kgriffs|afk13:30
therveEva-i, The wiki is wrong on that one13:33
therveI don't think you should use it as a reference13:33
therveAh no it's POST? Maybe it's right13:34
therveI think you're missing Flavio's point though13:34
therveThe compatibility is not from version X to version Y, it's while you're on version X13:35
therveBugs can be fixed, it depends on which problem you're talking about13:36
Eva-itherve: wiki is right in this case, requests are different and don't work when used with other API version13:37
exploreshaifalia flavor can have only one group?13:41
exploreshaifaliof we can have flavor belong to more than one group?13:41
Eva-i>The compatibility is not from version X to version Y, it's while you're on version X13:41
Eva-iI don't know what do you mean. We got API version X. This API must be backwards compatible with... what?13:41
Eva-itherve:13:41
*** ametts has joined #openstack-zaqar13:47
therveEva-i, itself13:47
Eva-iIt's like to say USB 3.0 is backwards compatible with USB 3.013:48
therveNo, it's zaqar v2.0 from mitaka is compatible with zaqar v2.0 from liberty13:49
*** achanda has joined #openstack-zaqar13:49
Eva-itherve: oh13:50
*** malini has joined #openstack-zaqar13:53
*** achanda has quit IRC13:56
Eva-iflaper87: what is API backwards compatibility in your opinion?13:57
flaper87Eva-i: https://www.youtube.com/watch?v=EYKdmo9Rg2s14:01
*** dynarro has joined #openstack-zaqar14:07
*** csoukup has joined #openstack-zaqar14:07
*** akanksha_ has joined #openstack-zaqar14:11
*** JAHoagie has quit IRC14:16
*** exploreshaifali has quit IRC14:16
*** mpanetta has joined #openstack-zaqar14:28
*** VeggieMeat_ has joined #openstack-zaqar14:58
*** kgriffsl has joined #openstack-zaqar15:02
*** kgriffsl is now known as kgriffs15:02
*** therve` has joined #openstack-zaqar15:03
*** mdnadeem has quit IRC15:06
*** kgriffs|afk has quit IRC15:06
*** VeggieMeat has quit IRC15:06
*** therve has quit IRC15:06
*** therve` is now known as therve15:11
*** mdnadeem has joined #openstack-zaqar15:12
*** fifieldt_ has quit IRC15:17
*** khushbu has quit IRC15:23
*** khushbu_ has joined #openstack-zaqar15:27
*** khushbu_ has quit IRC15:29
*** khushbu has joined #openstack-zaqar15:33
*** achanda has joined #openstack-zaqar15:37
*** achanda has quit IRC15:39
*** malini1 has joined #openstack-zaqar15:57
*** malini has quit IRC15:59
*** Qiming has quit IRC16:05
*** kgriffs is now known as kgriffs|afk16:05
Eva-iflaper87: good performance =)16:14
Eva-iflaper87: if you will have some time, would you please answer these questions https://etherpad.openstack.org/p/zaqar-backwards-compatibility-QA ?16:15
*** dynarro has quit IRC16:24
therveEva-i, I'm 100% positive that v2 must not be compatible with v1.116:33
therveThat's the whole point of having a v216:34
Eva-itherve: okay, how would you answer to "if yes" section of question number 4?16:36
therveNot sure there is a general rule, it's a case by case response16:39
*** achanda has joined #openstack-zaqar16:39
therveKeeping a completely wrong behavior is stupid16:39
Eva-itherve: what do you think about the particular case I provided?16:40
thervenot sure to be honest16:40
Eva-iyes, me too16:41
*** mpanetta has quit IRC16:41
therveI think it's an ok change though, because of what's in the bug16:42
therveIE the current behavior is broken for no good reason16:43
*** achanda has quit IRC16:44
*** achanda has joined #openstack-zaqar16:44
vkmctherve, have you tested the signed urls api?16:51
therveYes16:52
vkmcis the body for this request ok? curl -i -X POST http://192.168.122.167:8888/v2/queues/shared_queue/share -d "{'methods': ['GET', 'POST']}" -H "X-Auth-Token: $TOKEN"16:53
vkmcnot sure what I am missing there16:53
therveThat looks correct16:55
vkmcfor some reason it hangs on my env16:56
*** ekarlso has joined #openstack-zaqar16:56
ekarlsoHey guys16:56
ekarlsolooking at your API unit tests arent they really functional tests btw?16:56
thervehangs?16:56
vkmctherve, yeah, send the request and I never got a response16:57
vkmcekarlso, why you think so?16:57
ekarlsovkmc: since it uses live mongodb ?16:58
ekarlsoor doesnt it ?16:59
vkmctherve, http://paste.openstack.org/show/477183/16:59
vkmcekarlso, some of the tests require mongo yes17:00
vkmcbbl, lunch17:00
thervevkmc, Dang, no idea17:04
*** khushbu has quit IRC17:07
*** achanda has quit IRC17:14
*** khushbu_ has joined #openstack-zaqar17:19
*** achanda has joined #openstack-zaqar17:24
*** mpanetta has joined #openstack-zaqar17:25
*** pt_15 has joined #openstack-zaqar17:25
*** itisha has joined #openstack-zaqar17:26
*** achanda has quit IRC17:42
*** khushbu_ has quit IRC17:48
*** achanda has joined #openstack-zaqar17:48
*** khushbu_ has joined #openstack-zaqar17:56
*** stanchan has joined #openstack-zaqar18:07
*** khushbu_ has quit IRC18:24
*** achanda has quit IRC18:24
*** achanda has joined #openstack-zaqar18:28
*** khushbu has joined #openstack-zaqar18:28
*** khushbu has quit IRC18:31
*** khushbu_ has joined #openstack-zaqar18:36
*** khushbu_ has quit IRC18:39
*** khushbu_ has joined #openstack-zaqar18:48
*** khushbu_ has quit IRC18:48
*** khushbu_ has joined #openstack-zaqar18:52
*** khushbu_ has quit IRC18:54
*** khushbu has joined #openstack-zaqar18:58
*** khushbu has quit IRC19:04
*** khushbu_ has joined #openstack-zaqar19:08
*** kgriffs|afk is now known as kgriffs19:09
*** khushbu_ has quit IRC19:11
*** khushbu_ has joined #openstack-zaqar19:15
*** khushbu_ has quit IRC19:16
*** khushbu_ has joined #openstack-zaqar19:18
*** khushbu_ has quit IRC19:19
*** achanda has quit IRC19:19
*** khushbu_ has joined #openstack-zaqar19:23
*** khushbu_ has quit IRC19:27
*** khushbu has joined #openstack-zaqar19:30
*** khushbu has quit IRC19:32
*** khushbu_ has joined #openstack-zaqar19:36
*** kgriffs is now known as kgriffs|afk19:45
*** khushbu_ has quit IRC19:57
*** mpanetta has quit IRC20:05
*** malini1 has quit IRC20:06
*** achanda has joined #openstack-zaqar20:20
*** njohnston is now known as nate_gone20:21
*** achanda has quit IRC20:24
*** achanda has joined #openstack-zaqar20:24
*** achanda has quit IRC20:37
*** stanchan has quit IRC21:11
*** achanda has joined #openstack-zaqar21:30
*** stanchan has joined #openstack-zaqar21:59
*** csoukup has quit IRC22:10
*** sriram has quit IRC22:11
*** sriram has joined #openstack-zaqar22:14
*** sriram has quit IRC22:21
*** zigo has quit IRC22:25
*** zigo has joined #openstack-zaqar22:27
*** ametts has quit IRC22:30
*** elmiko is now known as _elmiko22:32
*** kgriffs|afk is now known as kgriffs22:34
*** akanksha_ has quit IRC22:58
*** kgriffs is now known as kgriffs|afk23:02
*** stanchan has quit IRC23:06
*** Qiming has joined #openstack-zaqar23:41
*** boris-42 has quit IRC23:58

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