#opendaylight-coe: Weekly_meeting_01_17

Meeting summary

1. 1. Prem premsankar (premsankar, 16:04:54)
   2. faseelak (faseelak, 16:33:19)
   3. decision that L2 should be used within a node, and use L3 across nodes (faseelak, 16:34:46)
   4. discussion whether service can be mapped to vpn-instance (faseelak, 16:35:33)
   5. Mohamed explains about the iptables mapping problem (faseelak, 16:35:50)
   6. https://wiki.opendaylight.org/view/OVSDB_Integration:LoadBalancer (faseelak, 16:42:16)
   7. fkautz says we have to consider the implications on the approach we are deciding on modelling service (faseelak, 16:44:58)
   8. implications on architecture of kube proxy (faseelak, 16:45:14)
   9. kubeproxy has to satisfy any service that comes in (faseela, 16:48:50)
   10. Mohamed adds if we use kubeproxy logic, for service, will require more time, as we have to propose to k8s community (faseela, 16:50:05)
   11. fkautz also agrees that k8s community might not agree on the approach (faseela, 16:50:34)
   12. fkautz suggests to take a fork from k8s branch (faseela, 16:50:53)
   13. priority for this week is to get pod connectivity across nodes (faseela, 16:55:07)
   14. Summary of the mapping (premsankar, 16:59:03)
   15. K8S Namespace = VPN Instance (premsankar, 17:00:23)
   16. PODS is known by ELAN interface, VPN interface (premsankar, 17:01:37)
   17. Each node gets CIDR/16 and PODS belonging to different namespaces gets IP address from this node's IP address range (premsankar, 17:04:45)
   18. Service mapping still needs to be discussed and the issue of making OVS work with IP tables is an issue (premsankar, 17:06:49)

Action items

1. (none)

People present (lines said)

1. faseelak (9)
2. premsankar (8)
3. faseela (5)
4. odl_meetbot (3)