#opnfv-ovsnfv: Weekly Open vSwitch for NFV meeting (21st November 2016)

Meeting summary

1. Roll Call (mdgray_, 14:00:40)
   1. Mark Gray (mdgray_, 14:00:45)
   2. Tom Herbert (tfherbert, 14:01:52)
   3. "This conference room number is no longer active" (tfherbert, 14:02:04)
   4. "The organizer has not yet started the meeting" (tfherbert, 14:04:11)
   5. https://global.gotomeeting.com/join/686783405 (mdgray_, 14:05:05)
   6. https://www.irccloud.com/pastebin/z17hXq5w/ (mdgray_, 14:05:15)
   7. call in doesn't work" I will fire up the VM and try..." (tfherbert, 14:05:53)
   
   
2. Agenda (mdgray_, 14:11:16)
   1. Colorado should be in good shape (mdgray_, 14:11:43)
   2. Danube planning has not started. (mdgray_, 14:11:56)
   3. Chunghan Lee (lch, 14:12:01)
   4. Discussion point about the tsc regarding alignment to Openstack release schedule. (mdgray_, 14:12:33)
   5. Vote was put out to OPNFV community regarding this. (mdgray_, 14:13:01)
   6. Call for agenda items (mdgray_, 14:14:56)
   
   
3. Colorado Apex Results (mdgray_, 14:16:21)
   1. Need to compare fuel and apex results to ensure that there are no gaps on either side. (mdgray_, 14:17:26)
   2. Need to check what versions of ovs and dpdk will be pulled into Danube for Fuel and Apex (mdgray_, 14:20:20)
   
   
4. Discussion about project (mdgray_, 14:20:27)
   1. Some discussion about potentially merging ovsnfv project with kvm4nfv or fds (mdgray_, 14:20:53)
   2. In order to make a project with a theme around userspace performance or low-latency (mdgray_, 14:21:25)
   3. i.e. not just about one component (mdgray_, 14:21:36)
   4. No opnfv process exists for this, therefore this would need to be added (mdgray_, 14:21:52)
   5. No decision has been made on this just informal discussions (mdgray_, 14:22:34)

Action items

1. (none)

People present (lines said)

1. mdgray_ (29)
2. tfherbert (6)
3. collabot` (3)
4. lch (1)