Let Analytics services connect to any collector based on discovery
Presently, the analytics services such as analytics-api, query-engine,
snmp-collector and topology always connect to local collector. If the
local collector service is down, then these services do not connect to
other active collector service, if present.
Side-effect of this behavior:
If the collector service is down, then the PRouterEntry UVEs and the
PRouterLinkEntry UVEs originated by the snmp-collector and the topology
service respectively would be missing from the /analytics/uves/prouter
output.
Fix:
analytics-api, query-engine, snmp-collector and topology should get the
collector list from the discovery service instead of connecting to the
local collector service.
Reviewed: https:/ /review. opencontrail. org/16014 github. org/Juniper/ contrail- controller/ commit/ 90a75d502717195 d90bef2766ecc2c 1bda54450f
Committed: http://
Submitter: Zuul
Branch: master
commit 90a75d502717195 d90bef2766ecc2c 1bda54450f
Author: Sundaresan Rajangam <email address hidden>
Date: Thu Dec 24 21:01:19 2015 -0800
Let Analytics services connect to any collector based on discovery
Presently, the analytics services such as analytics-api, query-engine,
snmp-collector and topology always connect to local collector. If the
local collector service is down, then these services do not connect to
other active collector service, if present.
Side-effect of this behavior: uves/prouter
If the collector service is down, then the PRouterEntry UVEs and the
PRouterLinkEntry UVEs originated by the snmp-collector and the topology
service respectively would be missing from the /analytics/
output.
Fix:
analytics-api, query-engine, snmp-collector and topology should get the
collector list from the discovery service instead of connecting to the
local collector service.
Change-Id: I62074e8516f4e7 eb88ac1d1c72706 7e87578794f
Partial-Bug: #1528770