08:29:19 <kubi> #startmeeting Yardstick work meeting
08:29:19 <collabot> Meeting started Thu Jul 21 08:29:19 2016 UTC.  The chair is kubi. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:29:19 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:29:19 <collabot> The meeting name has been set to 'yardstick_work_meeting'
08:29:34 <kubi> #topic call role
08:29:38 <kubi> #info Kubi
08:29:57 <Jing> #info Jing
08:30:05 <Kanglin> #info Kanglin
08:30:06 <Mingjiang5> #info Mingjiang
08:30:37 <songnon> #info songnon
08:30:53 <Yaoguang_Wang> #info Yaoguang
08:31:15 <kubi> #topic test suite evolution
08:32:36 <Mingjiang5> the new suite.yaml base on scenario is on-line
08:33:19 <kubi> Mingjiang5: great, so we change the test suite from per pod to per scenario now
08:33:21 <Mingjiang5> i've checked the latest ci, it has already been effected.
08:33:33 <kubi> Mingjiang5: great work
08:33:53 <zhihui_wu> #info zhihui
08:34:28 <LiHuan> #info LiHuan
08:34:36 <kubi> I guess you could give us a short demo for new test suite later
08:35:23 <kubi> and Ruijing Guo will give us a short demo about fuel -plugin yardstick later
08:35:48 <kubi> so, I guess you could show the demo in one GTM meeting.
08:36:17 <kubi> #info  the new suite.yaml base on scenario is on-line, yardstick change the test suite from per pod to per scenario now
08:36:27 <songnon> looking forward to the demos
08:37:16 <kubi> songnon: yes, I will organize it as soon as possible
08:37:24 <Mingjiang5> kubi: ok, i can also draft a simple guide for everybody to know about it
08:37:34 <kubi> Mingjiang5: thanks
08:37:43 <songnon> kubi: great
08:37:55 <kubi> #topic HA testing
08:38:18 <kubi> Kanglin: LiHuan: any news from your side?
08:39:18 <Kanglin> tc053(ha_tc006) have been submitted, and tc054(ha_tc007)will be submitted in recent days if there's no problem
08:39:59 <Kanglin> that means test cases on priority 2 will be finished soon
08:40:10 <kubi> Kanglin: that's great
08:41:07 <kubi> I guess we will create Colorado Branch at Aug 15th.
08:41:47 <kubi> So, after that point, only bug fix patch will be allowed to merged.
08:42:03 <Mingjiang5> Kanglin: great work
08:42:16 <Jing> great
08:42:21 <kubi> #topic DPDK testing
08:42:24 <Kanglin> we'll try to finish all before August
08:42:29 <qiujuan> #info qiujuan
08:42:57 <kubi> zhihui_wu: How about latency testing of DPDK testing?
08:44:08 <Mingjiang5> Kanglin: i think you can now start to pick some ha test cases and add them into the ci_suite to run in ci.
08:44:15 <zhihui_wu> Bad news. The pktgen-dpdk's developer told me that  the Lua side of using the Latency is not completed only the command line.
08:45:14 <kubi> zhihui_wu: do they have plan to support it?
08:45:34 <zhihui_wu> without lua api, the benchmank bash script is difficult to be written.
08:46:23 <zhihui_wu> I ask it today and wait for his reply
08:46:52 <kubi> zhihui_wu: thanks, please let us know if you get his reply.
08:47:04 <zhihui_wu> I finish 80% of Yardstick-233. but I blocks here.
08:47:44 <Kanglin> MIngjiang5: Got it, I'll do it later.
08:47:57 <kubi> zhihui_wu: One suggestion is  you can upload your code, but don't run it in with CI.
08:48:26 <kubi> zhihui_wu: so you could fix it soon if they support the lua api
08:48:53 <zhihui_wu> ok.
08:49:23 <kubi> zhihui_wu: thanks
08:49:36 <kubi> #topic release trouble shooting
08:50:03 <zhihui_wu> Just mentioned. Mingjiang told me there is no work on Yardstick-289.
08:50:04 <Mingjiang5> Kanglin: great, if you need any help, please let me know.
08:50:30 <kubi> I created a etherpad page for release trouble shooting.  Please feel free to comment it
08:50:33 <kubi> #link https://etherpad.opnfv.org/p/yardstick_release_c_troubleshooting
08:51:23 <kubi> zhihui_wu: Yes,  Mingjiang5 said yardstick already support parse the task args
08:52:01 <kubi> zhihui_wu: in test suite
08:53:09 <Mingjiang5> kubi: how to update the etherpad if i found a bug or any other problem?
08:53:14 <kubi> Thanks to songnon to fix a bug about nodes
08:54:22 <songnon> :)
08:54:27 <Mingjiang5> kubi: does it means that i should submit a jira of bug and mark it in the etherpad?
08:54:58 <kubi> Mingjiang5: Yes, that will be great. you can create a jira task and upload a patch to fix it.
08:56:02 <kubi> Mingjiang5: the purpose is to set up teams responsible for release
08:56:26 <kubi> Mingjiang5: and document known faults
08:57:05 <kubi> add info here to avoid duplicates
08:57:33 <kubi> #topic storperf integration
08:57:47 <kubi> Yaoguang_Wang: Jing: any update?
08:59:10 <Jing> I have some confuse on the storperf benchmark results, I am contacting mark to solve it.
08:59:51 <kubi> Jing: OK. did you setup storperf via yardstick now?
09:00:54 <Yaoguang_Wang> kubi: storperf plugin installation is okay. i will add the automatic admin-rc script
09:02:15 <kubi> Yaoguang_Wang: great
09:02:20 <kubi> Thanks
09:02:54 <Yaoguang_Wang> Actually we have benchmark results in devstack env. However, it did not output benchmark results in local POD.
09:02:58 <kubi> #info storperf plugin installation is okay. but there are some confuse on the storperf benchmark results
09:03:47 <Yaoguang_Wang> Expect Mark's help :)
09:03:55 <kubi> Yaoguang_Wang: Ok
09:04:29 <kubi> Yaoguang_Wang: please keep contract with Mark.
09:04:40 <Yaoguang_Wang> okay
09:04:49 <kubi> #topic document
09:04:56 <kalyan_> hi kubi
09:05:00 <kalyan_> hi all
09:05:16 <kubi> kalyan_: hi
09:05:44 <kubi> we should start our document work for new test cases now.
09:05:58 <kubi> what you need to do for a new test case includeds 4 steps
09:06:07 <kubi> 1. add a new opnfv_TC0XX.yaml
09:06:19 <kubi> 2. add a description file of test case .rst file
09:06:27 <kubi> 3. add the new TC into test suite to make it run with CI
09:06:35 <kubi> 4. create a new page for your test case at Grafana
09:07:40 <kubi> kalyan_: go head if you want to share something with us
09:08:00 <kalyan_> cyclictest through yardstick is working fine..
09:08:09 <kalyan_> thanks alot for your help
09:08:11 <kalyan_> :)
09:08:31 <kubi> kalyan_: you are welcome
09:09:10 <kubi> kalyan_: that will be better if you could help us to improve cyclictest test cases document
09:09:51 <kalyan_> sure, i will
09:09:59 <kubi> kalyan_: thanks
09:11:41 <kubi> #topic others
09:11:49 <kubi> anything else?
09:12:21 <kubi> ok, thanks all for todya
09:12:23 <kubi> today
09:12:27 <kubi> #endmeeting