14:31:01 <debrascott> #startmeeting Brahmaputra Daily Standup
14:31:01 <collabot> Meeting started Tue Jan 19 14:31:01 2016 UTC.  The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:31:01 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:31:01 <collabot> The meeting name has been set to 'brahmaputra_daily_standup'
14:31:13 <debrascott> #info agenda https://wiki.opnfv.org/releases/brahmaputra/minutes?do=edit
14:31:19 <debrascott> #topic roll call
14:31:24 <joekidder> #info Joe Kidder
14:31:26 <anac1> #Ana Cunha
14:31:31 <StuartMackie> #info Stuart Mackie
14:31:43 <morgan_orange> #info morgan Richomme
14:32:25 <debrascott> #info Debra
14:32:49 <frankbrockners> #info Frank Brockners
14:33:12 <frankbrockners> #link agenda https://wiki.opnfv.org/releases/brahmaputra/minutes#jan192016 (the above takes you to the edit option)
14:33:24 <debrascott> #topic Hardware / POD status
14:33:25 <debrascott> Ericsson POD 2 status
14:33:29 <trevor_intel1> #info Trevor Cooper
14:33:45 <fdegir> #info Fatih Degirmenci
14:33:59 <fdegir> #info Ericsson POD2 WIP
14:34:29 <frankbrockners> fdegir - any idea on when it'll be fixed?
14:34:45 <fdegir> frankbrockners: Daniel is back from vacation and getting hands on the POD
14:34:56 <bin_> #info Bin Hu
14:34:59 <fdegir> frankbrockners: I can give better estimation tomorrow
14:35:05 <frankbrockners> thanks fdegir - so reads like "soon"
14:35:13 <fdegir> yes
14:35:14 <frankbrockners> unless the hardware is broken
14:35:27 <fdegir> that's exactly what happaned - hardware had issues
14:35:32 <frankbrockners> ouch
14:35:38 <fdegir> either the firmware or something else with the switch
14:35:44 <fdegir> but we'll see
14:35:51 <frankbrockners> ok
14:36:22 <frankbrockners> move to scenarios?
14:36:23 <fdegir> #info LF POD2 is fully operational thansk to pbandzi
14:37:20 <debrascott> #topic Scenarios
14:37:37 <debrascott> #info Scenarios are locked down
14:37:54 * ChrisPriceAB thanks pbandzi
14:38:05 <debrascott> #info so far no projects have indicated that a scenario is missing for them, some will drop for other reasons
14:38:20 <debrascott> anything more on scenarios?
14:38:32 <anac1> #info yardstick working on a bug fix for scenarios 3&4 - patch on master, will cherry pick to stable when it is done
14:39:32 <debrascott> #topic installer status
14:39:50 <debrascott> #info are installers ready to code freeze today?
14:40:25 <debrascott> trozet: 1 liner please
14:40:40 <frankbrockners> #info from what I know, Fuel asked the code freeze to be pushed out by a few days
14:41:04 <frankbrockners> [1]JonasB - any details?
14:41:08 <debrascott> #info yes verified from Jonas
14:41:18 <frankbrockners> when's the new date?
14:41:59 <debrascott> #info JOID status from Narinder JOID team is working on documentation part of it and most likely would be completed by tomorrow. From functionality wise it is complete but documentation need some work to finish.
14:42:58 <debrascott> frankbrockners I would say let’s give until Th
14:43:16 <debrascott> Joid I think is read, and Apex too
14:44:28 <debrascott> I don’t have the latest from Compass they may appreciate a bit more time
14:45:28 <debrascott> Will double back with them to make sure Th would give enough time to finish test (provided pods stay available)
14:46:34 <debrascott> #info moving installer code freeze to 1/21 due to pod downtime over this past weekend
14:47:09 <debrascott> #topic test status
14:47:25 <debrascott> morgan_orange quick update, couple of lines
14:47:40 <morgan_orange> #functest tests suite runnable from CI perspective, heterogeneous and not reproducible results (due to lack of stability)
14:48:14 <debrascott> will moving code freeze to TH give enough time to stabilize?
14:48:34 <morgan_orange> the code is relatively stable, the results are not...
14:48:44 <morgan_orange> and the integration of companion projects just started
14:49:03 <morgan_orange> doctor, promise, ovno, onos integrated but not succefful run from CI yet
14:49:21 <morgan_orange> but should be testable and for sure adaptations would be required / installers & scenarios
14:49:44 <morgan_orange> we should not freeze test and installer code at the same time assuming that we must adapt to installer
14:49:46 <anac1> debrascott: if installer code freeze is 1/21 we need to verify it works for test, same day is not enough
14:49:52 <morgan_orange> if installers ar emoving we must usually follow
14:50:46 <debrascott> understood. I think 2 installers are in good shape to begin with now. Can you start with those two?
14:51:05 <morgan_orange> we are working with the 4 in //
14:51:15 <morgan_orange> you mean some are more stable
14:51:24 <debrascott> yes some are more stable
14:51:26 <morgan_orange> and troubleshooting should be easier..
14:51:43 <morgan_orange> well hopefully but yesterday we had no system to tests..
14:51:49 <anac1> #info yardstick - ODL scenarios not working
14:52:05 <anac1> we need time to troubleshoot and fix bugs
14:52:32 <anac1> #inf yardstick documentation - not all ready
14:52:34 <morgan_orange> +1
14:52:51 <morgan_orange> on stable targets
14:52:53 <anac1> we need 4 consecutive runs, we don't get even 2
14:53:38 <debrascott> anac1: what is the shortest time you think could get the kinks worked out? can you give an estimate? I know it is hard when troubleshooting & trying to get to fault
14:53:44 <anac1> #info yardstick - will continue to work on test result visualization
14:54:21 <debrascott> are we talking 2-3 days or weeks?
14:54:43 <anac1> debrascott: not 2-3 days
14:55:18 <debrascott> anac1: are there specific scenarios we could drop to shorten the time?
14:55:43 <anac1> once the installer code is frozen, we need time to veify it works and their help to fix the bugs
14:55:49 <anac1> verify*
14:56:33 <debrascott> obviously we won’t drop ODL but anything else that would reduce bugs to troubleshoot?
14:57:32 <debrascott> OK 3 minutes left.
14:57:36 <morgan_orange> not sure it is a problem of scenario
14:57:41 <morgan_orange> it is a problem of stability
14:57:42 <anac1> we need help from installers, once their code is frozen, that's my suggestion
14:58:00 <debrascott> OK, will note that
14:58:16 <debrascott> #topic project updates
14:58:20 <frankbrockners> help from installers *and* component teams/projects - correct?
14:58:30 <morgan_orange> yes
14:58:35 <anac1> frankbrockeners: yes
14:58:36 <frankbrockners> installers only install - but don't take responsibility for functioning
14:58:41 <debrascott> +1
14:59:35 <morgan_orange> test projects as well ..
14:59:41 <debrascott> #info Doctor will likely work on post install option but may not make the release
14:59:48 <anac1> frankbrockners: correct, testing need help from installers + feature
14:59:59 <debrascott> #info Policy test has dropped from the release
15:00:44 <debrascott> OK, top of the hour again. We can continue in the Release team meeting in 1 hr
15:00:51 <debrascott> thanks all for joining
15:01:01 <debrascott> #endmeeting