Questions about FOG Storage Node Installation and Use
-
Hi,
I’ve been trying to understand how a FOG storage node works as I’m looking to implement one at a separate off-site campus so that we can image computers and install snap-ins at that campus without requiring the images and snapins to go across their internet/WAN link for each computer.
I’ve read some wiki guides and other forum questions but there are a few things I do not yet understand so I have some questions I’m hoping someone can answer please?
-
As the off-site campus is on a seperate IP range and subnet than the main campus, should this be OK from a FOG perspective? Our routers have rules in place to allow access between the different IP ranges and we can currently access RDP/Shares between campuses etc.
-
How will the computers at the off-site campus know to use the off-site campus storage node to install images and snapins? Do we just point their DHCP server to pxe boot from that storage node, and also point the FOG client on those computers to the IP of the storage node? This is one of the things I’m not clear about.
-
At the off-site campus (and on the main campus) the internet connection firewall/filtering is quite restrictive so it probably won’t allow the installation of FOG through that IP range and internet connection. In the past I have connected the FOG server up to a direct internet connection to install it, but that requires me to have it on a different IP range than what FOG will end up running on. Is it possible to have the Operating System (e.g. Ubuntu) running on a temporary IP address (e.g 192.168.10.1) to allow the FOG installation to work, and then during the FOG install when it asks you for the IP address I could specify what the actual proper IP address will become (e.g. 10.50.240.30)? Would this then setup all the FOG settings and other associated software to run off the proper IP address which I would change the server/Ubuntu install to after installation?
Thankyou for any help you can provide!
Derek
-
-
I just have to say your use case is exactly why FOG storage nodes were created.
- The off campus site can have a different IP address range. The networks need to be fully routable. The storage node needs to access the master FOG server using mysql, http, and ftp. As long as those protocols are allowed then the storage node will be happy at the remote site. If you have fog clients installed on target computers at the remote site, they will need to talk to the master FOG server over http to check in. Just be aware that in this future setup, you will only be able to capture images to the master fog server at your main campus. Storage nodes can’t normally be used to capture images, they are designed to be deploy only.
- You will install the location plugin on the master fog server. Then you assign target computers to each location so they know what fog server they need to speak to. At the remote campus you WILL set the boot server to the local fog server so the remote campus doesn’t need to pxe boot over the wan connection.
- Changing the FOG server’s IP address is problematic after FOG is installed. You may be better served if your campus has a internet proxy server or install a second interface in your FOG server where you can temporarily connect it directly to the intenet router for FOG installation and updates.
-
Thankyou @george1421 for the prompt reply and information!
Unfortunately we do not have direct access to our router and internet firewall/proxy so it makes it difficult to test and setup this kind of arrangement, or even to be aware of what ports/protocols are allowed. This means it will probably be trial and error for me trying to implement this FOG storage node.
I just have some further questions to clarify your answers if you don’t mind?
-
Do you happen to know what ports mysql, http and ftp would be running over. I believe our routers are probably setup to allow access to certain IP ranges and ports rather than protocols as such. Would the ports be mysql 3306, http 80 and ftp 21?
-
Is there a guide I can follow on installing the location plugin and the perhaps even the FOG storage node setup?
-
It may be difficult for me to setup a second network interface with alternate internet access at the off-site campus in this instance, and even if I setup and installed the FOG storage node at the main campus I would still need to use a temporary IP address arrangement and then change the IP once I moved it to the off-site campus. Also how would the FOG installation (and associated software) know which network card to use then? I believe in the past I changed the IP address of a FOG server after installation following some guides or advice from somebody, but I have since lost that information. Is it still possible to do this with the newer versions of FOG? If so, are there any guides I can follow on this?
Thanks again!
Derek
-
-
@Derek-Newbold ok here goes…
-
firewall: yes those ports are correct. With just a comment. Remember that a FTP session is a two way street. Port 21 is used as the command channel and the remote site will connect back to the master fog server over port 20. FTP is a well known protocol so your firewall guys should already know this.
-
Location plugin. I was going to say nope, we don’t have anything… but then I look on the FOG Project wiki page: https://wiki.fogproject.org/wiki/index.php/Location_Plugin
-
What fog has issues with is changing the imaging LAN ip address after FOG is installed. As far as FOG is concerned that second interface is invisible. So its address can be assigned by dhcp, there or not it doesn’t matter as long as when its connected the fog server can reach the internet to download any packages needed from the host OS’ repo. Now don’t get me wrong you “can” change the fog server’s IP address after fog is installed but there are a number of places you need to change and then rerun the installer to fix the rest.
-
