16:00:05 #startmeeting Performance Team 16:00:06 Meeting started Tue Feb 23 16:00:05 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:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:10 The meeting name has been set to 'performance_team' 16:00:14 o/ 16:00:36 I think this time we won't have too many people presented dues to Russian holidays 16:00:45 o/ 16:01:01 so some updates from several people I'll try to give myself 16:01:04 gokrokve o/ 16:01:19 Last time most of participants were from US :-) 16:01:31 gokrokve that's true as well :) 16:01:47 let's wait for a few minutes 16:01:57 What do we have in the agenda? 16:01:59 Sure 16:02:21 gokrokve we have standard agenda for today 16:02:31 Test plans statuses 16:02:31 Status of Huawei lab 16:02:31 OSProfiler weekly update 16:02:36 Last week there was an e-mail discussion about DVR testing. 16:02:53 gokrokve interesting - may you please find the link to it? 16:02:58 IT will be great if we discuss a place to share these test results. 16:03:48 http://lists.openstack.org/pipermail/openstack-dev/2016-February/086933.html 16:03:51 my personal feeling is that performance-docs is a good enough place for that, but sadly I missed this thread 16:03:52 ack 16:04:42 gokrokve ok, so about this specific thread 16:04:56 these are folks from DragonFlow 16:05:10 and they'll share their results through performance-docs 16:05:31 but they wonder if there were published any DVR tests results simply to have something to compare with 16:06:03 gokrokve as you remember we wanted to ask our internal QA performance team to give us their 8.0 results 16:06:05 and use them 16:06:10 anyway 16:06:22 #action DinaBelova answer to http://lists.openstack.org/pipermail/openstack-dev/2016-February/086933.html 16:06:30 gokrokve thanks! 16:06:43 ok, so let's go back to the agenda 16:07:10 last time we had very quick meeting due to the lack of people, so no action items observed 16:07:25 so let's jump to the next section 16:07:25 #topic Test plans statuses 16:08:16 the short update from mirantis part of the team will be the following: we have DB testing in progress, MQ tests are under automation for now 16:08:36 and we have preparation work going on on the Mirantis-Intel lab 16:09:17 Ilya Sh. has demonstrated me how his automatization tool https://review.openstack.org/#/c/275092/ will work 16:09:44 pretty impressive - it allows automate both tests run and results collection 16:10:15 the last our decision was to abandon this patch and move the tool to the separated repo 16:10:35 cool 16:10:50 We definetely need this automation to make sure results are repeatable 16:10:50 I'll ask him to prepare short demo of what this tool will be used for, and share with wider audience 16:10:57 gokrokve indeed 16:10:57 nice 16:11:13 so he has shown me the DB testing automation 16:11:17 very interesting 16:12:01 we have discussed several technical things, so he has the idea of what needs to be implemented now to make the performa working for all our cases 16:12:24 #action ilyashakhat share small demo about performa with community 16:13:02 so that's all news for now from mirantis part of the team 16:13:06 any comments? 16:13:31 nope 16:13:58 ok, so let's jump to the next section 16:14:00 I am thinking about Nova scheduler testing with Fake drivers 16:14:24 gokrokve ok, do you want to share some details? 16:14:37 SpamapS mentioned that this method he used in his testing. 16:14:40 SpamapS was doing the similar effort 16:14:53 gokrokve indeed 16:14:56 Just wonder if it is possible to publish tests and results 16:15:01 SpamapS btw are you around? 16:15:16 To enable openstack developers and nova team specifically 16:15:45 2 weeks ago you mentioned you did not have sharable results, did something change from that time? 16:15:51 I think we can reproduce this quite easily but I don't want to hijack this work from others :-) 16:16:03 gokrokve indeed 16:16:26 last time we had lots of people presented, SpamapS mentioned that he did not have sharable results yet 16:16:36 and last time we did not have many people around 16:16:49 it looks like SpamapS is out of laptop now 16:17:07 #action DinaBelova check with SpamapS the status of hi stesting 16:17:21 gokrokve thanks for reminding 16:17:42 #topic Huawei lab status 16:17:47 kun_huang o/ 16:17:51 are you around? 16:18:47 due to the previous estimations Huawei lab should become available either very soon or already 16:18:59 btw 16:19:05 #link https://review.openstack.org/#/c/280843/1/doc/source/labs/huawei_lab.rst 16:19:29 kun_huang has published some draft about their lab, but I set -1 with several comments 16:20:05 so in short: right now it's too vague description of the HW that will be used in fact 16:20:19 #action kun_huang update https://review.openstack.org/#/c/280843/1/doc/source/labs/huawei_lab.rst 16:20:50 it looks like it is too late for kun_huang and he won't be able to answer lab-specific questions 16:21:03 so I'll ping him separately from the meeting 16:21:23 I'm mobile right now, laptop in 30 16:22:05 SpamapS ack - so can you please share the current status of your testing once you'll be able to 16:22:06 thanks 16:22:22 Been redirected into another area for the moment, I hope to be able to publish my perf work in a few weeks 16:23:10 SpamapS: we can split this effort by the way to two steps: publishing the methodology of fake driver testing and example of specific test plan / results you did 16:23:45 SpamapS I think this will be very helpful - as lots of Nova developers are thinking about how to use fake driver for such testing processes 16:24:53 ok, cool 16:25:01 thanks for sharing the news 16:26:05 ok, so let's go forward 16:26:21 #topic OSProfiler weekly update 16:26:47 last week several bug fixes were landed 16:27:08 including the one, that will enable Neutron testing 16:27:35 and I think this will fix neutron gates results for the neutron change as well 16:27:49 boris-42 promised to cut the release on Friday 16:28:18 it looks like this was done 16:28:22 #link https://github.com/openstack/osprofiler/tree/1.1.0/osprofiler 16:28:39 so I'll need to check if the requirements changes were merged 16:28:56 if yes, I'll update all needed commits 16:29:25 also interesting fact 16:30:00 I was pinged by several girls, that would like to take part in OPW program 16:30:30 so right now we're going through what they want to do in terms of the topics I proposed 16:31:00 so there is on dev and docs-related work that can be done for our team 16:31:17 so let's see if they are going to be chosen and continue the effort 16:31:42 any questions regarding osprofiler? 16:32:18 ack 16:32:20 #topic Open Discussion 16:32:41 gokrokve do you have something else to raise on the meeting? 16:34:35 ok, it looks like nope 16:34:38 #endmeeting