From e4766a513f2a8a14b8a07fe7b55b7d62896e8973 Mon Sep 17 00:00:00 2001 From: alazik Date: Thu, 11 Apr 2024 14:06:30 +0200 Subject: [PATCH] Add option to switch back to SSH REX mode BZ: https://bugzilla.redhat.com/show_bug.cgi?id=2269398 --- .../con_transport-modes-for-remote-execution.adoc | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/guides/common/modules/con_transport-modes-for-remote-execution.adoc b/guides/common/modules/con_transport-modes-for-remote-execution.adoc index 068d5fa9e6c..5c92e9816a1 100644 --- a/guides/common/modules/con_transport-modes-for-remote-execution.adoc +++ b/guides/common/modules/con_transport-modes-for-remote-execution.adoc @@ -9,6 +9,16 @@ The SSH service must be enabled and active on the target hosts. The remote execution {SmartProxy} must have access to the SSH port on the target hosts. Unless you have a different setting, the standard SSH port is 22. +[NOTE] +==== +If your {SmartProxy} already uses the `pull-mqtt` mode and you want to switch back to the `ssh` mode, run this `{foreman-installer}` command: + +[options="nowrap",subs="+quotes,verbatim,attributes"] +---- +# {foreman-installer} --foreman-proxy-plugin-remote-execution-script-mode=ssh +---- +==== + On {SmartProxies} in `pull-mqtt` mode, remote execution uses Message Queueing Telemetry Transport (MQTT) to publish jobs it receives from {ProjectServer}. The host subscribes to the MQTT broker on {SmartProxy} for job notifications using the `yggdrasil` pull client. After the host receives a notification, it pulls job details from {SmartProxy} over HTTPS, runs the job, and reports results back to {SmartProxy}.