7.5. Synchronizing by Organization

The satellite-sync tool offers the ability to import content to any specific organization. This can be done locally or via a remote syncing from hosted or another satellite.
The aim is for Satellite sync to be able to import content with respect to orgid. This targets two sets of users. One is the disconnected Multi-Org case, where the main source of content for the user is either to get content from channel dumps or to export them from connected satellites and import it to the Satellite. The user mainly hosts custom channels from disconnected satellites. If they wish to export custom channels from connected satellites, they can do so by organizational sync.
The other case is a connected Multi-Org satellite customer. These new flags could work as a means of moving content between multiple orgs.
Synchronizing by organization has a few rules that it follows to maintain the integrity of the source org.
  • If the source content belongs to a base org (any Red Hat content) it will default to the base org even if a destination org is specified. This ensures that the specified content is always in that privileged base org.
  • If an org is specified at the command line, it will import content from that org.
  • If no org is specified, it will default to org 1.
The following are three example scenarios where organizational IDs (orgid) are used to synchronize between Satellites:

Example 7.1.  Import content from Master to Slave satellite.

# satellite-sync --parent-sat=master.satellite.domain.com -c channel-name --orgid=2

Example 7.2.  Import content from an exported dump of a specific org

# satellite-sync -m /dump -c channel-name --orgid=2

Example 7.3.  Import content from Red Hat Network Hosted

# satellite-sync -c channel-name