Yes, i understand that thats the case from the code, what i would like to know however is the use cases of such policies... if anyone can explain them to me, or point me to a link/document i will appreciate it. (What i think is the switching between different physical entities and live migration but thats only my guess) and i wanted to understand how this works and if this is really the use case
On Thu, Aug 22, 2013 at 7:23 PM, Jesse Gross <je...@nicira.com> wrote: > On Thu, Aug 22, 2013 at 12:02 AM, Gal Sagie <gal.sa...@gmail.com> wrote: > > Hello everyone, > > > > I am new to OpenVswitch and would like to ask a fundamental question > > regarding the flow table. > > I looked the code and saw it has a 12-13 tuple matching key (unless i > miss > > understood) which consist of MAC's src and dst IP's , TCP/UDP ports, TOS, > > VLAN... > > > > What i am wondering is why is it not just L2 MAC's ? (with maybe support > for > > tunneling) > > Are these flow entries used for openvswitch support of "distirubition > > accross multipile physical networks" and live migration? > > (VM's on the same hypervisor cant have the same MAC's right? ) > > Open vSwitch (and OpenFlow) is not just an L2 switch. Since it's > possible to write policies against the upper layers, OVS needs to be > able to match on them. > -- Best Regards , The G.
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
