|
I'll split this up into 2 parts
I have an lvs up & running with (using rr)
1 director
2 real servers (rs1 & rs2)
5 thin clients
in production i will go with wlc
so what i dont know is how to persist xdmcp connects
or even if i need to bother with it
right now a udp on 177 get rr'd to the next rs
& the client is happily connected
a quick ipvsadm -L shows no entry in the table for that connect
so in a wlc scenario does ipvsadm get its load info from mon running
on rs1/r2 ? or is there a better way to implement this
for a large scale scenarion say 400 distributed thin client
users what would you use for the backend real servers ?
my current pick is a rack of 1U p4 2.4ghz + 2gbz ram + 1 40gb hdd
all the realservers will have a shared raid0+1 nfs storage
the thin clients are running X & i will be using lbxproxy in an attempt
to cut down bandwidth & compress as much as possible
The users will mainly be using kde (koffice & konsole)
if anyone has any success stories on deploying lvs with xdmcp please reply
:)
& any suggestions on hardware & bandwidth usage would be more than welcome
regards
Pete
| 