Is it possible to Capture to Storage Node only? (instead of master node)

[vince.villarreal]

So the way we have it setup is below:

Master FOG in PA
Storage FOG in TX

If someone in TX wanted to “capture” an image it will try to capture directly to the master node in PA (obviously will be extremely slow)

Any way to bypass that and have that image captured to Storage Node first?

[Tom Elliott]

Setup the TX node as a master node in its own group? Associate the image directly to that group.

[vince.villarreal]

@tom-elliott But if I do that, I can’t replicate image between both sites right?

[Tom Elliott]

@vince-villarreal if you put the image in both groups you can.

[Wayne Workman]

Tom is referring to FOG’s group-to-group replication.

• An image has one group as it’s primary group, but can be associated to many storage groups.
• The image will always capture to the primary group’s master storage node.
• Replication looks for images that belong to multiple groups - and replicates from the primary master to the other associated group’s master nodes.
• Replication then replicates images from each group’s masters to other ‘regular’ storage nodes in the master’s group.
• A storage node can belong to multiple storage groups - you just need a storage node entry for each. For example, a non-master in one group can be a master in another group.

See this for more information: https://wiki.fogproject.org/wiki/index.php?title=Replication

[Tom Elliott]

@wayne-workman I want to reclassify the last point you made so hopefully easier reading.

A Storage Node Definition can only belong to one group. However, if you create a second storage node using the same information as a peer siting node, except changing the name of the node, it can belong to another group. The code has been adjusted to read all nodes.

I know this may seem arbitrary in explanation but it more directly points out that a node definition can only be in one group.