we already have a ClusterRegistry available for holding this kind of metadata information (see ClusterRegistryFunctionalTest).
ATM it doesn't have a mechanism for reacting to remotely originated events - that is something that you need in order to register profiles that were added on remote nodes.
I guess we can work with this for this release, but I think it makes more sense to:
- extend the ClusterRegistry to also support notifications
- make this class use the cluster registry for storing the metadata
Would be nicer that way as we need a single mechanism to share metadata across cluster, and ATM we're using at least 3 repl caches:
- one for storing recovery info
- one for storing topology info for the HR server
- this one

how does that sound?