14:30:07 #startmeeting Brahmaputra Release Daily Standup 14:30:07 Meeting started Thu Jan 21 14:30:07 2016 UTC. The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:07 The meeting name has been set to 'brahmaputra_release_daily_standup' 14:30:29 #info Agenda https://wiki.opnfv.org/releases/brahmaputra/minutes 14:30:39 #topic roll call 14:31:17 attendees please # in 14:31:18 #info Joe Kidder 14:31:28 #info Frank Brockners 14:32:01 #info Ana Cunha 14:32:12 <[1]JonasB> #info Jonas Bjurel 14:32:59 #info Tim Rozet 14:33:18 #topic pod status 14:33:35 fdeger: are you with us? 14:34:33 #link https://wiki.opnfv.org/pharos_rls_b_labs#status_of_production_ci_resources_for_release_b 14:34:56 anyone aware of pod issues different from the wiki status? 14:35:08 #info Morgan Richomme 14:35:23 if up to date let’s move on. 14:35:45 #topic scenario status 14:36:00 anything new to add here? 14:36:10 new deployments, etc 14:36:22 debrascott: i sent you an email on our status 14:36:42 #info Apex is close to having SFC and AODH added, so sfc scenario will be working, and Doctor support will be there 14:36:44 #info Narinder Gupta 14:37:05 #info Stuart Mackie 14:37:44 trozet: good job 14:38:11 debrascott: thanks :) 14:38:13 #topic test status 14:38:37 morgran_orange: how is functest today? 14:38:54 #functest temp patch applied => functest fit again 14:39:21 Rally will create a new version on Monday, but we applied the patch in order to work 14:39:35 we force the use of a pip version < 8 14:39:41 does that mean pip working now? 14:39:48 ##undo 14:39:57 #info functest temp patch applied => functest fit again 14:40:03 #info test re-run 14:40:15 #info new vPing seems OK (tested on apex, fuel and joid) 14:40:30 #info integration functest/promise initiated 14:40:38 I will update the different table 14:41:08 morgan_orange: sounds like major improvements from yesterday! 14:41:14 pip always worked but the new version triggers an error in OpenStack rally 14:41:23 and we use if when creating functest docker file 14:41:41 we are back to Tuesday status...back to troubleshooting 14:41:59 what issues are you troubleshooting? 14:42:25 high leve 14:42:31 *level 14:42:57 we are not really troubleshooting to be honnest we run the tests and we collect the results. We can see that the integration of odl lead to a significant degradation of tempest results (which we may understand) but it is not the same on the different installers 14:43:03 so we have to understand the errors... 14:43:49 morgan_orange: thanks for explaining 14:44:02 see the page https://wiki.opnfv.org/tempest_brahmaputra_page 14:44:11 (not up to date probably) 14:44:12 <[1]JonasB> morgan_orange is that for ODL-L2 or L3 or both? 14:44:29 without controller almost 100% OK, with other scenario different figures and different errors 14:44:43 morgan_orange: we almost passed 100% with ODL L2 though? 14:45:14 tryes but it is not very stable from 1 run to another... 14:45:27 morgan_orange: its not? 14:45:40 in term of numbers of test run 14:45:59 morgan_orange: yeah the # of tests run seems to vary, but thats not an ODL problem, is it? 14:46:11 maybe we shoudl talk about this in #opnfv-testperf instead of this meeting 14:46:24 <[1]JonasB> I think we have a scenario config issue with Fuel for ODL-L3, I will look at it. 14:46:35 yes, let’s move on 14:46:52 anac1: yardstick? 14:46:55 #info Yardstick continues debugging on ODL and ONOS scenarios 14:47:02 trozet: apex/odl looks pretty stable - my bad the mai change was on apex/onos scenario (last one run) 14:47:10 #info integration with SFC started 14:47:29 #info results documentation for on-demand test cases started 14:47:45 anac1: what issues are you troubleshooting in ODL and ONOS scenarios? 14:48:33 morgan_orange: fyi we hit onos tracebacks on the controller, and failures in the python libraries, when testing floating IP, i think there is a bug there 14:48:34 debrascott: not possible to run yardstick on ODL, ONOS yet - SW debugging 14:49:23 anac1: yardstick sw or controllers? 14:49:48 debrascott: my impression is yardstick just doesnt run right now at all, anac1 is that correct? 14:50:40 we can get more details in test meeting in a few minutes 14:50:58 trozet: not on ODL and ONOS, correct 14:51:09 #topic installer status 14:51:18 trozet: works for os 14:51:42 JonasB: how is Fuel- ready to freeze? 14:52:02 debrascott: yardstick sw 14:52:23 <[1]JonasB> Not read to freeze, working with upstream problems. 14:52:30 anac1: got it, thanks 14:52:46 JonasB: what kind of issues with upstream? 14:54:00 <[1]JonasB> Not yet entirely stable, were working on it and hope to have better answers tomorrow. 14:54:37 JonasB: also, can you give time estimate yet or still trying to root cause? 14:54:55 <[1]JonasB> No estimate today 14:55:15 ok 14:55:37 trozet: Apex ready to code freeze when? 14:56:01 debrascott: assuming we can get both patches i referenced in my status verified today, we are good to do it tonight 14:56:26 narindergupta: joid ready to freeze? 14:57:18 debrascott: give me another day as still working on documentation. functionalitry wise we are good and debugging orange pod2 14:57:50 ok- good progress for Apex and JOID 14:58:17 narindergupta: still the same issue on Orange POD 2 - Failed to create a Glance image 14:58:42 #topic projects status 14:58:54 morgan_orange: yeah we figure it out that cinder volume failed to connect to ceph cluster 14:59:07 quick 1 liner from projects in attendance? 14:59:30 StuartMackie: where are we at with OpenContrail? 15:00:03 narindergupta: you can do documentation post code freeze 15:00:07 Components of the needed patch for OpenContrail/Liberty are identifed and being scripted 15:01:35 StuartMackie: good! which installlers still need the patch? 15:02:06 trozet: ok thanks then 15:02:43 debrascott: we dont have contrail working on Apex yet, I think we need Stuart's patch/help there 15:03:07 trozet: thanks, suspect it is for all 15:03:10 It should make things easier for all of them 15:03:24 OK top of the hour 15:03:28 thanks for attending 15:03:37 #endmeeting