You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the present time one must construct the snap hostname by looking at the node and slot locations of the snap. There are several reasons why this is less than ideal. First it is an implicit algorithm, there is no guarantee that the correlator internally will adhere to this algorithm. ie if someone moves a snap from one node to another, they must change both M&C and the hostname in hera-snap-head:/etc/hosts . Second the query is slow and one of the reasons why the grafana antenna ownership table takes a while to load.
At the present time one must construct the snap hostname by looking at the node and slot locations of the snap. There are several reasons why this is less than ideal. First it is an implicit algorithm, there is no guarantee that the correlator internally will adhere to this algorithm. ie if someone moves a snap from one node to another, they must change both M&C and the hostname in hera-snap-head:/etc/hosts . Second the query is slow and one of the reasons why the grafana antenna ownership table takes a while to load.
@bhazelton would like to find a better way.
The text was updated successfully, but these errors were encountered: