12.3. Configuring Global Settings
Table 12.2. Global Settings for Remote Execution
This is the default effective user for any job. When the job is executed the effective user of the process is changed accordingly (for example, by sudo). This option can be overridden per job template and job invocation.
Specifies which method to use to set the effective user on the target host. Currently only su and sudo are supported.
Search the host for any Capsule with remote execution configured. This is useful when the host has no subnet or if the subnet does not have a Capsule with remote execution enabled.
Search for a remote execution Capsule outside of the Capsules assigned to the host. If Locations or Organizations are enabled, the search will be limited to the host's Organization or Location.
The default user to use while the Capsule connects to the target using SSH. You can set the
You can set this by Host, Host Group, Operating System, Domain, Location, or Organization. This can also be a different user from the
|remote_execution_sync_templates||Defines whether job templates should be synchronized from disk when seeding a database.|
/etc/foreman/settings.yamlconfiguration file, but any manual changes that you make to this file are overwritten the next time you run
satellite-installer. Consequently, Red Hat recommends that you modify these parameters in the web UI. Alternatively, use the
foreman-rake configcommand from a console.
12.3.1. Choosing a Capsule for Remote Execution
falseto disable this behavior. This may be necessary in more complex environments, where not all Capsules can be used due to possible network isolation. In this configuration, you can assign a pool of Capsules to each subnet, and jobs are load balanced across them.
trueto enable fallback mode. In this configuration, remote execution will use any Capsule associated with the host, such as its Puppet Master, provided that Capsule also has remote execution configured.