FOG Portable
-
Hello,
i try to build a FOG server that I could move to different network.
I wonder it the “WEB HOST” and the “TFTP HOST” could be set automaticaly as the hostname of the OS. (already set manually as hostname instead of IP).
I have ethernet and wifi on the nano computer and both are DHCP.
How I could set route or something to say lan is for deploy (same range as current ip) and wlan is for the rest.Ex : my fog server ip is 192.168.0.73/24 and deploy works only on this subnet other IP (debian updates, fog updates, ntp, …) should use wifi.
Other point, could I set fog as DHCP server only if it doesn’t have lan ip to be able to deploy with a direct link to an other computer.
Thanks for your help
-
@jmeyer Myself and another form moderator (Wayne Workman) came up with the concept of a mobile fog deployment server. The concept is that you would load FOG on a portable device (laptop or mini computer) with all of the necessary items for image deployment. IMO if this was going to be a truly portable computer a laptop with the built in screen and keyboard would be a better option. If you functioning as a MSP wanted to sell an imaging service than the mini or micro computer would be a better choice.
So the concept of the mobile fog deployment server is that the portable computer would have a full fog system installed on it. To minimize setup the mobile deployment server will have its IP address assigned by the remote site’s dhcp server. In this case FOG would not be your remote’s site dhcp server but it would function as a dhcp client (more on this in a bit). The next part you need to address is how to get the pxe boot information in the remote sites dhcp environment. You will do that with dnsmasq configured in a proxy dhcp mode (I have a tutorial on how to set this up in fog in the tutorial section). In this mode the FOG server (dnsmasq) will only provide pxe boot details leaving the remote site’s dhcp server untouched. With this configuration once the mobile fog server is removed from the site no pxe booting information is left behind to cause the remote site’s issues.
The issue you will have is that because FOG’s configuration is intended to be static, having the fog server’s IP address being assigned by dhcp will cause the FOG server to fail to pxe boot, to fix that issue Wayne created a script to automatically update the statically defined fields in FOG to make the IP addresses a bit more dynamic (note this is a fog server issue and has nothing to do with the target network or computers) That script is here: https://github.com/FOGProject/fog-community-scripts/tree/master/MakeFogMobile Looking at it that script is 8 years old, I can’t speak to the suitability of that script with the current version of FOG. It may need to be tweaked, but that’s the beauty of opensource software, if it doesn’t do what you need, you can fix it yourself.
It is possible to create a mobile fog deployment server, and back in the day the one I used worked great. So it is possible to do with little effort.
