Itential Automation GatewayAnsible

Role execution parameters

Itential Automation Gateway (IAG) clients execute roles on a device using the REST /roles/{role_name}/execute route. The role execution input parameter is a JSON object that contains an array of host strings and an args object that includes a set of key/value pairs specific to the role. A JSON schema describing each role’s argument parameters is available via the /roles/{role_name} route. Detailed documentation on role endpoints can be found in the API Documentation section of the Automation Gateway UI.

Role request object

Below is a sample role input parameter for the itential_set_config role:

1{
2  "hosts":["eos_host"],
3  "args":
4  {  
5    "transactions": [
6      {
7        "action": "add",
8        "parents": ["interface Management 1"],
9        "config_line": "ip address 10.1.2.3/24",
10        "id": "anyIDString"
11      }
12    ]
13  },
14  "strict_args": true
15}

An Ansible role consists of a number of tasks, each of which produces its own results object, as discussed in the section that follows.

IAG collects the task results objects and returns them as an array in the order in which they were executed.

For information on execution flow in the release versions of IAG, see Execution flow by role type.

Task results object and key

The Itential Ansible roles include a task results object with a task key whose value always takes the form of the task key naming convention shown below:

1{role} response

Where {role} is replaced with the name of the role executed.

Example: itential_set_config response

The results object from that response task contains the response data from the role for the device.

All other task results can be ignored and are available for informational and debugging purposes only.

The format of the data contained within the results object varies per role.

A status key also indicates whether the task succeeded (SUCCESS) or failed (FAILURE).

Roles that contain multiple requests will have multiple response objects, each with their own status and results keys.

Role response

Below is the sample role response for the itential_set_config role:

1[
2    {
3        "role": "itential_set_config",
4        "task": "execute config module on eos platform",
5        "host": "eos_host",
6        "status": "SUCCESS",
7        "argument_warnings": null,
8        "results": {
9            "commands": [
10                "interface Management 1",
11                "ip address 10.0.5.17/24"
12            ],
13            "changed": true,
14            "session": "ansible_1548718829",
15            "updates": [
16                "interface Management 1",
17                "ip address 10.0.5.17/24"
18            ],
19            "diff": {
20                "prepared": "--- system:/running-config\n+++ session:/ansible_1548718829-session-config\n@@ -27,6 +27,7 @@\n
21    ip address 192.168.32.20/24\n !\n interface Management1\n+   ip address 10.0.5.17/24\n !\n ip route 0.0.0.0/0 10.0.2.2\n !"
22            }
23        }
24    },
25    {
26        "role": "itential_set_config",
27        "task": "itential_set_config response",
28        "host": "eos_host",
29        "status": "SUCCESS",
30        "argument_warnings": null,
31        "results": {
32            "config_request": {
33                "action": "add",
34                "config_line": "ip address 10.0.5.17/24",
35                "parents": [
36                    "interface Management 1"
37                ],
38                "id": "anyIDString"
39            },
40            "config_response": {
41                "failed": false,
42                "changed": true,
43                "id": "anyIDString"
44            },
45            "changed": false
46        }
47    }
48]