This is where virtualization can really help. You can test the entire new server in a virtual environment on one PC, place certain VMs on certain networks, etc. If you need to boot physical clients, if you have a dual port server attach a second network switch and run an LTSP server on each port. Or use VLANs.
Regards, On Wed, Sep 7, 2011 at 5:38 AM, Michael C. Robinson <plu...@robinson-west.com> wrote: > > The idea behind LTSP is to support thin clients and unfortunately, > redundancy is extremely hard to implement because the expectations > aren't compatible. There is no standard way to pick one server over > another during a network boot that I know of. > > Another issue, what specifically does one go the next version of LTSP > for? What is lacking in the current version that you need from the next > version? Sometimes, it is better to patch an older version that works > than it is to move to a newer version with new bugs. > > One option, you need a host OS on the server that doesn't run LTSP and > an emulated Linux environment(s) that does. This is a possible way to > fire up one server or the other so that the server you want is the one > you are running. Problem is, how do you test the new server while you > let your clients use the old? The immediate appeal of running LTSP on > the server under emulation is that you don't have to reboot. The > downside, well you have to have a hefty enough computer and you have to > understand emulation on top of understanding LTSP. If you can emulate a > subnet or if you can run a second subnet and a test client on that > secondary subnet... You should be able to emulate both LTSPs as long as > one runs on one subnet and the other runs on another subnet. DHCP could > be a problem though if you give out random IP addresses. Maybe on the > secondary subnet you can do static configuration??? So I'm saying do > static configuration on your test subnet and dynamic configuration on > your production subnet. Looks like this can work. > > BTW: If you have two physical subnets and you partition the servers > between them, both can be dynamically configured. Network cards are > pretty cheap these days and memory/hard disk space/processing power is > getting pretty cheap too. Only when you share media for two different > IP subnets does dhcp become problematic. > > > ------------------------------------------------------------------------------ > Using storage to extend the benefits of virtualization and iSCSI > Virtualization increases hardware utilization and delivers a new level of > agility. Learn what those decisions are and how to modernize your storage > and backup environments for virtualization. > http://www.accelacomm.com/jaw/sfnl/114/51434361/ > _____________________________________________________________________ > 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 -- Jay Goldberg | AvianBLUE Network Systems | (514) 667-9737 | http://www.avianblue.net/ ------------------------------------------------------------------------------ Using storage to extend the benefits of virtualization and iSCSI Virtualization increases hardware utilization and delivers a new level of agility. Learn what those decisions are and how to modernize your storage and backup environments for virtualization. http://www.accelacomm.com/jaw/sfnl/114/51434361/ _____________________________________________________________________ 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
