From d956cfa41f8e1a902af49855efbb446360009a25 Mon Sep 17 00:00:00 2001 From: Dmitri Popov Date: Thu, 30 Jan 2025 15:57:23 +0100 Subject: [PATCH] Trento requirements include --- trento/xml/article_sap_trento.xml | 93 +----------------------- trento/xml/html/rh-article-trento.html | 88 +++++++++++++++++++++++ trento/xml/trento-requirements.xml | 97 ++++++++++++++++++++++++++ 3 files changed, 186 insertions(+), 92 deletions(-) create mode 100644 trento/xml/html/rh-article-trento.html create mode 100644 trento/xml/trento-requirements.xml diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 2f0dbb9f..daa8d738 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -81,99 +81,8 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off - + -
- Requirements - This section describes requirements for the &t.server; and its - &t.agent;s. -
- &t.server; requirements - Running all the &t.server; components requires a minimum of 4 GB of RAM, - two CPU cores and 64 GB of storage. - When using K3s, such storage should be provided under /var/lib/rancher/k3s. - - - Trento is powered by event driven technology. Registered events are stored in a &postgresql; database with a default retention - period of 10 days. For each host registered with Trento, you need to allocate at least 1.5GB of space in the &postgresql; database. - - &t.server; supports different deployment scenarios: &k8s;, systemd and containerized. A &k8s; based deployment of &t.server; is meant to be - cloud native and OS agnostic. It can be done on the following services: - - - RKE1 (&rancher.k8s.engine; version 1) - - - RKE2 - - - a &k8s; service in a cloud provider - - - any other CNCF-certified &k8s; running on x86_64 architecture - - - A proper, production ready &k8s; based deployment of &t.server; requires &k8s; - knowledge. The Helm chart is meant to be used by customers lacking such knowledge - or who want to get started quickly. However, Helm chart delivers a basic deployment of the &t.server; with all the components running - on a single node of the cluster. -
-
- &t.agent; requirements - The resource footprint of the &t.agent; is designed to not - impact the performance of the host it runs on. - The &t.agent; component needs to interact with several - low-level system components that are part of the &sles4sap; distribution. - Trento requires unique machine identifiers (ids) on the hosts to be registered. Therefore, if any host in your environment is built as a clone of another one, - ensure that you change the machine identifier as part of the cloning process before starting the &t.agent; on it. - Similarly, Trento requires unique authkeys on the clusters to be registered. -
-
- Network requirements - - - - toms 2021-12-06: do we have UDP here too? - From any &t.agent; host, the Web component of the &t.server; must be reachable via HTTP (port TCP/80) or via HTTPS (port TCP/443) if SSL is enabled. - - - - - From any &t.agent; host, the checks engine component of the &t.server;, called Wanda, must be reachable via Advanced Message Queuing Protocol or AMQP (port TCP/5672). - - - - - The Prometheus component of the &t.server; must be able to reach the Node Exporter in the &t.agent; hosts (port TCP/9100). - - - - The &sap; Basis administrator needs access to the Web component of the &t.server; via HTTP (port TCP/80) or via HTTPS (port TCP/443) if SSL is enabled. - - -
-
- Installation prerequisites - - - - &t.server; - Access to &suse; public registry for the deployment of &t.server; containers, if we choose a &k8s; based deployment. - A registered &sles4sap; 15 (SP3 or higher) distribution, if we choose a systemd deployment. Both in the case of a containerized deployment. - - - - - &t.agent;s - A registered &sles4sap; 15 (SP3 or higher) distribution. - - - -
-
Installing &t.server; diff --git a/trento/xml/html/rh-article-trento.html b/trento/xml/html/rh-article-trento.html new file mode 100644 index 00000000..0bdf4045 --- /dev/null +++ b/trento/xml/html/rh-article-trento.html @@ -0,0 +1,88 @@ + +Revision History: Getting Started with Trento (Getting Started with Trento) + + + + + + + + + + + + + + + + + +

Revision History: Getting Started with Trento

2021-12-10

+

+ Initial version +

+
diff --git a/trento/xml/trento-requirements.xml b/trento/xml/trento-requirements.xml new file mode 100644 index 00000000..2b1453fa --- /dev/null +++ b/trento/xml/trento-requirements.xml @@ -0,0 +1,97 @@ + + + + %entities; +]> + +
+ Requirements + This section describes requirements for the &t.server; and its + &t.agent;s. +
+ &t.server; requirements + Running all the &t.server; components requires a minimum of 4 GB of RAM, + two CPU cores and 64 GB of storage. + When using K3s, such storage should be provided under /var/lib/rancher/k3s. + + + Trento is powered by event driven technology. Registered events are stored in a &postgresql; database with a default retention + period of 10 days. For each host registered with Trento, you need to allocate at least 1.5GB of space in the &postgresql; database. + + &t.server; supports different deployment scenarios: &k8s;, systemd and containerized. A &k8s; based deployment of &t.server; is meant to be + cloud native and OS agnostic. It can be done on the following services: + + + RKE1 (&rancher.k8s.engine; version 1) + + + RKE2 + + + a &k8s; service in a cloud provider + + + any other CNCF-certified &k8s; running on x86_64 architecture + + + A proper, production ready &k8s; based deployment of &t.server; requires &k8s; + knowledge. The Helm chart is meant to be used by customers lacking such knowledge + or who want to get started quickly. However, Helm chart delivers a basic deployment of the &t.server; with all the components running + on a single node of the cluster. +
+
+ &t.agent; requirements + The resource footprint of the &t.agent; is designed to not + impact the performance of the host it runs on. + The &t.agent; component needs to interact with several + low-level system components that are part of the &sles4sap; distribution. + Trento requires unique machine identifiers (ids) on the hosts to be registered. Therefore, if any host in your environment is built as a clone of another one, + ensure that you change the machine identifier as part of the cloning process before starting the &t.agent; on it. + Similarly, Trento requires unique authkeys on the clusters to be registered. +
+
+ Network requirements + + + + toms 2021-12-06: do we have UDP here too? + From any &t.agent; host, the Web component of the &t.server; must be reachable via HTTP (port TCP/80) or via HTTPS (port TCP/443) if SSL is enabled. + + + + + From any &t.agent; host, the checks engine component of the &t.server;, called Wanda, must be reachable via Advanced Message Queuing Protocol or AMQP (port TCP/5672). + + + + + The Prometheus component of the &t.server; must be able to reach the Node Exporter in the &t.agent; hosts (port TCP/9100). + + + + The &sap; Basis administrator needs access to the Web component of the &t.server; via HTTP (port TCP/80) or via HTTPS (port TCP/443) if SSL is enabled. + + +
+
+ Installation prerequisites + + + + &t.server; + Access to &suse; public registry for the deployment of &t.server; containers, if we choose a &k8s; based deployment. + A registered &sles4sap; 15 (SP3 or higher) distribution, if we choose a systemd deployment. Both in the case of a containerized deployment. + + + + + &t.agent;s + A registered &sles4sap; 15 (SP3 or higher) distribution. + + + +
+
\ No newline at end of file