Re: [ClusterLabs] newbie questions

2016-05-31 Thread Digimer
On 31/05/16 10:41 PM, Jay Scott wrote: > hooray for me, but, how? > > I got about 3/4 of Digimer's list done and got stuck. > I did a pcs cluster status, and, behold, the cluster was up. > I pinged the ClusterIP and it answered. I didn't know what > to do with the 'delay="x"' part, that's the thi

Re: [ClusterLabs] newbie questions

2016-05-31 Thread Jay Scott
hooray for me, but, how? I got about 3/4 of Digimer's list done and got stuck. I did a pcs cluster status, and, behold, the cluster was up. I pinged the ClusterIP and it answered. I didn't know what to do with the 'delay="x"' part, that's the thing I couldn't figure out. (I've been assuming the

Re: [ClusterLabs] newbie questions

2016-05-31 Thread Ken Gaillot
On 05/31/2016 03:59 PM, Jay Scott wrote: > Greetings, > > Cluster newbie > Centos 7 > trying to follow the "Clusters from Scratch" intro. > 2 nodes (yeah, I know, but I'm just learning) > > [root@smoking ~]# pcs status > Cluster name: > Last updated: Tue May 31 15:32:18 2016Last change: T

Re: [ClusterLabs] newbie questions

2016-05-31 Thread Digimer
On 31/05/16 04:59 PM, Jay Scott wrote: > Greetings, > > Cluster newbie > Centos 7 > trying to follow the "Clusters from Scratch" intro. > 2 nodes (yeah, I know, but I'm just learning) 2-Node is perfectly fine, you just need to be aware of a couple things (like prioritized fencing via 'delay="x"'

[ClusterLabs] newbie questions

2016-05-31 Thread Jay Scott
Greetings, Cluster newbie Centos 7 trying to follow the "Clusters from Scratch" intro. 2 nodes (yeah, I know, but I'm just learning) [root@smoking ~]# pcs status Cluster name: Last updated: Tue May 31 15:32:18 2016Last change: Tue May 31 15:02:21 2016 by root via cibadmin on smoking Stac

[ClusterLabs] (no subject)

2016-05-31 Thread DacioMF
Hi, I had 4 nodes with Ubuntu 14.04LTS in my cluster and all of then worked well. I need upgrade all my cluster nodes to Ubuntu 16.04LTS without stop my resources. Two nodes have been updated to 16.04 and the two others remains with 14.04. The problem is that my cluster was splited and the node

Re: [ClusterLabs] Three node cluster constraint

2016-05-31 Thread wd
You are right, my resource-stickiness settings are lost. after set it again, it's working now. On Tue, May 31, 2016 at 3:14 PM, Klaus Wenninger wrote: > On 05/31/2016 06:43 AM, wd wrote: > > I've do more searching, and found "crm_simulate -sL" tool, it says: > > > > native_color: vip-slave alloc

Re: [ClusterLabs] Three node cluster constraint

2016-05-31 Thread Klaus Wenninger
On 05/31/2016 06:43 AM, wd wrote: > I've do more searching, and found "crm_simulate -sL" tool, it says: > > native_color: vip-slave allocation score on node1: 100 > native_color: vip-slave allocation score on node2: 50 > native_color: vip-slave allocation score on node3: INFINITY might be due to re

Re: [ClusterLabs] How to use totem.interface.dynamic for corosync ?

2016-05-31 Thread wd
On Tue, May 31, 2016 at 3:08 PM, Jan Friesse wrote: > I'll try corosync 2.x >> So I need to edit configuration files on all node then call >> corosync-cfgtool -R or on one node is ok? >> > > You have to edit file on all nodes. Then call corosync-cfgtool -R on one > of the nodes. I see, thanks

Re: [ClusterLabs] How to use totem.interface.dynamic for corosync ?

2016-05-31 Thread Jan Friesse
I'll try corosync 2.x So I need to edit configuration files on all node then call corosync-cfgtool -R or on one node is ok? You have to edit file on all nodes. Then call corosync-cfgtool -R on one of the nodes. On Fri, May 27, 2016 at 6:28 PM, Jan Friesse wrote: hi, I use corosync wit