An issue was found in 1.5.6 that calls for an early next release to fix that. Find the details here if you run into problems with FTP connections on kernel updates or storage nodes in 1.5.6: https://github.com/FOGProject/fogproject/issues/311
I’ve though about this a little, for testing purposes we can do this.
On the HQ fog server, using a linux command prompt key in
sudo mkdir /images/tom
sudo touch /images/tom/sample.txt
On the remote fog server, using a linux command prompt key in
sudo mkdir /images/sam
sudo touch /images/sam/sample.txt
On the HQ fog server create a image name of test using the web ui.
Back on the HQ fog server’s linux console key in
sudo touch /images/test/sample.txt
Now let the replicator run.
A successful test will have on the HQ fog server in the /images directory
On the remote FOG server in the /images directory you should have
That will tell us
The replicator only acts upon files where it has an image definition in the database.
It will not step on images you captured on your remote server that are not in the HQ fog servers database.
@Tom-Elliott Ok, I understand. That’s a problem to me because all the server’s ip on the service vlan’s are protected. Then i must have the StorageNode on the Management VLAN.
By the moment i’ve solved the problem like i said on the last post. It’s a valid solution for me. But when i have time i try to implement a plugin to handle this dinamically from the interface.