@apollyonus I donât know what version of fog youâre running so without that I canât give you great information about what youâre asking.
In trunk, images can be replicated across groups. This is managed by what I call the âPrimaryâ master. All this is is the group that is the âownerâ or âgoldenâ image that is known to be good at the time of completion. This groupâs Master node will replicate the image to all nodes within the group as well as all other storage groups that are associated with the image. If you update the master on a different group, it will be overwritten because the Primary master is the one whoâs the âreal dudeâ. So if you wanted to use a different groupâs already replicated image as the âmasterâ of all, you would need to update the primary group status of that image.
This same principle works for snapins in trunk as well. Mind you, the group->group replication and snapin replication did not exist before whatâs currently in trunk. 1.2.0 and earlier did not have these capabilities.
Most often configurations of users with the location plugin, that iâve seen, create groups for the different node locations. These nodes will fall under the group. Why is this important you may ask? Because the way the location plugin was designed with 1.x.x versions of fog, you can associate a host to a location, and the location does NOT need to belong to a single node. This can allow versatility in that if you have a large building, all on the same network, you can have a location managed by many nodes even under the same group. 0.32 (known as the location patch) only allowed node->host imaging to occur. It had no replication capabilities, all it did is tell the host where to download itâs image. Uploads were still done to whatever was the master node.
The current location plugin is MUCH more powerful than the days when it was known as the location patch. First, it allows the Group to be a âlocationâ that a host (when assigned) can use similar to how the storage group/node system works without the location plugin. It just designates the host must operate under as specific group. Second, under trunk I guess, you donât have to have different image names that are essentially the same image anyway because (maybe this isnât specifically to locations but it certainly expands a locations power) they can cross different groups. Third, the location plugin can tell a host to use the location itâs under to get itâs initâs and kernels (even further limiting across WAN bandwidth usage).
I donât know if Iâve answered your questions, but yes, most people create a group with a single node that designate the location. That single node is the master of that group, so images needing to be uploaded are handled at that location as well.
