07:30:02 #startmeeting Yardstick work meeting 07:30:02 Meeting started Mon Sep 21 07:30:02 2015 UTC. The chair is anac1. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:30:02 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:30:02 The meeting name has been set to 'yardstick_work_meeting' 07:30:09 #info Ana Cunha 07:30:20 hi everyone 07:30:28 #info QiLiang 07:30:35 #info gao liang 07:30:45 #info Yimin Wang 07:30:49 #info Patrick 07:30:49 #info Kristian Hunt 07:30:53 #topic New yardstick project member 07:31:18 #info Yimin Wang has joined yardstick project 07:31:21 welcome! 07:31:22 welcome!!! 07:31:23 welcome! 07:31:27 welcome! 07:31:28 welcome! 07:31:30 Hi, everyone 07:31:46 thx 07:31:53 #topic bugs 07:31:54 #info Jingwen Hou 07:32:14 welcome Yimin 07:32:16 #info progress on yardstick-142 07:32:39 #info progress on yardstick-143 07:33:28 yardstick-143 ,the fix code is already committ to gerrit 07:33:46 #info yardstick-143 on-going, code to be pushed 07:33:53 thanks jingwen! 07:34:14 #action anac to follow up yardstick-142 07:34:20 you are welcome 07:34:26 #topic cooperation with ha 07:34:51 should we have an sw architecture meeting to discuss the framework? 07:35:11 agree 07:35:22 patrik? 07:35:25 agree too 07:35:47 ok, i'll plan for next week, ok? 07:36:00 ok for me 07:36:03 sure, thank you. 07:36:20 #action anac to call for a sw architecture meeting next week, to evolve yardstick framework 07:36:47 #topic cooperation with vsperf 07:37:05 #info follow up meeting planned for september 30th 07:37:10 we can discuss in etherpad about this issue synchronously 07:37:21 #action anac to call for meeting with vsperf 07:37:27 patrick1: yes, agree 07:38:06 #topic release-b planning 07:38:26 #info test projects will receive requests for test cases until september 25th 07:39:01 test cases cannot update after 9.25 ? 07:39:40 we want the other projects to inform us if they need help by sept 25th 07:40:14 this means, for example, project "x" needs yardstick help with test cases 07:40:35 got it 07:40:40 we can change the test cases after, also add our own (initiated by the yardstick team) 07:41:05 i think after we know who needs help from us it is easier to discuss the architecture 07:41:27 totally agree. 07:41:30 +1 07:42:25 #info yardstick will add one test case from odl 07:42:43 this was discussed last thursday, on test&performance meeting 07:43:00 together with cperf team? 07:43:11 yes 07:43:41 we agreed to reuse one test case to start with, performance-related 07:43:56 when i get the details sorted out, i will write a jira task 07:44:04 ok. good. 07:44:18 probably we will get help from cperf or sfc team 07:44:33 that would be helpful. 07:44:54 yes, for all of us, it think 07:45:21 #topic cyclictest 07:45:32 #info suggestion added in yardstick-122 07:46:08 kvm project is analysing, they will comment 07:46:25 i see 07:46:47 qiliang: any new comments? 07:47:59 agree with jorgen, and there some little question latter i will add on yardstick_ha etherpad for discussing 07:48:19 great, thanks ! 07:48:47 #action all to check etherpad yardstick_ha and add comments/ideas/questions 07:49:04 #topic support for centOS 07:49:30 #info troubleshooting on-going, jorgen working on this 07:50:52 #topic jenkins jobs 07:51:27 #info yardstick will have daily and weekly jobs 07:51:55 yardstick-147 created to help identify what test cases/samples to run when 07:53:16 i saw the functional tests, thanks ! 07:53:31 :) 07:53:56 kubi: well done! 07:54:00 If we want to speed up the total time when we execute samples in CI, maybe some test case's durations will be changed to shorter. 07:54:53 hi,Ana.I already execute all the testcases below /yardstick/sample. 07:55:04 patrick, agree, we need to find out which ones (a subset) to run daily and still get a good view on the platform 07:55:23 wuzhihui: did you measure how long time it took? 07:55:25 but there are some testcase executed failed. 07:55:27 +1 07:55:53 which testcase? 07:55:56 wizhihui: write comments on jira and the rest of us will help 07:55:58 maybe you can email the failed log and we can see and fix it 07:56:18 testcase iperf and ping-ext-ip 07:56:52 i need some help 07:56:58 ping-ext-ip is becasue of the Chinese network i think 07:57:11 iperf 07:57:42 becase ssh failed,SSHException('not a valid EC private key file 07:58:12 wuzhihui: please add the problems as comments in yardstick-147, we will try to reproduce the fault in other labs 07:58:21 ok 07:58:25 thank you 07:58:26 thanks ! 07:58:36 Ana, because Oct.1~7 is the traditional national holiday in China. so the chinese guys will not attend the yardstick weekly meetings in this durations. 07:59:01 ok, i will cancel oct 1st meeting 07:59:07 what holiday is it? 07:59:12 and I am not sure whether all of us can attend to the Sep.30 meeting since some guys maybe leave office ahead of the holiday. 07:59:16 nationnal day 07:59:24 National Day 07:59:34 ok, i will propose another date for sept 30 07:59:49 thx 08:00:10 #action anac to replan the meetings on sept 30 and oct 1st 08:00:23 thanks everyone, that's all for today 08:00:27 #endmeeting