07:30:01 #startmeeting Yardstick work meeting 07:30:02 Meeting started Mon Aug 17 07:30:01 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:11 #info Ana Cunha 07:30:20 hello everyone 07:30:43 hello 07:30:48 #info Kristian Hunt 07:30:49 please type your name 07:30:59 #info QiLiang 07:31:02 #info gao liang 07:31:06 #info Patrick 07:31:21 #info Jingwen Hou 07:31:37 #topic Jira 07:31:54 #info new test cases added to the tasks 07:32:13 YARDSTICK-112 --Investigate what tool to use for measuring packet delay variation; 07:32:22 #info suggestion to use netperf for packet delay variation 07:32:23 yes, i have some question on new jira 07:32:25 which tool will be selected? 07:32:41 1)show the changes of delay in testing process 07:32:43 i agree. 07:32:51 2)count the average delay of testing process 07:32:52 any objections to use netperf as you suggested? 07:33:02 yes 07:33:24 can we use netperf for 1) and 2)? 07:33:43 this tool count the average delay of testing process 07:34:28 do we agree to use netperf for 1), everyone object? 07:35:02 sorry, 2), my fault in typing 07:35:54 #info use netperf for average delay of testing process 07:36:03 agree to use netperf 07:36:39 more comments on Yardstick-112? 07:37:26 Dose it just to measure average delay? 07:38:38 what to use to show the changes of delay in testing process ? 07:38:54 Jingwen, any ideas? 07:39:22 i have no idea 07:39:46 may be we can investigate it after meeting 07:40:04 kubi: agree 07:40:23 agree 07:41:09 ok, move on. on Jira, any more questions ? 07:41:17 could you give more description on "YARDSTICK-115 Investigate method for memory availability" 07:41:27 what will be measured? it will be a performance test or reliability test? 07:41:39 this is a perfomance case? 07:42:54 i will add more details, not menat for performance 07:43:21 #action anac1 to add info/details in JARDSTICK-115 07:43:29 ok,thanks 07:44:06 after i add the details, let me know if it is not clear enough. 07:44:18 ok 07:45:11 i've clarified YARDSTICK-27 is not implemented 07:45:32 by the way ,which tools will be used in YARDSTICK-116 and YARDSTICK-117? 07:46:18 the same as the Processor availability, I think this Jira(YARDSTICK-117) is also not clear enough. Can we add some details? 07:46:19 need to check if perf will give what we need 07:46:38 ok, thank you, ana 07:46:42 #action anac1 to add details/info in YARDSTICK-117 07:47:20 i will add more test cases during this week, hope to add the clarifications too 07:48:30 anac1 what does multiple instances means in yardstick-27 ? 07:48:42 i've seen the question on YARDSTICK-26, i will answer 07:48:50 VMs? 07:48:51 QiLiang, multiple VMs 07:49:07 ok, thanks 07:49:22 ok, moving on. 07:49:50 #info test case to be added in cooperation with KVM project 07:50:21 i will add a task for adding cyclictest, kvm project need to specify the test case details 07:50:45 we'll communicate in the mailing list 07:51:42 Jingwen, i will conact you for the demo details, i need a few lines of text for the agenda 07:52:21 #topic other frameworks 07:52:26 Is it necessary to show the demo in 3+2 HA environment? 07:52:54 I start five VMs on one physical machine to simulate 3+2 HA environment, then install yardstick 07:53:00 Jingwen, not at this demo 07:53:29 can you manage for thursday? 07:54:33 i am not sure i can attend this weekly meeting 07:54:51 #info design meeting with VSPERF meeting will be on Auugst 31, UTC 14h00 07:55:06 Jingwen, can anyone else help? 07:55:31 if i can't , liangqi will instead of me 07:55:54 Jingwen, ok - i'll contact you for details. 07:56:01 if i can't , liangqi will instead of me 07:56:19 ok 07:56:42 #info as preparation for the design meeting, attend VSPERF demo on 27th August, thursday meeting, if possible 07:57:09 ok 07:57:23 ok 07:58:50 general question: do we need a longer meeting, or maybe a second meeting during the week - or it this current set up enough? 08:00:22 it think second meeting during this week is a good choice 08:00:38 i think 08:00:41 a second meeting 08:00:46 sounds great 08:00:55 ok, i will set up a doodle poll for weekday/time 08:01:29 #action anac1 to set up a doodle poll for second meeting slot 08:01:38 that's all for today, thanks everyone 08:01:47 #endmeeting