From ee3f7a8badf57888868b2d1b8cc4be78f7dbfc04 Mon Sep 17 00:00:00 2001 From: Dmitri Popov Date: Tue, 4 Feb 2025 11:58:40 +0100 Subject: [PATCH] Trento reorg install agents (#204) * Install agents include --------- Co-authored-by: Dmitri Popov --- trento/xml/article_sap_trento.xml | 147 +-------------------- trento/xml/trento-install-agents.xml | 183 +++++++++++++++++++++++++++ 2 files changed, 184 insertions(+), 146 deletions(-) create mode 100644 trento/xml/trento-install-agents.xml diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 6d445b79..19f3c4d6 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -83,152 +83,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off - -
- Installing &t.agent;s - - Expect changes in the installation procedure - - The product is under active development. Expect changes in the described - installation procedure. - - - - - Before you can install a &t.agent;, retrieve the API key of your &t.server;. - Proceed as follows: - - - - - Open the URL of the Trento Web console (http://TRENTO_SERVER_HOSTNAME). - It prompts you for a user name and password: - - - - - - - - - - - - Enter the credentials for the admin user - (established when installing &t.server;). - - - Click Login. As this is the first time you access the console, - you will be prompted to accept the license agreement. Click Accept to continue. - Otherwise, you cannot use Trento. - - - Once inside the console, go to Settings: - - - - - - - - - - - Click the Copy button to copy the key to your clipboard. - - - - To install the &t.agent; on an SAP host and register it - with the &t.server;, repeat the steps in : - - - Installing &t.agent;s - - - Install the package: - - &prompt.user;sudo zypper ref -&prompt.user;sudo zypper install trento-agent - - - - Open the configuration file /etc/trento/agent.yaml - and uncomment (use #) the entries for - facts-service-url, server-url and - api-key. Update the values appropriately: - - - - facts-service-url: the address of the AMQP RabbitMQ service used - for communication with the checks engine (wanda). The correct value of this parameter depends on - how &t.server; was deployed. - In a Kubernetes deployment, it is amqp://trento:trento@TRENTO_SERVER_HOSTNAME:5672/. If the default RabbitMQ username and password (trento) were updated using helm, - the parameter must use the custom value. - In a systemd or containerized deployment, the correct value is amqp://TRENTO_USER:TRENTO_USER_PASSWORD@TRENTO_SERVER_HOSTNAME:5672/vhost. If TRENTO_USER and TRENTO_USER_PASSWORD were replaced with custom values, you must use them. - - - - server-url: URL for the Trento Server (http://TRENTO_SERVER_HOSTNAME) - - - - - api-key: the API key retrieved from the Web console - - - - - - - If SSL termination has been enabled on the server side, you can encrypt the - communication from the agent to the server as follows: - - - Provide an HTTPS URL instead of an HTTP one. - - - Import the certificate from the CA that has issued your - &t.server; SSL certificate into the &t.agent; host as follows: - - - Copy the CA certificate in PEM format to /etc/pki/trust/anchors/. - If your CA certificate is in CRT format, convert it to PEM using the openssl - command as follows: - - openssl x509 -in mycert.crt -out mycert.pem -outform PEM - - - Run the update-ca-certificates command. - - - - - - - - Start the &t.agent;: - - &prompt.user;sudo systemctl enable --now trento-agent - - - Check the status of the &t.agent;: - &prompt.user;sudo systemctl status trento-agent -● trento-agent.service - &t.agent; service - Loaded: loaded (/usr/lib/systemd/system/trento-agent.service; enabled; vendor preset: disabled) - Active: active (running) since Wed 2021-11-24 17:37:46 UTC; 4s ago - Main PID: 22055 (trento) - Tasks: 10 - CGroup: /system.slice/trento-agent.service - ├─22055 /usr/bin/trento agent start --consul-config-dir=/srv/consul/consul.d - └─22220 /usr/bin/ruby.ruby2.5 /usr/sbin/SUSEConnect -s - -[...] - - - Repeat this procedure in all SAP hosts that you want to monitor. - - -
+
User management diff --git a/trento/xml/trento-install-agents.xml b/trento/xml/trento-install-agents.xml new file mode 100644 index 00000000..4585b909 --- /dev/null +++ b/trento/xml/trento-install-agents.xml @@ -0,0 +1,183 @@ + + + + %entities; +]> +
+ Installing &t.agent;s + + Before you can install a &t.agent;, you must obtain the API key of your &t.server;. + Proceed as follows: + + + + + Open the URL of the Trento Web interface + (http://TRENTO_SERVER_HOSTNAME). + It prompts you for a user name and password: + + + + + + + + + + + + + Enter the credentials for the admin user (specified during installation of + &t.server;). + + + + + Click Login. + + + + + When you are logged in, go to Settings: + + + + + + + + + + + + + Click the Copy button to copy the key to the clipboard. + + + + + To install the &t.agent; on an SAP host and register it with the &t.server;, + repeat the steps in : + + + Installing &t.agent;s + + + Install the package: + +&prompt.user;sudo zypper ref +&prompt.user;sudo zypper install trento-agent + + + + Open the configuration file /etc/trento/agent.yaml + and uncomment (remove the + # character) the entries for facts-service-url, + server-url and api-key. + Update the values as necessary: + + + + + facts-service-url: the address of the AMQP + RabbitMQ service used for communication with the checks engine + (wanda). The correct value of this parameter depends on how + &t.server; was deployed. + + + In a &k8s; deployment, it is + amqp://trento:trento@TRENTO_SERVER_HOSTNAME:5672/. If the + default RabbitMQ username and password + (trento:trento) were updated using Helm, the + parameter must use a user-defined value. + + + In a systemd or containerized deployment, the correct value is + amqp://TRENTO_USER:TRENTO_USER_PASSWORD@TRENTO_SERVER_HOSTNAME:5672/vhost. + If TRENTO_USER and + TRENTO_USER_PASSWORD have been replaced + with custom values, you must use them. + + + + + server-url: URL for the Trento Server + (http://TRENTO_SERVER_HOSTNAME) + + + + + api-key: the API key retrieved from the Web console + + + + + + + If SSL termination has been enabled on the server side, you can encrypt + the communication from the agent to the server as follows: + + + + + Provide an HTTPS URL instead of an HTTP one. + + + + + Import the certificate from the Certificate Authority that has + issued your &t.server; SSL certificate into the &t.agent; host as + follows: + + + + + Copy the CA certificate in the PEM format to + /etc/pki/trust/anchors/. If the CA + certificate is in the CRT format, convert it to PEM using the + following openssl command: + +openssl x509 -in mycert.crt -out mycert.pem -outform PEM + + + + Run the update-ca-certificates command. + + + + + + + + + Start the &t.agent;: + +&prompt.user;sudo systemctl enable --now trento-agent + + + + Check the status of the &t.agent;: + +&prompt.user;sudo systemctl status trento-agent +● trento-agent.service - &t.agent; service + Loaded: loaded (/usr/lib/systemd/system/trento-agent.service; enabled; vendor preset: disabled) + Active: active (running) since Wed 2021-11-24 17:37:46 UTC; 4s ago + Main PID: 22055 (trento) + Tasks: 10 + CGroup: /system.slice/trento-agent.service + ├─22055 /usr/bin/trento agent start --consul-config-dir=/srv/consul/consul.d + └─22220 /usr/bin/ruby.ruby2.5 /usr/sbin/SUSEConnect -s + +[...] + + + + Repeat this procedure on all SAP hosts that you want to monitor. + + + +