16:59:40 <frankbrockners> #startmeeting FDS synch
16:59:40 <collabot`> Meeting started Thu Dec  1 16:59:40 2016 UTC.  The chair is frankbrockners. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:59:40 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:59:40 <collabot`> The meeting name has been set to 'fds_synch'
17:00:36 <frankbrockners> hey folks
17:00:42 <michal-cmarada> #info Michal Cmarada
17:00:45 <frankbrockners> #info Frank Brockners
17:00:46 <michal-cmarada> hey
17:00:59 <vlavor> #info Vlado Lavor
17:01:28 <jlinkes__> #info Juraj Linkeš
17:02:21 <seanatcisco> #info Sean Chandler
17:02:35 <trozet> #info Tim Rozet
17:02:36 <frankbrockners> #info agenda for today (a) update on Cisco FDS POD / testing os-odl_l2-fdio-ha scenario (b) update on os-nosdn-fdio-noha (c) update on L3 scenario
17:02:56 <frankbrockners> anything else to discuss?
17:03:45 <frankbrockners> jlinkes__: any updates on (a) ha testing / Cisco FDS POD availability?
17:05:09 <jlinkes__> there seems to be progress with regards to dhcp traffic, but I was unable to test it, since now ipmi traffic is not working
17:06:17 <jlinkes__> notified davinder and seanatcisco also provided some more details
17:06:31 <frankbrockners> jlinkes__: thanks
17:07:21 <frankbrockners> any other progress from a test perspective (e.g. wrt/ race conditions in GBP etc.)
17:07:40 <frankbrockners> ?
17:07:42 <jlinkes__> from test perspective no
17:07:48 <jlinkes__> well
17:08:08 <jlinkes__> except for https://jira.opnfv.org/browse/FDS-152 https://jira.opnfv.org/browse/FDS-153 and https://jira.opnfv.org/browse/FDS-154 were created
17:08:20 <jlinkes__> now being investigated by michal-cmarada and vlavor
17:08:32 <frankbrockners> jlinkes__: thanks
17:08:48 <frankbrockners> michal-cmarada: any news?
17:10:10 <michal-cmarada> today i was looking into qrouter recreate issue. maybe there will be a way to update it without creating the qr-tap again
17:10:13 <vlavor> I went briefly through logs provided by Juraj, and I saw several errors caused by netconf - mainly failed transactions
17:10:51 <jlinkes__> is that odl netconf client?
17:11:06 <vlavor> yes
17:11:44 <vlavor> data were created by vbd/gbp but weren't sent to device because of it
17:12:12 <frankbrockners> vlavor: could that be a HC issue?
17:12:48 <vlavor> no this specific issue is not an HC issue
17:13:43 <frankbrockners> ok... was just wondering because of failed transactions. Would be good if you could work with jlinkes__
17:14:12 <frankbrockners> let's move to agenda topic (b) os-nosdn-fdio-noha status
17:14:39 <vlavor> I have contacted netconf guys, so they are working on it right now
17:14:41 <frankbrockners> we got the scenario into the release thanks to sean and onong's hard work
17:14:52 <frankbrockners> thanks vlavor
17:15:30 <frankbrockners> there are jira tickets for the open issues for the scenario: FDS-155 ... to FDS-161
17:15:42 <frankbrockners> those tickets don't have an owner jet
17:15:55 <frankbrockners> seanatcisco: could you get owners assigned?
17:16:21 <seanatcisco> if i have those rights
17:16:43 <seanatcisco> apparently so
17:17:21 <frankbrockners> in case you don't please send an email to opnfv-helpdesk@rt.linuxfoundation.org asking for access
17:17:25 <seanatcisco> FDS-161 really is only related to release notes/documentation which i also have to write for fd.io anyhow on the enic configuration
17:18:19 <seanatcisco> not sure who should look into the FD-155 bug (mariadb/mysqld)
17:18:54 <frankbrockners> there is one more update on the ha scenario that i forgot: trozet created a jenkins job for the scenario - so should be part of the pipeline now
17:19:40 <frankbrockners> jlinkes__: is FDS-155 something you could help with? or trozet?
17:19:47 <trozet> frankbrockners: I saw an email from you saying we wont release fdio-ha as part of C3.0?
17:20:35 <frankbrockners> trozet: yes - this is true. We still don't have an operational pod where we can test ha properly
17:20:57 <trozet> frankbrockners: what if it passes tonight on LF pod 1 :) ?
17:21:10 <frankbrockners> trozet: we had a set of issues seen on the cengn pod - but that was taken away for the cengn summit demos
17:21:51 <frankbrockners> trozet: I could beg the folks for more time... - but basically we're past the deadline for test results reporting. deadline was yesterday
17:22:16 <frankbrockners> trozet: am curious on test results of course
17:22:23 <trozet> frankbrockners: i mean, are we really that strict?
17:22:28 <jlinkes__> frankbrockers: I think https://jira.opnfv.org/browse/APEX-356 should help with FDS-155
17:22:35 <trozet> frankbrockners: when does C3.0 release?
17:22:57 <frankbrockners> trozet: apparently they are. the testing folks prepare documentation based on the results
17:23:17 <jlinkes__> frankbrockners: and I believe this is the upstream bug for it https://bugs.launchpad.net/tripleo/+bug/1524809
17:23:29 <trozet> frankbrockners: cant we just include the scenario in apex release notes and list any bugs?
17:23:35 <frankbrockners> trozet: i asked whether there might be other scenarios which are a bit late in the release call on Tuesday - but got no input/support
17:23:51 <trozet> frankbrockners: for example we dont have ovs dpdk functest results because of a bug with UCS
17:23:59 <trozet> frankbrockners: but we still release that scenario, works fine on virtual
17:24:52 <jlinkes__> trozet: we need https://jira.opnfv.org/browse/APEX-346 for the scenario to work - the old ODL won't work with new vpp/hc
17:24:59 <frankbrockners> trozet: we never got it to deploy without major issues (e.g. flapping services after the setup is operational for 5+ minutes) - so am feeling a bit uncomfortable.
17:25:06 <trozet> jlinkes__: yeah the patch is almost done CI
17:25:09 <frankbrockners> jlinkes__: any thoughts on readiness?
17:25:39 <trozet> frankbrockners: flapping services i thought was only seen on 1 pod
17:25:51 <trozet> frankbrockners: do you know when C3.0 release date is?
17:26:06 <jlinkes__> frankbrockners: readiness of the ha scenario?
17:26:16 <frankbrockners> trozet: formal release is Dec/5 - Monday
17:26:22 <frankbrockners> jlinkes__: yes
17:27:14 <frankbrockners> trozet: depending on how things go we could make the case for a Colorado 4.0 in the TSC on Tuesday
17:27:15 <jlinkes__> frankbrockners: well we did have one successful run of it on the cengn pod, so it might be ready if we fix FDS-152 and FDS-154
17:27:33 <jlinkes__> frankbrockners: or we have a lucky run where those two won't manifest
17:27:58 <jlinkes__> frankbrockners: I'm planning on trying out virtual deployment tomorrow
17:28:06 <frankbrockners> let's see how the deployments on the opnfv pipeline go
17:28:23 <frankbrockners> based on that we can see whether we can make a case for C4.0
17:28:45 <frankbrockners> I'm also not sure whether there are other scenarios which would benefit from a C4.0
17:29:04 <jlinkes__> frankbrockners: we need https://jira.opnfv.org/browse/APEX-346 for the scenario to work - the old ODL won't work with new vpp/hc
17:29:33 <jlinkes__> frankbrockners: so when that is done we should things maybe passing in ci
17:29:45 <jlinkes__> we should see things*
17:29:57 <frankbrockners> trozet: could you get APEX-346 done?
17:30:37 <trozet> frankbrockners: it is already done, just waiting on the patch to finish CI for stable/colorado
17:30:49 <frankbrockners> trozet: sounds good. keeping fingers crossed
17:30:56 <frankbrockners> given that we only have  a few more min, let's quickly touch on the L3 work....
17:31:13 <frankbrockners> michal-cmarada: any quick updates/status on L3 work?
17:32:00 <michal-cmarada> I think that the update for routing model is not yet ready
17:32:09 <michal-cmarada> i need to check
17:32:38 <frankbrockners> michal-cmarada: thanks.
17:33:08 <frankbrockners> so let's hope that the HA scenario passes CI. If that is the case I'll start a discussion tomorrow on a potential C4.0....
17:33:32 <frankbrockners> any other final thoughts?
17:34:02 <frankbrockners> if that is not the case then we're done
17:34:24 <frankbrockners> thanks everyone
17:34:39 <frankbrockners> #endmeeting