Replication of /images

[Tom Elliott]

It only replicates images. I believe you can actually create a template “image” definition, that simply points to the drivers directory. Mind you, replicating drivers can take a very long time, even if the drivers don’t take much disk space.

[Tom Elliott]

Here’s a forum post asking about, more or less, the same thing. (I had to fix a problem with them initially of course.)

https://forums.fogproject.org/topic/9158/replicating-drivers-across-fog-servers

[george1421]

@tom-elliott said in Replication of /images:

I believe you can actually create a template “image” definition, that simply points to the drivers directory.

This is correct. Just make a Image name of Drivers, and point the path to /image/drivers (assuming the OP is following one of my how-tos). The drivers will replicate to the storage nodes. Depending on the volume of drivers (size) and your link speed between the FOG master node and the storage node, it make take some time (days maybe if over a WAN connection).

[UWPVIOLATOR]

@george1421 @Tom-Elliott

Created the template and it did not replicate. Is it case sensitive?

[07-02-18 4:38:12 am] * We are group ID: 1. We are group name: Master
[07-02-18 4:38:12 am] * Starting Image Replication.
[07-02-18 3:52:01 am] | File or path cannot be reached.
[07-02-18 3:52:01 am] | Image Name: Drivers
[07-02-18 3:52:01 am] * Not syncing Image between s
[07-02-18 3:52:01 am] | File or path cannot be reached.
[07-02-18 3:52:01 am] | Image Name: Drivers
[07-02-18 3:52:01 am] * Not syncing Image between s
[07-02-18 3:52:01 am] | File or path cannot be reached.
[07-02-18 3:52:00 am] | Image Name: Drivers
[07-02-18 3:52:00 am] * Not syncing Image between s
[07-02-18 3:52:00 am] | File or path cannot be reached.
[07-02-18 3:52:00 am] | Image Name: Drivers
[07-02-18 3:52:00 am] * Not syncing Image between s
[07-02-18 3:52:00 am] | File or path cannot be reached.
[07-02-18 3:52:00 am] | Image Name: Drivers
[07-02-18 3:52:00 am] * Not syncing Image between s
[07-02-18 3:52:00 am] | File or path cannot be reached.
[07-02-18 3:52:00 am] | Image Name: Drivers
[07-02-18 3:52:00 am] * Not syncing Image between s
[07-02-18 3:52:00 am] | File or path cannot be reached.
[07-02-18 3:52:00 am] | Image Name: Drivers
[07-02-18 3:52:00 am] * Not syncing Image between s
[07-02-18 3:52:00 am] | Image Name: Drivers
[07-02-18 3:52:00 am] * Found Image to transfer to 7 s
[07-02-18 3:51:58 am] | Replication already running with PID: 16017

[Tom Elliott]

@uwpviolator the path would be case sensitive.

[Tom Elliott]

@uwpviolator and from what I can tell is it’s in the process of replicating not that it’s failing to replicate.

[george1421]

@uwpviolator can you show us the output of ls /images If your directory is /images/drivers, then your image definition is wrong. As Tom posted, case is important.

[UWPVIOLATOR]

@george1421 Yes I fixed that and it now looks like its replicating.

Now question. Can I tell this image (drivers) to replicate to other storage nodes other than our Master Group?

[Tom Elliott]

@uwpviolator if you associate different storage groups to the definition it should replicate all over the place

[george1421]

@uwpviolator If you only want to replicate the drivers but not the images to this other storage groups, that will be difficult to do sanely.

You might want to use rsync just /images/drivers to other master nodes in each of the other storage groups. Then replication will happen as it does with your current storage group.

[UWPVIOLATOR]

@tom-elliott @george1421 So it is taking forever to replicate just 1 Node drivers. We rsynced before but its almost copying every file again. What do we need to do to make the copies be the same and speed up replication? What does FOG use to check the file to see if it matches?