@george1421 I’m curious how you’re making the clients get said drivers from the storage nodes ? It’s exported as read-only via NFS and the other available option without any changes is FTP.
You could use a secured Samba share for this… There is a script that will do it for you on Fedora/CentOS here: https://forums.fogproject.org/topic/5145/script-to-install-samba-with-settings-for-fog
@george1421 I think that setting is hard coded… if there’s nothing to replicate, it will just check and then disconnect. It’s not resource intense.
Also, you could just turn off the FOGImageReplicator… Enable it on boot for safety, but if you don’t want it to check (which is odd), you could just turn it off after boot.
I think the replication looks in the database to see what needs copied… Not positive on this, but some work has been done in this area recently.
You could create a fake image with it’s path set as drivers to check if this is the case.
EDIT: Confirmed that the DB is consulted, and that creating a fake image with the path you want replicated would work.
First thought, figure out how to make the FOG Server return the storage node you want.
Take a look at this function:
I think if you can figure out how to pass in an IP address (and maybe subnet mask) to this, you can add logic to select the storage node you want.
The hard part will be figuring out how to pass in the IP address / subnet mask all the way from the unregistered host to the FOG Server and into this function. The easy part is adding a bunch of logic in here to return the node you want.
This link below is for USB devices, but it shows how the request is made and parameters are passed back. You could modify this to pass your IP, subnet, and whatever else to the fog server:
Notice that it writes to this file: /tmp/hinfo.txt
You would add lines somewhere in here to get the IP / subnets from the request that the host makes:
And you would pass that IP / subnet information into that optimal storage node function here somewhere:
Second thought, hack the storage node selection into a custom FOS build
Checkout this spot, it may have potential:
Another thought here is to look at how the Capone plugin sets this stuff. The script is called here:
And this is the file that gets executed, you see it sets a storage node IP, among other things:
https://github.com/FOGProject/fos/blob/c0238723ce381b5cd0340932086b10d47e79e26b/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.capone#L108
Third thought, postinit scripts
The method @george1421 suggested seems promising, but I am unsure how the postinit script would make changes to environment variables that will persist after the postinit script ends. If you could solve that somehow, this seems like the easy path.