Nornir Service Test Task¤
task api name:
test
The Nornir Service test
task designed to facilitate the execution of network tests. This task provides network operations engineers and network automation developers with tools to validate network configurations, ensure compliance, and monitor network performance. By leveraging the capabilities of the Nornir service, users can automate testing process, identify issues proactively, and maintain a robust network infrastructure.
Nornir service test
task uses Nornir TestsProcessor to run the tests and support test suites definition in YAML format, where test suite YAML files can be stored on and sourced from broker.
Nornir Test Sample Usage¤
Nornir service test
task uses suites in YAML format to define tests, sample tests suite:
- name: Check ceos version
task: "show version"
test: contains
pattern: "4.30.0F"
- name: Check NTP status
test: ncontains
pattern: "unsynchronised"
task: "show ntp status"
- name: Check Mgmt Interface Status
test: contains
pattern: "is up, line protocol is up"
task: "show interface management0"
File suite_3.txt
stored on broker and downloaded by Nornir service prior to running tests, below is an example of how to run the tests suite.
Example
C:\nf>nfcli
Welcome to NorFab Interactive Shell.
nf#
nf#nornir
nf[nornir-test]#
nf[nornir-test]#suite nf://nornir_test_suites/suite_3.txt FC spine,leaf
--------------------------------------------- Job Events -----------------------------------------------
07-Jan-2025 18:44:35 0c3309c54ee44397b055257a0d442e62 job started
07-Jan-2025 18:44:35.207 nornir nornir-worker-1 ceos-spine-1, ceos-spine-2 task started - 'netmiko_send_commands'
07-Jan-2025 18:44:35.211 nornir nornir-worker-2 ceos-leaf-1, ceos-leaf-2, ceos-leaf-3 task started - 'netmiko_send_commands'
<omitted for brevity>
07-Jan-2025 18:44:36 0c3309c54ee44397b055257a0d442e62 job completed in 1.391 seconds
--------------------------------------------- Job Results --------------------------------------------
+----+--------------+-----------------------------+----------+-------------------+
| | host | name | result | exception |
+====+==============+=============================+==========+===================+
| 0 | ceos-leaf-1 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 1 | ceos-leaf-1 | Check NTP status | FAIL | Pattern in output |
+----+--------------+-----------------------------+----------+-------------------+
| 2 | ceos-leaf-1 | Check Mgmt Interface Status | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 3 | ceos-leaf-2 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 4 | ceos-leaf-2 | Check NTP status | FAIL | Pattern in output |
+----+--------------+-----------------------------+----------+-------------------+
| 5 | ceos-leaf-2 | Check Mgmt Interface Status | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 6 | ceos-leaf-3 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 7 | ceos-leaf-3 | Check NTP status | FAIL | Pattern in output |
+----+--------------+-----------------------------+----------+-------------------+
| 8 | ceos-leaf-3 | Check Mgmt Interface Status | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 9 | ceos-spine-1 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 10 | ceos-spine-1 | Check NTP status | FAIL | Pattern in output |
+----+--------------+-----------------------------+----------+-------------------+
| 12 | ceos-spine-2 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 12 | ceos-spine-2 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 12 | ceos-spine-2 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 12 | ceos-spine-2 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 12 | ceos-spine-2 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 13 | ceos-spine-2 | Check NTP status | FAIL | Pattern in output |
+----+--------------+-----------------------------+----------+-------------------+
| 12 | ceos-spine-2 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 12 | ceos-spine-2 | Check ceos version | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
| 13 | ceos-spine-2 | Check NTP status | FAIL | Pattern in output |
+----+--------------+-----------------------------+----------+-------------------+
| 14 | ceos-spine-2 | Check Mgmt Interface Status | PASS | |
+----+--------------+-----------------------------+----------+-------------------+
nf[nornir-test]#
nf[nornir-test]#top
nf#
Demo
In this example:
nfcli
command starts the NorFab Interactive Shell.nornir
command switches to the Nornir sub-shell.test
command switches to thetest
task sub-shell.suite
argument refers to a path forsuite_3.txt
file with a set of tests to run.- Devices filtered using
FC
- "Filter Contains" Nornir hosts targeting filter to only run tests on devices that containspine
orleaf
in their hostname.
inventory.yaml
should be located in same folder where we start nfcli, unless nfcli -i path_to_inventory.yaml
flag used. Refer to Getting Started section on how to construct inventory.yaml
file
This code is complete and can run as is
import pprint
from norfab.core.nfapi import NorFab
if __name__ == '__main__':
nf = NorFab(inventory="inventory.yaml")
nf.start()
client = nf.make_client()
res = client.run_job(
service="nornir",
task="test",
kwargs={
"suite": "nf://nornir_test_suites/suite_3.txt",
"FC": "spine,leaf"
}
)
pprint.pprint(res)
nf.destroy()
Refer to Getting Started section on how to construct inventory.yaml
file.
Formatting Tests Output¤
NorFab interactive shell allows you to format the results of network tests into text tables. This is particularly useful for presenting test results in a clear and organized manner, making it easier to analyze and interpret the data. The NorFab interactive shell supports the table
command, which relies on the tabulate module to generate text tables. By outputting test results in table format, you can quickly identify issues and take appropriate action.
Using Jinja2 Templates to Generate Tests¤
Using Jinja2 Templates enables you to create dynamic test suites based on variables defined in your inventory or passed as job data. This approach allows you to tailor tests to specific devices or scenarios, ensuring that the tests are relevant and accurate. Jinja2 templates provide a powerful way to automate the creation of complex test cases, incorporating conditional logic, loops, and other advanced features to meet your testing requirements.
Templating Tests with Inline Job Data¤
Inline Job Data allows you to define test parameters directly within the job_data
argument, making it easy to customize tests on the fly. This feature is particularly useful for scenarios where test parameters need to be adjusted frequently or based on specific conditions. By templating tests with inline job data, you can ensure that your tests are always up-to-date and aligned with the current network state.
Using Dry Run¤
The Using Dry Run feature allows you to generate the content of network test suites without actually performing any actions on the devices. This is useful for validation purposes, as it enables you to verify the correctness of your tests before running them. By using dry run, you can identify potential issues and make necessary adjustments, ensuring that your tests will execute successfully when run for real.
Running a Subset of Tests¤
Running a Subset of Tests allows you to execute only a specific set of tests, rather than running the entire test suite. This is useful for targeted testing, such as validating changes in a particular part of the network configuration or focusing on specific devices features. By running a subset of tests, you can save time and resources, while still ensuring that critical aspects of the network are thoroughly tested.
Returning Only Failed Tests¤
Returning only failed tests enables you to filter the test results to show only the tests that have failed. This is particularly useful for quickly identifying and addressing issues, as it allows you to focus on the areas that require attention. By returning only failed tests, you can streamline the troubleshooting process and ensure that network problems are resolved efficiently.
NORFAB Nornir Test Shell Reference¤
The NORFAB Nornir Test Shell Reference provides a comprehensive set of command options for the Nornir test
task. These commands allow you to control various aspects of the test execution, such as setting job timeouts, filtering devices, adding task details to results, and configuring retry mechanisms. By leveraging these command options, you can tailor the behavior of the tests to meet your specific network management needs, ensuring that your network remains reliable and performant.
NorFab shell supports these command options for Nornir test
task:
nf#man tree nornir.test
root
└── nornir: Nornir service
└── test: Run network tests
├── timeout: Job timeout
├── workers: Filter worker to target, default 'all'
├── add_details: Add task details to results
├── run_num_workers: RetryRunner number of threads for tasks execution
├── run_num_connectors: RetryRunner number of threads for device connections
├── run_connect_retry: RetryRunner number of connection attempts
├── run_task_retry: RetryRunner number of attempts to run task
├── run_reconnect_on_fail: RetryRunner perform reconnect to host on task failure
├── run_connect_check: RetryRunner test TCP connection before opening actual connection
├── run_connect_timeout: RetryRunner timeout in seconds to wait for test TCP connection to establish
├── run_creds_retry: RetryRunner list of connection credentials and parameters to retry
├── tf: File group name to save task results to on worker file system
├── tf_skip_failed: Save results to file for failed tasks
├── diff: File group name to run the diff for
├── diff_last: File version number to diff, default is 1 (last)
├── progress: Emit execution progress
├── headers: Table headers
├── headers_exclude: Table headers to exclude
├── sortby: Table header column to sort by
├── reverse: Table reverse the sort by order
├── FO: Filter hosts using Filter Object
├── FB: Filter hosts by name using Glob Patterns
├── FH: Filter hosts by hostname
├── FC: Filter hosts containment of pattern in name
├── FR: Filter hosts by name using Regular Expressions
├── FG: Filter hosts by group
├── FP: Filter hosts by hostname using IP Prefix
├── FL: Filter hosts by names list
├── FM: Filter hosts by platform
├── FX: Filter hosts excluding them by name
├── FN: Negate the match
├── hosts: Filter hosts to target
├── *suite: Nornir suite nf://path/to/file.py, default 'PydanticUndefined'
├── dry_run: Return produced per-host tests suite content without running tests
├── subset: Filter tests by name
├── failed_only: Return test results for failed tests only
├── remove_tasks: Include/Exclude tested task results
└── job_data: Path to YAML file with job data
nf#
*
- mandatory/required command argument
Python API Reference¤
Function to test networks using a suite of tests.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
suite
|
Union[list, str]
|
Path to YAML file with tests or a list of test definitions. |
required |
subset
|
str
|
List or string with comma-separated non-case-sensitive glob patterns to filter tests by name. Ignored if dry_run is True. |
None
|
dry_run
|
bool
|
If True, returns produced per-host tests suite content only. |
False
|
remove_tasks
|
bool
|
If False, results will include other tasks output. |
True
|
failed_only
|
bool
|
If True, returns test results for failed tests only. |
False
|
return_tests_suite
|
bool
|
If True, returns rendered per-host tests suite
content in addition to test results using a dictionary with |
False
|
job_data
|
str
|
URL to YAML file with data or dictionary/list of data to pass on to Jinja2 rendering context. |
None
|
**kwargs
|
Any additional arguments to pass on to the Nornir service task. |
{}
|
Returns:
Name | Type | Description |
---|---|---|
dict |
dict
|
A dictionary containing the test results. If |
Raises:
Type | Description |
---|---|
RuntimeError
|
If there is an error in rendering the Jinja2 templates or loading the YAML. |
Source code in norfab\workers\nornir_worker.py
1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 |
|