14:02:07 #startmeeting Weekly Open vSwitch for NFV meeting (8th August 2016) 14:02:07 Meeting started Mon Aug 8 14:02:07 2016 UTC. The chair is mdgray_. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:02:07 The meeting name has been set to 'weekly_open_vswitch_for_nfv_meeting__8th_august_2016_' 14:02:19 #topic Roll Call 14:02:24 #info Mark Gray 14:04:09 #topic Agenda 14:04:36 #info Nothing special on the agenda. We will do status updates as we are getting close to Colorado release branching. 14:05:07 #info Michal Skalski 14:05:12 #info Are you starting up GoTo Meeting? 14:05:24 https://wiki.opnfv.org/display/SWREL/OVSNFV+Colorado+Release+Planning 14:08:17 #info Chunghan Lee 14:09:12 #topic Fuel update 14:09:37 #info Intel POD1 is fully deployed which allows for scenario testing 14:10:35 #info Fuel 9 OVS-DPDK plugin is currently not working. That is being debugged by Ruijing (Intel). 14:11:24 #info Believe the issue is due to update-alternatives is causing the non-dpdk version of ovs instead of the dpdk version 14:13:27 #info This worked about a month ago. The most recent iso does not work. Billy suggests that this is caused by recent changes in OVS which changes the command line parameters. Billy/Mark offer help to debug this issue. 14:15:43 #info Plan is to get CI (fuel-os-nosdn-ovs-noha) running by the end of the week. This test got pushed today! Great job @mskalski and @fzhadaev 14:16:57 #info If CI is pushed and plugin is complete no further code needs to be pushed for the August 15th Colorado branch date 14:17:11 #info Documentation will be required. Not sure when the date for this is. 14:17:42 #topic Apex update 14:18:19 #info @therbert is not here. Note that branch date for Colorado is August 15th. 14:30:38 #info Michal suggested that Ruijing's plugin needs to be updated to use update-alternatives for all packages 14:31:36 #info Billy/Mark suggest using older version of OVS plugin in this release to ensure that the ovsdb changes do not cause any unexpected issues. We would then fix this on the Colorado branch or a service release. 14:31:52 #endmeeting