21 Nov
2011
21 Nov
'11
10:53 p.m.
There are active DNS solutions you could use to provide failover/balancing. Alternatively,
I'd +1 Andy's suggestion of a loadbalancer. You can also do it with ldirectord,
varnish, and a number of other apps.
Sent from my mobile, apologies for brevity.
On 21 Nov 2011, at 20:09, Andy Smith <andy(a)bitfolk.com> wrote:
Hi Nigel,
On Mon, Nov 21, 2011 at 03:15:59PM +0000, Nigel Rantor wrote:
By redundancy here I am thinking load-balancing
web/db such that a single
server experiencing problems doesn't render the site unreachable.
On the BitFolk infrastructure side of things I've implemented
pacemaker/heartbeat (complex) and keepalived (simple), however
neither of these will work for customers since you can't move IP
addresses between VPSes.
I assume that VIPs aren't something that
people can set up without
network support.
Correct; anything which relies on moving an IP address currently
will not work, so that rules out most HA strategies.
If there is interest then we can add this ability. What would be the
requirements?
We can provide an API/facility to move IPv4 addresses and IPv6
prefixes between VPSes.
We can also do the HA side of things for you and provide some sort
of managed HAproxy[1] service (balance a TCP/HTTP between multiple
backends with dead backend removal).
Both of those would require you to have multiple VPSes and there
would be an additional charge for the service.
In terms of rapid scaling, you would be wanting to bring nodes
(VPSes) on and offline quickly, and BitFolk is just not set up to
handle that. If that is your goal you would probably want to look in
to a cloud provider from the start.
Cheers,
Andy
[1] http://haproxy.1wt.eu/
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users