15:02:17 <dmcbride> #startmeeting OPNVF Colorado 2.0 release
15:02:17 <collabot> Meeting started Thu Oct 20 15:02:17 2016 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:17 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:02:17 <collabot> The meeting name has been set to 'opnvf_colorado_2_0_release'
15:02:26 <dmcbride> #topic roll cll
15:02:32 <dmcbride> #topic roll call
15:02:37 <jose_lausuch> #info Jose Lausuch
15:02:38 <dmcbride> #info David McBride
15:02:50 <dmcbride> greetings team
15:03:30 <jmorgan1> #info Jack Morgan
15:03:51 <fzhadaev> #Fedor Zhadaev
15:03:56 <fzhadaev> #info Fedor Zhadaev
15:04:29 <ChrisPriceAB> #info Chris Price
15:05:15 <dmcbride> #topic documentation
15:05:21 <dmcbride> aricg: are you available
15:05:26 <sofiawallin> #info Sofia Wallin
15:06:13 <dmcbride> #info still waiting to hear back from aricg as to whether the re-merge was completed
15:06:27 <dmcbride> sofiawallin: any comments about documentation?
15:06:51 <jmorgan1> I know aricg did Pharos.git yesterday
15:06:58 <sofiawallin> No not right now, I haven't heard anything about the re merge yet.
15:07:31 <dmcbride> ok - lets switch to functest
15:07:38 <dmcbride> #topic Functest results
15:07:46 <sofiawallin> Waiting to get some documentation information about the additional scenarios for 2.0
15:08:00 <dmcbride> trozet: any comments about os-onos-nofeature-ha?
15:09:17 <sofiawallin> I have talked to Frank to the os-nosdn-fdio-noha and os-odl_l2-fdio-noha is fine
15:09:28 <dmcbride> #info os-onos-nofeature-ha shows some recent improvement. However, Jenkins still shows "partly cloudy" across the board
15:09:30 <jose_lausuch> dmcbride: not so bad results lately
15:10:38 <jose_lausuch> you can see positive trend on that one
15:11:28 <jose_lausuch> even onos-sfc seems to work last time
15:11:45 <dmcbride> sofiawallin: at least os-odl_l2-fdio-noha is on the dashboard.  That's an improvement over Tuesday.
15:11:46 <jose_lausuch> so we should see it positively growing
15:12:32 <dmcbride> frankbrockners: any comments on the fdio scenarios?
15:12:44 <sofiawallin> dmcbride: I'm gonna get a final answer from Frank on Monday. Include in 2.0 or not
15:14:33 <dmcbride> I haven't heard from Brady, but Os-odl_l2-sfc-ha looks to be improving
15:15:10 <jose_lausuch> dmcbride: I'm working with the sfc guys
15:15:22 <jose_lausuch> what i can say is that odl boron is unstable for sfc
15:15:27 <jose_lausuch> the test works ramdomly
15:15:35 <jose_lausuch> maybe colorado 3 brings better ersults...
15:15:58 <jose_lausuch> but we really depend on upstream fixes
15:16:09 <jose_lausuch> they are reporting bugs currently
15:16:38 <dmcbride> os-onos-sfc-ha looks like it's struggling
15:16:40 <jose_lausuch> the tests on that scenario work but the sfc test which is the most important :)
15:16:45 <dmcbride> same issue with ODL, I suppose
15:17:02 <dmcbride> phrobb: you're killing us man!
15:17:22 <jose_lausuch> but last run of onos-sfc worked
15:17:32 <jose_lausuch> let see how it looks like next week
15:17:47 <jose_lausuch> almost all the issues found are in netvirt :)
15:18:07 <jose_lausuch> missing flows most of the cases
15:18:17 <dmcbride> that's what Tim told me, also
15:18:37 <phrobb> jose_lausuch: are there resources in ODL land that should be asked to help resolve the sfc instability or are they already on it?
15:18:49 <jose_lausuch> we can't live without flows :)
15:19:34 <jose_lausuch> phrobb: the problem I see is that if we come to the community without concrete bug reports, it gets ignored
15:19:53 <jose_lausuch> so we are trying to dump the flows to jenkins console after a failed test execution
15:20:04 <jose_lausuch> so that we have an evidence of the failure
15:20:40 <jose_lausuch> how do we tell netvirt guys: :it fails sometimes" ? :)
15:21:00 <dmcbride> jose_lausuch: is it this one? https://bugs.opendaylight.org/show_bug.cgi?id=5586
15:21:32 <jose_lausuch> dmcbride: I dont think so
15:21:42 <phrobb> OK, thanks for making me aware.  I will see if I can rally more support from our side
15:21:58 <jose_lausuch> this is pointed to beryllium and we are with Boron
15:22:11 <jose_lausuch> phrobb: no prob. Thank you :)
15:22:39 <jose_lausuch> phrobb: basically, we need netvirt support
15:23:20 <jose_lausuch> you can talk to Brady or Manuel Buil who is troubleshooting that at the momment
15:23:25 <dmcbride> frankbrockners: do you have an update on the status of your scenarios for Col 2.0?
15:23:49 <dmcbride> aricg: ping
15:26:38 <dmcbride> it looks like Wei Su is the scenario owner for os-onos-sfc-ha
15:27:05 <dmcbride> I don't see him on IRC
15:27:27 <dmcbride> do we have anyone from Huawei that has contact with Wei Su?
15:27:57 <dmcbride> I'll try to follow up with him via email
15:28:28 <dmcbride> jose_lausuch: there were some glitches with the dashboard earlier in the week
15:28:39 <dmcbride> jose_lausuch: have those been resolved?
15:28:48 <jose_lausuch> dmcbride: I think it looks fine now
15:29:08 <dmcbride> jose_lausuch: agree - I haven't noticed any issues today
15:29:14 <jose_lausuch> the glitch you pointed out the other day was due to missing iterations
15:29:23 <dmcbride> ah
15:30:09 <jose_lausuch> well
15:30:24 <jose_lausuch> no graphs for some fuel scenarios
15:30:29 <jose_lausuch> I didnt check that though
15:30:43 <jose_lausuch> but if you refresh the page it works
15:30:50 <dmcbride> fzhadaev: I understood from your email that you are planning to re-release one or more scenarios with bug fixes?
15:31:39 <dmcbride> man - everyone is ignoring me today :(
15:31:49 <dmcbride> at least I got phrobb attention
15:31:53 <fzhadaev> yes& But for now we have critical issue which affects all jobs (deploy and test)
15:31:53 <jose_lausuch> :)
15:32:11 <phrobb> dmcbride: be careful what you wish for :-D
15:32:25 <fzhadaev> we need to fix it before we can see if we're ready for re-release in 2.0
15:32:33 <dmcbride> fzhadaev: how many scenarios are you re-releasing?  Is there a list?
15:32:55 <dmcbride> fzhadaev: I guess that would be the ones you marked for Col 2.0 on the scenario status page?
15:33:25 <fzhadaev> all related to ODL because we want to switch to the Boron
15:33:46 <dmcbride> fzhadaev: despite the ongoing problems with netvirt?
15:33:55 <dmcbride> fzhadaev: those don't affect you?'
15:34:33 <fzhadaev> for now we use old features :) so it's just moving to the next release
15:35:00 <dmcbride> ok - we are out of time
15:35:03 <fzhadaev> without actual using of new netvirt features
15:35:18 <dmcbride> please remember - documentation and testing wrap up on Monday
15:35:30 <jose_lausuch> ok
15:35:33 <dmcbride> release is on Thursday - one week from today
15:35:34 <fzhadaev> ok
15:36:01 <dmcbride> Col 2.0 will go live in about two weeks
15:36:22 <dmcbride> #endmeeting