[HELP]FOGServer Storage Node in 2 or more networks
Hello, i want a help with this scenario, in the matter of using FOG in 2 or more networks, specifically in the configuration of storage nodes. How should I configure my storage nodes (good practices and / or correct configuration) to work on more than one network? For example, make FOG work on computers in a LAN (vlan 0) and run on computers in a particular VLAN (vlan x).
My FOGServer actually now, have 2 interfaces configured, one in LAN network, and one in a VLAN network. I have 2 storage nodes configured, the vlan being marked as master. Also, other settings that need to be made? I believe this may be a future tutorial for other interested parties. Just to know the devs, I’m thinking of doing my college tcc on using FOGServer as an image server, maybe more specifically in school environments where multicasting is used, more of a network, etc … I’m still thinking about respect. xDD :DD
Best regards, Igor.
@igorpa2 Well with Normal FOG servers and Storage Nodes there are some things you need to keep in mind.
- Both Normal and Storage nodes and support pxe booting of clients. You would point the dhcp server scope to boot from the fog server that is closest to the client.
- The pxe booting client computer must be able to contact the full fog server during pxe booting to find out where it’s assigned fog server is located.
- Storage nodes must be in contact with the main fog server 100% of the time.
- All of the file transfers will happen between the client and the assigned storage node.
- You can only capture images to the master fog server. Storage nodes can only send images to target computes.
- For every computer that the FOG service is installed, it must be able to react the master FOG server to check in for waiting tasks.
- The Location plugin can be used to assign target computers to specific storage nodes. If the location plugin is not used then a random storage node will be assigned to the target computer.
The idea of a normal or master FOG server and storage nodes are to place storage nodes at remote locations behind sometimes slow WAN links. The remote clients would then load the pxe booting and imaging files from the local FOG server, not needed to pull the imaging across the slow WAN links. You can also use the master node and storage node on the same campus for load sharing if you are sending out a large number of unicast images to many clients. But then if you are imaging many clients at one time, multicasting is a better way to image.
Now, in our actual scenario, we are using in our computer labs, which are all in the same network. Fow now, we don´t have problems, but I was thinking about extending the use of fog in other scenarios, other machines on our campus, such as the work staff computers (which are inside our LAN network). This leads me to think about the ideal and correct use to make it work in two network environments. I know it works booting and running on both networks, but I believe not in the proper way, because who is outside my master node, can not deploy the image in the first boot, but in the second or third boot.
In fact it would not have more than one FOGServer installed on campus, only one only, but using it in more than one network inside the campus itself. I do not know if I understand right
Lets start out by asking, why do you feel you need more than 1 fog server on the same campus? There are valid reasons for doing such, but what are your reasons?
How many fog clients do you expect to deploy (i.e. computers where you install the FOG Service)?
Having 2 interfaces on a single fog server and expect both to support imaging is problematic. You successfully have 1 imaging nic and 1 or more management nics. That will work.