On 01/11/2017 10:10 AM, lejeczek wrote: > hi eveyone, > I have a simple, test setup, like this: > > $ pcs status > Cluster name: test_cluster > WARNING: corosync and pacemaker node names do not match (IPs used in > setup?) > Stack: corosync > Current DC: work2.whale.private (version 1.1.15-11.el7_3.2-e174ec8) - > partition with quorum > Last updated: Wed Jan 11 16:02:15 2017 Last change: Wed Jan 11 > 15:53:36 2017 by root via crm_attribute on work1.whale.private > > 3 nodes and 3 resources configured > > Online: [ work1.whale.private work2.whale.private work3.whale.private ] > > Full list of resources: > > Fencing (stonith:fence_xvm): Started work1.whale.private > virtualIP (ocf::heartbeat:IPaddr2): Started work2.whale.private > Website (ocf::heartbeat:apache): Started work3.whale.private > > Daemon Status: > corosync: active/enabled > pacemaker: active/enabled > pcsd: active/enabled > > > but it does not make sense (bare in mind a beginner talks) right? > How come pcs decided to have VirtualIP and Website are started on > different nodes? > And it actually did, virtuall IP pings but httpd is not there, indeed > running on another node. > What am I missing? > > many thanks, > L.
You may want to see "Clusters From Scratch": http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Clusters_from_Scratch/index.html especially sections 6.4-6.6 _______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org