NMS-19060: Cleanup docs build for CentOS 10 support

* Fix includes and removed duplicate include for CentOS 9 and 10.
* Simplify variables for compatible versions used in the system
requirements.
* Fixed build warnings for Kafka topic placeholders and masquarded them
  so that they are not tried to be resolved as an Antora variable.

Signed-off-by: Ronny Trommer <ronny@no42.org>

Author: indigo423

docs/antora.yml

@@ -7,17 +7,12 @@ asciidoc:
     package-prefix: opennms
     experimental: true
     source-language: asciidoc@
-    xrefstyle: short@
-    compatible-centos7: '7.x'
-    compatible-centos-stream9: '9.x'
-    compatible-centos-stream10: '10.x'
-    compatible-rhel7: '7.x'
-    compatible-rhel8: '8.x'
-    compatible-rhel9: '9.x'
-    compatible-rhel10: '10.x'
-    compatible-ubuntu: '20.04 LTS'
-    compatible-debian: '9 - 11'
-    compatible-rocky-linux: '9.x'
+    xrefstyle: short@´
+    compatible-centos: '9.x, 10.x'
+    compatible-rhel: '8.x, 9.x, 10.x'
+    compatible-ubuntu: '20.04 LTS - 24.04 LTS'
+    compatible-debian: '9 - 12'
+    compatible-rocky-linux: '9.x, 10.x'
     compatible-opennms-plugin: '9 - 11.2'
     compatible-oia: '1.6.1'
     compatible-cassandra: '4.17.0'
@@ -27,9 +22,9 @@ asciidoc:
     compatible-postgresql: '13.x - 15.x'
     compatible-rrdtool: '1.7.x'
     jasperreportsversion: '6.3.0'
-    latest-meridian-stable: '2023'
+    latest-meridian-stable: '2025'
     postgresql-version: '15'
-    jmx-prom-exporter-version: '1.3.0'
+    jmx-prom-exporter-version: '1.4.0'
 nav:
 - modules/ROOT/nav.adoc
 - modules/releasenotes/nav.adoc

docs/modules/deployment/pages/core/centos/adoptium.adoc

@@ -0,0 +1,18 @@
+.Add Adoptium repository. See official https://adoptium.net/installation[docs] for more information.
+[source, console]
+----
+sudo bash -c 'cat <<EOF > /etc/yum.repos.d/adoptium.repo
+[Adoptium]
+name=Adoptium
+baseurl=https://packages.adoptium.net/artifactory/rpm/${DISTRIBUTION_NAME:-$(. /etc/os-release; echo $ID)}/\$releasever/\$basearch
+enabled=1
+gpgcheck=1
+gpgkey=https://packages.adoptium.net/artifactory/api/gpg/key/public
+EOF'
+----
+
+.Install Temurin Java {compatible-javajdk}
+[source, console, subs="attributes"]
+----
+sudo dnf install temurin-{compatible-javajdk}-jdk
+----

docs/modules/deployment/pages/core/getting-started.adoc

@@ -1,7 +1,7 @@
 
 [[getting-started-core]]
 = Installation and Configuration
-:description: Install and configure OpenNMS instance including PostgreSQL set up on CentOS/RHEL 9, Debian/Ubuntu, and Docker.
+:description: Install and configure OpenNMS instance including PostgreSQL set up on CentOS 9, Debian/Ubuntu, and Docker.
 
 This section explains how to install and configure a new {page-component-title} instance, including the following tasks:
 
@@ -70,26 +70,25 @@ include::../time-sync.adoc[]
 == Set up PostgreSQL
 
 TIP: PostgreSQL 14 and 15 use the `scram-sha-256` https://www.postgresql.org/docs/14/auth-password.html[password authentication] method by default.
-If you use older versions of PostgreSQL, you should change the method in `postgresql.conf` and in `pg_hba.conf` before installing the {page-component-title} core instance.
+If you use older versions of PostgreSQL, you should change the method to `md5` in the `pg_hba.conf` before installing the {page-component-title} core instance.
 
 == Pool size and maximum database connections
 
-You must configure the PostgreSQL https://www.postgresql.org/docs/15/runtime-config-connection.html[max_connections] setting to at least twice the maximum pool size in {page-component-title}.
+You must configure the PostgreSQL https://www.postgresql.org/docs/15/runtime-config-connection.html[max_connections] setting to allow at least 70 connections.
+The number of connections is defined by the `maxPool` setting for each datasource (opennms 50 + opennms-admin 10 + opennms-monitoring 10).
+The `maxSize` is not used with the `HikariCPConnectionFactory`, which is deprecated and just here for backward compatibility.
 
-The default maximum pool size value in {page-component-title} is 50, but it applies to each connect in `opennms-datasources.xml`: `opennms` (the main connection used at runtime) and `opennms-admin` (the connection used during administrative operations, including installation).
-Therefore, your `max_connections` setting should be at least 100.
-
-If you change the default pool size, make sure you also update the `max_connections`.
+If you change the max pool size, make sure you also update the `max_connections`.
 You typically set this in `PG_HOME/data/postgresql.conf`, but you may also use the `ALTER SYSTEM` syntax.
-You must restart the PostgreSQL server for the changes to take effect.
+You must restart the PostgreSQL server to take effect.
 
 NOTE: You may find https://pgtune.leopard.in.ua/[PGTune] useful to calculate configuration parameters for PostgreSQL.
 As with all third-party tools, we do not endorse or guarantee it.
 Use it at your own discretion.
 
 [{tabs}]
 ====
-CentOS/RHEL 9::
+CentOS 9::
 +
 --
 include::centos-rhel9/postgresql.adoc[]
@@ -124,7 +123,7 @@ Do not expose the web console or sign in pages directly to the Internet without
 
 [{tabs}]
 ====
-CentOS/RHEL 9::
+CentOS 9::
 +
 --
 include::centos-rhel9/install-core.adoc[]
@@ -163,18 +162,12 @@ endif::[]
 
 [{tabs}]
 ====
-CentOS/RHEL 9::
+CentOS 9/10::
 +
 --
 include::centos-rhel/initialize-core.adoc[]
 --
 
-CentOS 10::
-+
---
-include::centos/initialize-core.adoc[]
---
-
 ifeval::["{page-component-title}" == "Horizon"]
 Debian/Ubuntu::
 +

docs/modules/deployment/pages/core/message-broker/kafka-topics.adoc

@@ -12,26 +12,26 @@ All IPC topics use the following format:
 
 Where:
 
-* `{instanceId}` = OpenNMS instance ID (default: `OpenNMS`)
-* `{component}` = IPC component type (e.g., `rpc-request`, `rpc-response`, `Sink`, `twin`)
-* `{endpoint}` = Module or endpoint identifier
-* `{location}` = Minion location (where applicable)
+* `\{instanceId}` = OpenNMS instance ID (default: `OpenNMS`)
+* `\{component}` = IPC component type (e.g., `rpc-request`, `rpc-response`, `Sink`, `twin`)
+* `\{endpoint}` = Module or endpoint identifier
+* `\{location}` = Minion location (where applicable)
 
 == RPC Topics
 
 RPC (Remote Procedure Call) topics are used for request/response communication between Core and Minion.
 
 === Request Topics (per location)
 
-Format: `{instanceId}.{location}.rpc-request`
+Format: `\{instanceId}.\{location}.rpc-request`
 
 Example: `OpenNMS.Default.rpc-request`
 
 NOTE: One request topic is required per Minion location.
 
 === Response Topic (global)
 
-Format: `{instanceId}.rpc-response`
+Format: `\{instanceId}.rpc-response`
 
 Example: `OpenNMS.rpc-response`
 
@@ -41,7 +41,7 @@ NOTE: A single response topic is used for all RPC responses.
 
 Sink topics are used for one-way message streaming from Minion to Core (e.g., events, traps, telemetry, flows).
 
-Format: `{instanceId}.Sink.{moduleId}`
+Format: `\{instanceId}.Sink.\{moduleId}`
 
 === Required Sink Topic
 
@@ -80,7 +80,7 @@ These topics are only needed when the corresponding feature is enabled:
 
 === Telemetry/Flow Sink Topics
 
-Telemetry and flow topics use the module ID format `Telemetry-{queueName}`. The queue name is defined in `telemetryd-configuration.xml`.
+Telemetry and flow topics use the module ID format `Telemetry-\{queueName}`. The queue name is defined in `telemetryd-configuration.xml`.
 
 NOTE: These are default queue names. If queue names were customized in `telemetryd-configuration.xml`, topic names will differ.
 
@@ -117,7 +117,7 @@ NOTE: These are default queue names. If queue names were customized in `telemetr
 | Graphite metrics
 |===
 
-NOTE: The actual telemetry topic names depend on your telemetry daemon configuration. The queue name is specified in `telemetryd-configuration.xml` and the module ID is `Telemetry-{queueName}`.
+NOTE: The actual telemetry topic names depend on your telemetry daemon configuration. The queue name is specified in `telemetryd-configuration.xml` and the module ID is `Telemetry-\{queueName}`.
 
 .Example Sink Topics
 ----
@@ -139,15 +139,15 @@ Twin topics are used for configuration synchronization between Core and Minion.
 
 === Request Topic (global)
 
-Format: `{instanceId}.twin.request`
+Format: `\{instanceId}.twin.request`
 
 Example: `OpenNMS.twin.request`
 
 === Response Topics
 
-Global response topic: `{instanceId}.twin.response`
+Global response topic: `\{instanceId}.twin.response`
 
-Per-location response topic: `{instanceId}.twin.response.{location}`
+Per-location response topic: `\{instanceId}.twin.response.\{location}`
 
 .Example Twin Topics
 ----

docs/modules/deployment/pages/core/system-requirements.adoc

@@ -35,12 +35,10 @@ OpenNMS {page-component-title} requires one of the following operating systems:
 | Operating System  | Compatible Versions (64-bit)
 
 | RHEL
-| {compatible-rhel9} +
-{compatible-rhel10}
+| {compatible-rhel}
 
 | CentOS
-| {compatible-centos-stream9} +
-{compatible-centos-stream10}
+| {compatible-centos}
 
 ifeval::["{page-component-title}" == "Horizon"]
 | Debian
@@ -94,4 +92,4 @@ Components marked with an asterisk are required:
 |===
 
 == Containerized environments
-See xref:deployment:core/containers.adoc[containerized deployment] for information on deploying {page-component-title} via Kubernetes or OpenShift.
+See xref:deployment:core/containers.adoc[containerized deployment] for information on deploying {page-component-title} via Kubernetes or OpenShift.

docs/modules/deployment/pages/minion/system-requirements.adoc

@@ -35,11 +35,10 @@ OpenNMS {page-component-title} runs on the following operating systems:
 | Operating System  | Supported Versions (64-bit)
 
 | RHEL
-| {compatible-rhel8} +
-{compatible-rhel9}
+| {compatible-rhel}
 
 | CentOS
-| {compatible-centos-stream}
+| {compatible-centos}
 
 ifeval::["{page-component-title}" == "Horizon"]
 | Debian