OVS vlan-port entries are deleted on tor-agent restart

[Praveen]

When ToR agent is restarted, we retain the logical-switch entries in the OVSDB. But, the vlan-port entries in OVSDB table are deleted and re-added. This is due to design constraint in handling vlan-port entries received in response to monitor request in OVSDB.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/8429
Submitter: Prabhjot Singh Sethi (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/8429
Committed: http://github.org/Juniper/contrail-controller/commit/b3a75380d05e1c339399d2dc172f97ba5ec4dce9
Submitter: Zuul
Branch: master

commit b3a75380d05e1c339399d2dc172f97ba5ec4dce9
Author: Prabhjot Singh Sethi <email address hidden>
Date: Wed Mar 18 12:47:40 2015 +0530

Audit Functionality for OVSDB

- Infra change to support stale entry creation in KSync
which cleanup up after the configured timer.
- test code to test ksync infra.
- removed monitor send wait logic and replaced with
audit functionality with stale entry infra
- Adding remote session ip to ovs peer info
- changing key of physical port to physical device, port
same as ovs schema, which also helps generating stale
entries for logical ports.
- deriving VrfOvsdbObject out of OvsdbDBObject to allow
creation of stale ovsdb vrf entries to accomodate
stale unicast mac remote entries.
- fix to delete UnicastMacRemoteTable on empty table cb
if object was scheduled for delete (with route table
still present), earlier it was cleaning up on route
table delete.

Closes-Bug: 1424036
Closes-Bug: 1417432
Change-Id: Ib24af4fe9da2e1babedadf0fa61358e81ddeba2f