====================================== #opendaylight-ovsdb: OVSDB weekly call ====================================== Meeting started by Madhu at 19:03:53 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-ovsdb/2014/ovsdb_weekly_call/opendaylight-ovsdb-ovsdb_weekly_call.2014-08-19-19.03.log.html . Meeting summary --------------- * Neutron L3 support (Madhu, 19:04:08) * LINK: http://dtucker.co.uk/hack/building-a-router-with-openvswitch.html dave_tucker’s blog on new L3 features (tbachman, 19:05:08) * existing pipeline had to be modified in order to support new L3 features (tbachman, 19:05:59) * Table 0 is a classifier, to determine which table to send to next (tbachman, 19:06:22) * Table 100 is ACLs (tbachman, 19:06:27) * Table 105 is for ARP Responder (tbachman, 19:06:35) * Table 5 is for L3 Rewrites (tbachman, 19:06:42) * Table 10 is for L3 Routing (tbachman, 19:06:48) * Table 15 is for L3 Forwarding (tbachman, 19:07:14) * Table 20 is for L2 Rewrites (L2 Tun Encap) (tbachman, 19:07:26) * Table 20 is for L2 Forwarding (tbachman, 19:07:39) * the DVR mechanism that is demonstrated will require an external access from every compute node (Madhu, 19:19:48) * LINK: https://gist.github.com/79503d5b3752e5dc64e7 (dave_tucker, 19:22:25) * Neutron security groups (tbachman, 19:23:34) * TCP flags are being used for state (tbachman, 19:25:24) * long term plan is OVS use of conn tracker (tbachman, 19:25:54) * LINK: https://github.com/dave-tucker/odl-neutron-drivers/blob/master/odldrivers/lbaas/driver.py skeleton LBaaS driver (tbachman, 19:39:48) * Trello Board (tbachman, 19:40:38) * Neutron security groups (revisited) (tbachman, 19:41:22) * The range feature for ports isn’t implemented yet, but individual ports work (tbachman, 19:42:03) * Madhu says that if there are any NXM requirements, let him know ASAP (tbachman, 19:43:07) * We allow specific ports inbound on TCP SYN (tbachman, 19:43:58) * the fields focused on are TCP Protocol, TCP port min/max, and IP Prefix (tbachman, 19:50:09) * networkstatic stayed away from using resubmit, in order to support HW platforms (tbachman, 19:53:14) * Pipeline discussion (tbachman, 19:53:30) * dave_tucker says a convention would be helpful so that services know where to put their rules in the pipeline (tbachman, 19:55:21) * There’s a question of where security groups should live (tbachman, 19:56:50) * Would they be better implemented in the beginning of the pipeline and use resubmit or should it be somewhere else in the pipeline (tbachman, 19:57:26) Meeting ended at 20:08:05 UTC. People present (lines said) --------------------------- * tbachman (38) * Madhu (8) * odl_meetbot (5) * dave_tucker (3) * networkstatic (0) Generated by `MeetBot`_ 0.1.4