08:30:06 <kubi001> #startmeeting Yardstick Work Meeting
08:30:06 <collabot> Meeting started Mon Aug 15 08:30:06 2016 UTC.  The chair is kubi001. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:30:06 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:30:06 <collabot> The meeting name has been set to 'yardstick_work_meeting'
08:30:27 <kubi001> #roll call
08:30:36 <kubi001> #topic roll call
08:30:44 <Jing___> #info Jing
08:30:46 <LiHuan> #info LiHuan
08:30:47 <kubi001> #info kubi
08:30:56 <Kanglin_> #info Kanglin
08:30:56 <TapioT> #info Tapio Tallgren
08:31:01 <Mingjiang> #info Mingjiang
08:31:46 <songnon> #info songnon
08:32:34 <kubi001> #topic release trouble shooting
08:33:20 <kubi001> Mingjiang: what's the status of compass CI job?
08:34:10 <kubi001> Jing___:  could you report the status of Fuel CI job?
08:34:20 <kubi001> Mingjiang: what's the status of compass CI job?
08:34:22 <Mingjiang> there's a bug today
08:34:28 <Mingjiang> solved
08:34:45 <kubi001> Mingjiang: great, which bug?
08:35:02 <Mingjiang> tc075
08:35:25 <kubi001> storperf test case?
08:35:31 <Mingjiang> still got one storperf problem
08:35:41 <Jing> fuel CI job failed in os-odl_l2-bgpvpn-ha and os-onos-nofeature-ha today
08:36:09 <Mingjiang> can not start storperf docker currently
08:36:40 <Mingjiang> when using plugin command
08:37:09 <kubi001> Jing___: because os-odl_l2-bgpvpn-ha can't support floating ip function,  so that scenario will failed
08:38:17 <kubi001> Jing___:    's the root cause of os-onos-nofeature-ha?
08:38:25 <kubi001> what is
08:38:26 <Jing> kubi001: so what do we need to do for os-odl_l2-bgpvpn-ha?
08:39:07 <Mingjiang1> I'm working with Jing to solve the storperf problem and fix it asap
08:39:16 <Jing> ssh fail on tc011
08:39:20 <kubi001> Mingjiang1: great
08:39:55 <kubi001> Jing: please let the scenario owner know the failure
08:40:20 <Jing> kubi001:sure.
08:40:33 <kubi001> #link https://etherpad.opnfv.org/p/yardstick_release_c_troubleshooting
08:41:10 <kubi001> please update this page when you encounter the failure and bugs
08:41:35 <Mingjiang1> kubi001: ok
08:42:18 <kubi001> #info storperf still need to troubleshooting with a issue which is yardstick can not start storperf docker currently
08:43:18 <kubi001> #info  the failure of os-onos-nofeature-ha of fuel  is  caused by ssh failure on TC011
08:43:43 <kubi001> #action Jing notice the scenario owner for above failure
08:43:57 <kubi001> Thanks Mingjiang1, Jing
08:44:27 <kubi001> zhihui_:  could share the status of yardstick ci Job which are run at zte-pod
08:45:17 <kubi001> #topic Stable Branch of Colorado
08:46:04 <kubi001> As Mingjiang said at last Thursday, We have plan to checkout the branch at this Thursday, (UTC:00)
08:46:32 <kubi001> Any suggestion about the deadline?
08:47:51 <kubi001> #info Yardstick will checkout the stable branch at this Thursday.
08:49:08 <kubi001> after that, we need to cherry pick the patch to stable branch, and only the bugfix will be allowed.
08:49:26 <kubi001> zhihui_: ping
08:49:45 <Mingjiang1> kubi001: mainly, we should make sure all the feature or testcase in colorado merged and fix the red situation, make ci turn to blue.
08:50:54 <kubi001> Mingjiang1: yes, you are right, we should clear up all the bugs which make the CI failed from yardstick side.
08:51:50 <kubi001> Mingjiang1: But, some failure may be caused by installers.
08:52:52 <kubi001> #topic documentation
08:54:53 <kubi001> the structure of  documentation for testing project will be similar with Brahmaputra
08:56:20 <kubi001> please upload the guide which already located at wiki to yardstick repo.
08:56:33 <kubi001> #topic others
08:57:00 <Mingjiang1> last time goutham
08:57:27 <Mingjiang1> has missed the meeting, seems like he has some confusion about the time
09:00:55 <zhihui_> kubi, zte-pod1 is in process of migration from nanjing to shanghai, so the deploy ci job is not successful.
09:01:59 <songnon> it looks like kubi has dropped
09:02:14 <Mingjiang1> yeah, he seems off-line
09:02:18 <zhihui_> ok
09:02:40 <Mingjiang1> zhihui_: do you know how long it'll take ?
09:02:49 <kubi001> sorry ,I was offline ,now is OK
09:03:01 <Mingjiang1> fyi: (17:00:57) zhihui_: kubi, zte-pod1 is in process of migration from nanjing to shanghai, so the deploy ci job is not successful.
09:03:14 <kubi001> zhihui_: any more patch for DPDK testing?
09:03:16 <zhihui_> On zte-pod3 with scenrio  os-nosdn-kvm-ha, yardstick is ok.
09:03:21 <kubi001> Mingjiang1: thanks
09:03:31 <kubi001> great
09:04:24 <zhihui_> Mingjinag1: maybe two days is ok.
09:05:17 <kubi001> zhihui_: cool
09:06:15 <Mingjiang1> #info zte-pod1 is in process of migration, it may take two days to be available
09:06:43 <kubi001> Mingjiang1: thanks
09:07:11 <kubi001> dut to times up. I will end this meeting
09:07:23 <kubi001> thanks for everyone
09:07:37 <kubi001> #endmeeting