Re: [Pacemaker] pacemaker + cman - node names and bind address

2013-12-05 Thread Nikola Ciprich
Hello Digimer, and thanks for Your reply. I understand your points, but my question is about something a bit different.. example: I have two nodes, node1 (lan address resolves to 192.168.1.1) and node2 (lan address resolves to 192.168.1.2). connected using crosslink (10.0.0.1, 10.0.0.2). I'd

[Pacemaker] Why Pacemaker automatically creates constraints ?

2013-12-05 Thread Gaëtan Slongo
Hi ! I'm trying to configure a cluster using pacemaker 1.1 and corosync since 2 days (on Debian wheezy). Many of my current problems are related to the contraint creation. When I manually move a resource (or when a failback occurs) this kind of constraint is automatically created : location

[Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread James Oakley
I have Pacemaker 1.1.10 cluster running on openSUSE 13.1 and I am trying to get pacemaker-remote working so I can manage resources in LXC containers. I have pacemaker_remoted running in the containers. However, I can't seem to get crm configured to talk to the daemons. The only documentation I

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread emmanuel segura
did you try in this following way? primitive lxc_db0 ocf:heartbeat:lxc \ params container=db0 config=/var/lib/lxc/db0/config \ meta remote-node=db0 2013/12/5 James Oakley jf...@funktronics.ca I have Pacemaker 1.1.10 cluster running on openSUSE 13.1 and I am trying to get

Re: [Pacemaker] Why Pacemaker automatically creates constraints ?

2013-12-05 Thread Lars Marowsky-Bree
On 2013-12-05T17:12:01, Gaëtan Slongo gslo...@it-optics.com wrote: Hi ! I'm trying to configure a cluster using pacemaker 1.1 and corosync since 2 days (on Debian wheezy). Many of my current problems are related to the contraint creation. When I manually move a resource (or when a failback

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread Lars Marowsky-Bree
On 2013-12-05T08:57:48, James Oakley jf...@funktronics.ca wrote: Unfortunately, crm does not let me add it. I tried forcing it using crm_resource, but it's not working. It shows up now: primitive lxc_db0 @lxc \ params container=db0 config=/var/lib/lxc/db0/config \ meta

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread James Oakley
On Thursday, December 5, 2013 9:08:46 AM emmanuel segura emi2f...@gmail.com wrote: did you try in this following way? primitive lxc_db0 ocf:heartbeat:lxc \ params container=db0 config=/var/lib/lxc/db0/config \ meta remote-node=db0 I get the same behavior this way, unfortunately. -- James

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread emmanuel segura
Follow the Lars comment I think this is because crm doesn't know about the remote-node attribute 2013/12/5 James Oakley jf...@funktronics.ca On Thursday, December 5, 2013 9:08:46 AM emmanuel segura emi2f...@gmail.com wrote: did you try in this following way? primitive lxc_db0

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread James Oakley
On Thursday, December 5, 2013 9:21:18 AM Lars Marowsky-Bree l...@suse.com wrote: primitive lxc_db0 @lxc \ params container=db0 config=/var/lib/lxc/db0/config \ meta remote-node=db0 I think this is because crm doesn't know about the remote-node attribute. It can render

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread emmanuel segura
what happen if you try ping db0 from your physical host? 2013/12/5 James Oakley jf...@funktronics.ca On Thursday, December 5, 2013 9:21:18 AM Lars Marowsky-Bree l...@suse.com wrote: primitive lxc_db0 @lxc \ params container=db0 config=/var/lib/lxc/db0/config \ meta

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread James Oakley
On Thursday, December 5, 2013 10:21:01 AM emmanuel segura emi2f...@gmail.com wrote: what happen if you try ping db0 from your physical host? Yes, networking is fine. I can ping ssh, etc. and there is no firewall running. -- James Oakley jf...@funktronics.ca

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread Lars Marowsky-Bree
On 2013-12-05T10:10:08, James Oakley jf...@funktronics.ca wrote: That's why I used crm_resource to add it. If I dump the config with cibadmin, it looks consistent with the example here:

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread James Oakley
On Thursday, December 5, 2013 11:51:01 AM Lars Marowsky-Bree l...@suse.com wrote: However, the nodes do not show up in crm status output as in the examples in the documentation. I also tried creating a resource to run on a remote node, but it said the node didn't exist. Right. Do they

[Pacemaker] Reg. cone and order attributes

2013-12-05 Thread ESWAR RAO
Hi All, Can someone help me with below configuration?? I have a 3 node HB setup (node1, node2, node3) which runs HB+pacemaker. I have 3 apps dummy1, dummy2 , dummy3 which needs to be run on only 2 nodes among the 3 nodes. By using the below configuration, I was able to run 3 resources on 2

Re: [Pacemaker] Reg. cone and order attributes

2013-12-05 Thread Vladislav Bogdanov
06.12.2013 07:58, ESWAR RAO wrote: Hi All, Can someone help me with below configuration?? I have a 3 node HB setup (node1, node2, node3) which runs HB+pacemaker. I have 3 apps dummy1, dummy2 , dummy3 which needs to be run on only 2 nodes among the 3 nodes. By using the below

Re: [Pacemaker] Pacemaker 1.1.10 and pacemaker-remote

2013-12-05 Thread Vladislav Bogdanov
05.12.2013 19:57, James Oakley wrote: I have Pacemaker 1.1.10 cluster running on openSUSE 13.1 and I am trying to get pacemaker-remote working so I can manage resources in LXC containers. I have pacemaker_remoted running in the containers. However, I can't seem to get crm configured to talk

Re: [Pacemaker] Reg. cone and order attributes

2013-12-05 Thread ESWAR RAO
Thanks Vladislav. I will work on that. Thanks Eswar On Fri, Dec 6, 2013 at 11:05 AM, Vladislav Bogdanov bub...@hoster-ok.comwrote: 06.12.2013 07:58, ESWAR RAO wrote: Hi All, Can someone help me with below configuration?? I have a 3 node HB setup (node1, node2, node3) which runs