Address agent review comments - arp module
Address agent review comments - pkt
Delete VRF state upon clearing all ARP entries when VRF is deleted
Use upper_bound instead of iterating thru arp cache
* Add a command line option to assert upon vrouter returning an error for
  come operation
Bug: 2688
This bug deals with migrating data when upgrade happens. This fix
initially takes care of 1.3-1.4 data upgrade required. It moves the contents
of the old index table in 1.3 to the new index table in 1.4
Run over each row-key in the index table.Lookup for the flow info in the
FlowRecord table and insert the information in the new table. After
update truncate the old tables.
The db-utils take oldversion as its argument and runs through a chain of
upgrade functions to move the data.
Merge pull request #590 from Juniper/sundar_qe_ut

fix build break in query_engine/test
use the iterator to deleted ARP entry in DeleteArpEntry
Merge pull request #533 from haripk/master

Address agent code review comments
Minor code restrucutre
Rename AgentRouteEvent to Event and move it under VnswInterfaceListener class
Rename VnswIntfState to State and move it under VnswInterfaceListener class
Merge pull request #591 from praveenkv/master

Minor code restrucutre
Removing a redundant declaration
Changes to check for wrong version number as input
Get the version from contrail-analytics-venv
Merge pull request #589 from Juniper/arvindv-upgrade_script

Bug: 2688
Test subscribe/unsubscribe to two different incarnations of instance.

The first subscribe/unsubscribe are processed after the table has been
marked as deleted but has not yet been destroyed. The second subscribe
is received before the table and instance have been destroyed. Later,
the old table and instance are destroyed and new incarnations created.
The subscribe needs to happen on the new incarnation.
Merge pull request #592 from Juniper/nsheth_xmpp_deferq

Test subscribe/unsubscribe to two different incarnations of instance.
Comment the code and re-order functions into groups
Change to do LPM check while looking up a route from Floating-IP
- prefer local route over route from Floating-IP if LPM match
  against local route.
- prefer Floating-IP over local route for same prefix length
- prefer Floating-IP fip1 over fip2 based on vrf_name and addr.
Merge pull request #595 from praveenkv/master

Comment the code and re-order functions into groups