14:30:11 #startmeeting Brahmaputra Daily Standup 14:30:11 Meeting started Tue Feb 9 14:30:11 2016 UTC. The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:11 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:11 The meeting name has been set to 'brahmaputra_daily_standup' 14:30:22 #link agenda https://wiki.opnfv.org/releases/brahmaputra/minutes 14:30:36 #topic roll call 14:30:41 #info chris price 14:31:11 #info Jonas will not make it today, Fuel statius 14:31:12 #info Morgan Richomme 14:31:19 #info Narinder Gupta 14:31:23 #info Ana Cunha 14:31:25 #info Jonas will not make it today, Fuel status on https://wiki.opnfv.org/fuel_opnfv/b_release_status 14:31:29 #info Uli Kleber 14:31:53 #info Heather Kirksey 14:31:54 ChrisPriceAB: thanks! 14:32:11 #info Frank Brockners 14:32:19 #info Test Status 14:32:40 Morgan_Orange: what is the latest on Functest status? 14:33:31 nothing really new since yesterday...we fixed a patch thta triggers some regression on Functest 14:33:47 and we are now analyzing the errors linked to Tempest on the different installers 14:34:26 we identified during the weekly meeting the list miles (some vPing on odl_l3 and onos scenario) + boosting Tempest results on apex, fuel and joid 14:34:30 #info Ashlee Young 14:34:57 radez - did the switch to ODL Be resolve the issue that Functest and Yardstick cannot be run in sequence? 14:35:09 #info Joe Kidder 14:35:46 frankbrockners: looks like as in joid i can see it ran for intel pod6. 14:35:53 hey guys, sry I'm late 14:36:06 welcome radez, see above :D 14:36:12 Tempest failed to run so we don't actually know if it fixed it or not 14:36:23 Vping passed on L3 ODL 14:36:27 and yardstick passed on ODL L2 14:36:31 so we got some results 14:36:40 radez: workaround for Li is removed 14:36:47 radez: yes it is fixed now 14:37:12 awesome, I'll fire off a new run then and we'll see if we can get newe results on everything 14:37:21 radez: we introduced a regression on fixing the last compass error, but it is oK now 14:37:30 Li issues are fixed? Or Be resolved the issues? 14:37:52 Be resolved them ashyoung 14:37:54 ashyoung: we're not sure yet, the tests that were killing things didn't fire last night from the functest regression 14:37:57 ashyoung: let's check the results on Be 14:38:10 #info Trevor Cooepr 14:38:11 K 14:38:15 #info Dan Radez 14:38:31 I'll run new tests as soon as I can and report when I have new results 14:38:48 narindergupta: Li workaround removed also for joid 14:39:19 anac: thanks yeah we migrate to Be yesterday and last night run was success 14:39:37 from installer prspective 14:41:25 anything more for functest or Be with the installers? 14:41:29 #info the CR to uplift from Li to Be will be on the TSC call following this. As far as I have seen the results are in favour and we have seen no issues in making the move at this time. 14:41:54 ChrisPriceAB: +1 14:42:01 :) 14:42:14 anac1: anything new on yardstick this morning? 14:43:00 have some issues with the test results server - it is working now but was unavailable earlier today 14:43:53 nothing else new 14:44:01 anac - could you check / email aricg on those issues 14:44:06 anac: did this impact collecting results from overnight runs? 14:44:24 frankbrockners: will do 14:44:32 we've seen some issues before - and aricg put up a couple of monitoring scripts to analyze the situation further 14:44:32 debrascott: yes if no server available, no results stored in the DB 14:44:46 frankbrockners: peter contacted aric on this topic 14:44:58 morgan_orange: that’s what I thought, just didn’t know when it went down 14:46:17 debrascott: but we have the results in jenkins however 14:46:37 morgan_orange: thanks 14:47:03 #topic TSC call topics 14:47:19 #link https://etherpad.opnfv.org/p/steps_to_brahmaputra scenario's for discussion on the TSc related to the release date 14:49:39 Why are there no SR plans in scenario 1? 14:49:41 #info also as above, discussion on passing the CR to uplift to BE 14:49:58 because the intention is to carry all scenario's to release. 14:50:33 What do we do if a scenario misses March 8? 14:50:45 move to C 14:51:03 #info Scenario 2 is helpful because it allows ARMband to come in before C release 14:51:56 Joekidder: How is ARMband doing toward reaching stable? 14:53:04 In scenario 1, what is the risk we don't make it? 14:53:23 (scenario 2 seems to be more safe) 14:53:29 potential for slip, but we can simply cut scope one assumes 14:53:37 debrascott - we are getting close to having bootstrap and target images...working in Fuel 8...also working loose ends in Functest against Arno in parallel 14:54:17 +1 for scenario 2:) 14:54:27 joekidder: so if you had opportunity to go out in an SR in late March likelihood is good that you would make it 14:54:55 debrascott: we hope so. Will know better in the next few days. 14:55:15 There would even be SR2 in scenario 2 14:55:30 uil-k: potentially 14:55:52 it's on the list on April 21 14:56:20 uli-k_: yes with a caviat “if needed” on the title line 14:56:40 ARM would be a reason ;-) 14:56:52 uli-k_: +1 14:57:01 ok, anything else for today? 14:57:06 TSC 14:57:18 any status on ocl integration? 14:57:44 Still working on getting Liberty working in JOID - slow progress 14:59:20 OK, lets transition to TSC. Thanks all for joining! 14:59:30 #endmeeting