(imported topic written by MartinZ91)
Hey everyone,
Did someone already create a relevance which decides if the BESclient computer is the active/passive member of a cluster?
We want to deploy patches also to cluster environments. It is (our) good practice to install the patches on the passive node first, then fail over the cluster and install it on the now passive node.
We would need this not just for Windows, but for AIX, Solaris und Linux’s.
I know, that MS Clusters can be administered from the command line with the “cluster [/list]” command. The Unix’es could determine the active/passive state by looking to mounted file systems of some quorum disk. If I create tasks with such commands and store the results in a (client-local) text file, there is the risk, that relevance checking this text file later on and patching accordingly will see a incorrect cluster state, because in the time gap between the task execution and the relevance evaluation there has been a cluster fail over.
I would appriciate tipps from the community, before I run into develloping those task/relevance.
Thank You in advance, Martin