Changing my Fog Server to an isolated network
-
Hello All,
I have an existing fog on my current network. I am considering changing it over to an isolated network.
The Isolated network will have DHCP windows server.
My questions are how to change my existing fog server over to the isolated.
- Can I do this without losing all my images
- Can I simply just change the IP address associated with Fog Server or are there other steps involved.
Will I still need to use DNSMASQ or ProxyDHCP and what is the best way to convert it.
-
Do you want to put fog on an isolated network, or do you want to setup an isolated network just for imaging?
If you put fog on a network that can not reach the internet then you will not be able to update FOG as new versions are released.
But to answer your question, you will not loose your captured images that are already done.
Changing your IP address of the fog server is a bit complex, but Wayne did put together a script to manage the move. I would download these files: https://github.com/FOGProject/fog-community-scripts/tree/master/MakeFogMobile
- I would download those scripts first
- Change the ip address of eth0
- Update the FOG server ip address in /opt/fog/.fogsettings
- Run Wayne’s script or go through manually and update the IP addresses in fog settings and storage node settings, and then /tftpboot/default.ipxe and finally in your dnsmasq settings.
-
Here is what I am really trying to accomplished.
I have a fog server working great at headquarters, as I mentioned before in a previous post need I to service some machines that are branch locations versus bringing them down to headquarters.
I tried to setup a storage node but the replication over this slow network has been a daunting task.
So I thought maybe I will make another machine with all the images from headquarters to take on the go to this remote location and create a small network to accomplish it to prevent pulling those images over the network.
So I thought about creating an isolated network of 5 to machines and just imagine this way till our network is up to part. Since the remote location has their own subnet I was thinking to have DHCP running so that they could assign ip address out with the new image server scheme. So, I don’t have to take apart of the existing network or keeping changing the ip to accomplishing this.
So I guess my question is now, does this make sense to do it this way or is there an easier way to tackle all of this.
Thanks in advance for your help. -
@cnkpadobi IF it was me, I would just take and setup a small fog server (older desktop, intel nuc, raspberry pi3 <said with a squint>) to the remote location and set it up. No need to have an isolated network as long as your remote dhcp server points to the remote fog server and not the one at HQ, the remote computers will never know about the HQ fog server.
-
Ok awesome, that will work.
I would love to not do an isolated network but it seems that I will have an issue if I install the box with a static ip and then take it to another location I will have to keep changing the ip every new location correct? Also since they are connected via WAN how do I ensure it will pick up the right server every time. When I was testing storage node here at the HQ I was able pickup the storage node in one of the remote locations.
-
@cnkpadobi Well an isolated network means that you will have to move the device each time you want to image it. Doing that remotely means you need capable on site people to move the equipment. That’s not always possible.
What you want to do here is have 2 independent fog servers. If you have dhcp setup so that each site only talks to its own fog server then there will not be any cross WAN traffic (except for remote management web calls). There is nothing special you need to do.
As for setting up at HQ and moving to a remote site. You can renumber the remote fog server IP. You just need to go into the FOG management GUI and change the IP addresses there for the storage node configuration and under fog settings. And then lastly in /tftpboot/default.ipxe make sure that is updated to the new FOG server address.
I haven’t tried this but you may be able to just reset the ip address at the remote site, update the /opt/fog/.fogsettings file and rerun the installer. That may fix everything for you. I’m not positive one way or the other.
-
have you considered setting up the storage node, disabling replication, and updating the files manually?
