Rolling FOG out to US Site

[george1421]

@RobTitian16 TBH I forget where we are in this setup. So I’ll try to answer correctly

For a multimaster setup you will need to log into each fog server at the location or region where you want to deploy the image. This has two sides, yes it is more work because you have to know what region you are in to deploy an image. But this also stops you accidentally imaging a machine from the UK when you meant to do that in the US. Right now FOG doesn’t have the level of control to say tech X and only deploy to the US an Tech Y can only deploy to UK if you use a single master node with multiple storage nodes.

The idea of a multimaster setup is that each master node at each location is independent where they don’t need a connection to HQ to be able to image systems. This then reduces the importance of the WAN for image deployment. If you use a single master node with storage nodes then you MUST have the WAN up to be able to image at the remote locations. The decision is yours on how you want to run things.

A down side to the multimaster setup is that you don’t have one place to look for all computers in your organization since each remote site has their own master node with its own sql database.

As for replication… I don’t think this information is visible on how well / where it is in the progress. You can setup replication and let it do its thing. The remote sites won’t see the image until you load the image details on the remote FOG servers (in a multi mode setup) as for the storage node, it shouldn’t let you create the task unless the image is available on the storage node.

IMO FOG needs a little more work in the distributed enterprise area. There are some things that I wish FOG did for my business. But we’ve been able to work around them to have a successful FOG system.

[Wayne Workman]

You can look at the replication log in the log viewer.
web interface -> fog configuration -> log viewer -> image replication

You can look at sending and receiving bandwidth on the master node and new remote node via the Web interface.

You can look at used space on the remote node, refresh the page to watch it grow or wait for the auto refresh via the Web interface.

You could use iftop -n to actively monitor bandwidth at the CLI.

You could look to see the number of lftp instances with ps -aux | grep lftp

You could check the status of the image replicator service with systemctl status FOGImageReplicator or service FOGImageReplicator status

[RobTitian16]

@george1421 Thanks for the help It really is appreciated!

I thought it might be easier to export my current FOG server, change the settings to match the US site (i.e. IP address, default gateway, etc.) and then send it to them on a USB.
Are there any FOG settings I would need to change? Obviously on the VM itself I need to change the host name and network settings.

[george1421]

@RobTitian16 @Wayne-Workman has a script for fog servers with a dynamic IP address (i.e. assigned by dhcp) that would probably help here. That way you can be sure you get all of the places changed. Changing the fog server IP address after setup is a bit of a pain to do manually.

[Wayne Workman]

@george1421 It also configures dnsmasq by default, remember. if you set dodnsmasq to 0 inside of /opt/fog/.fogsettings after installation, it would keep dnsmasq disabled, but the rest of the bits and pieces would keep the IP updated.

We could probably write a simplified version to just change the IP where needed, from the source of the FOGUpdateIP tool, all the bits and pieces are there already for fedora/centOS/Debian.

[RobTitian16]

@Wayne-Workman I’d prefer to use a static IP if possible (but am open to using a DHCP assigned IP if it’s easier to do). I followed this: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address and am currently updating the US FOG server to the latest version of trunk with the new settings. Would this suffice, or would I need to do additional configuration with the server?

[Wayne Workman]

@RobTitian16 Nothing additional, those are all the steps involved. DHCP or Static is up to you. I’ve used both just fine, both have strengths where the other has weaknesses. It’s a matter of preference.

[george1421]

@RobTitian16 I only mentioned the script and its intended function because it would do what you needed to re-ip a host. But I agree with Wayne maybe a simpler one time run script would be in order, because sometimes you DO have to renumber a FOG server after its been setup.

[RobTitian16]

@Wayne-Workman Many thanks, gents. It all seems to be working here in the UK so I’ll ship it out tomorrow and hopefully set up the new VM later on this week/next week.
If I run into any issues I’ll post back

[RobTitian16]

This post is deleted!

[RobTitian16]

@Wayne-Workman Thanks for this, Wayne. Is it normal to see:

[11-01-16 9:14:18 am] | Image name: Win7Clientx86
[11-01-16 9:14:18 am] * Found Image to transfer to 1 node(s)

On both the master node in the UK and the US storage node? I can’t see any received data on the US FOG server, so I’m concerned that the replication is not working correctly.

[george1421]

@RobTitian16 Is the US server a full FOG server or a storage node?

If both are full fog servers then you only configure the master server for the UK, the US fog server shall think its standalone. So you don’t setup any storage groups or anything. That is all done on the UK server.

[RobTitian16]

@george1421 The US server is a full FOG server, but it’s listed as a storage node on the UK server. The only storage nodes on the US server are its own.

[Tom Elliott]

@RobTitian16 Are they associated to groups? If they are, is there another group they can belong to?

Replication only happens on nodes from a master->subordinate system. This is only with per group.

If an image belongs to multiple groups, though, the “primary” group will be the master and it will only distribute to other master nodes (as the master nodes will distribute to their group’s subordinates).

[RobTitian16]

@Tom-Elliott Yes, on the UK server the images I want to replicate belong to the primary storage group called UK, and a secondary storage group called US.
The US server is listed as a storage node on the UK server, although I’ve just noticed it isn’t listed as a master node. The UK server is in its own storage group, as is the US server, so I assume all I need to do is enable the US server as a master node and it should then work?
P.S. sorry if it seems like a dumb question… I just don’t want replication to occur the wrong way/have the images wiped.

[Tom Elliott]

@RobTitian16 Replication will only go Primary Master->Master between groups.

Replication will only go Master -> Subordinate within their respective groups.

I don’t know how else to make it clear.

Every group MUST have at least one “master” node. If one is not defined but there’s only one node in the group that node will “be” the master for that group (as it’s the only one available anyway).
If one is not defined and there’s multiple nodes in the group, the “Oldest” created node of that group will be assumed as the master until otherwise stated.

Replication doesn’t work “up the tree” if you will.

[RobTitian16]

@Tom-Elliott Ahh okay, thanks. I’ve changed it to the master node now for that group, so I shall wait and see what happens in that case.

[Tom Elliott]

@RobTitian16 I feel I should add some caveats to this.

The replication process is self monitored. If a replication task was started, but has not completed, the next cycle will be aware of this and will not try to replicate the file over. If replication has completed between two points and both sides have the same files the images will not be touched.

Only items (Snapins and Images) that are defined as “to Replicate” will be replicated.

Any extra data within a storage location (snapins or images) will not be removed unless that data is defined within the main system and told to do so.

For example, let’s say you decided to create a backup of image1 and you locally backed it up on a node that is not a “master”. You locally backup image1 with the name of image1_backUp within the Images storage location. image1_backUp will be untouched.

If you made a backup in the same fashion, but on a master node, that data will not be replicated to other nodes.

Only defined items will be replicated. Data loss is limited due to this implementation. At one point, FOG did used to replicate it’s images folder implicitly. This meant anything that was not a part of the “master’s” data record on another node would be removed and only the data within the master would be available on any node. This, essentially, meant that you could not maintain backup’s of things from other nodes without having to have another location available on that system. This also meant you had no granular control over what can/cannot be replicated. This is where the “Master Node” warning came from. I have not updated it because I think it’s better to be “cautious” in the case something weird does happen.

Essentially, the methods to replicate images and snapins are now much better controlled (I think) with less potential of data loss.

[george1421]

While its probably not necessairy to post this image, this is from my initial request for a multi master storage node setup. The intent was to show the relationship between the master node and the remote fog servers.

ref: https://forums.fogproject.org/topic/6014/create-the-concept-of-a-foreignmasterstorage-deployment-node

[RobTitian16]

@Tom-Elliott Indeed, that all does make sense. Many thanks for your help! I can see the replication is going across perfectly fine.
One thing to note: I had to use the local account and the password for the ftp access, instead of the username and password listed in /opt/fog/.fogsettings (which is what it says in step 12 of https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Storage_Management).