Red Hat NETWORK - USER 3.0 Przewodnik Instalacji Pobierz pdf (Strona 57)

Bi-directional sync

satellite-sync --iss-parent=staging-satellite.example.com -c custom-channel

6.5.2. Bi-directional sync

Administrators can configure an environment where two RHN Satellite servers act as masters of each

other. For example, Satellite A and B can sync content from one another.

Figure 6.5. Bi-directional syncing

Both Satellites would need to share SSL certificates, then set the iss_parent option in the /etc/

rhn/rhn.conf file of Satellite A to point to the hostname of Satellite B, and do the same for Satellite

B to point to Satellite A as the iss_parent.

6.6. Synchronizing by Organization

Satellite-sync has a new enhancement as part of the inter satellite sync feature where a user can

import content to any specific organization. This can be done locally or by a remote syncing from

hosted or another satellite.

The aim is for Satellite sync to be able to import content with respect to org_id. 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:

1. Import content from master to slave satellite.

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

2. Import content from an exported dump of a specific org

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

1 2 ... 52 53 54 55 56 57 58 59 60 61 62 ... 85 86

Brak uwag

Red Hat NETWORK - USER 3.0 Przewodnik Instalacji Strona 57