| 1 |
Do you have reservations in the DHCP server? Or are the addresses truly |
| 2 |
dynamic? |
| 3 |
|
| 4 |
Dynamic, any "servers" that would require forwarding I just run on my server |
| 5 |
|
| 6 |
Are you relying on the client's UEFI implementation to provide the menu? |
| 7 |
Or are you using PXELINUX for the menu? (I know it's a nuance, but it |
| 8 |
is a difference.) The latter is much easier to centrally manage than |
| 9 |
the former. |
| 10 |
|
| 11 |
----Actually I haven't found the need for a menu at all, dnsmasq serves whatever kernel I have symbolically linked to the clients from their boot folder |
| 12 |
|
| 13 |
|
| 14 |
Does the UEFI stack get the same IP via DHCP that the OS gets via DHCP? |
| 15 |
Is there any sort of contention? Does UEFI release the IP before |
| 16 |
bootstrapping the PXELINUX image? Does the DHCP server view the |
| 17 |
multiple requests from the same client MAC as a form of a refresh? Or |
| 18 |
does it just offer the same IP? |
| 19 |
|
| 20 |
----I've had this same IP for months on this machine, I would assume the same for the others, as far as log messages from the server, it answers the same to each request from the same mac as far back I I've scrolled through |
| 21 |
|
| 22 |
|
| 23 |
|
| 24 |
Are all clients booting the same kernel, thus using the same command line? |
| 25 |
|
| 26 |
This means that clients must use DHCP to retrieve their IP address. |
| 27 |
|
| 28 |
---Yes all are booting the same kernel |
| 29 |
|
| 30 |
|
| 31 |
I guess there is some opportunity to return different files (PXELINUX |
| 32 |
image / config and / or kernel file) to different clients to get |
| 33 |
different behavior. But that might be more complexity than is necessary. |
| 34 |
|
| 35 |
Would you please share the kernel command line? I'm quite curious what |
| 36 |
the syntax is for NFS root. |
| 37 |
|
| 38 |
---- ip=dhcp root=/dev/nfs rootfstype=nfs rw nfsroot=ServerIP:/diskless/root,nolock,fsc,tcp,proto=tcp,vers=4,nfsvers=4.2,rsize=1048576,wsize=1048576 raid=noautodetect |
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
That makes me think that you are using a separate NFS export for each |
| 43 |
machine's root. |
| 44 |
|
| 45 |
---all the same root, I actually just have a custom bash script in local.d (openrc) for handling specifics for each node (adding dvd/blueray whatever to fstab) |
| 46 |
|
| 47 |
I have wondered about trying to do something similar (likely start in a |
| 48 |
VM) that has (at least) one machine specific export for things like |
| 49 |
/etc, but would then try to use a common export for things like /usr, |
| 50 |
/lib, and maybe /var. |
| 51 |
|
| 52 |
--- anything that conflicts like /var/log I just have as tmpfs on each machine |
| 53 |
|
| 54 |
|
| 55 |
- What is common between the diskless clients and what is unique. |
| 56 |
- PXELINUX image / config |
| 57 |
- Kernel image |
| 58 |
- NFS exports |
| 59 |
- What do your exports look like. |
| 60 |
- What sort of configuration you have in your DHCP server that's |
| 61 |
specific to this. |
| 62 |
- Any sticky reservations, possibly with machine specific parameters. |
| 63 |
- Other things that I can't think of at the moment. |
| 64 |
|
| 65 |
Thank you again. Very interesting stuff. |
| 66 |
|
| 67 |
--- https://wiki.gentoo.org/wiki/Diskless_nodes I got my start from reading that, well unless you count doing diskless with ubuntu in the way way past, my hard drive died then and I wasn't about to just use a livedvd unable to really install anything lol |
Archives