Bruce, It is great to hear that salt is reporting status from all the nodes in the cluster. Let me see if I understand your question: You want to know what conditions cause us to recognize a working cluster? see https://github.com/ceph/calamari/blob/master/cthulhu/cthulhu/manager/manager.py#L135 https://github.com/ceph/calamari/blob/master/cthulhu/cthulhu/manager/manager.py#L349 and https://github.com/ceph/calamari/blob/master/cthulhu/cthulhu/manager/cluster_monitor.py Let’s check that you need to be digging into that level of detail: You switched to a new instance of calamari and it is not recognizing the cluster. You what to know what you are overlooking? Would you please clarify with some hostnames? i.e. Let say that your old calamari node was called calamariA and that your new node is calamariB from which are you running the get_heartbeats? what is the master setting in the minion config files out on the nodes of the cluster if things are setup correctly they would look like this: [root@node1 shadow_man]# cat /etc/salt/minion.d/calamari.conf master: calamariB If this is the case the thing I would check is the http://calamariB/api/v2/cluster endpoint is reporting anything? hope this helps, Gregory > On May 12, 2015, at 4:34 PM, Bruce McFarland <Bruce.McFarland@xxxxxxxxxxxxxxxx> wrote: > > Increasing the audience since ceph-calamari is not responsive. What salt event/info does the Calamari Master expect to see from the ceph-mon to determine there is an working cluster? I had to change servers hosting the calamari master and can’t get the new machine to recognize the cluster. The ‘salt \* ceph.get_heartbeats’ returns monmap, fsid, ver, epoch, etc for the monitor and all of the osd’s. Can anyone point me to docs or code that might enlighten me to what I’m overlooking? Thanks. > _______________________________________________ > ceph-calamari mailing list > ceph-calamari@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-calamari-ceph.com -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
