Host/Group replication between FOG Servers

[Wayne Workman]

@adukes40 said in Host/Group replication between FOG Servers:

Quick follow up though. Say I have machine 1 in building A, and it gets moved to building B. building A’s group location points to A’s server and building B to B’s server. if machine 1 is in building A, it should pull from that server. If it gets moved to building B, what happens if :
A) I forget to change the group it is associated to? Will it sill try to pull form building A from building B over the WAN?
B) If I do add it to a group pointing to building B’s server, will the host automatically but updated just by removing it from group A and adding to group B?

First, you must understand that group settings are not persistent. Merely moving a host from one group to another only changes the groups it’s in. Best way I can explain it to you is when you apply settings to a group, you’re really just applying the settings one-time to all hosts in the group. Meaning, if you set AD credentials on a group, and then add another host to that group, that new host doesn’t have those settings because it wasn’t in the group when the settings were applied.

A) It will pull from building A over the WAN.

B) No. See what I said above.

Also - you may consider NOT setting a location on a host. That’s an option too, although I wouldn’t really recommend it if your WAN is slow.

[Wayne Workman]

@adukes40 said in Host/Group replication between FOG Servers:

Additional side note, can i register hosts at a separate location and have those hosts show up on the main server? Would I just need to register them and then do an export and import them to the main server?

You’re misunderstanding how it works, I’ll expalin. The main server is the top dog, it runs the web interface and the database.

All other servers should be configured as storage nodes. This is an option in the FOG Installer. All registrations at all sites communicate - ultimately - with the main server. You can configure all sites DHCP option 066 to point to the main server - or - to the local nodes, but if it’s pointing to the local nodes, those nodes are just relaying info to the main server. Nothing but images and snapins are stored on the nodes. The location plugin expands on this, by allowing the nodes to serve kernels and inits as well - which is a pretty good thing.

I should make another video… more comprehensive about multi-server setups…

[adukes40]

AH ok, so when i go to set up the main server I do it as a “normal” installation, and the other schools should be installed as “storage” only? By doing this is Location A has the main server and database, and I go to place a new machine that hasnt been registered yet at Location B, then the registration will automatically go to Location A to the database? Am I correct in saying that?

I was going to install at the other sites to test replication on the WAN, i just installed the newest SVN and it is having trouble connecting to the database. IDK whats going on, for now I think i will just try to go rest my head a bit. I understand better about how it is going to work, and thanks for your patience and explanation. It really is helping me grasp it better.

[Wayne Workman]

@adukes40 You’re understanding sounds right.

Once you start using it, you’ll realize you were thinking way to hard about this lol.

[adukes40]

well i just set up a new master, and storage node. Going to play with it more today to get a better feel. Thanks Wayne! I will try to remember to report back to tell hows its going.

[adukes40]

here is what I am getting when a snapin tries to replicate. I did notice I typoed one letter in the password, but I fixed that. Before it couldn’t communicate until i fixed the letter, but now I get the below message in the log.

[adukes40]

I am also getting stuck here on PXE. I am at the remote location trying to register a host, but I cannot get past this part. just sits with a blinking cursor

[Wayne Workman]

@adukes40 The replication error is likely permissons or SELinux.

with the iPXE stuff, did you put in the correct main server IP during installing the storage node? You must also put in the correct MySQL fogstorage password for the storage node during installation too.

[adukes40]

@Wayne-Workman said in Host/Group replication between FOG Servers:

@adukes40 The replication error is likely permissons or SELinux.

with the iPXE stuff, did you put in the correct main server IP during installing the storage node?
===Yes, it is the IP of the new main server I created.

You must also put in the correct MySQL fogstorage password for the storage node during installation too.
===I have placed all the needed passwords. Here are the SS’s to show:

Main server info:

Remote storage info:

Storage Node information from the /.fogsettings file:

What is typed into the management gui (copy and pasted):

Username: fog
Password: hXFzePJJGCBLw7uudEVDry9gGWL9AcO70FOtAblUxF4=

i assume each node is supposed to have different storage management passwords? Because when i compare the two nodes, the Password is different.

[adukes40]

This post is deleted!

[adukes40]

Also are permissions something I will need to set on all remote sites?

[Wayne Workman]

@adukes40 said in Host/Group replication between FOG Servers:

i assume each node is supposed to have different storage management passwords?

Correct. At this point, we need more details. Exactly what version of FOG trunk are you running, and what Linux distribution and version?

[adukes40]

Ubuntu 14.04 LTS

Fog 7713

Fresh installed last night… between 8pm - 11pm EST.

[Wayne Workman]

@adukes40 Are the storage nodes the same version of FOG? It does matter. Also, you said you previously had a full fog server at each site? Are you using those or did you build fresh?

[Wayne Workman]

Also, to see if FTP credentials are right and pathing is correct, security is correct, firewall is correct, you can connect from the main fog server to the node via FTP to test credentials.

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

[adukes40]

@Wayne-Workman I shut off any other instances of FOG last night. there are currently only 2 instances running, The main server which is across town, and the storage instance located here at my shop. the 10.103 address is the main server, and the 10.106 address is the storage location at my location. both were setup exactly the same. Only difference is the DCHP server address, gateway, and local IP of the fog servers themselves. both runnin Ubuntu 14.04, FOG 7713. I was making them side by side last night to hopefully keep them the same version and they are. I download the install using this:
sudo svn co http://svn.code.sf.net/p/freeghost/code/trunk I left the mysql password blank when setting up the Main as well.

[adukes40]

Here is what the permissions look like on the Main:

and here is the storage only:

[adukes40]

it looks like firewall is disbaled, I was able to send a file from the remote server to the main server manually. this is what i get for the remote location still:

Error communicating with the database. Error: SQLSTATE[HY000] [1045] Access denied for user ‘fogstorage’@‘localhost’ (using password: YES)

[Wayne Workman]

@adukes40 make sure the fog storage password is correct on the storage node. If it’s not, change it in /opt/fog/.fogsettings and rerun the installer on the storage node.

You can test MySQL credentials from the node to the main by connecting to it via something like this:

MySQL -u fogstorage -h x.x.x.x -p

Not sure if that syntax is right but its close. you can Google examples.

[Wayne Workman]

Also to clarify, for the ftp test, you should have been on the main server testing ftp ccredentials to the node. Testing from the node to the main doesn’t tell you if the nodes ftp credentials are good because you weren’t testing them.

And, the MySQL test should be run from the node.

You can use SSH to be “in” whatever server you need to run the tests.