Unifying ISS and Hub pages

CHANGELOG.md

@@ -1,3 +1,5 @@
+- Moved Inter-Server Sunchronization documentation from Administration
+  to Large Deployments Guide
 - Enhanced instructions about router advertisements and parameter
   value needed for IPv6 route in Installation and Upgrade Guide
   (bsc#1241034)

l10n-weblate/administration.cfg

@@ -28,9 +28,6 @@
 [type: asciidoc] modules/administration/pages/image-management.adoc $lang:translations/$lang/modules/administration/pages/image-management.adoc
 [type: asciidoc] modules/administration/pages/image-mgmt-container-inspection.adoc $lang:translations/$lang/modules/administration/pages/image-mgmt-container-inspection.adoc
 [type: asciidoc] modules/administration/pages/infra-maintenance.adoc $lang:translations/$lang/modules/administration/pages/infra-maintenance.adoc
-[type: asciidoc] modules/administration/pages/iss.adoc $lang:translations/$lang/modules/administration/pages/iss.adoc
-[type: asciidoc] modules/administration/pages/iss_intro.adoc $lang:translations/$lang/modules/administration/pages/iss_intro.adoc
-[type: asciidoc] modules/administration/pages/iss_v2.adoc $lang:translations/$lang/modules/administration/pages/iss_v2.adoc
 [type: asciidoc] modules/administration/pages/live-patching-channel-setup.adoc $lang:translations/$lang/modules/administration/pages/live-patching-channel-setup.adoc
 [type: asciidoc] modules/administration/pages/live-patching-sles12.adoc $lang:translations/$lang/modules/administration/pages/live-patching-sles12.adoc
 [type: asciidoc] modules/administration/pages/live-patching-sles15.adoc $lang:translations/$lang/modules/administration/pages/live-patching-sles15.adoc

l10n-weblate/reference.cfg

@@ -11,9 +11,6 @@
 [type: asciidoc] modules/reference/pages/admin/bootstrap-script.adoc $lang:translations/$lang/modules/reference/pages/admin/bootstrap-script.adoc
 [type: asciidoc] modules/reference/pages/admin/cobbler.adoc $lang:translations/$lang/modules/reference/pages/admin/cobbler.adoc
 [type: asciidoc] modules/reference/pages/admin/general.adoc $lang:translations/$lang/modules/reference/pages/admin/general.adoc
-[type: asciidoc] modules/reference/pages/admin/iss-configuration.adoc $lang:translations/$lang/modules/reference/pages/admin/iss-configuration.adoc
-[type: asciidoc] modules/reference/pages/admin/iss-master-setup.adoc $lang:translations/$lang/modules/reference/pages/admin/iss-master-setup.adoc
-[type: asciidoc] modules/reference/pages/admin/iss-slave-setup.adoc $lang:translations/$lang/modules/reference/pages/admin/iss-slave-setup.adoc
 [type: asciidoc] modules/reference/pages/admin/manager-config-organizations.adoc $lang:translations/$lang/modules/reference/pages/admin/manager-config-organizations.adoc
 [type: asciidoc] modules/reference/pages/admin/manager-configuration.adoc $lang:translations/$lang/modules/reference/pages/admin/manager-configuration.adoc
 [type: asciidoc] modules/reference/pages/admin/monitoring.adoc $lang:translations/$lang/modules/reference/pages/admin/monitoring.adoc

l10n-weblate/specialized-guides.cfg

@@ -16,6 +16,7 @@
 [type: asciidoc] modules/specialized-guides/pages/large-deployments/hub-online-sync.adoc $lang:translations/$lang/modules/specialized-guides/pages/large-deployments/hub-online-sync.adoc
 [type: asciidoc] modules/specialized-guides/pages/large-deployments/hub-reporting.adoc $lang:translations/$lang/modules/specialized-guides/pages/large-deployments/hub-reporting.adoc
 [type: asciidoc] modules/specialized-guides/pages/large-deployments/hub-reqs.adoc $lang:translations/$lang/modules/specialized-guides/pages/large-deployments/hub-reqs.adoc
+[type: asciidoc] modules/specialized-guides/pages/large-deployments/iss_v2.adoc $lang:translations/$lang/modules/specialized-guides/pages/large-deployments/iss_v2.adoc
 [type: asciidoc] modules/specialized-guides/pages/large-deployments/monitoring.adoc $lang:translations/$lang/modules/specialized-guides/pages/large-deployments/monitoring.adoc
 [type: asciidoc] modules/specialized-guides/pages/large-deployments/operation-reqs.adoc $lang:translations/$lang/modules/specialized-guides/pages/large-deployments/operation-reqs.adoc
 [type: asciidoc] modules/specialized-guides/pages/large-deployments/overview.adoc $lang:translations/$lang/modules/specialized-guides/pages/large-deployments/overview.adoc

modules/administration/nav-administration-guide.adoc

@@ -47,8 +47,6 @@ endif::[]
 ** xref:space-management.adoc[Disk Space Management]
 ** xref:image-management.adoc[Image Building and Management]
 ** xref:infra-maintenance.adoc[Infrastructure Maintenance Tasks]
-** xref:iss_intro.adoc[Inter-Server Synchronization]
-*** xref:iss_v2.adoc[Inter-Server Synchronization version 2]
 ** xref:live-patching.adoc[Live Patching]
 *** xref:live-patching-channel-setup.adoc[Channel Setup for Live Patching]
 *** xref:live-patching-sles15.adoc[Live Patching on SLES 15]

modules/administration/pages/disconnected-setup.adoc

@@ -213,4 +213,4 @@ Instead, a warning sign will be displayed and no {scc} online check will be perf
 ====
 
 An alternative to disconnected setup may be to copy content between servers using Inter-Server Synchronization (ISS).
-For more information, see xref:administration:iss_v2.adoc[Inter-Server Synchronization - Version 2].
+For more information, see xref:specialized-guides:large-deployments/iss_v2.adoc[Inter-Server Synchronization - Version 2].

modules/administration/pages/infra-maintenance.adoc

@@ -95,7 +95,7 @@ To avoid this always update the [package]``salt-minion`` package when available.
 
 If you are using an Inter-Server Synchronization slave server, update it after the {productname} Server update is complete.
 
-For more on Inter-Server Synchronization, see xref:administration:iss.adoc[].
+For more information, see xref:specialized-guides:large-deployments/iss_v2.adoc[Inter-Server Synchronization - Version 2].
 
 
 
@@ -118,4 +118,4 @@ The only exception is for the duration of updates where it is expected that the
 [WARNING]
 ====
 Always upgrade the server first, then any proxy.
-====
+====

modules/reference/nav-reference-guide.adoc

@@ -154,9 +154,6 @@ endif::[]
 ***** xref:admin/restart.adoc[Restart]
 ***** xref:admin/cobbler.adoc[Cobbler]
 ***** xref:admin/monitoring.adoc[Monitoring]
-**** xref:admin/iss-configuration.adoc[ISS Configuration]
-***** xref:admin/iss-master-setup.adoc[ISS Master Setup]
-***** xref:admin/iss-slave-setup.adoc[ISS Slave Setup]
 **** xref:admin/task-schedules.adoc[Task Schedules]
 **** xref:admin/task-engine-status.adoc[Task Engine Status]
 **** xref:admin/show-tomcat-logs.adoc[Show Tomcat Logs]

modules/specialized-guides/nav-specialized-guides-guide.adoc

@@ -106,6 +106,7 @@ endif::[]
 **** xref:large-deployments/hub-auth.adoc[Hub Authentication]
 **** xref:large-deployments/hub-reporting.adoc[Hub Reporting]
 **** xref:large-deployments/hub-online-sync.adoc[Hub Online Synchronization]
+**** xref:large-deployments/iss_v2.adoc[Inter-Server Synchronization version 2]
 *** xref:large-deployments/retail-large-scale.adoc[Large Retail Environments]
 *** xref:large-deployments/tuning.adoc[Tuning Large Installations]
 *** xref:large-deployments/monitoring.adoc[Monitoring Large Scale Deployments]

modules/specialized-guides/pages/large-deployments/hub-multi-server.adoc

@@ -2,13 +2,19 @@
 = Multiple Servers with Hub to Manage Large Scale Deployments
 
 If you need to manage a large number of clients, in most cases you can do so with a single {productname} Server, tuned appropriately.
-However, if you need to manage tens of thousands of clients, you might find it easier to use multiple {productname} Servers, in a hub, to manage them.
+
+However, if you need to manage tens of thousands of clients, you might find it easier to use one of the following mechanisms:
+
+* Inter-Server Sunchronization (ISS)
+* {productname} Hub
+
+ISS is based on exporting data from one server (source) and importing it on another (target) server.
+For more information, see xref:specialized-guides:large-deployments/iss_v2.adoc[Inter-Server Synchronization - Version 2].
+
 
 {productname} Hub helps you manage very large deployments.
 The typical Hub topology looks like this:
 
 image::typical-hub-architecture-overview.svg[scaledwidth=80%]
 
-To copy contents between servers, you can use Inter-Server Synchronization (ISS).
-ISS allows you to export data from one server (source) and import it on another (target) server.
-For more information, see xref:administration:iss_intro.adoc[].
+This chapter gives more details about Hub deployment.

modules/specialized-guides/pages/large-deployments/hub-online-sync.adoc

@@ -244,7 +244,6 @@ If the channel exists, the organization will stay unchanged.
 
 Now channels will be created on the peripheral server and everything will be set up to mirror the channels with the next regular repository synchronization task.
 
-
 [IMPORTANT]
 ====
 The repository synchronization will not start immediately after clicking the confirmation button.

modules/administration/pages/iss_v2.adoc → modules/specialized-guides/pages/large-deployments/iss_v2.adoc

@@ -2,13 +2,13 @@
 = Inter-Server Synchronization version 2
 
 If you have more than one {productname} installation, you will need to copy contents between servers.
-Inter-Server Synchronization (ISS) allows you to export data from one server (source) and import it on another (target) server.
+Inter-Server Synchronization (ISS) allows you to export data from one server (hub) and import it on another server (peripheral).
 This is useful for hub deployment scenarios or disconnected setups.
 
 
 == Install Inter-Server Synchronization packages
 
-To use ISS you need to install the [package]``inter-server-sync`` package on source and target servers.
+To use ISS you need to install the [package]``inter-server-sync`` package on hub and peripheral servers.
 
 
 
@@ -20,8 +20,8 @@ To use ISS you need to install the [package]``inter-server-sync`` package on sou
 Use [literal]``mgrctl term`` before running steps inside the server container.
 ====
 
-.Procedure: Export data on source server
-. On the source server, on the command line execute the ISS export command.
+.Procedure: Export data on hub server
+. On the hub server, on the command line execute the ISS export command.
   The [option]``-h`` option provides detailed help:
 +
 ----
@@ -32,8 +32,8 @@ The export procedure creates an output directory with all the needed data for th
 
 
 
-.Procedure: Copy export directory to target server
-. Contents from the source server needs to be synchronized to the target server.
+.Procedure: Copy export directory to peripheral server
+. Contents from the hub server needs to be synchronized to the peripheral server.
   On the command line, as root, execute:
 +
 ----
@@ -45,8 +45,8 @@ When all contents is copied, start importing it.
 
 
 
-.Procedure: Import data on target server
-. On the target server, on the command line execute the ISS import command.
+.Procedure: Import data on peripheral server
+. On the peripheral server, on the command line execute the ISS import command.
   The [option]``-h`` option provides detailed help:
 +
 ----
@@ -58,13 +58,13 @@ inter-server-sync import -h
 == Database connection configuration
 
 
-Database connection configuration is loaded by default from ``/etc/rhn/rhn.conf``.
-Properties file location can be overridden with parameter ``--serverConfig``.
+Database connection configuration is loaded by default from [path]``/etc/rhn/rhn.conf``.
+Properties file location can be overridden with parameter [literal]``--serverConfig``.
 
 
 
 == Known limitations
 
-* Source and target servers need to be on the same version.
+* Hub and peripheral servers need to be on the same version.
 * Export and import organization should have exactly the same name.
   The organization name is case sensitive.