Monday, 2015-04-27

*** OneLostSoul has joined #openstack-zaqar00:10
OneLostSoulflwang, will OpenStack run under OpenStack ?00:16
*** sriram has quit IRC00:25
*** kgriffs|afk is now known as kgriffs01:02
*** achanda has joined #openstack-zaqar01:09
*** kgriffs is now known as kgriffs|afk01:12
*** sebasmagri has quit IRC01:20
*** sebasmagri has joined #openstack-zaqar01:23
*** akanksha has quit IRC01:37
*** achanda has quit IRC02:02
*** amitgandhinz has joined #openstack-zaqar02:09
*** amitgandhinz has quit IRC02:17
*** amitgandhinz has joined #openstack-zaqar02:18
*** amitgandhinz has quit IRC02:25
*** amitgandhinz has joined #openstack-zaqar02:26
*** amitgandhinz has quit IRC02:28
*** kgriffs|afk is now known as kgriffs02:51
*** kgriffs is now known as kgriffs|afk03:01
*** exploreshaifali has joined #openstack-zaqar04:09
*** davideagnello has joined #openstack-zaqar04:24
*** davideagnello has quit IRC04:28
*** kgriffs|afk is now known as kgriffs04:40
*** kgriffs is now known as kgriffs|afk04:49
*** OneLostSoul has quit IRC05:03
*** exploreshaifali has quit IRC05:14
*** achanda has joined #openstack-zaqar05:39
*** cpallares has joined #openstack-zaqar05:44
*** cpallares1 has joined #openstack-zaqar05:45
*** cpallares1 has quit IRC05:48
*** kgriffs|afk is now known as kgriffs06:28
*** kgriffs is now known as kgriffs|afk06:38
*** dynarro has joined #openstack-zaqar06:56
therveHello08:06
therveIt's a bit strange to have both the tests/ and the zaqarclient/tests directory in the client08:06
therveIs it expected? Is one replacing the other?08:06
*** openstackstatus has joined #openstack-zaqar08:07
*** ChanServ sets mode: +v openstackstatus08:07
*** exploreshaifali has joined #openstack-zaqar08:07
-openstackstatus- NOTICE: Restarting gerrit because it stopped sending events (ETA 15 mins)08:10
therveIt looks like tests in zaqarclient/tests are not the ones that are actually run?08:13
*** openstackgerrit has quit IRC08:13
*** achanda has quit IRC08:16
*** openstackgerrit has joined #openstack-zaqar08:16
*** kgriffs|afk is now known as kgriffs08:17
therveHum yeah files are not named appropriately in zaqarclient/tests08:17
*** kgriffs is now known as kgriffs|afk08:27
*** achanda has joined #openstack-zaqar08:59
*** dynarro has quit IRC09:23
*** chandankumar has joined #openstack-zaqar09:32
flaper87therve: zaqarclient/tests contains the base clases that `tests/` inherit from09:35
therveflaper87, Why, though?09:35
flaper87it's like that because packagers normally strip tests out and we still want to ship the base clases so that other's can inherit from there when implementing their own transports09:35
therveNot a single project has a top level tests/ directory, afaik09:36
flaper87we do :)09:37
therveRight, but packagers still package other projects. Anyway09:37
therveThe main issue I saw is that you have classes like QueuesV1_1QueueFunctionalTest which end up not being instantiated09:38
flaper87sure, but it's not a rule that it has to be the way we do it. There are different opinions w.r.t where tests should live09:38
flaper87Yeah, we've a bug tracking a refactor to our tests09:38
flaper87so we can reduce confusion and duplication09:38
flaper87We might end up merging everything in a single tests package09:38
therveI'd strongly advocate doing that09:38
flaper87some more context here: http://blog.flaper87.com/post/test-concepts-and-python/09:39
flaper87brb09:39
thervePackagers I know want to test projects when creating packages. Not sure how striping the tests out help.09:42
therveBut! That's cosmetic, I guess I understand how it works now.09:43
therveThe main question I have now is how we can make the client works with 1.109:44
*** achanda has quit IRC09:55
*** achanda has joined #openstack-zaqar10:00
*** kgriffs|afk is now known as kgriffs10:06
*** achanda has quit IRC10:11
*** kgriffs is now known as kgriffs|afk10:16
*** flwang1 has joined #openstack-zaqar10:27
flwang1vkmc: flaper87: ping10:27
flwang1morning10:28
flwang1or evening10:28
vkmcmorning flwang1!10:56
flwang1vkmc: just wanna confirm the meeting time10:56
flwang1did you get a chance to catch flaper87?10:56
vkmcflwang1, not really... he might be around later though10:57
vkmcflaper87, flaper87, flaper8710:57
flwang1vkmc: ok, no worries10:58
flaper87o/10:58
vkmcoh, he is like candyman :)10:59
flaper87I don't think I'll be able to join tomorrow at that time. Lets try to use our meeting times for this meeting. What do you think?10:59
flaper87Also, before we meet to discuss what's next, we need to work on sessions ideas. We've 2 session's slots to fill and many things to do11:00
flaper87I'm working on a plan for the summit that I'll be sharing this week11:00
flwang1flaper87: i think i have 1 hour from now on11:00
flwang1btw, in case vkmc missed, i can't join the summit :(11:00
flaper87AFAIR, the meeting topic was "Let's discuss next steps"11:01
flaper87right?11:01
flwang1so i'd like to get some thoughts before the summit and will catch with you after the summit again11:01
flaper87I don't think we're ready to discuss that yet. For instance, we ought to review carefully the replies we got on that last Zaqar thread11:01
flaper87Then we need to review carefully our gate status and client status11:02
flaper87therve has been working with the client and facing some issues11:02
flwang1flaper87: no matter what it's, i just think we need get our weekly meeting back and start to plan something and do it11:02
flaper87those are kind of expected since we've been focusing on the server11:02
flaper87flwang1: yes, that we're going to do11:02
flaper87but after the summit11:02
vkmcflaper87, maybe we could have a short meeting before the summit?11:03
vkmcconsidering flwang1 won't be able to come11:03
flaper87I agree, I didn't say we are not going to have one11:03
flaper87I said that we should review this material before we do11:03
flaper87basically, I'm asking to move this meeting to next week11:04
flwang1flaper87: i'm monitoring that thread11:04
vkmcok, that sounds great then11:04
flwang1and now i'm a fan of Zane Bitter11:04
flaper87I'll schedule it, don't worry.11:04
flaper87We'll have to use our channel11:04
flaper87and we'll restore the meetings after the summit11:04
vkmcwe could focus this week to catch up on things11:04
vkmclet's set up an etherpad so we don't forget things11:05
flaper87we need to fix the gate, test the client, file bugs and fix them. There's a bit of house cleaning to do11:05
flwang1vkmc: <311:05
flaper87vkmc: I've one11:05
flwang1flaper87: yep, the gate of client is always failed11:05
flaper87I haven't shared it because I'm still working on it a bit11:05
flaper87and I just got back11:05
flwang1but unfortunately, i can't recreate it locally11:06
vkmcflaper87, ok, we wait for it then :)11:06
flaper87cool, you'll both hear back from me11:06
flaper87brb11:06
flwang1vkmc: can you reproduce the client failure?11:21
*** chandankumar has quit IRC11:22
vkmcflwang1, the ones pointed out by therve? yes11:22
flwang1vkmc: https://review.openstack.org/#/q/status:open+project:openstack/python-zaqarclient,n,z11:23
openstackgerritFei Long Wang proposed openstack/zaqar: Fix duplicated test cases of notifier  https://review.openstack.org/17771611:24
flwang1vkmc: i'm talking this one, check-zaqarclient-dsvm-functional11:26
flwang1this gate is always failed now11:26
flwang1but I can't reproduce it11:27
*** chandankumar has joined #openstack-zaqar11:35
vkmcflwang1, I have to finish some stuff in trove side, I'll come back to you later if I can reproduce those11:41
flwang1vkmc: sure, thanks11:41
*** kgriffs|afk is now known as kgriffs11:55
*** akanksha has joined #openstack-zaqar11:55
therveflwang, Those failures are easy, I think11:58
therveThe zaqar server is just not setup correctly11:58
therveI can reproduce it on a fresh devstack, at least11:59
*** exploreshaifali has quit IRC12:01
*** chandankumar has quit IRC12:03
flwang1therve: cool, never install zaqar with devstack :)12:04
flaper87flwang1: sshh, that's not a good thing to say when we have a gate set up12:04
flwang1therve: so how did you reproduce that?12:04
flaper87flwang1: or did you mean that you've never done that ?12:04
*** kgriffs is now known as kgriffs|afk12:04
flwang1flaper87: i always run zaqar directly instead of devstack12:05
flwang1flaper87: sorry for the confusing12:05
therveflwang, Well I installed zaqar in devstack, and then run the functional tests12:06
*** openstackgerrit has quit IRC12:06
flwang1therve: ah, ok, i will try12:06
*** openstackgerrit has joined #openstack-zaqar12:06
therveflaper87, So what can I do to help fixing those issues with 1.1 on the client?12:07
therveFWIW I'm working on https://blueprints.launchpad.net/heat/+spec/software-config-zaqar and it's somewhat blocking me12:07
*** chandankumar has joined #openstack-zaqar12:18
flaper87therve: I'm currently heads down on fixing the client gate. We need to enable pools in devstack but we first need to move devstack's scripts into Zaqar's codebase12:20
flaper87A series of patches12:20
* therve nods12:20
flaper87therve: that said, pls, send as many patches as you can/want to help us bringing it up to speed12:20
flaper87we need to fix v1.1 and add support for v212:20
flaper87If you really want to help with that then I'd probably say that adding support for v2 would be amazing12:21
flwang1flaper87: please let me know if I can help12:21
therveWell, working on v2 while v1.1 doesn't work seems counterproductive :)12:22
therveI thought the devstack scrips were moved a week ago already12:23
flaper87therve: the reason I'm asking is because I might be able to fix v1.1 quickier than it would take me to implement v2 and we need both12:23
flaper87therve: did that patch land ?12:23
therveflaper87, 6 days ago AFAICT12:23
flaper87you are correct12:24
flaper87so, next patch is change devstack12:24
flaper87we are almost there12:24
flaper87therve: another thing, since you brought the tests thing up, I'd be more than happy if you'd show up with a patch that merges those packages and improves our story there12:24
flaper87:D12:24
* flaper87 drops that bomb there12:24
therveflaper87, So, the issue is that if you merge them, they fail :)12:25
therveWe'd need a strategy12:25
* flaper87 is all ears12:26
therveWe can skip the ones that fail12:27
therveAnd then fix them one by one12:27
therveOr first make them pass, and do the merge afterwards12:27
therveThe difficult part is fixing them anyway, the merge part is easy :)12:31
flwang1therve: pls feel free let's know what we can do12:32
therveI'd rather push the merge for now, I'm more interested in fixing bugs12:34
therveThe real first step is fixing the gate, though12:34
flwang1therve: yep12:34
flwang1i think flaper87 is working on that12:34
flwang1i have to offline now12:34
*** openstackgerrit has quit IRC12:37
*** openstackgerrit has joined #openstack-zaqar12:37
*** sriram has joined #openstack-zaqar13:11
therveSo I may be going down the rabbit hole, but13:12
therveIs it expected that GET /v1.1/queues/doesnotexist return a 200?13:12
therveIt seems to be the storage default behavior13:12
sriramyeah, thats seems right.13:13
sriramtherve: it is perceived that a queue always exists.13:13
sriramtry to post a message to a non-exisiting queue, queue gets created and message posted.13:13
thervesriram, So queue.exists doesn't make sense anymore for 1.1?13:13
sriramfollows a lazy-create policy.13:13
sriramtherve: its abstracted from the user, but the storage level code requires it for actually looking if such a thing exists in the DB.13:14
sriramI havent been doing any active devevlopment, for a long time now. things could have changed :)13:15
thervesriram, Right, but the user-facing client API is still there13:15
sriramping vkmc or flaper87 when they get back in..13:15
therveThanks for the infos :)13:16
sriramtherve: you are right, its debatable that it could be removed.13:16
sriramsince its an abstraction anyway13:16
*** openstackgerrit has quit IRC13:21
*** openstackgerrit has joined #openstack-zaqar13:22
*** chandankumar has quit IRC13:32
*** kgriffs|afk is now known as kgriffs13:40
*** exploreshaifali has joined #openstack-zaqar13:45
*** dynarro has joined #openstack-zaqar13:47
-openstackstatus- NOTICE: gerrit has been restarted to clear a problem with its event stream. change events between 13:09 and 13:36 utc should be rechecked or have approval votes reapplied as needed to trigger jobs13:48
*** mpanetta has joined #openstack-zaqar13:48
*** kgriffs is now known as kgriffs|afk13:50
*** ametts has joined #openstack-zaqar13:54
*** amitgandhinz has joined #openstack-zaqar13:57
*** kgriffs|afk is now known as kgriffs13:59
*** exploreshaifali has quit IRC14:06
*** kgriffs is now known as kgriffs|afk14:08
*** achanda has joined #openstack-zaqar14:33
openstackgerritThomas Herve proposed openstack/python-zaqarclient: Fix handling of 1.1 API  https://review.openstack.org/17779214:36
therveflaper87, ^^^14:36
*** achanda has quit IRC14:41
*** kgriffs|afk is now known as kgriffs14:42
*** davideagnello has joined #openstack-zaqar15:09
*** davideagnello has quit IRC15:13
*** chandankumar has joined #openstack-zaqar15:41
*** chandankumar has quit IRC16:19
*** dynarro has quit IRC16:36
*** davideagnello has joined #openstack-zaqar17:05
*** exploreshaifali has joined #openstack-zaqar17:10
*** exploreshaifali has quit IRC17:20
*** achanda has joined #openstack-zaqar17:20
*** chandankumar has joined #openstack-zaqar17:48
*** flwang1 has quit IRC18:03
*** davideagnello has quit IRC18:10
*** davideagnello has joined #openstack-zaqar18:12
*** exploreshaifali has joined #openstack-zaqar18:30
*** davideagnello has quit IRC19:04
*** davideagnello has joined #openstack-zaqar19:06
*** dguerri is now known as _dguerri19:11
*** _dguerri is now known as dguerri19:17
*** chandankumar has quit IRC19:26
*** ametts has quit IRC19:27
*** dguerri is now known as _dguerri19:32
*** exploreshaifali has quit IRC19:39
*** exploreshaifali has joined #openstack-zaqar19:41
*** akanksha has left #openstack-zaqar19:44
*** _dguerri is now known as dguerri20:20
*** exploreshaifali has quit IRC20:22
*** sriram has quit IRC20:23
*** dguerri is now known as _dguerri20:39
*** _dguerri is now known as dguerri20:39
*** flwang1 has joined #openstack-zaqar21:22
*** mpanetta has quit IRC21:54
*** amitgandhinz has quit IRC22:07
*** kgriffs is now known as kgriffs|afk22:48

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