08:34:15 <kubi001> #startmeeting Yardstick Work Meeting 08:34:15 <collabot> Meeting started Thu Aug 18 08:34:15 2016 UTC. The chair is kubi001. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:34:15 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic. 08:34:15 <collabot> The meeting name has been set to 'yardstick_work_meeting' 08:34:27 <kubi001> #topic roll call 08:34:32 <kubi001> #info kubi 08:34:36 <Mingjiang1> #info Mingjiang 08:34:43 <Kanglin_> #info Kanglin 08:34:43 <QiuJuan> #info qiujuan 08:34:44 <TapioT> #info Tapio Tallgren 08:34:50 <henrikN> #info henrikN 08:35:00 <mywulin> #info mywulin 08:35:17 <kubi001> hi, TapioT and henrikN 08:35:19 <Jing> #info Jing 08:35:28 <TapioT> Hello 08:35:28 <henrikN> hi kubi 08:35:46 <kubi001> henrikN: nice to see you again. :) 08:36:07 <kubi001> #topic release status 08:36:16 <henrikN> kubi001: thanks, good to be back 08:36:50 <kubi001> Mingjiang1: could you share the status of compass CI job 08:38:05 <Mingjiang1> #link https://build.opnfv.org/ci/view/yardstick/job/yardstick-compass-baremetal-daily-master/ 08:39:00 <Mingjiang1> for baremetal in huawei-pod1 there's a bug about storpef in nosdn-nofeature, lvjing has fix it and propose the patch 08:39:58 <Mingjiang1> #link https://build.opnfv.org/ci/view/yardstick/job/yardstick-compass-virtual-daily-master/ 08:40:07 <kubi001> #info there is still a bug of storpef-integration test case, Jing post a patch to fix it 08:40:10 <Mingjiang1> for virtual ci, the status is good 08:40:57 <kubi001> and I saw there are several failure scenario for baremetal pod. 08:41:37 <kubi001> such as os-onos-nofeature 08:41:51 <kubi001> Mingjiang1: you get the root cause of those scenario? 08:42:03 <kubi001> did you 08:42:44 <Mingjiang1> for onos, it seems not from yardstick 08:43:30 <Mingjiang1> i'm still working with onos people to discover it locally 08:43:31 <kubi001> Mingjiang1: ok, so we need to clear up the bug from yardstick side before we checkout the stable branch 08:43:44 <kubi001> Mingjiang1: thanks a lot 08:44:26 <kubi001> Jing: How about the fuel CI job? 08:44:36 <Jing> kubi001: For fuel CI job, SSH failure in onos-nofeature scenario has been fixed. This scenario is passed. The onos-ovs scenario was failed yesterday, failed on TC002-ping. 08:45:09 <kubi001> #info For fuel CI job, SSH failure in onos-nofeature scenario has been fixed 08:46:02 <kubi001> Jing: so that should not be caused by Yardstick side, Yes? 08:46:09 <Jing> And I think the failure in onos-ovs is not from yardstick. 08:46:16 <kubi001> Jing: great 08:46:24 <kubi001> Jing: Thanks 08:46:45 <Jing> :-D 08:47:44 <kubi001> #info we only need to wait the storperf-integration test case result before we checkout stable branch. 08:49:08 <kubi001> #info Kubi will delay the branch date to Next Monday to check the storperf-integration test case result 08:49:54 <kubi001> #topic Yardstick Introduce for new contributors 08:50:51 <henrikN> is this perhaps the wiki page I was mentioning 08:51:49 <kubi001> henrikN: no, I shared a idea about giving a Yardstick demo for new contributors to let them easily to understand the yardstick framework 08:51:57 <henrikN> ok sounds great 08:52:22 <kubi001> henrikN: the wiki page also will be needed :) 08:52:27 <pava2> kubi001: I send some patch regarding arm64 archtecture pods for yardstick and I wanted to put you or someone else knoleageble to review 08:53:31 <kubi001> #info I have a plan to give a demo at Next Thursday for new contributors, please feel free to comment it 08:53:45 <kubi001> #topic Arm pod with Yardstick 08:54:11 <henrikN> kubi: you want comments before the demo or after the demo? if before - is it available already? 08:54:26 <kubi001> pava2: Hi, I have checked those patch, It looks good to me 08:55:21 <kubi001> henrikN: I mean, before the demo, what you want to know, what you want to discuss at that meeting 08:56:00 <kubi001> pava2: what's your plan with the Yardstick and Functest? 08:56:03 <henrikN> kubi001: ok 08:56:34 <pava2> kubi001: We need to run it for the release Colorado.1.0 for arm 08:57:09 <pava2> kubi001: I also send patch for creating hte yardstick ci job on arm-pod1 08:57:39 <pava2> kubi001: funtest is already supported from brahma 08:59:15 <kubi001> pava2: yes, I saw that patch, As we will checkout the branch soon, I think we can merge your patch to master after branching, we could cherry pick it to stable branch when that could successfully run several times at master 08:59:41 <kubi001> pava2: Is it ok for you? 09:00:14 <pava2> kubi001: as long as it get's there before the release it's great :) 09:00:27 <kubi001> pava2: sure 09:01:52 <kubi001> #info some patch regarding arm64 archtecture pods for yardstick will be merged after branching, then Kubi will cherry pick it to stable branch when that could successfully run several times at master 09:02:27 <kubi001> pava2: anything else? 09:03:24 <pava2> kubi001: probably I will need to Modify the Docker file as the yardstick docker image need some libs for crossbuilds 09:04:33 <pava2> kubi001: that's pretty much it for now 09:05:46 <kubi001> pava2: I see, do you need a new Docker file for Arm? 09:08:04 <pava2> kubi001: the jompserver uses amd64 so the docker image is ok mostly just I need to add some pakcages like qemu-user-static binfmt-support libc6:arm64 in order to make the yardsick-server-cloud image a arm64 09:08:55 <kubi001> pava2: that's OK 09:09:31 <kubi001> please upload your patch, Mingjing and Jiing, could you help to review? 09:10:09 <pava2> kubi001: ok 09:10:36 <Mingjiang1> kubi001: of course 09:11:50 <kubi001> #info It is still need to add some pakcages like qemu-user-static binfmt-support libc6:arm64 to build "yardsick-server-cloud image a arm64 " 09:12:15 <kubi001> Mingjiang1: thanks 09:12:25 <kubi001> pava2:thanks for your work. 09:12:34 <kubi001> anything else? 09:12:48 <pava2> kubi001; thaks for your help 09:12:55 <pava2> kubi001: not from me 09:13:37 <kubi001> #topic others 09:13:51 <kubi001> #info please let kubi know if some of you have any requirement about yardstick introduction 09:14:02 <kubi001> Thanks all for today 09:14:12 <kubi001> #endmeeting