Change ksync flow to use flow handle as part of the key, so on index change
we will delete the previous object with old index and create new with current
index.

Change-Id: I6f29b30c573739d69f4f23df391ec153689c31b4
Adding syslog support in contrail-log

Change-Id: I09f6620abed6c2013d6371d16fe218799ed45a33
Enable agent tests for CI (non flaky).
Remove build error for flaky test.

Change-Id: I88b3bbf94fd05d3c2953b6218cb426ae29d9fb4b
Initial checkin for contrail storage stats daemon [ review changes ]
1. added unit tests
2. renamed/restructured SConscript files
3. restructured setup.py
4. added stats-daemon.conf
5. added test packages in SConscript
6. modified storage_nodemgr.py based on review comments
7. added latency changes
8. added diff logic for read/write bytes/counts for gui
9. storage package added in alphabetical order
10. #common is removed from requirements.txt
11. default values are #'d in stats-daemon.conf
12. big functions are modified to sub function calls in nodemgr.py
13. argument parsing in nodemgr.py is done using argparse
14. more unit test cases added in test_storage_nodemgr.py
15. indentation done in nodemgr.py
16. storage node mgr name changed to storage stats mgr
17. entry point added in setup.py
18. removed stderr logging
19. try-except removed in storage-nodemgr.py for importing
    sandesh files
20. storage.sandesh disk name removed and uuid added similar
    to osd structure.
21. added (tags="") empty tag in storage.sandesh
Change-Id: Id78a11da6d9f89cf46da8236136d0b758f3ebf01
Loadbalancer class

Change-Id: Id787834fcfa6d723bf843a5cbcc41d057973935b
Generate the haproxy configuration

Change-Id: I02053792b7e133edf9a7fe667d92dcdba154089d
Fix concurrency issue in lifetime manager.

Some unit tests failed during TearDown when trying to access a
virtual method for a partially destroyed object.  One thread was
in the process of removing a dependent object's LifetimeRef from
the parent LifetimeActor's dependency list. This was happening
via the destructor for the dependent object.  At the same time,
the main thread was in the process of propagating Delete from the
parent LifetimeActor to it's dependents.

Fix is to perform propagation of delete from the LifetimeManager
task rather than doing it inline from the Delete method.  Notice
that this splits up delete propagation into multiple steps.  An
actor propagates delete to it's immediate children.  If a child
has a LifetimeActor it gets added to the LifetimeManager queue.
Further propagation happens when the child LifetimeActor itself
is processed from the queue.

This change broke some tests which expected that the delete is
propagated inline.  As an example, if the MemebershipManager is
stopped and has requests to process, and a routing instance is
deleted, the tables for the instance don't get marked deleted
as BgpServer::IsReadyForDeletion doesn't let the LifetimeManager
task process the queue.

Fixed this issue by adding a MayDestroy method to LifetimeManager.
Instead of not processing the LifetimeManager queue at all, we
now process the first item on the queue, invoking Shutdown and
PropagateDelete if needed, and then put the LifetimeActor back on
the queue if MayDestroy returns false.

Defined a BgpLifetimeManager class whose MayDestroy method calls
BgpServer::IsReadyForDeletion.

Change-Id: I6b5688f5362fbf5591c84c78f56e4a682cb95587
Make BGP state machine use short timers in tests.

Few tests such as rarget_peer_test used to fail occasionally because
bgp peers could not be established within the wait time of the test.

Make all such tests use the StateMachineTest class, which has short
timers. Remove duplicate definitions of StateMachineTest and move it
to bgp_server_test_util.h.

Rename StateMachineTest in state_machine_test to StateMachineUnitTest.

Remove unnecessary use of mock classes for BgpXmppChannelManager and
BgpXmppChannel in a few tests.

Change-Id: I53885053b673da1dcb0725b5d04e9ad00dd94caf
Converting contrail-status from shell script to python script. Adding the
file only now.. Once this is committed, will add this file to contrail-setup package..

Change-Id: Ib9ddd92b89753dd884b810247b1ef0e6f4c342a9
Closes-Bug: #1349980
The issue is when we process rabbitmq message for instance ip delete, we
access the virtual network. In case of the problem, the VN is deleted by
this time. Hence the exception is thrown in "dbe_delete_notification" function of InstanceIpServer.
Fix:
1. ip_free_notify should only free the ip from the subnet it already knows.
2. Even if the "dbe_xxx_notification" fails, inform the if map server.  This is to ensure that cassandra and if map are in sync.
3. Add logging for "dbe_oper_subscribe" exceptions. The error is critical and hard to debug without this error log.

Change-Id: I1851a3b6a3efd96f632db16a1a8e6ea23a1feda0
Fix svc_monitor tests by adding a missing arg

This commit d318b73fbab8f0c200c71adf642968a624a7db29
introduced a cluster_id arg but this arg is not
initialized in the test file.

Change-Id: I770e5f2c949afd408b8906439e711e7f619afa57
Fixing test case, adding default xml config and enable sub_node
in ip_perms.
moving test_integration from flaky to non-flaky test suite.

Change-Id: I86c7284485d39e90450d34c1e57622c2f521546e
Decrease the TCP keepalive idle time to detect peer-down event earlier.

Change-Id: I35e0ba5ed846562505c9ed0fad556a26de38380a
Bug 1341335: If service chain has been destroyed, delete the corresponding vrf assign rule. If all service chains have been destroyed for an interface, delete the whole table

Change-Id: I48cf2e3c256ebfefa2c264c96d83dc60a6d075d1
Merge "Converting contrail-status from shell script to python script. Adding the file only now.. Once this is committed, will add this file to contrail-setup package.."
Merge "Decrease the TCP keepalive idle time to detect peer-down event earlier."
Bug 1344233: Avoid crashing if virtual network cannot be read

Change-Id: I30543f33cc31b9190e4b6ed6e40dff90e0f80c72
Merge "Bug 1341335: If service chain has been destroyed, delete the corresponding vrf assign rule. If all service chains have been destroyed for an interface, delete the whole table"
Bug 1337457: Use vm name to fill device-id

Change-Id: I56756428f6a45b9fe747917af6ceb6aa8a8d3029
Raises the correct exception when adding interface to subnet

This fix changes the exception raised when trying to
add a router interface on a subnet while the
router already has a interface on that subnet.

Change-Id: Ic6034f1c1badf21ff6fafac0441de43857fd0e9f