Home Lab

balanga said:
What have you got on your Home Lab
Click to expand...
Protectli Vault FW6E with coreboot bios running opnsense bare metal.
Protectli Vault Pro VP6670 with coreboot bios running proxmox with shitload of LXCs and VMs.
Grandstream Switch GWN7816P.
Teltonika RUTC50 running stock firmware and serving as 5G network failover.
4 x Grandstream GWN7665 ceiling mounted access points all over the house.
Some Nokia garbage ONT provided by ISP with 10G internet.
Eaton 9SX UPS.
 
Big server and a pool of machines that boot via PXE (diskless).

Each physical machine can boot any of the OS installs based on what the server says, there is no fixed assignment.
 
cracauer@ said:
Big server and a pool of machines that boot via PXE (diskless).

Each physical machine can boot any of the OS installs based on what the server says, there is no fixed assignment.
Click to expand...

I've never done PXE before... can you talk a bit more about the basic setup? I guess the big server exposes boot disks, and the other machines point to them?
 
patmaddox said:
I've never done PXE before... can you talk a bit more about the basic setup? I guess the big server exposes boot disks, and the other machines point to them?
Click to expand...
No, the server in this setup doesn't export boot disk images (that would be iSCSI).

PXE is firmware that knows how to interpret a software loading location from a DHCP server. That location is on a tftp server. In the FreeBSD model a special FreeBSD program "pxeboot" is loaded from tftp. The DHCP answer had additional parameters passed. That is used to verklicker the "pxeboot" program where the root filesystem will be. It then accesses that root directory over NFS to load the kernel. It passed the root filesystem location to the kernel, which mounts it. At that point you have a bootable system, the kernel just calls init.

The Linux pxeboot sequence is slightly different.
 
You must log in or register to reply here.
Back
Top