<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Thank you Honza, I will give that a go and report back.<br><br><div>Kind regards,</div><div><br></div>Steven Iveson<div><br></div><br><div>> From: users-request@clusterlabs.org<br>> Subject: Users Digest, Vol 12, Issue 11<br>> To: users@clusterlabs.org<br>> Date: Fri, 8 Jan 2016 08:54:17 +0100<br>> <br>> Send Users mailing list submissions to<br>> users@clusterlabs.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://clusterlabs.org/mailman/listinfo/users<br>> or, via email, send a message with subject or body 'help' to<br>> users-request@clusterlabs.org<br>> <br>> You can reach the person managing the list at<br>> users-owner@clusterlabs.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Users digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: Passing and binding to virtual IP in my service<br>> (Andrei Borzenkov)<br>> 2. Re: Passing and binding to virtual IP in my service<br>> (Andrei Borzenkov)<br>> 3. Multiple Corosync Instance on a Single Host (Steven Iveson)<br>> 4. Re: Passing and binding to virtual IP in my service<br>> (Dejan Muhamedagic)<br>> 5. Pacemaker 1.1.14 - Release Candidate 5 (Ken Gaillot)<br>> 6. Parallel adding of resources (Arjun Pandey)<br>> 7. Re: Multiple Corosync Instance on a Single Host (Jan Friesse)<br>> 8. Help required for N+1 redundancy setup (Rishin Gangadharan)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Thu, 7 Jan 2016 14:14:17 +0300<br>> From: Andrei Borzenkov <arvidjaar@gmail.com><br>> To: Cluster Labs - All topics related to open-source clustering<br>> welcomed <users@clusterlabs.org>, Nikhil Utane<br>> <nikhil.subscribed@gmail.com><br>> Subject: Re: [ClusterLabs] Passing and binding to virtual IP in my<br>> service<br>> Message-ID: <568E4889.7000106@gmail.com><br>> Content-Type: text/plain; charset=utf-8<br>> <br>> 07.01.2016 13:09, Kristoffer Gr?nlund ?????:<br>> > Nikhil Utane <nikhil.subscribed@gmail.com> writes:<br>> > <br>> >> Of course, one way is to pass the same virtual IP configuration to my<br>> >> resource agent:<br>> >> "<nvpair id="ClusterIP-instance_attributes-ip" name="ip"<br>> >> value="10.206.1.253"/>"<br>> >> But this will be duplicate information and error-prone.<br>> >> There ought to be a better way. :)<br>> >><br>> > <br>> > Hi,<br>> > <br>> > You can use attribute references to avoid having to configure the same<br>> > value twice. It is documented here for the crmsh syntax:<br>> > <br>> > http://crmsh.github.io/man/#topics_Features_AttributeReferences<br>> > <br>> <br>> <br>> Is it crmsh-script only or it is also stored in CIB? How would it look<br>> like in CIB then?<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Thu, 7 Jan 2016 14:19:35 +0300<br>> From: Andrei Borzenkov <arvidjaar@gmail.com><br>> To: Cluster Labs - All topics related to open-source clustering<br>> welcomed <users@clusterlabs.org><br>> Subject: Re: [ClusterLabs] Passing and binding to virtual IP in my<br>> service<br>> Message-ID: <568E49C7.7090109@gmail.com><br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> 07.01.2016 13:42, Jorge F?bregas ?????:<br>> > On 01/07/2016 05:28 AM, Nikhil Utane wrote:<br>> >> So my question is, how to pass the virtual IP to my UDPSend OCF agent so<br>> >> that it can then bind to the vip? This will ensure that all messages<br>> >> initiated by my UDPSend goes from vip.<br>> > <br>> > Hi,<br>> > <br>> > I don't know how ping -I does it (what system call it uses) but I think<br>> > you'll have to implement that if you want your program to source<br>> > connection from a particular virtual IP.<br>> > <br>> > As far as I know, the way this is usually done these days is by creating<br>> > routes. Something like:<br>> > <br>> > ip route change 192.168.14.0/24 dev eth0 src 192.168.14.4<br>> > <br>> > <br>> >> Out of curiosity, where is this virtual IP stored in the kernel?<br>> >> I expected to see a secondary interface ( for e.g. eth0:1) with the vip<br>> >> but it isn't there.<br>> > <br>> > Well, in the old days we used to have a "virtual interface" (eth0:1,<br>> > eth0:2 etc) but the proper modern way is to use "virtual addresses"<br>> > within a single interface. The caveat is that you need to use the ip<br>> > command to show these virtual addresses (ifconfig is not aware of them):<br>> <br>> You can assign label to address which will then be visible in ifconfig; i.e.<br>> <br>> ip addr add 1.2.3.4/24 label eth0:foo dev eth0<br>> <br>> will actually make new address appear in ifconfig output as "eth0:foo"<br>> interface.<br>> <br>> > <br>> > ip addr show<br>> > <br>> > You'll see there the notion of a primary IP and secondaries. The system<br>> > will initiate connection from the primary by default (unless you specify<br>> > a route like the one above).<br>> > <br>> > HTH,<br>> > Jorge<br>> > <br>> > _______________________________________________<br>> > Users mailing list: Users@clusterlabs.org<br>> > http://clusterlabs.org/mailman/listinfo/users<br>> > <br>> > Project Home: http://www.clusterlabs.org<br>> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> > Bugs: http://bugs.clusterlabs.org<br>> > <br>> <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Thu, 7 Jan 2016 11:00:18 +0000<br>> From: Steven Iveson <sjiveson@live.com><br>> To: "users@clusterlabs.org" <users@clusterlabs.org><br>> Subject: [ClusterLabs] Multiple Corosync Instance on a Single Host<br>> Message-ID: <DUB122-W4354D4C47FA212AB457DEAB2F50@phx.gbl><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> Hi list,<br>> 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.<br>> Whilst I can change the UDPU port used by Corosync, a second instance (container) fails with a socket error. Here's the relevant logs:<br>> 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.<br>> Can this be overcome? Is there a way to specify a different socket?<br>> Many thanks in advance.<br>> Kind regards,<br>> Steven Ivesonsteve@iveson.eu@sjivesonBlogs: https://packetpushers.net/author/siveson/Books: http://www.amazon.com/Steven-Iveson/e/B00BIR04XM/07734 778 184 <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://clusterlabs.org/pipermail/users/attachments/20160107/b2cba53c/attachment-0001.html><br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Thu, 7 Jan 2016 17:29:25 +0100<br>> From: Dejan Muhamedagic <dejanmm@fastmail.fm><br>> To: Cluster Labs - All topics related to open-source clustering<br>> welcomed <users@clusterlabs.org><br>> Subject: Re: [ClusterLabs] Passing and binding to virtual IP in my<br>> service<br>> Message-ID: <20160107162925.GA19203@walrus.homenet><br>> Content-Type: text/plain; charset=utf-8<br>> <br>> Hi,<br>> <br>> On Thu, Jan 07, 2016 at 02:14:17PM +0300, Andrei Borzenkov wrote:<br>> > 07.01.2016 13:09, Kristoffer Gr?nlund ?????:<br>> > > Nikhil Utane <nikhil.subscribed@gmail.com> writes:<br>> > > <br>> > >> Of course, one way is to pass the same virtual IP configuration to my<br>> > >> resource agent:<br>> > >> "<nvpair id="ClusterIP-instance_attributes-ip" name="ip"<br>> > >> value="10.206.1.253"/>"<br>> > >> But this will be duplicate information and error-prone.<br>> > >> There ought to be a better way. :)<br>> > >><br>> > > <br>> > > Hi,<br>> > > <br>> > > You can use attribute references to avoid having to configure the same<br>> > > value twice. It is documented here for the crmsh syntax:<br>> > > <br>> > > http://crmsh.github.io/man/#topics_Features_AttributeReferences<br>> > > <br>> > <br>> > <br>> > Is it crmsh-script only or it is also stored in CIB?<br>> <br>> Everything ends in the CIB.<br>> <br>> > How would it look<br>> > like in CIB then?<br>> <br>> Normally, you don't need to know. I don't :)<br>> <br>> Thanks,<br>> <br>> Dejan<br>> <br>> <br>> > <br>> > _______________________________________________<br>> > Users mailing list: Users@clusterlabs.org<br>> > http://clusterlabs.org/mailman/listinfo/users<br>> > <br>> > Project Home: http://www.clusterlabs.org<br>> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> > Bugs: http://bugs.clusterlabs.org<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Thu, 7 Jan 2016 16:06:18 -0600<br>> From: Ken Gaillot <kgaillot@redhat.com><br>> To: Cluster Labs - All topics related to open-source clustering<br>> welcomed <users@clusterlabs.org><br>> Subject: [ClusterLabs] Pacemaker 1.1.14 - Release Candidate 5<br>> Message-ID: <568EE15A.3010505@redhat.com><br>> Content-Type: text/plain; charset=utf-8<br>> <br>> The source code for the latest (and possibly final) Pacemaker 1.1.14<br>> release candidate is available at<br>> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.14-rc5<br>> <br>> This release fixes a significant regression introduced in commit<br>> 12ca8bb: If a node had a fencing topology with multiple levels, only the<br>> last level would actually be used.<br>> <br>> This release also fixes misspellings in various log messages and updates<br>> the SNMP MIB.<br>> <br>> Everyone is encouraged to download, compile and test the new release.<br>> Your feedback is important and appreciated.<br>> <br>> If there are no significant issues found, this will likely become the<br>> final 1.1.14 release next week.<br>> <br>> P.S. The Pacemaker-1.1.14-rc4 tag was applied to the master branch by<br>> mistake, so please do not use it. :)<br>> -- <br>> Ken Gaillot <kgaillot@redhat.com><br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 6<br>> Date: Fri, 8 Jan 2016 12:04:01 +0530<br>> From: Arjun Pandey <apandepublic@gmail.com><br>> To: Cluster Labs - All topics related to open-source clustering<br>> welcomed <users@clusterlabs.org><br>> Subject: [ClusterLabs] Parallel adding of resources<br>> Message-ID:<br>> <CAKpWUY=fftNfj-AJSDn7SLfS+-GAH_baJ74zK-0vQ_yqTd+S3g@mail.gmail.com><br>> Content-Type: text/plain; charset=UTF-8<br>> <br>> Hi<br>> <br>> I am running a 2 node cluster with this config on centos 6.6<br>> <br>> Master/Slave Set: foo-master [foo]<br>> Masters: [ messi ]<br>> Stopped: [ronaldo ]<br>> eth1-CP (ocf::pw:IPaddr): Started messi<br>> eth2-UP (ocf::pw:IPaddr): Started messi<br>> eth3-UPCP (ocf::pw:IPaddr): Started messi<br>> <br>> where i have a multi-state resource foo being run in master/slave mode<br>> and IPaddr RA is just modified IPAddr2 RA. Additionally i have a<br>> collocation constraint for the IP addr to be collocated with the master.<br>> <br>> Now there are cases where i have multiple virtual IP's ( around 20 )<br>> and for failover time gets substantially increased in these cases.<br>> Based on the logs what i have observed is the IPaddr resources are<br>> moved sequentially. Is this really the case ? Also is it possible to<br>> specify that they can be added simultaneously, since none of them have<br>> any sort of corelation with the other ?<br>> <br>> If it's sequential what is the reason behind it ?<br>> <br>> <br>> Thanks in advance.<br>> <br>> Regards<br>> Arjun<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 7<br>> Date: Fri, 8 Jan 2016 08:47:50 +0100<br>> From: Jan Friesse <jfriesse@redhat.com><br>> To: Cluster Labs - All topics related to open-source clustering<br>> welcomed <users@clusterlabs.org><br>> Subject: Re: [ClusterLabs] Multiple Corosync Instance on a Single Host<br>> Message-ID: <568F69A6.3040609@redhat.com><br>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>> <br>> Steven,<br>> <br>> > Hi list,<br>> > 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.<br>> > Whilst I can change the UDPU port used by Corosync, a second instance (container) fails with a socket error. Here's the relevant logs:<br>> > 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.<br>> > Can this be overcome? Is there a way to specify a different socket?<br>> <br>> Corosync is not designed for running multiple instances. But using <br>> docker is different story (it's more or less VM, so there should be no <br>> problem).<br>> <br>> You can try to look what socket is already in use (for example use <br>> strace) but I believe main problem is shared /dev/shm. Can you try to <br>> mount fresh tmpfs to /dev/shm in docker container?<br>> <br>> Regards,<br>> Honza<br>> <br>> > Many thanks in advance.<br>> > Kind regards,<br>> > Steven Ivesonsteve@iveson.eu@sjivesonBlogs: https://packetpushers.net/author/siveson/Books: http://www.amazon.com/Steven-Iveson/e/B00BIR04XM/07734 778 184 <br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > Users mailing list: Users@clusterlabs.org<br>> > http://clusterlabs.org/mailman/listinfo/users<br>> ><br>> > Project Home: http://www.clusterlabs.org<br>> > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>> > Bugs: http://bugs.clusterlabs.org<br>> ><br>> <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 8<br>> Date: Fri, 8 Jan 2016 07:52:52 +0000<br>> From: Rishin Gangadharan <RG00423341@TechMahindra.com><br>> To: "'users@clusterlabs.org'" <users@clusterlabs.org><br>> Subject: [ClusterLabs] Help required for N+1 redundancy setup<br>> Message-ID:<br>> <596f7e307e23463f8b75d8dcd0af1087@BLREXCHMBX003.TechMahindra.com><br>> Content-Type: text/plain; charset="us-ascii"<br>> <br>> Hi<br>> Can anybody tell be ,how to configure corosync pacemaker with crmsh for active -active and N+1redundancy setup for kamailio.<br>> <br>> Thanks<br>> Rishin<br>> <br>> <br>> <br>> <br>> <br>> ============================================================================================================================<br>> 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.<br>> ============================================================================================================================<br>> <br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <http://clusterlabs.org/pipermail/users/attachments/20160108/ed6f7dc9/attachment.html><br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> Users mailing list<br>> Users@clusterlabs.org<br>> http://clusterlabs.org/mailman/listinfo/users<br>> <br>> <br>> End of Users Digest, Vol 12, Issue 11<br>> *************************************<br></div> </div></body>
</html>