Question about lvs architecture.

[Dan Baughman]

Basically we are going to cluster some cold fusion servers and I don't want
to pay the 10 grand Adobe wants for an enterprise license to do what we
want.  We have a lot of app's deployed that use a cookie stored on the
client in conjunction with the user's ip to access server side session
data.  To reimplement the apps we've deployed to access a db instead of the
session data would be considerable.

Looking at the persistent option, that seems to be exactly what I'm looking
for.




On 5/9/06, mike <mike503 at gmail.com> wrote:
>
> not sure how long you want to track the information, but you might be
> able to handle this with iptables and firewall marks. then you can
> group requests by any sort of iptables-configurable tracking (by
> port(s), ip ranges, etc...) - also i think there's a persistence
> configuration option in ldirectord (or is it keepalived, i always get
> them confused - or maybe both.)
>
> i don't understand the need though for session persistence like this;
> i'd expect a centralized session manager (msession for instance) or
> just using a central database for the information would suffice.
> that's how i've been doing it, not sure why everyone has all these
> unique requirements to make sure they can persist sessions across IP
> addresses and AOL proxies and such. seems overkill, i've never had a
> problem. of course, i don't know your specific application, but it
> sounds on the level of an HTTP request...
>
> On 5/9/06, Dan Baughman <dan.baughman at gmail.com> wrote:
> > Internally, ldirectord must make decisions about where to send what
> > connection request, right?  I want to implement a hash table to keep
> track
> > of where previous connections from an ip went, and send them to the same
> > server.
> >
> > Previously I was advised to use the CF Scheduler, can anyone elaborate
> > further on that before I start to look at the code?   I need this to
> > maintain that a user will have a persistent session with one user.
> >
> > Any sort of timeout is optional.  Once an ip gets a server it can always
> get
> > that same server.  I had previously thougth of giving the session a
> timeout,
> > but now I'm leaning towards just having it maintain the hash forever,
> and
> > I'll just restart the director deamon every night at  2 am (or never).
> >
> > Any pointers?
> > _______________________________________________
> > LinuxVirtualServer.org mailing list - lvs-users at LinuxVirtualServer.org
> > Send requests to lvs-users-request at LinuxVirtualServer.org
> > or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> >
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users at LinuxVirtualServer.org
> Send requests to lvs-users-request at LinuxVirtualServer.org
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>