Comment 3 for bug 1724474

Greetings, Looking at the specification for service management, and this proposal seems to focus around providing insight into what node maps to what conductor. The addition to it seems to be able to provide insight into the heartbeat table which is used for the hash ring. I don't necessarily see value in providing a declaration of if a conductor is absolutely up or down, however insight into if the node is considered to be part of the hash ring at that moment and then the resulting mapping information of conductor to nodes would provide a great deal of information to assist in troubleshooting.

I think the simplest route would be to provide an api endpoint that returns information of conductor to node mapping as calculated out of the hash ring based upon the current heartbeat data.

As this would touch the API, we will need a specification. I don't think this ties in well with service management since that would be a larger amount of work to provide uniformity, and would be operationally contentious. Of course, it entirely depends on how it is implemented, hence why a spec would be helpful.