08:30:05 #startmeeting Yardstick Work Meeting 08:30:05 Meeting started Mon Aug 22 08:30:05 2016 UTC. The chair is kubi001. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:30:05 Useful Commands: #action #agreed #help #info #idea #link #topic. 08:30:05 The meeting name has been set to 'yardstick_work_meeting' 08:30:39 #topic roll call 08:30:42 #info kubi 08:30:46 #info Jing 08:30:49 #info Mingjiang 08:31:00 #info Kanglin 08:32:51 #topic stable branch 08:33:55 I have sent the request to helpdesk, yardstick will branch the stable branch with Commit ID:27e254c2273e4be503053db882948b8abf53b269 08:34:21 #info Yardstick has sent the stable branch request. 08:34:53 I mean It is the head of yardstick master at now 08:36:42 any question about this? 08:37:01 #topic CI Job status 08:37:25 Mingjiang1: could you share the status of compass verify job 08:38:45 for yardstick, i think there's no bugs discovered by compass scenario. 08:38:50 for now 08:39:21 what 's status of each compass scenario? 08:39:36 still there has some problem in scenario os-onos-sfc-ha, os-ocl-nofeature-ha. 08:40:14 #link https://wiki.opnfv.org/display/yardstick/Yardstick+Colorado+CI+Status 08:40:35 but it failed before yardstick test case start 08:40:37 Mingjiang1: pleasehelp to fill this table 08:40:50 Mingjiang1: Ok, I see, Thanks 08:41:06 yes, i will update it 08:41:51 #info there still has some problem in scenario os-onos-sfc-ha, os-ocl-nofeature-ha which occured before yardstick test case starting 08:42:08 Jing: How about fuel? 08:42:13 two scenarios exceed the 180 mins time limit, I am working on analyse the cause, but probably not caused by yardstick. 08:42:40 for the stable branch, after colorado is generated, what's the difference for our work, can you please introduce to us? 08:44:05 Mingjiang1: good question, After branching the stable branch, we need to cherry pick the patch to stable branch if your patch needed to be merged in the stable branch. 08:44:47 and only bugfix and documentation will be allow to cherry pick to the stable branch. 08:45:01 #info qiujuan 08:45:33 and also some patch such as Arm pod will be allowed. 08:46:13 Mingjiang1: Is it clear? any further question? 08:46:46 Jing: thanks for your work, please let us know if you find the root cause of timeout. 08:46:55 sure 08:47:08 so you mean, after the colorado is generated, we still work on the master, and cherry pick only bugfix, docs and special change into the colorado, right? 08:47:10 #info two scenarios exceed the 180 mins time limit for fuel verify job 08:48:00 Mingjiang1: yes, correct 08:48:33 Jing: which sceanario were timeout? 08:49:20 onos-sfc-ha onos-nofeature-ha 08:49:35 kubi001: i see, thanks. 08:49:49 #info two scenarios are onos-sfc-ha onos-nofeature-ha 08:51:06 #topic yardstick introduce and new feature demo 08:52:23 I 'd like to organize a GTM to let some active developers to give a yardstick introduce for new contributors 08:53:35 Mingjiang1: could you share some idea about yardstick framework and test suite evolution with our team. 08:54:06 you mean in the gtm, right? 08:54:29 Mingjiang1: yes, give a presentation at gotomeeting 08:55:04 when would that be? I may need some time to prepare for it 08:56:01 I'm not sure if this thurday meeting is ok for you? 08:56:51 I will to attend Huawei Connect conference at next Thursday 08:57:21 i think it's better if you can put it on next monday. 08:58:20 It seem that only few contributors will attend monday meeting. most of them only attend Thursday meeting. I guess. 08:58:43 Ok, I will try to contact other contributors to find a good time slot 08:59:06 Let's discuss more detail via email 09:00:12 kubi001: ok, if i can make it this thursday, i'll let you know. thanks. 09:00:53 Mingjiang1: great 09:01:05 #topic others 09:01:13 anything else? 09:01:28 Thanks for today. 09:01:34 #endmeeting