[ClusterLabs] Passing and binding to virtual IP in my service
Hi, I have my cluster up and running just fine. I have a dummy service that sends UDP packets out to another host. Resource Group: MyGroup ClusterIP (ocf::heartbeat:IPaddr2): Started node1 UDPSend(ocf::nikhil:UDPSend): Started node1 If I ping to the virtual IP from outside, the response goes via virtual IP. But if I initiate ping from node1, then it takes the actual (non-virtual IP). This is expected since I am not binding to the vip. (ping -I vip works fine). So my question is, how to pass the virtual IP to my UDPSend OCF agent so that it can then bind to the vip? This will ensure that all messages initiated by my UDPSend goes from vip. Out of curiosity, where is this virtual IP stored in the kernel? I expected to see a secondary interface ( for e.g. eth0:1) with the vip but it isn't there. -Thanks Nikhil ___ Users mailing list: Users@clusterlabs.org http://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
Re: [ClusterLabs] Passing and binding to virtual IP in my service
On 01/07/2016 05:28 AM, Nikhil Utane wrote: > So my question is, how to pass the virtual IP to my UDPSend OCF agent so > that it can then bind to the vip? This will ensure that all messages > initiated by my UDPSend goes from vip. Hi, I don't know how ping -I does it (what system call it uses) but I think you'll have to implement that if you want your program to source connection from a particular virtual IP. As far as I know, the way this is usually done these days is by creating routes. Something like: ip route change 192.168.14.0/24 dev eth0 src 192.168.14.4 > Out of curiosity, where is this virtual IP stored in the kernel? > I expected to see a secondary interface ( for e.g. eth0:1) with the vip > but it isn't there. Well, in the old days we used to have a "virtual interface" (eth0:1, eth0:2 etc) but the proper modern way is to use "virtual addresses" within a single interface. The caveat is that you need to use the ip command to show these virtual addresses (ifconfig is not aware of them): ip addr show You'll see there the notion of a primary IP and secondaries. The system will initiate connection from the primary by default (unless you specify a route like the one above). HTH, Jorge ___ Users mailing list: Users@clusterlabs.org http://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
Re: [ClusterLabs] Passing and binding to virtual IP in my service
Aah. Got it. Forgot about the ip addr command. Cool. So now I have the option to bind as well as use route command. Kristoffer answered about using attribute references so I should be all set. Thanks Guys. On Thu, Jan 7, 2016 at 4:12 PM, Jorge Fábregaswrote: > On 01/07/2016 05:28 AM, Nikhil Utane wrote: > > So my question is, how to pass the virtual IP to my UDPSend OCF agent so > > that it can then bind to the vip? This will ensure that all messages > > initiated by my UDPSend goes from vip. > > Hi, > > I don't know how ping -I does it (what system call it uses) but I think > you'll have to implement that if you want your program to source > connection from a particular virtual IP. > > As far as I know, the way this is usually done these days is by creating > routes. Something like: > > ip route change 192.168.14.0/24 dev eth0 src 192.168.14.4 > > > > Out of curiosity, where is this virtual IP stored in the kernel? > > I expected to see a secondary interface ( for e.g. eth0:1) with the vip > > but it isn't there. > > Well, in the old days we used to have a "virtual interface" (eth0:1, > eth0:2 etc) but the proper modern way is to use "virtual addresses" > within a single interface. The caveat is that you need to use the ip > command to show these virtual addresses (ifconfig is not aware of them): > > ip addr show > > You'll see there the notion of a primary IP and secondaries. The system > will initiate connection from the primary by default (unless you specify > a route like the one above). > > HTH, > Jorge > > ___ > Users mailing list: Users@clusterlabs.org > http://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 > ___ Users mailing list: Users@clusterlabs.org http://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
Re: [ClusterLabs] [Q] crmsh release plan for pacemaker-1.1.14?
2016-01-07 17:21 GMT+09:00 Kristoffer Grönlund: > Keisuke MORI writes: > >> I/'Hi, >> >> 2016-01-07 16:35 GMT+09:00 Kristoffer Grönlund : >>> Keisuke MORI writes: >>> Hi, I would like to know if there is any plan of the new crmsh release schedule which cooperate with Pacemaker-1.1.14. The latest release of crmsh-2.1.4 does not work well with Pacemaker-1.1.14-rc4 because of the unmatched schema. # crm configure load update sample.crm ERROR: CIB not supported: validator 'pacemaker-2.4', release '3.0.10' ERROR: You may try the upgrade command ERROR: configure: Missing requirements # Regards, -- Keisuke MORI >>> >>> Hello, >>> >>> Yes, I am planning a new release of crmsh very soon. The development >>> version of crmsh should work well with 1.1.14, so I would recomend using >>> that for now. >>> >>> There are a few issues that I would like to investigate before the >>> release, but regardless I will release a new version soon. >> >> Great! >> I would look forward to it. >> >> Will it be 2.1.5 or 2.2.0 based on the master branch? >> I'm concerned that 2.2.0 seems require an additional dependency for >> python-parallax. >> > > I will release both 2.1.5 and 2.2.0. > > Yes, 2.2.0 will require python-parallax. There are packages for > python-parallax available on the OBS [1]. It is also installable via > PyPI [2]. > > 2.1.5 will be based on the current 2.1.4 branch will additional bug > fixes, and will not require python-parallax. > > [1]: > https://build.opensuse.org/package/show/devel:languages:python/python-parallax > [2]: https://pypi.python.org/pypi/parallax/ Thank you for your detailed answer! Everything is clear to me now. Regards, -- Keisuke MORI ___ Users mailing list: Users@clusterlabs.org http://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
[ClusterLabs] Multiple Corosync Instance on a Single Host
Hi list, I have a situation where I would like to run multiple instances of Corosync, each 'group' on a number of hosts, with each instance providing HA for a dedicated service, thus allowing for benefits around change control, risk management, service/environment separation and the like. The hosts in question run nothing but Docker containers, with the Corosync (+Pacemaker) containers using host mode networking. Whilst I can change the UDPU port used by Corosync, a second instance (container) fails with a socket error. Here's the relevant logs: Jan 06 13:47:55 [19] rancher-one corosync info[QB] server name: cmapJan 06 13:47:55 [19] rancher-one corosync error [QB] Could not bind AF_UNIX (): Address already in use (98)Jan 06 13:47:55 [19] rancher-one corosync info [QB] withdrawing server socketsJan 06 13:47:55 [19] rancher-one corosync error [MAIN ] Can't initialize IPCJan 06 13:47:55 [19] rancher-one corosync error [SERV ] Service engine 'corosync_cmap' failed to load for reason 'qb_ipcs_run error'Jan 06 13:47:55 [19] rancher-one corosync error [MAIN ] Corosync Cluster Engine exiting with status 20 at service.c:356. Can this be overcome? Is there a way to specify a different socket? Many thanks in advance. Kind regards, Steven ivesonst...@iveson.eu@sjivesonBlogs: https://packetpushers.net/author/siveson/Books: http://www.amazon.com/Steven-Iveson/e/B00BIR04XM/07734 778 184 ___ Users mailing list: Users@clusterlabs.org http://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
[ClusterLabs] Help required for N+1 redundancy setup
Hi Can anybody tell be ,how to configure corosync pacemaker with crmsh for active -active and N+1redundancy setup for kamailio. Thanks Rishin Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ___ Users mailing list: Users@clusterlabs.org http://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
[ClusterLabs] Parallel adding of resources
Hi I am running a 2 node cluster with this config on centos 6.6 Master/Slave Set: foo-master [foo] Masters: [ messi ] Stopped: [ronaldo ] eth1-CP(ocf::pw:IPaddr): Started messi eth2-UP(ocf::pw:IPaddr): Started messi eth3-UPCP (ocf::pw:IPaddr): Started messi where i have a multi-state resource foo being run in master/slave mode and IPaddr RA is just modified IPAddr2 RA. Additionally i have a collocation constraint for the IP addr to be collocated with the master. Now there are cases where i have multiple virtual IP's ( around 20 ) and for failover time gets substantially increased in these cases. Based on the logs what i have observed is the IPaddr resources are moved sequentially. Is this really the case ? Also is it possible to specify that they can be added simultaneously, since none of them have any sort of corelation with the other ? If it's sequential what is the reason behind it ? Thanks in advance. Regards Arjun ___ Users mailing list: Users@clusterlabs.org http://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