08:30:23 #startmeeting Yardstick work meeting 08:30:23 Meeting started Mon Jun 6 08:30:23 2016 UTC. The chair is kubi. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:30:23 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:30:23 The meeting name has been set to 'yardstick_work_meeting' 08:30:32 #info Kubi 08:30:38 #info qiujuan 08:30:42 #info Jing 08:31:00 #info Kanglin 08:31:11 #info QiLiang 08:32:30 #topic HA Testing 08:32:55 qiujuan: Kanglin: i got a great reply from HA team. 08:33:02 thanks for your great work 08:33:50 kubi: Thank you :) 08:34:11 HA team invite you to atttend next HA meeting at Jun 15th. 08:35:02 We'll attend it 08:35:08 that's great 08:35:28 #info Kanglin and qiu juan will attend next HA meeting at Jun 15th. 08:36:27 what's status of HA enhanced framework evolution? 08:37:23 kubi,I have finished the first sub task 08:37:40 qiujuan: well done 08:37:59 please let us know if you need some support from yardstick team 08:38:16 OK,thank you 08:38:55 #info HA enhanced framework evolution first sub task has been finished 08:39:05 #topic copyright information 08:40:44 i want to clarify that the original copyright information should not be changed 08:41:06 #info Jun Li 08:41:27 additions can be made for relevant code changes 08:41:42 kubi: agree 08:42:04 got it 08:42:08 #info please keep in mind that original copyright information should not be changed 08:42:57 kubi:agree 08:43:05 One more thing, qiujuan Kanglin and goutham , they should be individual contributors 08:43:43 goutham: i'm not sure whether your company is member of opnfv 08:44:48 if not, you will be individual contributors and will not represent any company. 08:45:24 so, your copyright infomation should be your name and email address. 08:45:46 #topic code review 08:45:53 yep that's a good way to find the right person to talk... 08:46:30 #link https://gerrit.opnfv.org/gerrit/#/c/14687/ 08:46:53 here is MatthewLi 's patch, please feel free to give comments 08:46:58 and #link https://gerrit.opnfv.org/gerrit/#/c/15193/ 08:47:02 :) 08:47:07 MatthewLi: yes, thanks 08:48:16 ok kubi 08:48:33 goutham: thanks 08:48:45 #topic JIRA Status 08:48:48 will confirm you on this soon 08:49:04 goutham: did you have JIRA account? 08:49:43 no kubi 08:50:07 as off now i dont have a jira account .. 08:50:18 you can apply Linux Foundation account 08:50:25 that will be work 08:51:30 is there any other jira status want to update? 08:52:11 #topic OPNFV Summit 08:52:23 please let us know if any of you will attend Berlin Summit. 08:52:35 I will be there :0 08:52:38 :) 08:52:56 me too. 08:53:08 great. anyone else? 08:54:09 #info MatthewLi, jing and Kubi will attend Berlin Summit. 08:54:41 i have book a yardstick breakout session at Design Summit. let 's meet up there 08:54:57 :) 08:55:20 see you there. 08:55:46 #link https://wiki.opnfv.org/display/EVNT/Berlin+Design+Summit+Project+Breakouts+and+Hacking 08:55:59 #topic others 08:56:07 hi all...i am able to run cyclictests through yardstick..is there any way to trigger cyclictests for kvmfornfv ? as a part of ci.... 08:57:14 ok kubi i will do that 08:57:34 qiliang27: i remembered that cyclictest need a specific pod, isn't it? 08:58:20 cyclictest is different form other test cases 08:58:20 we didn't make it as a OPNFV test case, it only located on sample/cyclictest.yaml 08:59:29 kvmfornfv project try to integrate with installer in release 08:59:58 qiliang27: in Rel B?? 09:00:09 cyclictest need some update in release c 09:00:18 release c 09:00:25 qiliang27: OK 09:00:30 current code is for release b 09:00:41 and need a specific pod to test 09:01:05 kalyan: what 's your idea? 09:01:33 and just a prototye test for kvm4nfv project 09:01:47 Actually we are running yardstick cyclictests manually.... 09:02:43 bt we want to trigger this directly if any changes made in kvmfornfv 09:03:09 As of now we are running these testcases locally in our lab.. 09:03:40 then u can link the pod to community jenkins? may this can help u #link https://git.opnfv.org/cgit/octopus/tree/docs/octopus_docs/opnfv-jenkins-slave-connection.rst 09:03:59 qiliang27: i guess this need to write JJB in releng to trigger yardstick testing 09:04:28 kubi: yes 09:04:28 MatthewLi: you are CI expert. please give some ideas 09:05:17 kubi: first thing is what installer are u integrated with kalyan, second to connect your pod to community jenkins 09:05:31 third to trigger the job 09:05:39 kalyan: did test need whole opnfv openstack installation ? 09:05:40 MatthewLi: thanks 09:06:05 qiliang27: yep that's also I want to ask 09:07:06 To install kvmfornfv we used the build script we cloned.. 09:07:35 kalyan: how did you run cyclictest in you lab? 09:07:45 this is actually without openstack till now... 09:08:13 almost the same as in rel b? 09:08:36 then you need a specific pod connect to community ci 09:08:47 kalyan: then u can do such as what storperf do now 09:08:48 and write some jjb 09:08:56 qiliang27: agree 09:09:01 installed kvmfornfv through build script..then installed yardstick and ran cyclictests.... 09:09:34 one cyclictest is with openstack setup... 09:10:19 cyclictest.yaml .. 09:10:54 cyclictest-node-context.yaml ...this is without openstack.. 09:11:00 kalyan: yes 09:12:11 kalyan: so which one did you use ? 09:12:23 after your pod connect to community ci , you can creat a test suite for your pod. then, use jjb to trigger it 09:13:02 i guess he perfer to node-context.yaml 09:13:14 i have tried both...but currently i am going with cyclictest-node-context.yaml without opnstack 09:14:27 ok, cyclictest.yaml doesn't work for with latest code. 09:14:57 qiliang27: MatthewLi: thanks for your answers 09:15:17 MatthewLi: thanks alot :) 09:15:24 #link https://git.opnfv.org/cgit/releng/tree/jjb/kvmfornfv/kvmfornfv.yml 09:15:34 kalyan: we can discuss it for more details via email 09:15:39 kalyan: we can talk more 09:15:41 yep 09:16:03 kubi : yes..sure.. 09:16:18 #email matthew.lijun@huawei.com 09:16:28 kalyan: thanks for your great question 09:16:37 kubi & quiliang : thanks a lot :) 09:16:54 One more thing 09:16:56 #info due to chinese Dragon Boat Festival, this Thursday meeting will be canceled. 09:17:05 :) 09:17:11 matthewli: done.. 09:17:22 have a happy vacation:) 09:17:28 :) 09:17:39 kalyan: liangqi1@huawei.com 09:17:47 thanks all for today. 09:17:54 #endmeeting