On 18/06/2013, at 1:46 PM, Jon Eisenstein <j...@animoto.com> wrote: > > On Jun 17, 2013, at 11:31 PM, Andrew Beekhof <and...@beekhof.net> wrote: > >> >> On 18/06/2013, at 7:19 AM, Jon Eisenstein <j...@animoto.com> wrote: >> >>> tl;dr summary: On EC2, we can't reuse IP addresses, and we need a reliable, >>> scriptable procedure for replacing a dead (guaranteed no longer running) >>> server with another one without needing to take the remaining cluster >>> members down. >> >> This is almost certainly the wrong approach. >> Have you tried their Virtual Private Network feature? This allows for the >> use of predictable IPs. > > We've previously decided against it due to the performance impact of IPSec > and the complications involved in managing the network routing against the > rest of our stack. It's something that we're investigating more, but the > timeline's a bit longer than our HA need here.
Ok. First question - what version of corosync? 1 or 2? Is cman in use? Which distro? I think 2 is the most likely to be made workable here. > If VPC becomes the only viable option, we may unfortunately have to abandon > the cluster approach altogether for now, which I'm trying to avoid. > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
