16:00:14 #startmeeting Performance Team 16:00:14 Meeting started Tue Mar 1 16:00:14 2016 UTC and is due to finish in 60 minutes. The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:17 The meeting name has been set to 'performance_team' 16:00:24 o/ 16:00:33 folks, let's wait for a few minutes 16:00:53 to see if ilyashakhat will be able to join 16:01:39 ilyashakhat rohanion o/ 16:01:57 hi! 16:02:01 hi everyone 16:02:21 ok, so let's have some minutes to see if somebody else will join 16:02:41 we have standard agenda for today 16:02:43 #link https://wiki.openstack.org/wiki/Meetings/Performance#Agenda_for_next_meeting 16:04:03 #topic Action Items 16:04:13 ok, so going through previous week action items 16:04:20 #link http://eavesdrop.openstack.org/meetings/performance_team/2016/performance_team.2016-02-23-16.00.html 16:04:54 so in fact gokrokve answered that email thread I as going to 16:05:20 in short: we're going to publish DVR vs non-DVR openstack topology Rally results to performance-docs 16:05:48 Yep. I plan to do RST doc this week 16:06:03 right now we have groomed results for MOS 7.0 (kilo), and non-groomed for MOS 8.0 (liberty) 16:06:05 I never did this before so it will take a little bit longer 16:06:21 gokrokve did you talk to our QA team about liberty results? 16:06:33 Nope. I will do this today 16:06:51 gokrokve ack, I just wonder if they started work on grooming already 16:07:11 I've seen runs, but have no idea if they somehow made them structured 16:07:20 ok, cool 16:07:52 it looks like kun_huang was not able to go through his action item about https://review.openstack.org/#/c/280843/1/doc/source/labs/huawei_lab.rst 16:08:04 so let's keep it open till next meeting 16:08:13 #action kun_huang update https://review.openstack.org/#/c/280843/1/doc/source/labs/huawei_lab.rst 16:09:05 and about SpamapS testing - last time he joined us at the end of meeting and shared that he was distracted a bit from that task 16:09:30 SpamapS - btw, were you able to continue your work on that nova testing we discussed? 16:10:47 ok, it looks like this time slot is not comfortable for SpamapS at all :) probably I'll need to have two times for this meeting - maximum PST friendly and maximum Europe/China friendly 16:11:08 gokrokve, ilyashakhat, rohanion - what do you think about it btw? 16:11:23 I support this 16:11:36 fine for me 16:11:40 and I support the one for EU :) 16:11:49 This time is particularly hard as this is kids drop to school time 16:12:22 #action DinaBelova propose to have to times for this meeting to openstack-dev - US and Europe/China friendly and switch them on weekly basis 16:12:26 ok, cool 16:12:38 so it looks like we went through all our action item 16:12:42 items* 16:12:49 Let's proceed 16:12:51 #topic Test plans statuses 16:13:07 ok, so today ilyashakhat and rohanion have joined us 16:13:42 and we may ask them to share the status of DB / MQ testing we at Mirantis currently are working on 16:13:50 ilyashakhat - will you start? 16:15:10 we've updated MQ test plan and going to use OMsimulator as primary tool 16:16:14 ilyashakhat afaik you are using your new tool performa for this testing 16:16:23 DinaBelova: yep 16:16:28 were you able to add add public docs to share? 16:16:36 a moment 16:18:18 the new tool is called Performa and it is targeted to simplify test execution and report generation 16:18:39 some very-very short words are published at http://performa.readthedocs.org/en/latest/ 16:18:57 #link http://performa.readthedocs.org/en/latest/ 16:19:21 ilyashakhat thanks! 16:19:24 the repo with the code is still in my private github (https://github.com/shakhat/performa) 16:19:45 so right now it'll support MQ and DB test plans we've shared already, afaik 16:20:01 yep, but the work is in progress 16:20:03 ilyashakhat do you think we can move it to openstack space before next meeting? 16:20:08 ilyashakhat sure 16:20:24 I suppose we should do this 16:20:39 #action ilyashakhat move Performa to openstack space 16:20:46 ok, cool 16:21:13 I also have a sample for the report - http://docs-draft.openstack.org/14/286614/1/check/gate-performance-docs-docs/f8862d3//doc/build/html/test_results/mq/omsimulator/index.html 16:21:14 rohanion is working right now on testing ZeroMQ as a oslo.messaging backend for OpenStack 16:21:29 #link http://docs-draft.openstack.org/14/286614/1/check/gate-performance-docs-docs/f8862d3//doc/build/html/test_results/mq/omsimulator/index.html 16:21:38 ilyashakhat thank you sir! 16:22:06 you;re welcome :) 16:22:19 there gonna be more news soon! 16:22:24 cool! 16:22:31 rohanion the floor is yours :) 16:22:39 hm 16:23:00 rohanion on what scale are you testing it right now and with what OpenStack? 16:24:17 I use OpenStack Liberty deployed with Fuel 8.0 on a 200-node environment 16:25:16 I've finished measuring the number of used sockets and the results are not very fabulous 16:25:37 ok, any examples? 16:25:41 sure 16:26:16 here's the number of used sockets on 3 controller nodes with 197 compute nodes running as slaves 16:26:31 10.20.0.27: 32057 16:26:33 10.20.0.22: 31899 16:26:35 10.20.0.28: 33490 16:26:46 hehehe 16:26:53 and what about computes? 16:27:01 currently we won't make it to 2000 node scale 16:27:01 something average for them? 16:27:09 a minute 16:27:13 rohanion obviously yes :D 16:27:40 btw am i right it's liberty OpenStack but oslo.messaging is mitaka? 16:27:46 no 16:27:53 oslo.messaging is liberty too 16:28:12 hm, so no modifications to zeromq driver? 16:28:12 it's a patched version with backported mitaka features 16:28:20 ah, I got it 16:28:38 the average number of sockets on compute nodes is approximately 540 16:29:02 rohanion ok, so it looks like the bottleneck is for controllers, that was expected 16:29:15 rohanion dims - any ideas on how to workaround this? 16:29:54 probably we'll try to use horizontal scaled proxies to minimize the number of connections 16:30:08 but it will significantly affect the overall performance 16:30:09 rohanion : let's invite ozamiatin here 16:30:22 agree 16:31:03 ok, let's wait him to join 16:31:04 apparently he's out of office rn 16:31:21 heh, very sad 16:31:34 ok, so let's make sure you'll find the way to workaround it 16:31:57 we'll brainstorm it tomorrow, yes 16:32:20 #action rohanion share ideas on how to workaround the fact that ZeroMQ eats too many sockets on OpenStack controller nodes 16:32:32 so we'll go back to this topic next time 16:32:36 fine 16:32:47 ok, so let's proceed 16:33:13 I'll skip Huawei lab status this time again as kun_huang is away 16:33:20 #topic OSProfiler weekly update 16:33:50 so obviously last week we were fixing bugs in profiler and I tried to keep all osprofiler related changes up to date 16:34:17 some of them (like updataing heat to use consolidated in profiler options) were merged 16:35:04 as for others, there was a stupid issue in openstack client 16:35:21 I've introduced with the integration patch 16:35:38 #link https://launchpad.net/bugs/1551160 16:35:38 Launchpad bug 1551160 in python-openstackclient "interactive openstack console: run_subcommand() takes exactly 2 arguments (1 given)" [Undecided,Fix released] - Assigned to Dina Belova (dbelova) 16:35:44 so it was fixed today 16:35:57 I'm going to focus on keystone change in nearest future 16:36:07 #link https://review.openstack.org/#/c/103368/ 16:36:21 and try to understand what's going on with failing jobs 16:36:30 in fact I have no idea yet what's going on 16:36:50 logs are vague :( 16:37:48 and I'm going to fix https://review.openstack.org/278155 and https://review.openstack.org/278157 as well, as they can still be merged to mitaka 16:38:16 as that's not a feature in fact, just switching to other options place and that's it 16:38:46 so that's all from my side for now 16:39:04 it looks like boris-42 is not here, so we may close this topic as well 16:39:28 #topic Open Discussion 16:39:43 gokrokve ilyashakhat rohanion dims - anything else to share? 16:39:59 DinaBelova : none from me 16:40:15 nope 16:41:07 hm 16:41:32 ok, cool 16:41:37 so let's finish then 16:41:41 thanks everyone! 16:41:46 #endmeeting