Then you should search how to DHCP Proxy or your current DHCP Server on how to specifiy the boot file.
Search for the term “DHCP Proxy” if your current DHCP Server can’t specify a boot file. :)
in an old Forum post I found a way to shedule replicating by disabling the two Services FOGImageReplication and FOGSnipInReplication. Since we have multiple locations and a limited upload WAN I wanted to ask you how can I control how much Replications can be done at the time? On our Internal testing I found out it checks if a replication needs to be done and start to replicate on every location at the same time.
Any Idea out there how to control that? 🤔
BTW: I changed IMAGEREPSLEEPTIME to 60, so that after enabling the service via CRON it only takes one minute until it starts replication. Is that correct? And what happens with the replication, wenn I stop it via CRON and systemctl, does it interrupt the replication process aswell or finish it?
Year I read the article and now watched the video.
IIUC it only uses this for the images that I created and NOT the self generated Boot entrys. But thanks for all the help. My next step is now to find out how to configure how often it should be replicated. I’ll have a look at it :)
@Sebastian-Roth Sorry for the late response!
I installed the location Plugin but tbh, I don’t understand how to use it :(
I’m using the latest version and NOT the dev branch.
one quick question to you: Are in the iPXE Menu settings more variables available as
The reason I’m asking is the following. I added some custom entries like the Live Mint boot, but since we have the different location, someone could then start this entry in switzerland and occupie all of our VPN Traffic while it loads all data via NFS. Not the best solution 😇
To “resolve” this issue I had two ideas: Either I’m creating users for every location and somehow restrict the acces to that menu (if thats possible) or I’m rsync the data to every storage node and edit the bootmenu somehow with a variable like
Does such variable exist?
@Gurf What is the exact error message? I’m a bit confused about your line:
Maybe the vmlinuz and initrd.lz are in the wrong location?
I set up the server, that every HTTP traffic gets redirected to HTTPS. My dumb mistake: I forgot to setup SSL on the NODE! So it looks like that because I used https://fog.xyz/fog it trys to reach the nodes via SSL as well! After setting up SSL on the node, Boom:
So sorry for directing you on a complete wrong path 🙈