08:30:11 <anac1> #startmeeting Yardstick work meeting
08:30:11 <collabot> Meeting started Mon Feb  1 08:30:11 2016 UTC.  The chair is anac1. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:30:11 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:30:11 <collabot> The meeting name has been set to 'yardstick_work_meeting'
08:30:17 <anac1> #info Ana Cunha
08:30:21 <chenshuai1> #info chenshuai
08:30:32 <kubi1> #info kubi
08:30:39 <patrick1> #info patrick
08:30:57 <anac1> #topic Release-B
08:31:11 <patrick1> anac1: Qiliang was out of office these days.
08:31:31 <anac1> #info we are now on code freeze - bug fixes and documentation can continue
08:31:36 <anac1> patrick1: thanks
08:31:38 <patrick1> anac1: for his wedding
08:32:14 <anac1> patrick1: great news, my congratulations for him !
08:32:40 <anac1> #info development for release-C can go on master branch
08:32:49 <patrick1> anac1: :)
08:32:56 <andrasb> #info andrasb
08:33:19 <anac1> patrick1: how long will he be away ? whole week ? next week is spring festival?
08:33:42 <chenshuai1> he will be back on this Thursday in China time
08:33:44 <patrick1> anac1: he will be back on Feb. 4
08:34:00 <anac1> #topic ODL scenario failure
08:34:55 <anac1> thanks, i'll send hm an e-mail with congratulations, happy time !
08:34:57 <patrick1> anac1: Yes, next week is spring festival. so guys in China may not go to work.
08:35:20 <anac1> ok, let's fix the odl problem this week
08:36:58 <patrick1> hope so
08:37:05 <anac1> #info recap on odl scenario problem: the patch 8143 didn't work on the POD
08:37:12 <anac1> jnon: any news?
08:37:37 <jnon1> no news
08:37:44 <chenshuai1> anac1: is this tickets to remove secgroup?
08:38:08 <anac1> chenshuai1: yes, but it didn't work - so it is reverted
08:38:08 <chenshuai1> jnon1:  is this tickets to remove secgroup?
08:38:31 <chenshuai1> anac1: could we try to use default secgroup ?
08:38:45 <anac1> chenshuai1: we did
08:38:59 <jnon1> the patch was to use default secgroup
08:39:28 <jnon1> it worked perfectly on the virtual pod but not on the bare metal ones
08:40:04 <anac1> has anyone tried to run yardstick only, or before functest, on odl scenario ?
08:40:58 <chenshuai1> anac1: qiliang tried yardstick on compass with me , but it's on the virtual pod
08:41:20 <anac1> according to tim rozet's mail in mailing list,  " If it is not an issue with your configuration, then it is possible that this is a reprocussion of running functest before yardstick in CI.  We had issues in Arno where running pieces of functest would leave the system rendered in an unusable state due to sync issues between ODL DB and Neutron DB from resource creation/deletion.  "
08:41:33 <anac1> chenshuai1: did it work on virtual ?
08:41:55 <chenshuai1> anac1: if use default secgroup, it's working
08:42:25 <anac1> chenshuai1: same as for jnon, try on baremetal ?
08:42:32 <jnon1> chensuai1: same for me, worked with default group
08:42:45 <chenshuai1> anac1: yes, we are preparing baremetal pods
08:42:48 <anac1> jnon1: but not on baremetal, right ?
08:42:58 <chenshuai1> anac1: not tried yet
08:43:27 <anac1> chenshuai1: when you try on baremetal, could you also execute once before functest ? or yardstick only ?
08:43:45 <anac1> chenshuai1: just to check if there is any impact
08:43:51 <chenshuai1> anac1: yardstick only i think
08:44:07 <anac1> chenshuai1: ok, thanks
08:44:13 <chenshuai1> anac1: ok, we can do the whole procedure also
08:44:21 <anac1> ok, thanks
08:44:43 <anac1> jnon: what's the plan for fule odl scenario ?
08:44:49 <anac1> fuel*
08:45:48 <anac1> as lf pod2 and ericsson pod2 are under upgrade to fuel 8, we have to wait until it's done ?
08:46:31 <jnon1> plan is to test troubleshoot and test again with fuel8, there is a new odl version beryllium
08:46:57 <chenshuai1> jnon1: is beryllium issued officially?
08:47:27 <jnon1> chensuai1: i dont know
08:47:46 <chenshuai1> jnon1: ok, thanks
08:47:58 <anac1> chenshuai1: it is delivered in fuel8
08:48:20 <chenshuai1> anac1: ok
08:48:46 <patrick1> now in huawei lab, we have got several BM pods recently,  we will make them work asap, then for yardstick testing and troubleshooting.
08:49:18 <anac1> patrick1: great, we need bm and the fuel pods are not available for troubleshooting yet
08:49:58 <anac1> #info same odl fault on fuel, compass, apex and joid
08:50:06 <patrick1> anac1: ok. let's move on.
08:50:21 <anac1> patrick1: ik
08:50:23 <anac1> ok
08:50:33 <anac1> #topic documentation
08:50:47 <jnon1> and i was told that odl lithium does not support icmp rules in secgroup
08:51:32 <anac1> #info in-going work to fix autodoc for the code docstrings
08:51:36 <anac1> #undo
08:51:36 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1e01f90>
08:51:49 <anac1> #info on-going work to fix autodoc for the code docstrings
08:52:16 <anac1> #topic other
08:52:42 <anac1> #info sfc test case merged last friday - needs to be tested
08:54:10 <anac1> #info patch pushed to help  yardstick-226
08:54:34 <anac1> anyone wants to add something?
08:56:05 <anac1> #info 4 consecutive runs for the test cases are required for release testing
08:56:31 <anac1> #info for each scenario
08:57:10 <anac1> #info anac1 will start cleaning up commiters list for inactive commiters
08:57:13 <kubi1> what's "consecutive" mean /
08:57:38 <anac1> means in a row, 4 times success runs
08:57:39 <kubi1> four times for one ci task?
08:58:21 <anac1> 4if we run one per day, it means 4 days without interruptions
08:58:27 <kubi1> ok
08:58:31 <kubi1> thank you
08:58:35 <anac1> np
08:59:03 <kubi1> parser is weekly task
08:59:47 <anac1> ok, parser, like ha, is not necessary to run daily - i'll document in the release notes
08:59:56 <kubi1> ok
09:00:44 <anac1> i'll try to push release notes draft soon, so we can all add those details there and make sure all is properly documented
09:00:58 <anac1> so we don't miss something
09:01:24 <patrick1> great.
09:01:29 <kubi1> :)
09:01:54 <anac1> thanks all for today
09:01:57 <anac1> #endmeeting