On Thu, Dec 08, 2016 at 06:27:48PM -0200, Rafael David Tinoco wrote: > Definitely. Since PCS is a package to *configure* corosync. I do agree > with your statement (above and bellow).
True, but there is another use-case where you install it on an existing cluster to get a web interface. In this case you don't want it to touch existing setup by default. > Unfortunately PCS fails silently for a lot of things, including > missing files (or even missing corosync binary, that is why I put > it as a "dependency" -> https://goo.gl/sZxest <https://goo.gl/sZxest>). Not sure how you got this because installing pcs all of the following get installed: pcs -> pacemaker -> corosync > Just trying to make PCS functional "by default" since now it will be > used as the clustering configuration tool for MSSQL Linux HA and they > need it configured by default (or capable of). I would argue that pcs is functional as all three daemons are running: * corosync * pacemaker * pcsd What is not functional is the cluster as a whole, but this will always require some manual configuration as it spans more than one host and we cannot handle that in packaging. In your case you would need to run something like: pcs cluster destroy pcs cluster auth node1 node2 pcs cluster setup --start --name cluster node1 node2 pcs resource create ... -- Valentin
