Add execution nodes

You can define remote execution nodes in the [execution_nodes] group of your inventory file:

[execution_nodes]
<fqdn_of_your_execution_host>

By default, an execution node uses the following settings that you can update as needed:

receptor_port=27199
receptor_protocol=tcp
receptor_type=execution

• receptor_port - The port number that receptor listens on for incoming connections from other receptor nodes.
• receptor_type - The role of the node. Valid options include execution or hop.
• receptor_protocol - The protocol used for communication. Valid options include tcp or udp.

By default, execution nodes automatically peer with all automation controller nodes. To configure an execution node to peer with specific automation controller nodes instead, use the receptor_peers variable.

Example:

[execution_nodes]
# Uses default peering (peers with all controller nodes)
exec1.example.com
# Only peers with specific controller nodes
exec2.example.com receptor_peers='["controller1.example.com","controller2.example.com"]'
# Hop node that peers with specific execution nodes
hop1.example.com receptor_type=hop receptor_peers='["exec1.example.com","exec2.example.com"]'