Can a FOG Server setup as a Storage Node serve tftp files?
-
Let me start by saying that we do NOT have pxe set up on our prod network, because reasons out of my control.
My plan is to have two identical servers running FOG, the only difference would be that the primary FOG server would be offline and serving DHCP/PXE on a local switch, while the secondary will be just an NFS server, on the prod network, that I use to image remotely, without PXE, but starting the ipxe chain using the custom FOG efi boot image on the hdd0 of the client workstations.
I will also find a way to sync the two servers so the images and hosts will be the same. But I believe if the secondary is a Storage node, I wouldn’t have to sync them. So can a Storage Node still serve tftp files so that I could boot off of it remotely?
-
@brakcounty said in Can a FOG Server setup as a Storage Node serve tftp files?:
I could always do a mysqldump export and import from the primary fog server to the secondary right?
Sure thing!
-
@sebastian-roth I could always do a mysqldump export and import from the primary fog server to the secondary right?
-
@george1421 said in Can a FOG Server setup as a Storage Node serve tftp files?:
The gotcha to this is the image definitions in the database are not sync’d between the master FOG server and the remote FOG server.
I may add a comment here. It’s not just the image definition but also hosts, groups, snapins and whatever else you use. All these things need to be replicated or manually created on the second server if it’s not installed as a storage node.
I am not saying this is bad or doesn’t work. Just want to mention it so you know what you are looking for.
-
@brakcounty said in Can a FOG Server setup as a Storage Node serve tftp files?:
I will also find a way to sync the two servers so the images and hosts will be the same. But I believe if the secondary is a Storage node, I wouldn’t have to sync them. So can a Storage Node still serve tftp files so that I could boot off of it remotely?
Yes if you setup the second node as a storage node and is reachable by a full fog server the you can use FOG’s internal sync.
The second option is to make the two full fog servers. Manually add the remote FOG server as a storage node (by definition) to the master FOG server. The FOG sync doesn’t care if the remote fog server is a storage node or full fog server it will sync the raw data between them. Understand this is a very manual process to setup. But then the raw data will sync. The gotcha to this is the image definitions in the database are not sync’d between the master FOG server and the remote FOG server. You can do this manually by the web ui to export and then import the image definition files. If you had a mind to you could use powershell or a bash shell and the API to export the image definitions and then import them too.
Lastly you can always use rsync to sync the raw data files between servers and then not need to mess with the fog ui configuration and fog replicator.
The only right answer here is the best fit for your org.
tftp:
The storage node has the full tftp files on it. So it can send pxe boot files to the remote computer. The problem you will have is the master fog server knows what interface its imaging network is on and it won’t send out the right information on its business lan interface. I think 2 independent FOG servers with file sync is a better solution.
