1 |
Since I'm rambling now, guess I should do the rest of the memory download... |
2 |
|
3 |
One of the big problems with Linux diskless is it really doesn't scale well, it doesn't |
4 |
allow for clients to run multiple versions of the os, nor for different arch types to |
5 |
co-exist off one server of a different arch type. |
6 |
|
7 |
Additionally, a typical diskless setup exports /usr as a read only file system (which by |
8 |
most definitions, it is supposed to be). Lots of developers ignore this and never think |
9 |
about writing a small file into some /usr/... path during normal operation. Linux is |
10 |
usually much better at leaving /usr read only. But there is an argument that /usr/portage |
11 |
should be /var/portage. But */portage is pretty easy to move, so it's not a big deal. See - |
12 |
|
13 |
http://www.kurobox.com/online/tiki-index.php?page=InstallGentooBeta1 |
14 |
|
15 |
Under the heading - "Configuring Portage" |
16 |
|
17 |
Another not so well thought out diskless problem with Linux is all the setups use one kernel |
18 |
under /tftpboot or, at least the Gentoo Diskless guide uses /diskless, which makes it |
19 |
a bit movable, but then falls into showing the path as - /diskless/xxx.xxx.xxx.xxx (an IP number) |
20 |
instead of using the node name. The other problem, is they all assume only one kernel vs. a |
21 |
kernel for each host. |
22 |
|
23 |
For a good idea of how a robust diskless setup should be done, please see - |
24 |
|
25 |
http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0650&db=bks&srch=&fname=/SGI_Admin/Diskless_AG/sgi_html/pr01.html |
26 |
|
27 |
The SGI IRIX Diaskless Workstation Administration Guide. |
28 |
|
29 |
So here's a general overview of how a robust diskless infrastructure should be done - |
30 |
|
31 |
- The server should be capable of supporting multipe arch types, even OS types, as |
32 |
long as the NFS' are compatible. |
33 |
- The diskless trees should be capable of being moved to other drives or even servers. |
34 |
- Clients should be known by host name, not IP. The server's /etc/hosts, /etc/resolv.conf |
35 |
should define all that's needed for a client to operate, thus can simply be copied, intact, |
36 |
to each client's /diskless/client-name/etc. |
37 |
- Common files across clients, should reside in common share trees, which are exported read |
38 |
only. |
39 |
- Clients should be capable of operating as full systems, minus having a local disk. |
40 |
- A set of wrapper scripts is needed to allow for package management of share trees |
41 |
and client trees. |
42 |
- Client system management, excluding package management, should be done on the |
43 |
diskless client. |
44 |
- DCHP providing is reserved to the diskless server. Nothing says it can't also provide |
45 |
general DHCP support for other systems beyond the diskless clients. |
46 |
- Diskless nodes should be capable of having attached storage, even shared mounts |
47 |
from NAS and SAN systems. |
48 |
- In a production or a secure environment, diskless should be robust enough to allow |
49 |
changing it on a daily basis - swapping drives out to meet changing needs of visiting |
50 |
clients while still giving access to shared storage. (Linux is not robust in this aspect.) |
51 |
|
52 |
fwiw, here are the weekly diskless things I and my piers do with diskless - |
53 |
|
54 |
Regularly run a 16P O3K booted diskless off a 2P O350 server under IRIX, along |
55 |
with other nodes - some O2s running under a different share tree, and a Voyager |
56 |
system (two pipe Gfx visualization system) booted across multiple sub-nets. |
57 |
|
58 |
Do a weeky update of IRIX on 3 diskless servers and run long term testing - >110hrs, |
59 |
max load on 11 clients of mixed arch types. btw - these servers are all on the same sub-net. |
60 |
|
61 |
Do daily booting and installs via a diakless boot of new Linux kernels on ia64 systems via |
62 |
a fileserver running Gentoo. The systems install kernels and other Linux updates via diskless |
63 |
network boots, then reboot up as regular systems and run automated system testing. |
64 |
|
65 |
Bob |
66 |
- |
67 |
-- |
68 |
gentoo-user@g.o mailing list |