[Tilesathome] Two new ROMA...

[Mathieu Arnold]

+-le 24.11.2008 11:12:33 -0500, Matthias Julius a dit :
| Mathieu Arnold <mat at mat.cc> writes:
| 
|> I'm pleased to announce that there are now three ROMA servers, the new two
|> are located at frdrmd.roma.osm.phyrefile.com, api1.osm.absolight.net.
| 
| Great!
| 
|> 
|> There may be some rough edges, but both have been serving a few clients for
|> some time now.
|> 
|> There also is a haproxy (which may still need tuning, but, hey, can't know
|> that untill more people use it.) located on the last server, the simplest
|> way to use it would be to put :
|> 
|> API_ROMA = http://api1.osm.absolight.net:8080/api/%v/map?bbox=%b
|> 
|> in your tilesAtHome.conf.
|> 
|> If you don't want to change that old ROMA url, you could do :
|> 
|> APIServers = ROMA2,API,ROMA,XAPI
|> API_ROMA2 = http://api1.osm.absolight.net:8080/api/%v/map?bbox=%b
|> 
|> which would let you keep a backup in case the haproxy goes down and the
|> main API and the XAPI goes down too :-)
| 
| With more API servers available we should start thinking about some
| load balancing.  There is no point in having one server sweat and the
| others getting bored.
| 
| One way could be to have the client try all APIServers in random order
| instead of the order defined in the config.
| 
| Another way could be round-robin DNS which would not require the
| client config to be changed when a API server goes on- or offline.
| The drawback would be that the client would not know anymore which
| server it actually had tried which might make it more difficult to
| find out what server is going crazy.
| 
| Better ideas?

Hum, the beter idea is hum, to use the haproxy I configured, which spreads
the load between the three ROMA servers, which is the one I put in the
examples up there, no ?

-- 
Mathieu Arnold