=================================================================== #opnfv-ovsnfv: Weekly Open vSwitch for NFV meeting (March 7th 2016) =================================================================== Meeting started by mdgray at 13:01:14 UTC. The full logs are available at http://ircbot.wl.linuxfoundation.org/meetings/opnfv-ovsnfv/2016/opnfv-ovsnfv.2016-03-07-13.01.log.html . Meeting summary --------------- * Roll Call (mdgray, 13:01:21) * Mark Gray (mdgray, 13:01:24) * Billy O'Mahony (billyoma, 13:01:39) * Simona Coppola (Simona_, 13:01:48) * Agenda (mdgray, 13:05:14) * LINK: https://etherpad.opnfv.org/p/ovsnfv-meet (mdgray, 13:05:16) * C-Release Planning (mdgray, 13:06:20) * Draft C-Release backlog is on Wiki (mdgray, 13:08:43) * Simona will send out an e-mail with the details (mdgray, 13:10:08) * ACTION: Everyone: Review the backlog to give any feedback. (mdgray, 13:10:51) * ACTION: Tom: Update the Apex feature list with key backlog items and to fix any mistakes. (mdgray, 13:11:21) * Tom Herbert (tfherbert, 13:12:40) * Release C milestone 1 is tomorrow (mdgray, 13:15:48) * Simona will drive this with feedback from committers (mdgray, 13:16:23) * .. and contributers (mdgray, 13:17:34) * Debra Scott has left Linux Foundation and OPNFV - may change a few things around release planning. (mdgray, 13:18:14) * Priority Path through OVS based on Requirements (Lead: Al Morton - 45 minutes) (mdgray, 13:18:39) * sorry to see Debra go. (tfherbert, 13:18:41) * Al presenting slides. Mark will put them up on the wiki. (mdgray, 13:20:01) * LINK: https://wiki.opnfv.org/_media/qos_mechanisms.pdf (mdgray, 13:26:46) * Al is outlining the current standards related to QoS (mdgray, 13:27:29) * This highlights the need for QoS (mdgray, 13:27:48) * Many of the requirements are for service quality i.e. end-to-end (mdgray, 13:28:31) * The eventual allocation to a virtual switch would depend on other equipment in the path, speed of light, etc (mdgray, 13:30:09) * Two class prioritization should make sense initially (mdgray, 13:38:21) * Initial implementation should focus on this. (mdgray, 13:39:03) * Further work could expand on this (mdgray, 13:39:18) * We can assume that traffic is already marked (mdgray, 13:40:23) * We need flexibility as to which field in the packet contains the priority information (mdgray, 13:41:31) * This could be programmed in a protocol oblivious way (mdgray, 13:42:50) * Need to map this to a priority as handled by the switch (mdgray, 13:43:30) * Tom noted that other vswitches have this type of functionality (mdgray, 13:47:06) * OVS architecture will make this tricky (mdgray, 13:49:25) * Al has outlined some observations previously made (mdgray, 13:49:37) * Is OpenFlow control required? (mdgray, 13:54:40) * Perhaps we should do a smaller prototype first? (mdgray, 13:54:56) * Similar control interface in OpenFlow for Packet_In messages (mdgray, 13:57:28) * Plan to follow up on this discussion at Hackfest (look for Al, Billy and Tom having heated discussion in front of a whiteboard!) (mdgray, 14:00:53) * This needs to be formally documented. If no one else volunteers, Mark can do this. (mdgray, 14:01:56) * Need vsperf tests to show the benefit of this (mdgray, 14:02:13) Meeting ended at 14:02:28 UTC. People present (lines said) --------------------------- * mdgray (41) * tfherbert (6) * collabot` (4) * Paul_ (1) * Simona_ (1) * billyoma (1) Generated by `MeetBot`_ 0.1.4