Re: [gentoo-user] LTSP vs. Diskless Nodes

[Bob Sanders]

On Sat, 29 Oct 2005 09:45:22 +0100
Ryan Viljoen <ravilj@×××××.com> wrote:

> I am wondering what the difference is between using LTSP and Diskless Nodes
> is for creating a thin client network.
>
> http://www.gentoo.org/doc/en/ltsp.xml
> http://www.gentoo.org/doc/en/diskless-howto.xml#doc_chap3
>
> What would be the advantage of using LTSP. From what I have read (bearing in
> mind it is 3:41am [image: :(] ) the seem to offer the same thing.
>

Bear in mind this reply is from someone that has only done very, very, minor fooling
with LTSP, but has run a lot of diskless nodes - using IRIX.

LTSP is pretty much limited to x86.  It's also pretty well pre-defined, and pre-compiled.
The nice thing is the infrastructure is setup, which limits the amount of initial work that
needs to be done.  The downside is if you want clients other than x86, it tends to get
in the way.

The diskless howto, is pretty basic, and doesn't expand on more than what is needed to,
essentially, bootup the equivlant of a LiveCD.

Neither gives you the a client that is a full system booted off a diskless server.

Things missing, include - package management for the clients.  Full, filesystem support, though
LTSP is a bit easier to set up local swap and /tmp.

If you have limited needs - where the clients are pretty much static, I'd suggest the following
from ease of implementation and support - easiest to more work -

	- Puppy Linux on a USB stick
	- Gentoo LiveCD booted from a Catalyst created CD/USB/etc.
	- LTSP
	- Gentoo Diskless Howto
	- Gentoo Diskless cluster

For a more robust set of clients, where updates are easy and package management is in
effect, the following needs to be created -

	- a share tree where all clients use the same libs, read only (assumes the same arch).
		Typically, this includes - /usr /bin /sbin /lib.
	- a client tree and swap tree for each client - read/write.  Usually includes - /var, /etc.
		/home, /opt, /root.  It also includes links to the share tree - /usr /include /lib.
	- a set of scripts to manage all this in a sane manner on the server.
	- Package management becomes an issue, thus lots of work would be needed.  Typically,
		it's easier (less thinking, script creation) to provide clients with pre-compiled binaries
		and do package management in the background on the server, allowing clients
		read only access to see what is installed.

All-in-all, the easiest to implement is a RAM based distribution - Puppy Linux on a local r/w
device - USB stick, CF, SD, CD-r/w, DVD-ram, which can be booted from a diskless server,
then runs a a standalone unit.  It's easy to control what configuration and what aux packages
are available - easy to get additional packages.  The server can be a development/build system
for the clients.

Bob
-  
-- 
gentoo-user@g.o mailing list