Foreman Remote Execution Setup

[aruzicka]

Hi,

@chr1s

But how do the setup look like, if we run forman on N diffent nodes? Do we need a seperate/central redis or dynflow-sidekiq cluster?

This actually depends on you and your needs, you can do both. Someone else was in a similar situation before and I posted more elaborate answer there Foreman Tasks with new Redis support - #3 by aruzicka , the same will apply here.

@chr1s

But do we need to start a seperate dynflow process on the Foreman Smart Proxy?

Again, it depends. There are two options. Either you run dynflow inside the smart proxy or you run it as a standalone process.

@chr1s

Here it is not 100% clear for us, which extra gem we need. Only the *_core or all (smart_proxy_remote_execution_ssh, smart_proxy_dynflow, smart_proxy_dynflow_core, foreman_remote_execution_core, foreman-tasks-core)

Either way, you need to load all the relevant non *_core gems into the smart proxy. Those are the ones which define the APIs, settings and features.

The easiest way is to run dynflow inside the smart proxy. For that, you just need to require all the relevant *_core gems and it should be good to go. This is actually the way how things get set up by the installer on deb based platforms.

@chr1s

start a seperate dynflow process on the Foreman Smart Proxy? How is it done? Where can we find the dynflow binary?

Alternatively, you could set up smart_proxy_dynflow_core from source (GitHub - theforeman/smart_proxy_dynflow: Dynflow runtime for Foreman smart proxy), require all the *_core gems into it and configure the smart proxy to use this external process (in config/settings.d/dynflow.yml). This is what the installer does on EL* based platforms.

Both ways have its pros and cons, the internal dynflow is easier to deploy, but if under heavy load it could have negative impact on other smart proxy functionality.