High Availability of a web server on a distributed cloud

Dave Cramer davecramer-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Mon Jan 14 19:58:55 UTC 2013


Well I don't want to use a single provider such as amazon. Which makes
things more difficult.

So the problem is essentially how to duplicate their elastic ip's

Dave Cramer


On Mon, Jan 14, 2013 at 2:51 PM, Fernando Duran <liberosec-FFYn/CNdgSA at public.gmane.org> wrote:

> If the application is HTTP a relatively simple solution is to use nginx as
> a load balancer
> http://blog.jsdelivr.com/2013/01/nginx-load-balancing-basics.html plus
> some hearbeat/monitoring to detect/alert when a node goes down.
>
> High availability is an excellent area to learn about
> networking/scripting/trade-off decisions etc but it's very hard to get
> right, esp. the first time. I think is very worth it using the cloud
> provider's solutions, like Amazon's (or Rackspace's) load balancers and
> autoscaling.
>
> ---------------------
> Fernando Duran
> http://www.fduran.com
>
>
> >________________________________
> > From: Dave Cramer <davecramer-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org>
> >To: tlug-lxSQFCZeNF4 at public.gmane.org
> >Sent: Monday, January 14, 2013 8:57:39 AM
> >Subject: [TLUG]: High Availability of a web server on a distributed cloud
> >
> >
> >It is relatively simple to distribute an application to a number of
> servers and use haproxy to switch ip's. What I can't figure out is how to
> switch make sure that the IP that points to ha-proxy can be moved easily if
> that machine fails ?
> >
> >
> >DNS round robin doesn't exactly work. I have a very limited understanding
> of BGP is it possible to do without BGP ?
> >
> >
> >
> >Dave Cramer
> >
> >
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20130114/5f8f941e/attachment.html>


More information about the Legacy mailing list