14:30:33 #startmeeting Brahmaputra Daily Standup 14:30:33 Meeting started Fri Jan 22 14:30:33 2016 UTC. The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:33 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:33 The meeting name has been set to 'brahmaputra_daily_standup' 14:30:44 #link agenda https://wiki.opnfv.org/releases/brahmaputra/minutes 14:30:50 #topic roll call 14:31:00 #info Bin Hu 14:31:10 #info Morgan Richomme 14:31:34 #info Joe Kidder 14:31:48 #info Ashlee Young 14:32:12 #info Frank Brockners 14:32:13 #info Fatih Degirmenci 14:32:33 #info Tim Rozet 14:32:37 #info Ana Cunha 14:33:04 #topic Install/Deploy tools status (Quick status from all 4 installers) 14:33:26 JonasB: * Update on Fuel testing/stabilization> ready to freeze? 14:34:09 is jonas here yet? 14:34:37 debrascott: i can go if we want to move Fuel to go last and wait for Jonas? 14:34:42 [1]JonasB: ping? 14:34:46 trozet: go ahead 14:35:06 #info Apex got SFC and Aodh (Doctor) support merged last night 14:35:25 #info The last thing we don't have is contrail support 14:35:33 #info but we are ready to freeze, we are not sure if thats going to make it 14:35:42 trozet: claps and applause! 14:35:56 debrascott: thanks :) 14:36:15 I don’t see Stuart on yet to answer status on Contrail. 14:36:36 trozet: did you receive the patch from him? 14:36:40 #info Trevor Cooper 14:37:04 debrascott: no I don't think so. The problem is we are trying to build the artifacts ourselves, because it looks like there is no RPM pre built for us with liberty support. 14:37:12 debrascott: from what we found it only supports Juno 14:37:20 debrascott: so radez is trying to hack at it to get it to work 14:37:29 #info Narinder Gupta 14:37:58 debrascott: I don't have high hopes at this point, but we are still trying until code freeze, but dont hold up code freeze because of that 14:38:08 trozet: check with Stuart again. Yesterday sounded like he had a working patch to hand you. 14:38:23 #info for JOID we are ready for code freeze as last pending issue related to Orange pod has been fixed 14:38:35 debrascott: will do 14:38:49 narindergupta_aw: awesome, claps and applause to you as well 14:39:18 #info last from Compass was they are also ready to freeze 14:39:44 OK, until JonasB: arrives lets move on to test 14:39:49 #topic Test 14:39:58 #info Stuart Mackie 14:40:07 #info Functest tests more stable, several successfull run done since 24h 14:40:16 #info all tables updated 14:40:29 #info onos first successfull run on apex and compass 11/11 14:40:48 morgan_orange: sighs of relief here. Good to hear stability is coming along 14:40:51 woo hoo 14:41:23 #info some concerns on the config of some PoDs, we were able to run the same tempest suite on 3 different PoDs with the same scenario 14:41:46 morgan_orange: and same results? 14:42:01 we got very different results..on Orange Pod 91% OK, On Intel POD5 35% 14:42:38 well OK, being able to run is a good start…stability still an issue across pods 14:42:43 Intel POD5 14ù, Intel POD6 34% 14:42:58 yep but here it is a question of network config of the POD 14:43:25 other concern it seems that ODL suite may be provide different results according to ODL version... 14:43:32 all the installers do not use the same version 14:43:47 #link https://wiki.opnfv.org/tempest_brahmaputra_page 14:43:59 #link https://wiki.opnfv.org/onos_brahmaputra_page 14:44:01 morgan_orange: that can be documented though, right? 14:44:20 I mean if it is known & expected 14:44:26 yes 14:44:29 morgan_orange - what versions of ODL do the different installers use? 14:44:30 not a big deal 14:44:46 isn't everyone using Lithium SR3? 14:44:47 frankbrockners: good question... 14:45:14 maybe installers can jump in and answer? 14:46:14 trozet: ODL version used by Apex? 14:46:33 narindergupta: ODL version used by JOID? 14:47:10 #info Apex uses Lithium SR3 for all scenarios, except Be for SFC 14:47:23 #info test DB ready for migration, mail sent for transfer to LF on Monday 14:47:41 morgan_orange: excellent 14:48:08 are we ready to move on to Yardstick? 14:48:20 #info yardstick - ONOS first succesfull run on Compass 14:48:45 #info continue troubleshooting ODL scenarios 14:48:59 anac1: claps and applause for you too considering yesterday you couldnt run anything!! 14:49:28 anac1: what issues do you have with ODL scenarios? 14:49:59 debrascott: we are debugging resource creation in ODL 14:50:32 woo hoo! 14:50:55 ashyoung: onos rocks :) 14:51:12 :) 14:51:13 anac1: OK good. Keep us informed. Please reach out at any time for help from any team 14:51:26 ashyoung:+1 14:51:29 debrascott: sure 14:52:07 JonasB: did you join us? 14:52:29 #topic project status 14:53:00 StuartMacki: what’s up with contrail, Apex says they don’t have the patch working yet? 14:54:13 Correct - they moved to a different set of puppet modules and got further, but need to use a new neutron plugin 14:54:26 I didn't hear back if they made more progress. 14:54:49 Our internal CI was down yesterday which held up our own efforts 14:55:04 StuartMacki: trozet says no and they need to freeze 14:55:30 StuartMacki: is the new neutron plugin the one radez is using? 14:55:41 StuartMacki: any other installers successful with deploy? 14:55:58 StuartMacki: https://github.com/Juniper/contrail-neutron-plugin on master branch? 14:56:09 Not with Liberty 14:56:30 StuartMacki: radez is still hacking at that trying to get it into our build, it has some dependency python packages hes trying to resolve 14:56:37 StuartMacki: so hes not stuck per say 14:56:57 StuartMacki: but if you could confirm my question that would really help us 14:57:24 trozet: are you asking which one he is using or which one he should use 14:57:57 StuartMacki: i'm asking which one we should be using 14:58:22 Latest on master is best place to be 14:58:24 StuartMacki: master branch on https://github.com/Juniper/contrail-neutron-plugin compatible with liberty? 14:58:29 StuartMacki: ok thanks 14:58:38 debrascott: when is the code freeze going to happen? 14:59:25 trozet we need you to close down soon but Fuel is still outstanding so I think we can wait for that. Will have to follow up with JonasB off line since he didn’t join us today. 14:59:49 trozet: yesterday he expected that by today he’d be able to estimate time to freeze 15:00:11 debrascott: yeah well the freeze should be across the entire project, so we will just work until you set the freeze time 15:00:11 If you can freeze then test teams can have easier time troubleshooting & testing w/Apex scenarios 15:00:38 When you make changes their troubleshooting scenarios change 15:01:34 debrascott: we arent making any major feature additions to current scenarios 15:01:39 I would say try to get Contrail support in, with plan to freeze tonight. We’ll do day per day until Fuel can freeze 15:01:50 debrascott: just trying to add contrail as a separate scenario, shouldnt have any impact on the others 15:02:07 trozet: yes but rebuilding changes test setup enough that issues change day to day 15:02:26 debrascott: thats not fair, the code freeze should be the same for all installers? 15:02:48 debrascott: why give fuel special permission? 15:03:03 trozet: agree- Fuel has too many components that only it installs 15:03:08 * fdegir prefers to stay silent 15:03:24 frankbrockners: speak up 15:03:34 * fdegir leaves... 15:03:49 trozet: not trying to be unfair, just trying to get each ready and I don’t know yet when Fuel will be 15:04:13 trozet: asking that you plan day to day for freeze 15:04:17 * frankbrockners believes this is a larger TSC level debate 15:04:37 frankbrockners: agree 15:04:56 debrascott: we are ready to freeze, and only working on bug fixes for the sceanrios we have support for, but until the common code freeze happens we will work for contrail 15:05:14 trozet: agree 15:05:23 debrascott: ok 15:05:27 debrascott: thanks 15:05:33 trozet: waiting to here from Fuel if they can freeze today 15:06:11 debrascott: ok just drop me an email when the code freeze will be when you find out 15:06:33 trozet: will send out to tech-discuss and all installers 15:06:45 ok, past the hour 15:06:58 thanks everyone for attending 15:07:05 Good progress made 15:07:06 Thanks! 15:07:12 #endmeeting