Hi, Just some thoughts.
On 6/15/07, John Lucas <[EMAIL PROTECTED]> wrote: > On Friday 15 June 2007 00:56, Lee Portnoff wrote: > > We have a building with 25 LTSP clients. We will open another location > > across town. I need to choose to design the network. > > > > A few topologies come to mind: > > (1) to keep servers in building A and login from building B. However, > > if there is a problem with the Internet, then all the computers in > > building B, are down. Perhaps you could contract a seperate, internet indepenant connetion from your local provider to connect building A and B, and use freenNX. How often do you expect the connection to go down? Would the users get by without the connection if it did go down? If all users are on the ltsp system, then you wouldn't need the internet connection. > > (2) to have servers in both buildings; but synchronization may be > > problematic. (And will take bandwidth) Are the users going to move between buildings? If not, each server has the homes of its local users. No need to sync. Shared files could be held just in building A. > > (3) to take a hybrid approach. Remote login as in topology (1); > > however, each night 'Copy/Rsync/Unison' building A to building B. This > > way in the event of Internet failure, building B can run locally. So > > there I have nicely synchronized files, offsite backup, low bandwidth > > usage. > > note: (mainServer has dual Xeon processor and 8gb ram w/ raid drives) > > You could sync your homes over to building B every night but only as a backup. If your connection goes down, change your home mount point (or something like that). This could also be your general backup policy too. We are starting to do something like this too. In building B most users are still using windows PC's, but some are using NX to open a session in building A. Four months running smoothly. Chris. > > So please cast your vote for 1, 2 or 3. Or make your own suggestion. > > many thanks. > > > > A bit more information might help: > > - Will the same users be utilizing both sites? > - How many LTSP users will be using this second (new) site? > - What data *need* to be synchronized? > - How much Internet bandwidth does each site have? > > While it should be possible to run a few NX sessions over the Internet to your > existing site, running LTSP sessions (using XDMCP or LDM) would not be > practical nor recommended; bandwidth requirements are too high and the > performance would be less than dismal. > > Realtime synchronizing/mirroring would suck up a significant amount of > (expensive) Internet bandwidth. Depending on what sort of data needs to be > synched and how often, rsync might be the better approach, particularly if > what needs to be synched are home directories since users should not be at > both sites at the same time. As for authentication, LDAP could be used, but > make sure that each site has it's own LDAP server (master at current site, > slave at new site) and use SSL/TLS for transport and address-restrict access > to the LDAP services. I assume you are using a VPN; you might also consider a > point to point (private) leased line to connect the two sites and eliminate > the VPN overhead and offload your Internet connections. > > In general I would limit inter-campus dependancy as much as practical. Having > been responsible for net services on two island campuses, I know you *will* > have network outages and anything you can do to allow both sites to operate > independently will make things better. > > -- > "History doesn't repeat itself; at best it rhymes." > - Mark Twain > > | John Lucas [EMAIL PROTECTED] | > | St. Thomas, VI 00802 http://mrjohnlucas.googlepages.com/ | > | 18.3°N, 65°W AST (UTC-4) | > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _____________________________________________________________________ > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss > For additional LTSP help, try #ltsp channel on irc.freenode.net > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
