Categories

• Announcements

  Get the latest news on what's happening.
  167
  Topics
  691
  Posts

  

  Well done lads!
• General Topics

  View tutorials or talk about FOG in general.

  General

  Tutorials
  1905
  Topics
  15363
  Posts

  J

  I have about 8 Intel NUCs that have no hard disks, but I want to boot them off of some NFS shares and have them automatically start some workloads (e.g. Minecraft server). I have done something very similar to this with BeagleBones / Raspberry Pies. Those have flash memory where you can store the instructions for mounting and booting a NFS share. To my knowledge, a full scale x86 computer has no similar place where I can put these instructions. So I have been using FOG to push NFS bootstrapping instructions over PXE. I would say I even like this even better because I never have to worry about configuration on the NUCs themselves. Network, power, go! So far I have booted the ubuntu live cd. At this point, I could turn around and modify the rc.local of the live cd to mount another NFS share and start executing workload from there. There are several things that would not be ideal here. E.g. Any packages needed for workload must be reinstalled on every boot, and eventually I will run out of RAMdisk for temporarily installing packages. I realized when setting up boot for the live CD that effectively all I provided via FOG was a kernel binary, an initial ramdisk, and instructions to mount the NFS volume with the real OS. I hijacked the kernel/initrd from the usb installer to boot my NFS share instead of looking for the installer on local media. kernel tftp://${fog-ip}/xubuntu/18.04.2/vmlinuz initrd tftp://${fog-ip}/xubuntu/18.04.2/initrd imgargs vmlinuz root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/images/os/xubuntu/18.04.2/ locale=en_US.UTF-8 keyboard-configuration/layoutcode=us toram quiet splash boot || goto MENU Right now, these instruction point at the install cd for ubuntu and tell it to go into live mode without prompt. However, I don’t really want the live disk. I want to effectively mount the OS over network. I think it would be fairly easy to point this to an already installed NFS root of ubuntu (unique for every NUC). It might be as simple as extracting the squashfs. It is something I need to look into. I have a few specific questions that you might be able to help with. Can I bootstrap an NFS share some easier way? I.E. running the NFS mount instructions inside of FOG instead of inside a temporary kernel / initrd? How can I make this the default boot option for these systems in FOG? I have not been able to register these systems because they don’t have a hard disk. I do not know how to uniquely identify each of my NUCs from within the fog boot select screen. I need something that I can shove into the ‘nfsroot’ path above that is unique for every nuc. Is there some ${mac-address} or similar I can use here?
• Technical Help

  Get help with your FOG system.

  FOG Problems

  Hardware Compatibility

  Windows Problems

  Linux Problems

  Mac Problems

  General Problems
  9071
  Topics
  89075
  Posts

  

  @faresalandlos Yes you can. For FOG 1.4.4 you can use a Pi2. For FOG 1.5.x you need a Pi3 or Pi4 just because of the added CPU requirements.
• Developers

  Report bugs, request features, or get the latest progress.

  General

  Feature Request

  Bug Reports
  2023
  Topics
  19233
  Posts

  S

  Moved this topic to bug reports as this is definitely something we messed up in the code when @Fernando-Gietz added the filter option to the reports. @Rivybeast I am working on this and have pushed a first fix of the “Inventory Report”. If you are keen to give it a try you can simply download the latest file from github and put that into /var/www/html/fog/lib/reports/ on your FOG server (probably best to rename the existing file - e.g. to inventory_report.report.bak - so you can switch back to that easily just in case. I’ll work on the other reports as well before I merge the whole lot back into dev-branch.