14:59:37 <dmcbride> #startmeeting Colorado 2.0 Release
14:59:37 <collabot> Meeting started Thu Oct 13 14:59:37 2016 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:59:37 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:59:37 <collabot> The meeting name has been set to 'colorado_2_0_release'
14:59:49 <dmcbride> #topic roll call
14:59:56 <dmcbride> #info David McBride
15:00:18 <fzhadaev> #info Fedor Zhadaev
15:00:40 <jose_lausuch> #info Jose Lausuch
15:00:51 <jmorgan1> #info Jack Morgan
15:02:03 <dmcbride> #topic Functest status
15:02:32 <dmcbride> trozet: looks like we're starting to see some recovery in Functest results for Apex, as predicted
15:03:27 <dmcbride> my compliments to the Joid team - Functest results are rock solid
15:04:47 <dmcbride> do we have anyone available from Fuel?
15:06:06 <dmcbride> looks like issues with ONOS, OVS-HA
15:08:15 <dmcbride> #topic documentation
15:08:30 <dmcbride> any questions about documentation for Col 2.0?
15:08:55 <dmcbride> See Sofia's email from today
15:09:36 <dmcbride> recall that Col 2.0 documentation is in a different location
15:09:52 <fzhadaev> Hi David. I'm from Fuel. Sorry, I had connection issues.
15:10:06 <dmcbride> #link http://artifacts.opnfv.org/opnfvdocs/colorado/2.0/docs/documentation/index.html
15:10:21 <jmorgan1> dmcbride: sounds like we need to post documentaiton even if nothing changed, correct?
15:10:39 <dmcbride> jmorgan1: correct
15:11:10 <dmcbride> fzhadaev: no problem - did you see my comments about functest results on Fuel?
15:11:17 <dmcbride> fzhadaev: any comments?
15:12:19 <fzhadaev> for now we have some floating issue. investigation in progress.
15:12:35 <dmcbride> fzhadaev: seems like there has been some degradation in results for 3 or 4 scenarios
15:13:34 <dmcbride> team - I am taking Friday off, so I will be cancelling the Col 2.0 release meeting for Friday
15:13:50 <dmcbride> we will pick up again on Monday
15:14:14 <dmcbride> does anyone have any pressing issues related to Col 2.0 that they would like to discuss?
15:14:50 <dmcbride> going back to documentation...
15:15:06 <dmcbride> note that Aric corrected one item in Sofia's email instructions
15:15:31 <dmcbride> she said to cherry-pick to Colorado 2.0, but there is no Colorado 2.0 branch
15:15:45 <dmcbride> so, just cherry-pick to the Colorado stable branch
15:16:49 <dmcbride> schedule reminder
15:17:10 <dmcbride> testing and documentation should wrap up on Oct 24
15:17:18 <dmcbride> the release is on Oct 27
15:18:41 <dmcbride> jose_lausuch: any concerns or issues wrt Col 2.0?
15:18:54 <jose_lausuch> dmcbride: for Functest?
15:19:05 <dmcbride> jose_lausuch: anything
15:19:31 <dmcbride> jose_lausuch: weird thing I noticed with the Functest dashboard for Fuel
15:19:32 <jose_lausuch> dmcbride: not at all, some feature projects are fixing some test bugs in Functest
15:19:36 <jose_lausuch> but thats all
15:19:41 <jose_lausuch> we dont have major concerns
15:20:01 <dmcbride> jose_lausuch: sometimes the trend graphs don't show up for some or all of the scenarios
15:20:11 <dmcbride> jose_lausuch: but if you refresh, then they appear
15:20:14 <jose_lausuch> http://testresults.opnfv.org/reporting/functest/release/colorado/index-status-fuel.html
15:20:23 <jose_lausuch> it happens to me as well
15:20:26 <jose_lausuch> not sure why
15:20:33 <jose_lausuch> are you using Chrome?
15:20:38 <dmcbride> yes
15:20:57 <jose_lausuch> firefox or chromium works better I think
15:21:03 <jose_lausuch> but not a big deal
15:22:14 <dmcbride> @frankbrockners intent-to-release still shows a ? for Col 2.0 for os-odl_l2-fdio-noha
15:22:14 <collabot> dmcbride: Error: "frankbrockners" is not a valid command.
15:22:26 <jose_lausuch> we are actually working on Danube improvements
15:22:35 <jose_lausuch> #
15:22:44 <dmcbride> frankbrockners: intent-to-release still shows a ? for Col 2.0 for os-odl_l2-fdio-noha
15:22:51 <jose_lausuch> fdio is getting better
15:23:05 <jose_lausuch> we merged a patch some days ago
15:23:12 <jose_lausuch> that make the tests pass
15:24:12 <jose_lausuch> or at least it passes healthcheck
15:24:25 <jose_lausuch> frankbrockners: are floating ips supported in fdio?
15:24:38 <jose_lausuch> if not, we need to exclude vping ssh
15:25:28 <dmcbride> frankbrockners: is snubbing us
15:25:44 <dmcbride> does anyone have contact with Wei Su?
15:26:06 <dmcbride> I'm still trying to get him to update intent-to-release for two of his scenarios
15:27:18 <jose_lausuch> not me
15:27:47 <jmorgan1> as a side question, why do we support noha senarios?
15:28:41 <dmcbride> jmorgan1: that's a community / scenario owner decision
15:29:18 <dmcbride> presumably so that you have a reference to isolate ha-specific failures
15:29:33 <trozet> dmcbride: u sure it was os-odl_l2-fdio-noha
15:29:49 <trozet> dmcbride: i thought i marked that with ? for either l3 or ha
15:31:16 <dmcbride> trozet: yes, os-odl_l2-fdio-noha on Apex, with Frank identified as scenario owner
15:31:34 <jmorgan1> trozet: for the fdio and even sfc scenarios, they don't have ha option, is this because of a lack of hardware resources you think?
15:31:39 <dmcbride> There is a "?" in the column for intent-to-release for Col 2.0
15:33:45 <dmcbride> ok - that's it for today, unless there are any other comments or questions
15:33:55 <jmorgan1> thanks, dmcbride
15:33:58 <dmcbride> remember - NO meeting tomorrow
15:34:06 <dmcbride> I will be OOO on Friday
15:34:09 <dmcbride> back on Monday
15:34:34 <dmcbride> jmorgan1: thank you for participating
15:34:39 <dmcbride> thanks to everyone for participating
15:34:46 <dmcbride> #endmeeting