On Mon, Mar 27, 2017 at 07:43:24PM +0530, nusid...@redhat.com wrote: > From: Numan Siddique <nusid...@redhat.com> > > OVN implements native DNS resolution which can be used to resolve the > internal DNS names belonging to a logical datapath. > > To support this, a new table 'DNS' is added in the NB DB. A new column > 'dns_lookups' is added in 'Logical_Switch' table which references to the > 'DNS' table. > > Following flows are added for each logical switch which has atleast one > DNS entry in the 'dns_lookups' column > - A logical flow in DNS_LOOKUP stage which uses the action 'dns_lookup' > to transform the DNS query to DNS reply packet and advances > to the next stage - DNS_RESPONSE. > > - A logical flow in DNS_RESPONSE stage which implements the DNS responder > by sending the DNS reply from previous stage back to the inport. > > Signed-off-by: Numan Siddique <nusid...@redhat.com>
I think that Guru has a new design in mind but I have a few minor comments. The documentation mentions dns_lkup but we renamed it to dns_lookup. s/atleast/at least/ in a comment. You can simplify matches like "udp && udp.src == 53" to just "udp.src == 53", because matching on udp.src implies udp. Similarly for "ip && udp.dst == 53". _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
