21:00:48 #startmeeting Zaqar 21:00:48 Meeting started Mon Sep 15 21:00:48 2014 UTC and is due to finish in 60 minutes. The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:49 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:52 The meeting name has been set to 'zaqar' 21:00:55 #topic Roll Call 21:01:14 kgriffs: vkmc malini 21:02:05 mmh, anyone ? 21:02:09 o/ 21:02:16 vkmc: hey :D 21:02:27 looks like it'll be a chat between you and me today 21:02:28 o/ 21:02:34 flaper87, and kgriffs! :D 21:02:38 there he is 21:02:40 :D 21:02:52 * kgriffs drinks teh powerade 21:02:56 * kgriffs is ready to rock 21:03:04 ok, lets do it 21:03:10 #link https://wiki.openstack.org/wiki/Meetings/Zaqar#Agenda 21:03:19 #topic Smoke testing planning for RC (kgriffs) 21:03:27 actually, wait 21:03:30 actions 21:03:38 #topic review actions from last meeting 21:03:47 #link http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-09-08-15.00.html 21:03:54 vkmc To document where API checks should go (API or Storage layer) 21:04:04 flaper87, already in the review queue 21:04:10 vkmc: sweet 21:04:15 do you have a link? 21:04:24 https://review.openstack.org/#/c/121424/ 21:04:26 sure thing 21:04:36 #link https://review.openstack.org/#/c/121424/ 21:04:43 let me know if the location I chose is ok 21:04:50 or if it fits better somewhere else 21:04:57 sure thing, thanks vkmc 21:05:02 next action 21:05:02 np 21:05:03 flaper87 to start adding v1.1 to the client 21:05:09 #link https://review.openstack.org/#/q/status:open+project:openstack/python-zaqarclient+branch:master+topic:bp/api-v1,n,z 21:05:17 it's all up for review 21:05:36 ok, lets move on 21:05:39 yup, I'll review the ones you added earlier tonight 21:05:46 vkmc: +1 21:05:50 #topic Smoke testing planning for RC (kgriffs) 21:05:53 kgriffs: floor is yours 21:06:09 ok, so I had put that up there because I wanted to make sure the RC was rock-solid 21:06:19 one thing that doesn't get a lot of testing in pooling 21:06:52 kgriffs: +1 21:06:56 and also keystone middleware, although there shouldn't be a big issue there 21:07:04 kgriffs, +1 21:07:05 o/ sorry for the late 21:07:14 I've been meaning to setup pooling in devstack by default 21:07:20 hi flwang1 \o 21:07:31 hey guys 21:07:36 I'll try to do that next week 21:07:38 flwang1: 'sup ? 21:07:40 hi flwang1 21:07:53 #action flaper87 to make devstack use pools by default 21:08:00 I have been inspecting the errors in functional testing for pools today 21:08:05 currently we are skipping those tests 21:08:16 oh 21:08:19 I also had to add the tests for v1.0, will do that for next week 21:08:20 vkmc: +1 we need to stop skiping them 21:08:24 * flwang1 is frustrating with nova evacuate + ceph recently 21:08:45 so, let me tell you what I've been up to and we can see if there is any other RC testing we need to get done 21:08:59 * flaper87 listens 21:09:08 saturday I started setting up a new testing cluster 21:09:15 ubuntu 14.04 21:09:19 instead of deb 7 21:09:25 (since I can now get that at Rackspace) 21:09:58 so, I have one load generator, one load balancer running nginx (I didn't want to mess with haproxy right now) 21:10:13 2 web heads, although I will probably add 1-2 more 21:10:22 1 db box currently running a single redis instance 21:10:35 and then I kept the 3-member replica set for mongo because... 21:10:48 I needed a pool catalog and redis driver doesn't support that 21:10:56 so what I have now 21:11:04 is zaqar set up in a pooled configuration 21:11:17 I have been hammering it all day with lots of tests with varying load, each test run 5 minutes 21:11:44 the pool only has a single redis node in it right now 21:11:50 and I only have one web head active 21:11:58 my plan is to do another round after adding a web head 21:12:16 (up to 4) 21:12:21 all that sounds really good 21:12:29 Any numbers you can share? 21:12:38 at that point I'm thinking redis will saturate and I will add 1-3 more procs to the pool 21:13:14 sweeet 21:13:23 re smoke testing, everything looks great from the server side. Very reliable, although stdev goes high towards the end, no failed requests 21:13:33 but 21:13:59 I did have some trouble getting zaqar-bench working since the patch to remove the v1 from the import statement 21:14:13 mmmh 21:14:27 sorry about that. Any clue of what the error was about ? 21:14:27 can't remember for sure 21:14:54 It'd be weird if it's related to that but you know... software 21:14:58 but somebody should go run that with everything latest and see if it is OK. I might have reverted and put the v1 back in, and then I had to hack the claim_id param in python-zaqarclient again 21:15:13 let me see 21:15:36 #link https://git.openstack.org/cgit/openstack/python-zaqarclient/tree/zaqarclient/queues/client.py 21:15:37 wait 21:15:39 I lied 21:15:42 kgriffs: ^ that's what the client do 21:15:44 does* 21:15:45 I think that might have been a red herring 21:15:50 oh ok 21:15:52 and I did end up removing v1 module 21:16:02 but the claim_id error was still preventing me from deleting claimed messages 21:16:17 right, that has been taken care of, IIRC 21:16:19 vkmc: ^ 21:16:20 until I hacked messages.py in the client lib to accept a claim_id param in __init__ 21:16:26 I think I reviewed/approed your patch 21:16:30 vkmc: ^ 21:16:30 at least, as of saturday 21:16:40 kgriffs: yeah, I +2 on sunday 21:16:42 IIRC 21:16:43 oic 21:16:46 gtk 21:17:02 kgriffs: thanks a lot for working on all that 21:17:04 really 21:17:12 thanks 21:17:13 it's been really helpful and encouraging 21:17:46 oh, I should also mention 21:17:47 Do you think we can make that server you're using a third-party CI for benches ? 21:17:53 until we get rally going 21:17:58 I added stdev, mean, max, and 99 percentile to zaqar-bench 21:17:59 flaper87, that one depends in kgriffs patch 21:18:08 flaper87, I added the comment on Gerrit 21:18:08 vkmc: oh, mmh. 21:18:12 vkmc: ok 21:18:19 I was going to use Tsung, but it was going to be a real pain to model our scenarious so I thought it would be quicker to keep using zaqar-bench 21:18:19 I'll take a look again in a bit 21:18:20 (for now) 21:18:24 kgriffs -2 it because we didn't know the root cause 21:18:35 vkmc: yeah, TBH I haven't had time to dig into that 21:18:40 vkmc: wait, are we talking about the same patch? 21:18:45 vkmc: link? :D 21:18:46 if someone could investigate, that would be cool 21:18:48 flaper87, the claims_id one 21:19:13 #link https://review.openstack.org/#/c/120867/ 21:19:28 flaper87: vkmc's patch depends on my patch that moves deleting queues to the end of the test instead of beginning, 21:19:38 depends on 21:19:43 https://review.openstack.org/#/c/119900/1 21:19:49 ah ok, but I guess we can make it not depend on yours 21:20:03 yeah, it's just that without my patch zaqar-bench hangs everytime 21:20:05 super strange 21:20:05 sure thing 21:20:10 yeap ^ 21:20:12 at least we can move that one forward 21:20:20 yeah but the gate is not blocked on that, right? 21:20:34 no, we don't have a job that runs zaqar-bench do we? 21:20:34 at least you can pull that one from master and the bench env should work 21:20:40 without hacking the client 21:20:46 right 21:20:55 kgriffs: not yet, I'd like to add one but I don't think infra will be happy if we load the server :P 21:21:02 not sure, I should probably ask 21:21:10 IIRC that bug appeared after kgriffs fix 21:21:13 regarding numbers, I will have some graphs soon on the wiki 21:21:20 without kgriffs fix, it just enters a loop 21:21:20 but for now 21:21:28 vkmc: if you can make your patch not depend on kgriffs's we can approve it today 21:21:33 flaper87, will do 21:21:34 we'll investigate the other issue 21:21:36 keeping observers steady at 50, but increasing producers 21:21:44 we peak at about 5000 messages posted/sec 21:22:01 that is for 1 web head and the CPUs end up at about 80% 21:22:01 sweet 21:22:09 sweet sweet sweet 21:22:11 redis box is doing like 50% 21:22:19 (for one CPU) 21:22:24 web heads are 20 CPUs 21:22:34 and no fancy configs, right? 21:22:48 I don't recall what nginx was (4 workers) but probably around 50% each proc 21:23:20 flaper87: I didn't spend a ton of time tuning configs. mostly defaults I think. 21:23:29 but I will post them and you can see 21:23:29 that's even better 21:23:53 if we're doing good with default, I guess tuning them will help increasing those numbers 21:23:55 nah, we need to suck more 21:24:06 ;) 21:24:08 :P 21:24:12 ROFL 21:24:28 ok cool 21:24:37 again, kgriffs, thanks for all that work. 21:24:41 sure 21:24:44 if there are no more questions, lets move on 21:24:54 #topic Zaqar client 21:25:00 btw, it takes forever to run these, but I'll try to trickle out the results as much as possible 21:25:02 thanks kgriffs :D 21:25:12 yw 21:25:14 :D 21:25:19 * vkmc not so sad panda 21:25:30 so, very quick. I don't mean to put any preassure on anyone but we need to release the client before the 18th 21:25:39 so... 21:25:41 #link https://review.openstack.org/#/q/status:open+project:openstack/python-zaqarclient,n,z 21:25:52 also, I'm working on this: 21:25:54 #link https://review.openstack.org/#/c/120437/3 21:26:05 if you guys want to take a look it'd be cool 21:26:11 (especially malini) 21:26:14 I will review them 21:26:15 I'll let her know 21:26:36 I think all v1.1 patches are up 21:26:42 I also fixed the functional tests 21:26:50 and other things that I found on my way 21:27:05 if there's anything missing please, by all means, don't tell me 21:27:11 :P 21:27:16 jokes apart, fix it 21:27:23 now seriously, let me know :) 21:27:29 I'll happily work on that 21:27:43 any questions? otherwise let's move on 21:28:00 cool 21:28:05 #topic What had to be said has been said, I hope 21:28:40 well, you know. 2 weeks, 1 thread and a half, lots of emails, tons of comments. 2 meetings, lot of noise and mixed emotions 21:29:02 if something hasn't been said, I believe it's already becoming quite late. that said, anything could happen. 21:29:16 Our third, and last, meeting is tomorrow. 20 UTC 21:29:34 will it be the final decision? 21:29:35 Our time during the meeting will be, AFAIK, dedicated to vote 21:29:39 flwang1: yes 21:29:46 no more 3h discussions 21:29:59 few comments and then vote 21:30:20 whatever happens, I'm very proud of what we've accomplished and more importantly we'll keep doing it 21:30:32 so, thank you all and lets keep up the amazing work 21:30:44 my feeling is most like awaiting trial 21:30:52 LOOOOOL 21:30:55 +1 flwang1 21:30:56 yeah, pretty much that 21:31:00 I feel the same way 21:31:01 I mean I can't control my fate 21:31:10 you can add to that a few head bangs on the desk 21:31:25 flwang1: that sounds, you can't trust the system 21:31:27 :P 21:31:45 anyway... questions? thoughts? etc? move on? 21:31:47 flaper87: you know what I mean, man 21:31:55 flwang1: I do know ;) 21:31:58 but hey, questions regarding the design or the tools used in Zaqar has been replied 21:32:15 idk if it will make any difference, but I'll try to publish another round of perf test results before tomorrow 21:32:16 i assume there is no appeal :) 21:32:19 and the team did the best to clear things up 21:32:29 +1 kgriffs 21:32:34 kgriffs: I think it's important, yes. 21:32:40 kk 21:32:56 kgriffs: thanks for your effort, it's awesome 21:33:19 thanks man 21:33:25 * flaper87 gives kgriffs a truck full of pop-tarts 21:33:31 * flaper87 just burried kgriffs 21:33:33 muahahahaha 21:33:46 :) 21:33:48 * kgriffs puts in pantry for the zombie apocalypse 21:33:55 LOL 21:33:57 * kgriffs everyone's invited to his house 21:34:05 the pop-tart-zombie apocalypse 21:34:17 it will be scary. and delicious 21:34:17 ok, anything else? 21:34:24 ROFL 21:34:29 #topic Summit sessions submission 21:34:38 ok, heads up... again :) 21:34:45 #link https://etherpad.openstack.org/p/kilo-zaqar-summit-topics 21:35:00 put whatever you want to talk about there. There won't be a design session tool this time 21:35:12 we'll help organizing and prioritizing things ourselves using our own tools 21:35:30 I figured it'd be better to stick with the already existing etherpad so put things in that link 21:35:50 We'll start discussing those sessions in our meetings starting next week 21:36:08 ok 21:36:08 one of those proposals will be used for the next OPW mentee 21:36:11 #link https://wiki.openstack.org/wiki/OutreachProgramForWomen/Ideas#Coding 21:36:35 Zaqar has been participating in OPW for the last 2 cycles 21:36:46 I'm very proud of this and I'm super proud of our mentees 21:36:54 :D 21:37:10 I think we should keep giving back to the community and OPW is a good way to do that 21:37:30 I've put myself as a mentor but please, if you've an idea and want to mentor do not hesitate to add it 21:37:53 WE've got enough good, exiting and hard enough tasks that new mentees can work on 21:38:01 that's it from me 21:38:04 questions? 21:38:23 * kgriffs is cool 21:38:28 #topic Rally 21:39:02 we talked with boris-42 last week and he volunteered to host a hangout where he would explain us how Rally works 21:39:07 internals and whatnot 21:39:22 I contacted with him as well 21:39:25 it'd be cool if we all can participate. What time would work for you ? 21:39:41 is 21 UTC good ? (that would be this exact time) 21:39:45 i was told we just need 20 mins to get a plugin in Rally :) 21:39:56 flwang1: yeah, it looks easy 21:40:15 kgriffs: vkmc flwang1 is 21 UTC ok? 21:40:20 i'm OK 21:40:23 I'm ok too 21:40:23 I was thinking on proposing Thursday 21:40:29 when is it? 21:40:30 but TC hate simple/easy stuff 21:40:38 let me see 21:41:01 thur at 2100 should work 21:41:09 sweet, ok. 21:41:16 cool, it works for me too 21:41:33 I'll let boris-42 know (unless we woke him up with all this pings) 21:41:42 Thur, 21 UTC it is 21:42:05 he said he'd be in PST this week and the next week so, I'm sure he won't be asleep 21:42:10 * kgriffs is going to build an irc-pinger and hide it under flaper87's pillow 21:42:11 any questions? 21:42:28 * flaper87 doesn't use a pillow 21:42:32 ok, I lied 21:42:35 * kgriffs curses! foiled again. 21:42:36 I just thought that was fun 21:42:38 :P 21:43:07 * flaper87 has the weirdest sleeping pattern ever 21:43:13 anyway 21:43:17 #topic open discussion 21:43:54 please, review the client patches 21:43:56 :P 21:44:00 * flaper87 breaks the ice 21:44:04 please review the CLI patches as well 21:44:05 :p 21:44:08 ... or frozens it again 21:44:10 :P 21:44:13 vkmc: +1 21:44:23 so we have client v1.1 and CLI v1.0 21:44:37 vkmc: well, to be fair that cli works for v1.1 too 21:44:43 at least it should 21:44:46 most of it 21:44:49 * flaper87 hopes 21:44:51 :) 21:44:53 yeah :) 21:45:12 cool, that's it, folks 21:45:23 have a great rest of the day you all! 21:45:23 groovy 21:45:30 thanks Mr. Percoco 21:45:46 * flaper87 bows and says some words in a weird language 21:45:49 thanks Fla, you too! 21:45:57 #endmeeting