contrail-topology.conf is not configured with discovery section

[Vinoth Kannan Ganapathy]

contrail-topology.conf is not provided with DISCOVERY section by default. Hence in case of multi node setup, if the analytics configured on the host other than config node, contrail-topology service stuck at initializing

[csguser@contrail-node1 ~]$ ssh root@10.102.44.43 sudo contrail-status
root@10.102.44.43's password:
== Contrail vRouter ==
supervisor-vrouter: active
contrail-vrouter-agent active
contrail-vrouter-nodemgr active

== Contrail Analytics ==
supervisor-analytics: active
contrail-alarm-gen active
contrail-analytics-api active
contrail-analytics-nodemgr active
contrail-collector active
contrail-query-engine active
contrail-snmp-collector active
contrail-topology initializing (Discovery:Collector, Collector connection down)

== Contrail Database ==
contrail-database: active
supervisor-database: active
contrail-database-nodemgr active
kafka active