14:30:25 #startmeeting Brahmaputra Daily Standup 14:30:25 Meeting started Thu Feb 4 14:30:25 2016 UTC. The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:25 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:25 The meeting name has been set to 'brahmaputra_daily_standup' 14:30:35 #link agenda https://wiki.opnfv.org/doku.php?id=releases/brahmaputra/minutes 14:30:51 #topic roll call 14:31:03 #info Ashlee Young 14:31:11 #info Jonas Bjurel 14:31:14 HKirksey: good morning! 14:31:27 #info ebrjohn Brady Johnson 14:31:32 #info Ana Cunha 14:31:36 #info Morgan Richomme 14:32:11 #Topic test status 14:32:32 morgan_orange: good morning, how is functest today? 14:32:47 #info Narinder Gupta 14:32:51 #info Bin Hu 14:33:05 #info functest: I tried to capture the situation per scenario/per installer for Functest 14:33:05 #link https://wiki.opnfv.org/functextnexttaks 14:33:15 info functest: it is static => if you want something dynamic => go to dashboard 14:33:15 #link http://testresults.opnfv.org/proto/index-pod.html 14:33:23 #info Dan Radez 14:33:26 #info functest: according to success criteria, we have already 1 validated scenario: compass/onos 14:33:26 #info functest: another one jst needs iterations to be validated: compass/nosdn 14:33:26 #info functest: some are closed but the criteria of 90% of success on Tempest is not reached 14:33:26 #info functest: support on troubleshooting the Tempest error / scenario / installer welcome -- 14:33:37 #info functest: morning errors on CI were not due to tests but to result pushed in artifacts (need config on jumphosts), now artifacts are pushed 14:33:44 #info functest: joid has better results on non CI POD (Orange POD2) regarding Tempest (92%), so just considering CI POD could be unfair fo installer if PODs have some network issues 14:33:57 #link http://artifacts.opnfv.org/logs/functest/opnfv-jump-1/brahmaputra/2016-02-03_19-05-12/brahmaputra/tempest/tempest.log 14:34:12 #info ex of log pushed to artifact (here tempest log on apex) 14:34:19 #link http://artifacts.opnfv.org/logs/functest/opnfv-jump-1/brahmaputra/2016-02-03_19-05-12/brahmaputra/rally/opnfv-neutron.html 14:34:25 #info functest: new release of the LF test dashboard (still things to fix especially the installer versions) 14:34:42 that is all for me 14:35:17 #info Trevor Cooper 14:35:49 #info Joe Kidder 14:35:50 morgan_orange: thank you. wiki status link yoiu shared is very helpful!! 14:35:55 #info Weidong Shao 14:36:08 debrascott: yes but I do not like wiki status... 14:36:14 especially when we have CI 14:36:29 it is impossible to reflect the reality as things ar emoving all the time... 14:36:34 morgan_orange: I understand, struggling with wiki status updates myself 14:36:44 I prefer dynamic dashboard 14:36:50 same info but reflecting the reality 14:37:11 morgan_orange: we’ll get to the dynamic one. Hopefully for C 14:37:28 Let’s move on 14:37:40 anac1: good morning, how is yardstick doing today? 14:37:44 #info yardstick run on odl scenario successful for ODL Be 14:38:11 anac1: this is with workaround in place? 14:38:27 #info investigation on-going to understand whether functest before or after has effect on the success 14:38:35 #info no workaround 14:38:57 anac1: WOW! that is good news!!! 14:39:08 #info at this point, we'll execute more experiments before reaching conclusions 14:39:24 viktor sent an email about how to check if we dont clean things properly, we could include it in the jjobs 14:39:41 #info need to understand from the installers whether ODL Be is an intall option 14:39:52 install* 14:40:10 jose_lausuch: +1 14:40:20 I thought it was 14:40:33 In fact, I thought it was desirable 14:40:51 trozet, narindergupta ^^? 14:41:13 debrascott: default is Lithium but there is option to do berilium 14:41:20 Apex is the same 14:41:36 we have an sfc option that is based on Be 14:41:48 debrascott: in case of joid one config option has to change in yaml file which can be done using jjb 14:41:50 radez: could you provide us with a fresh install of ODL Be in LF POD1 ? 14:42:18 jonasbjurel:^^? 14:42:26 anac1: we're very close to being able to, will yardstick not work on Li? 14:42:33 or are we going to do both? 14:42:34 narindergupta: same for you, could you provide us with a fresh install (and help us with the access to the POD) ? 14:43:00 wshao:^^?? 14:43:08 anac1: we need a pod where i can run the install. Currently pod5 has for ci 14:43:12 radez: on ODL Li, we have the ping+ssh faults, need a workaround that is temporary, i'd prefer ODL Be 14:43:37 narindergupta: ok, thanks 14:43:39 debrascott: Yes supported by Fuel 14:43:55 anac1:k, I was planning to see if I can get you a clean Li env today or tomorrow for yardstick, and as soon as we can have Be too we'll stand that up for you 14:43:57 we do not have ODL Be yet. 14:44:20 radez: great, thanks ! let's get sfc done 14:44:49 anac1: would your rather we focus on Be for yardstick? or do you still want li? 14:45:07 i'd prefer Be 14:45:30 Hi folks, I'm not able to join today. But can I ask us to keep the very latest information up on https://etherpad.opnfv.org/p/steps_to_brahmaputra 14:45:55 ChrisPriceAB: my next topic for today 14:45:58 The sections at the bottom can show the successive deploys etc in order that we are able to start to pick "release ready" scenario's asap 14:46:06 thanks debra, will run away now. :D 14:46:10 #Topic Schedule building ot relase 14:46:13 question on ODL Be, is it desirable to use it? We can try that in Compass, if that is the goal 14:46:16 we will use the workaround for Li, if the installer don't have Be yet 14:47:14 wshao: can you try ODL Be with compass ? 14:48:14 ok ,we will try it tomorrow (China time). 14:48:31 anac1: Good discussion, ready to move on? 14:48:59 wshao: thanks, yardstick guys n China can help - they are also on top of the issues 14:49:09 debrascott: sure 14:49:20 Ok, thanks. 14:49:25 anac1: ok cool 14:49:32 https://etherpad.opnfv.org/p/steps_to_brahmaputra 14:50:02 in order to keep a schedule that I can work real time we need to have more details in the above link 14:50:43 We may be asked to make tradeoff’s with different scenarios 14:50:50 what to cut and what to keep 14:51:15 and what time could be saved if dropping certain scenarios 14:51:58 anac1: can you do something similar for yardstick as morgan_orange has done for functest? 14:52:35 we need to understand what features might be dropped in yardstick if we drop certain scenarios 14:53:04 we also need to understand what has already been working/failing/not tested yet in a high level overview 14:53:06 Debrascott: The selected scenarios need to be coordinated across functest and yardstick 14:53:24 Sounds like if we can get Compass to support, Be, we might be able to get the largest portion of features supported 14:53:36 I mean scenarios 14:53:36 We cannot run different sets of scenarios for functest and yardstick 14:53:38 jonasbjurel: yes, which is why we need a similar view to compare 14:54:20 jonasbjurel: we need to see what is running successfully in both yardstick & functest scenarios 14:54:20 Something in the way Be vs Li handle the security groups 14:54:39 ashyoung: could be other faults too 14:54:44 right 14:54:59 Regarding the Security Groups in ODL-Li, do you know if ODL Group Based Policy is installed? 14:55:22 if so, GBP "uses" (interracts with) security groups 14:55:30 debrascott: Are we basing releasecontent primarily on what is working or not? 14:55:32 ebrjohn_: maybe a question for the installers ? 14:55:41 from the ODL karaf console, try this: feature:list -i | grep grou+ 14:55:52 feature:list -i | grep group 14:56:05 ebrjohn_: as i wrote, there might be other faults on Li causing the failure 14:56:38 anac1: ok, just a possibility 14:57:16 question is what ODL version to focus on 14:57:38 jonasbjurel: that’s a place to start, but may have other factors too which is why we need to understand features view 14:59:13 I recommend progressing on what is working, while others dive in to seeing how to fix the broken scenarios 14:59:26 anac1: my question above? 14:59:33 So, I suggest continue with Be, while we look into Li 14:59:57 debrascott: i'll get to it as soon as I can 15:00:36 anac1: thank you. The board will give us pressure to understand this view, HKirksey has asked for it already 15:00:50 ashyoung: makes sense to me 15:01:19 ashyoung: +1 15:01:37 OK, top of the hour already…how does it go so fast? 15:02:37 Thank you for attending everyone. I’m looking at your Jira Dashboards for some status but if you have any specific blocking issues or successes please send me an email to high light those in daily update. 15:02:46 Flies by when we're having fun 15:03:10 assuming I can get my browser + wiki update working again 15:03:19 ashyoung: +1 15:03:20 Gonna keep digging into the Li issues and also into getting compass/Be working 15:03:25 Endmeeting 15:03:31 Thanks!!! 15:03:32 #endmeeting