Hi Kobus, so, the most interesting part is missing... :-)
I really hoped you will use a clonable resource agent running a haproxy instance on every node transmitting the current status via peer config, so that a switchover wouldn't loose state. In this scenario it would be interesting to see which IP resource is used as haproxy would try to bind to nonexisting IP. Probably a ClusterIP resource. Thank you anyway. Best regards Andreas Mock Von: Kobus Bensch [mailto:kobus.ben...@trustpayglobal.com] Gesendet: Montag, 24. Februar 2014 16:53 An: Andreas Mock; haproxy@formilux.org Betreff: Re: AW: Release Date of HAProxy version 1.5 Hi Andreas Sure. Here is my pacemaker config. I have tried to use the HAproxy resource, but for some reason it does not switch properly when one node fails. So for now, due to time constraints, I have written a script to check which noide is master and to start haproxy on that node and stop it on the slave. I will have another go at getting the HAproxy resource to work, unless of course there is someone on the list that is already doing it and is willing to share some info. node dc1ntgalb0101.domain.com node dc1ntgalb0102.domain.com primitive dc1ntgaip01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.110" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntgblv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.119" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntgilv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.125" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntgrlv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.122" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntgxlv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.116" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntiblv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.121" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntiilv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.127" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntirlv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.124" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntixlv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.118" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntmblv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.120" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntmilv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.126" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntmrlv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.123" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" primitive dc1ntmxlv01 ocf:heartbeat:IPaddr2 \ params ip="10.11.115.117" cidr_netmask="24" \ op monitor interval="30s" \ meta target-role="Started" colocation proxyservices inf: dc1ntgaip01 dc1ntgxlv01 dc1ntmxlv01 dc1ntixlv01 dc1ntgblv01 dc1ntmblv01 dc1ntiblv01 dc1ntgrlv01 dc1ntmrlv01 dc1ntirlv01 dc1ntgilv01 dc1ntmilv01 dc1ntiilv01 property $id="cib-bootstrap-options" \ dc-version="1.1.10-14.el6_5.2-368c726" \ cluster-infrastructure="classic openais (with plugin)" \ expected-quorum-votes="2" \ stonith-enabled="false" \ no-quorum-policy="ignore" rsc_defaults $id="rsc-options" \ resource-stickiness="100" On 24/02/2014 15:38, Andreas Mock wrote: Hi Kobus, I would be interested in your pacemaker agent config? Can you post your pacemaker snippet? What resource agent are you using? Thank you in advance. Regards Andreas Mock Von: Kobus Bensch [mailto:kobus.ben...@trustpayglobal.com] Gesendet: Montag, 24. Februar 2014 10:55 An: haproxy@formilux.org<mailto:haproxy@formilux.org> Betreff: Re: Release Date of HAProxy version 1.5 Hi I asked the same question and was advised to at least start testing. I have done so and can say that we have not experienced any downtime due to haproxy. I use it in conjunction with corosync/pacemaker. I would probably advise the same. Start testing now. Kobus On 24/02/2014 09:29, Haroon Asher wrote: Hello, We are using ha-proxy from past 3 years in our production environment. Now we are looking to use SSL Certificate on our site for which we will require haproxy version 1.5. Can you please let us know then when its release is planned or by when it will be stable enough to be used in production. I appreciate your response on that. Regards, Haroon -- Kobus Bensch Senior Systems Administrator Address: 22 & 24 | Frederick Sanger Road | Guildford | Surrey | GU2 7YD DDI: 0207 871 3958 Tel: 0207 871 3890 Email: kobus.ben...@trustpayglobal.com<mailto:kobus.ben...@trustpayglobal.com> [cid:image001.png@01CF3182.608AEAA0] Trustpay Global Limited is an authorised Electronic Money Institution regulated by the Financial Conduct Authority registration number 900043. Company No 07427913 Registered in England and Wales with registered address 130 Wood Street, London, EC2V 6DL, United Kingdom. For further details please visit our website at www.trustpayglobal.com<http://www.trustpayglobal.com>. The information in this email and any attachments are confidential and remain the property of Trustpay Global Ltd unless agreed by contract. It is intended solely for the person to whom or the entity to which it is addressed. If you are not the intended recipient you may not use, disclose, copy, distribute, print or rely on the content of this email or its attachments. If this email has been received by you in error please advise the sender and delete the email from your system. Trustpay Global Ltd does not accept any liability for any personal view expressed in this message. -- Kobus Bensch Senior Systems Administrator Address: 22 & 24 | Frederick Sanger Road | Guildford | Surrey | GU2 7YD DDI: 0207 871 3958 Tel: 0207 871 3890 Email: kobus.ben...@trustpayglobal.com<mailto:kobus.ben...@trustpayglobal.com> [cid:image001.png@01CF3182.608AEAA0] Trustpay Global Limited is an authorised Electronic Money Institution regulated by the Financial Conduct Authority registration number 900043. Company No 07427913 Registered in England and Wales with registered address 130 Wood Street, London, EC2V 6DL, United Kingdom. For further details please visit our website at www.trustpayglobal.com<http://www.trustpayglobal.com>. The information in this email and any attachments are confidential and remain the property of Trustpay Global Ltd unless agreed by contract. It is intended solely for the person to whom or the entity to which it is addressed. If you are not the intended recipient you may not use, disclose, copy, distribute, print or rely on the content of this email or its attachments. If this email has been received by you in error please advise the sender and delete the email from your system. Trustpay Global Ltd does not accept any liability for any personal view expressed in this message.
<<inline: image001.png>>
