07:30:05 #startmeeting Yardstick work meeting 07:30:05 Meeting started Mon Oct 19 07:30:05 2015 UTC. The chair is anac1. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:30:05 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:30:05 The meeting name has been set to 'yardstick_work_meeting' 07:30:14 #info Ana Cunha 07:30:27 #info QiLiang 07:30:28 #info Kristian Hunt 07:30:58 #topic Jira 07:31:22 #info anything more to do on yardstick-100? 07:31:38 no 07:31:50 #info Jingwen Hou 07:32:03 #agreed anac1 to close yardstick-100 07:32:09 #info Rex Lee 07:32:13 #topic OPNFV community labs 07:32:35 #info there was a discussion last thursday on test&performance meeting 07:32:45 #link https://wiki.opnfv.org/feature_test_project_matrix 07:33:03 #info a tale was added in testing wiki, see link above 07:33:25 i have added info for yardstick, double check, please 07:33:43 ok 07:34:36 we have jira for vnffg 07:34:54 ok, i will add, thanks 07:35:51 #info release b testing will need to use other community labs in addition to LF 07:37:08 any questions? 07:37:28 ok, i get it 07:38:05 ok, we need to define the pod.yaml to get going 07:39:13 fdegir: you around? 07:39:22 I wrote down some thoughts on how this might work… https://spirent.box.com/s/gt37aq9orqc18i3p1ujfz9aq3vcj18tc 07:39:59 jnon: have you started looking in pod.yaml 07:40:22 #info need to start specificiation for pod.yaml 07:40:22 not started 07:40:27 ok 07:40:41 #topic test case template 07:41:29 #info 2 versions exist for test case template 07:41:51 what the general opinion ? i prefer v2. 07:42:33 I think the template using table structure looks cleaner 07:42:47 yes, that's the v2 07:42:55 +1 for v2 07:43:14 anyone disagree to remove the previous version and use v2 ? 07:43:43 +1 for v2 07:43:55 #agreed use template v2 for test case specification 07:44:11 +1 v2 07:44:20 #info patrick 07:44:22 #topic test result api 07:44:24 sorry for late 07:44:33 no problem 07:44:33 +1 for v2 07:44:45 ok, v2 seems to be the consensus 07:45:04 #action anac1 to remove previous template version from gerrit 07:45:47 v2 +1 07:45:54 any news on test result api ? 07:46:01 i saw morgan's patch 07:46:15 yes? 07:46:31 it seems that functest2dashboard need commit to releng 07:46:54 ok, you informed morgan, right? 07:47:07 https://jira.opnfv.org/browse/RELENG-45 07:47:12 not yet 07:47:38 will inform morgan later after meeting 07:47:49 ok, thanks 07:47:56 this morning there is some problem with my computer 07:48:11 #info functest2dashboard need commit to releng 07:48:29 qiliang: understand 07:48:57 #topic framework architecture 07:49:13 #link https://etherpad.opnfv.org/p/yardstick_framework 07:49:36 ana, i have a question about V2.: should we put the the meaning of options of the scenarios into the TC description? or just let the option description into the docstring of scenario, and give the link into the tc description? I wonder the beginner cannot write the whole test case when read this scenario's rst. 07:49:41 #info use the link above for adding comments 07:50:24 patrick1: yes, i saw your comment. i think we should put the options too, to help the beginners 07:50:39 great:) 07:51:05 i will update with your comment 07:51:05 doe we have to describe all options in TC ?? 07:52:18 it's better to give the link of docstring , because the docstring will include the options mean and related link in each scenario's py. 07:52:39 I think only options relevant for the TC should be described in TC description !? 07:53:27 that's right. 07:54:02 so, we mean describe the options that we use in the TC, right? 07:54:56 we just describe the options we use. 07:55:27 ok, we write a few examples and review, i add general info in the template 07:55:55 ok 07:56:10 nice 07:56:25 #action tc001 and tc002 examples using the v2 template, including options we use, for review next meeting 07:57:05 or other tcxxx 07:57:19 #topic meeting time 07:57:45 we in europe will change to winter time from next weekend 07:57:59 can we move this meeting (and thursday) 1 hour later? 07:58:11 ana, kubi cannot attend this meeting, but he comment that the ut coverage more strictly. YARDSTICK-108 07:58:28 he send the email last week 07:58:32 yes, i saw his e-mail 07:59:28 i agree, anyone has an opinon? 07:59:43 opinion 08:00:10 I think it will influence everyone, so maybe we will make a vote for 4 line limitation. 08:01:05 after kubi's patch merger it will be hard to update existed code 08:01:34 we need add a lot ut now 08:01:36 looks like we need time to think, vote next meeting? 08:01:45 ok 08:01:57 yes, maybe we will finish some technical debt 08:01:59 ok 08:02:23 #action all the check kubi's e-mail about 4 line limitation, vite next meeting thursday 08:02:47 hi, ana, about yardstick -172 "sla check of scenarios", i have submit code to gerrit 08:03:23 https://gerrit.opnfv.org/gerrit/#/c/2615/ 08:03:30 for yardstick-172 08:03:45 i will check 172 08:03:59 #action all to comment on yardstick-172 08:04:00 jnon: thank you 08:04:08 thanks 08:04:13 #link https://gerrit.opnfv.org/gerrit/#/c/2615/ 08:04:39 #action discuss yardstick-172 next meeting 08:04:47 jnon also help review heat context refactor patch :) 08:05:03 jnon: that's another one for you 08:05:10 yes i will :) 08:05:18 ana, I have heard there is a joint meeting on the OPNFV summit with HA team? 08:05:20 #action review heat context refactor patch 08:05:43 patrick1: you mean the breakout session? 08:05:49 yes 08:06:32 i saw the agenda from Fuqiao. 08:07:07 that's open for everyone, here's the link https://etherpad.opnfv.org/p/OPNFV_Design_Summit_2015 08:07:30 i hope we will have a chance to discuss face to face 08:07:54 that would be greate 08:07:56 great 08:08:14 projects will also have presentations, see: https://etherpad.opnfv.org/p/OPNFV_Summit_demo_theater 08:08:53 ok, that's all for today, thanks for your time ! 08:08:58 #endmeeting