Hi Guruchanran, Thanks for your work!
On Wed, Oct 21, 2015 at 2:53 PM, Gurucharan Shetty <shet...@nicira.com> wrote: > > + > +OVN provides network virtualization to containers. OVN's integration with > +Kubernetes works in two modes - the "underlay" mode or the "overlay" mode. > + > Could you help briefly describe what are the scenario, pros & cons of each mode? > > +We then create 2^(32-x) logical ports for that logical switch (with the > parent > +port being the VIF_ID of the hosting VM). On the worker node, for each > +logical port we write data into the local Open vSwitch database to > +act as a cache of ip address, its associated mac address and port uuid. > + > +The value 'x' chosen depends on the number of CPUs and memory available > +in the VM. > Well, this 'x' might be hard to pre-define. We might have to end up with reserving big enough subnets for a host to be able to host small pods. But that would mean waste of IP space. Of course it is not an issue in deployments where IP space is adequate. > +Since one of the k8 requirements is that each pod in a cluster is able to > +talk to every other pod in the cluster via IP address, the above > architecture > +with interconnected logical switches via a logical router acts as the > This ideal sounds good. But I have a concern about the scalability. For example, 1000 logical switches (for 1000 hosts in a cluster) connects to a single logical router. Would this scale? Thanks, Han _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
