Configuring Inter-Server Synchronization (ISS)
Configure Inter-Server Synchronization on your downstream orcharhino Server to provide content to its hosts.
Inter-Server Synchronization configurations
Depending on network connectivity between upstream and downstream orcharhino Servers, you can synchronize content over HTTPS with network sync or by exporting and importing content when servers are air gapped.
There are two possible ISS configurations of orcharhino, depending on how you deployed your infrastructure:
- ISS Network Sync
-
If your upstream server can communicate with the downstream server over a network, you can synchronize content over HTTPS.
Configure your orcharhino to synchronize content over a network. For more information, see Configuring server to synchronize content over a network by using orcharhino management UI.
- ISS Export Sync
-
If your upstream and downstream servers are air gapped, you can synchronize content by using export and import.
Configure your orcharhino to synchronize content by using export and import. For more information, see Configuring projectserver to synchronize content through exports by using orcharhino management UI.
Configuring orcharhino Server to synchronize content through exports by using orcharhino management UI
If you deployed your downstream orcharhino Server as air gapped, configure your orcharhino Server as such to avoid attempts to consume content from a network.
-
In the orcharhino management UI, navigate to Content > Subscriptions.
-
Click Manage Manifest.
-
Switch to the CDN Configuration tab.
-
Select the Export Sync tab.
-
Click Update.
Configuring orcharhino Server to synchronize content through exports by using Hammer CLI
If you deployed your downstream orcharhino Server as air gapped, configure your orcharhino Server as such to avoid attempts to consume content from a network.
-
Log in to your orcharhino Server by using SSH.
-
Set CDN configuration to sync by using exports:
$ hammer organization configure-cdn \ --name="My_Organization" \ --type=export_sync
Configuring orcharhino Server to synchronize content over a network by using orcharhino management UI
To synchronize content over a network, configure your downstream orcharhino Server to pull repositories from a connected upstream orcharhino Server.
-
A network connection exists between the upstream orcharhino Server and the downstream orcharhino Server.
-
You imported the same subscription manifest on both the upstream and downstream orcharhino Server.
-
On the upstream orcharhino Server, you enabled the required repositories for the organization.
-
The upstream user is an admin or has the following permissions:
-
view_organizations -
view_products -
export_content -
view_lifecycle_environments -
view_content_views
-
-
On the downstream orcharhino Server, you have imported the SSL certificate of the upstream orcharhino Server using the contents of
http://upstream-orcharhino.example.com/pub/katello-server-ca.crt. -
The downstream user is an admin or has the permissions to create product repositories and organizations.
-
Navigate to Content > Subscriptions.
-
Click Manage Manifest.
-
Navigate to the CDN Configuration tab.
-
Select the Network Sync tab.
-
In the URL field, enter the address of the upstream orcharhino Server.
-
In the Username, enter your username for upstream login.
-
In the Password, enter your password or personal access token for upstream login.
-
In the Organization label field, enter the label of the upstream organization.
-
Optional: In the Lifecycle Environment Label field, enter the label of the upstream lifecycle environment. Default is
Library. -
Optional: In the Content view label field, enter the label of the upstream content view. Default is
Default_Organization_View. -
From the SSL CA Content Credential menu, select a CA certificate used by the upstream orcharhino Server.
-
Click Update.
-
In the orcharhino management UI, navigate to Content > Products.
-
Select the product that contains the repositories that you want to synchronize.
-
From the Select Action menu, select Sync Now to synchronize all repositories within the product.
You can also create a synchronization plan to ensure updates on a regular basis.
Configuring orcharhino Server to synchronize content over a network by using Hammer CLI
To synchronize content over a network, configure your downstream orcharhino Server to pull repositories from a connected upstream orcharhino Server.
-
A network connection exists between the upstream orcharhino Server and the downstream orcharhino Server.
-
You imported the same subscription manifest on both the upstream and downstream orcharhino Server.
-
On the upstream orcharhino Server, you enabled the required repositories for the organization.
-
The upstream user is an admin or has the following permissions:
-
view_organizations -
view_products -
export_content -
view_lifecycle_environments -
view_content_views
-
-
On the downstream orcharhino Server, you have imported the SSL certificate of the upstream orcharhino Server using the contents of
http://upstream-orcharhino.example.com/pub/katello-server-ca.crt. -
The downstream user is an admin or has the permissions to create product repositories and organizations.
-
Connect to your downstream orcharhino Server using SSH.
-
View information about the upstream CA certificate:
$ hammer content-credential show \ --name="My_Upstream_CA_Cert" \ --organization="My_Downstream_Organization"Note the ID of the CA certificate for the next step.
-
Set CDN configuration to an upstream orcharhino Server:
$ hammer organization configure-cdn \ --name="My_Downstream_Organization" \ --type=network_sync \ --url https://upstream-orcharhino.example.com \ --username upstream_username --password upstream_password \ --ssl-ca-credential-id "My_Upstream_CA_Cert_ID" \ --upstream-organization-label="_My_Upstream_Organization" \ [--upstream-lifecycle-environment-label="My_Lifecycle_Environment"] \ [--upstream-content-view-label="My_Content_View"]The default lifecycle environment label is
Library. The default content view label isDefault_Organization_View.
|
The text and illustrations on this page are licensed by ATIX AG under a Creative Commons Attribution Share Alike 4.0 International ("CC BY-SA 4.0") license. This page also contains text from the official Foreman documentation which uses the same license ("CC BY-SA 4.0"). |