14:30:26 #startmeeting Brahmaputra Daily Standup 14:30:26 Meeting started Thu Jan 14 14:30:26 2016 UTC. The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:26 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:26 The meeting name has been set to 'brahmaputra_daily_standup' 14:30:33 #topic roll call 14:30:44 #info debra 14:30:58 #info Frank Brockners 14:31:02 #info Ana Cunha 14:31:06 #info Bin Hu 14:31:07 #info Joe Kidder 14:31:11 #info Ashlee Young 14:31:29 #link draft agenda for today: https://wiki.opnfv.org/releases/brahmaputra/minutes#jan142016 14:31:33 <[1]JonasB> #info Jonas Bjurel 14:31:33 #info Trevor Cooper 14:31:39 #info Fatih Degirmenci 14:32:45 #topic Hardware / POD status 14:32:46 Is https://wiki.opnfv.org/pharos_rls_b_labs#status_of_production_ci_resources_for_release_b up to date? 14:33:15 #info POD/HW status is same as yesterday 14:33:27 #info The page is up to date, reflecting current status 14:33:33 ok good lets move on 14:33:56 #Topic Scenarios status (Definition, Deployment status) 14:34:41 Morgan_Orange did you cleanup these webpages?https://wiki.opnfv.org/brahmaputra_testing_page#available_scenarios clean up (AI: Morgan) 14:34:42 https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios clean up (AI: Morgan) 14:34:50 should I give short status regarding naming? 14:34:52 I tried 14:35:01 but I think we should remove the table available scenario 14:35:12 as available scenario are available on the jenkins page 14:35:15 it is more accurate 14:35:20 #info Short scenario naming convention is applied to Fuel and Joid. WIP with Compass 14:35:27 #info Jenkins Job structuring/naming convention is applied to Compass, Fuel, and Joid 14:35:32 #info Details are on 14:35:38 #link https://wiki.opnfv.org/brahmaputra_testing_page#scenario_and_jenkins_job_naming_scheme 14:35:50 #info The jobs can be seen on 14:36:02 #link https://build.opnfv.org/ci/view/OPNFV%20Platform%20CI%20-%20Alternative%20View/ 14:36:58 I would suggest to rely only on the jenkins view for the available scenario (remove from the wiki page) and keep a table for the candidate scenario until they are implemented 14:37:24 morga_orange1: just so long as everyone can find easily and access easily 14:38:08 <[1]JonasB> I added one scenario for virtual traffic classifyer which apparently need VLAN segmentation 14:38:26 morgan_orange1: why would you remove after they are implemented? 14:39:03 because they are no more cnadidate, they become available scenario 14:39:30 +1 on removing the "available" table 14:39:30 <[1]JonasB> morgan_orange1: Do we want to add vlan segmentation as a scenario candidate? 14:39:35 morgan_orange1: OK, that makes sense 14:39:47 let's add the above link to the wiki instead 14:39:56 +1 14:40:26 ah - link is already there... 14:40:26 #info Narinder Gupta 14:40:35 so no need to do anything but remove 14:41:28 can we move to installers? 14:41:55 #topic Install/Deploy tools - 1-line status summaries 14:42:33 JonasB one line update please 14:42:42 <[1]JonasB> #info Fuel 8 rebasement done, work/race ongoing with rebasing the plugins. Scenarios are done to the point I think is needed, we can add more later 14:42:49 narindergupta, [1]JonasB, weidong, trozet - any updates? 14:42:51 for joid installer i am seeing few failure which i will be fixing it today. 14:42:58 thanks [1]JonasB 14:43:03 <[1]JonasB> #info Most of the scenarios run for Stable and Master 14:43:20 #info trozet sent out his report in email again 14:43:49 <[1]JonasB> #info One more plugin will be integrated this week, it's for the policy framework 14:44:09 <[1]JonasB> #info end fuel report, questions? 14:44:38 #info not much change in Apex from yesterday 14:44:46 thanks JonasB 14:44:58 I'll have a report sent this afternoon 14:45:03 Driving atm 14:45:09 #info for joid installer i am seeing few failure which i will be fixing it today. 14:45:09 narindergupta?? 14:45:37 trozet will include it in my daily- thanks 14:46:34 narindergupta: any progress with OpenContrail plugin for JOID? 14:46:59 opencontrai nitration is complete 14:47:15 Yeah! 14:47:34 Are we ready to move to test status? 14:47:35 <[1]JonasB> narindergupta: Is this OpenContrail + Liberty? 14:47:40 debrascott, we have plugin in joid but few bug fix needs to be done by juniper team for liberty 14:48:28 open contrail + kilo has tested an liberty changes needed in charm not in joid. Which juniper team is working on. 14:48:47 narindergupta: thank you. I understand. 14:48:56 onos also plugin is availble in joid 14:49:13 narindergupta: excellent 14:49:19 and huwaie team is working on charms and few correction 14:49:45 but from joid prospective we can deploy today through joid 14:50:21 any other question debrascott ? 14:50:30 No, thnk you 14:50:36 Lets move on to test 14:50:59 #topic Testing status 14:51:51 morgan_orange1: functest status? 14:51:57 #info functest troubleshooting in progress 14:52:46 morgan_orange1: what issues? 14:53:19 #info wiki pages initiated to have a summary per testcases https://wiki.opnfv.org/functextnexttaks 14:53:33 lots of tests failed (mainly network issues) 14:54:35 * frankbrockners wonders who came up with "functextnexttaks" 14:54:37 and integration of companion projects 14:54:46 just started (promise, onos) 14:55:01 lacking also stability from one run to another 14:55:10 * frankbrockners would have expected functestnexttasks :-) 14:55:34 https://wiki.opnfv.org/vping_brahmaputra_page 14:55:43 https://wiki.opnfv.org/vims_brahmaputra_page 14:55:52 https://wiki.opnfv.org/tempest_brahmaputra_page 14:57:15 morgan_orange1: those are helpful 14:57:45 Quick question: what's holding up any of the onos-related test cases from getting status? 14:57:50 where are you at in troubleshooting? still fault analysis? 14:57:51 but almost unmainable...I would expect that dashboarding would provide something more consistent and easy to maintain... 14:58:12 +1 that 14:58:13 but the prototype I saw does not answer to my expectation 14:58:21 that’s needed 14:58:54 before we move to talk about dashboard pls answer above questions 14:58:56 folks - just a note on meeting hygene 14:58:57 ashyoung: I thing the integration started, we have now onos labs so it should be ok 14:59:06 can we #info some of the points said here? 14:59:20 awesome! 14:59:41 #info yardstick: for fuel: odl scenario fails (ssh timeout), for compass: working last night, however one new fault found today, for joid: troubleshooting, for apex: started yardstick integration on baremetal with help from apex team 15:00:07 have to leave for another meeting 15:00:32 anac1: ty, yes we are top of the hour again. 15:00:50 thanks!!! 15:01:02 #info if we did not get to your status please send me an email 15:01:20 #endmeeting