9.2. Organizational Synchronization

Inter-Satellite Synchronization can also be used to import content to any specific organization. This can be done locally or by using remote synchronization. This function is useful for a disconnected satellite with multiple organizations, where content is retrieved through channel dumps or by exporting from connected satellites and then importing it to the disconnected satellite. Organizational synchronization can be used to export custom channels from connected satellites. It can also be used to effectively move content between multiple organizations.
Organizational synchronization follows a clear set of rules in order to maintain the integrity of the source organization:
  • If the source content belongs to the NULL organization (that is, it is Red Hat content) it will default to the NULL organization even if a destination organization is specified. This ensures that specified content is always in the privileged NULL organization.
  • If an organization is specified at the command line, content will be imported from that organization.
  • If no organization is specified, it will default to organization 1.
The following are three example scenarios where organizational IDs (orgid) are used to synchronize satellites:

Example 9.1. Import Content from Master to Slave Satellite

This example imports content from master to slave satellite:
satellite-sync --parent-sat=master.satellite.example.com -c channel-name --orgid=2

Example 9.2. Import Content from an Exported Dump of an Organization

This example imports content from an exported dump of a specific organization:
$ satellite-sync -m /dump -c channel-name --orgid=2

Example 9.3. Import Content from Red Hat Network Hosted

This example imports content from Red Hat Network Hosted (assuming the system is registered and activated):
$ satellite-sync -c channel-name