[Serdev] Group membership functions

[Jan Janak]

Greg, comments inline.

On 24-07 08:51, Greg Fausak wrote:
> Howdy,
> 
> I've been looking at the opposite, and wondered if there
> is an easy way to do it?

  Not out of the box, it requires some coding, which is actually on my
  todo list, but with low priority.


> What I'd like to do is completely eliminate the caching function
> in SER for all database related lookups.  For instance,
> lookup("location") and lookup("aliases").  Instead of using an
> in memory cache I'd like the SER server to go to the database everytime.
> 
> The database itself does a good job with disk caching, indexing, etc.
> The main reason for doing this is so that I can run many servers
> *without*
> the replication gear.

  Yes, that would be possible, but as I said, with some additional
  coding and changes to usrloc module.

> My overall plan is to use one of the swamp class C addresses I have.
> 
> 1) Create linux boxes with zebra on it (zebra.org), advertise
>    the class C to my internet provider.
> 2) Place these boxes all over the world, each of them has
>    the same IP address (and a unique secondary address).
> 3) Create a centralized database server running with replication.
> 4) All related services would go on ip addresses in the advertised
>    class C.  Like NAT translation, dns, etc..
> 
> Then, each operation hits the SER server, the central database is
> consulted if necessary.  If any of the SER servers goes down the
> UA is unaware, because BGP routing will deliver the request to the
> next closest server.

  But in this case the central database could be the single point of
  failure.

    Jan.