tree 05e09b99fd55cef614fece07704a73721ccaf015
parent 0854c0427e37bc2ff824d31ebf2b0d0cd9f8c1a2
author Carmelo Cascone <carmelo@opennetworking.org> 1552072289 -0800
committer Carmelo Cascone <carmelo@opennetworking.org> 1552437808 +0000

Reduce the chance of apps triggering fake mastership events

The GeneralDeviceProvider works with device IDs with prefix "device:",
which is the same leadership topic prefix used by the Mastership
service. This caused an issue when any app was creating leadership
contests with topic deviceId.toString() (e.g. XConnectManager,
DefaultRoutingHandler, etc), as the resulting leadership events where
picked by the mastership service and propagated, because of the "device:"
prefix.

This patch minimizes the occurrence of such issue by choosing a more
specific leadership topic prefix for the mastership service. However,
the right solution would be to add isolation of leadership contests
between different services/apps.

Change-Id: I333fd9796a66bb4ca04cd2facd337ac57a2947b2