Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
NETCONF Functionality Test Suite
Purpose
This test ensures the functionality of the ONOS's ability to use the NETCONF communication protocol to configure switches.
Test Overview
This test uses a single node which will be emulated via mininet. It will use a combination of the REST API and the ONOS CLI to connect, configure, and disconnect a device using the NETCONF protocol. This test does not configure specific devices, but rather demonstrates the ability of ONOS to configure a device using NETCONF assuming the appropriate drivers and variables are set.
The specifics of the device to be connected should be set in the .params file.
| Test Cases # | Description | Pass Criteria | Road Map |
|---|---|---|---|
| 1 | Set up test parameters | Pass if params are set | Finished |
| 2 | Set cell and build, uninstall, and install ONOS | Pass if sets cell correctly and build, uninstall, and install passes | Finished |
| 10 | Setup Mininet with 1.0 OVS | Pass if mininet, switch assignment and topology comparison all pass | Finished |
| 11 | Setup Mininet with 1.3 OVS | Pass if mininet, switch assignment and topology comparison all pass | Finished |
| 14 | Stop Mininet | Pass if mininet and switches are successfully stopped | Finished |
Make sure the netconf app is activated | Pass if NETCONF app is successfully started or already running | Finished | |
Write a configuration file and upload it to ONOS through REST API to connect a device | Pass if config file is written and a 200 response is given by ONOS REST | In progress | |
Get and Set configurations using the device-controllers and device-set controllers method | Pass if valid responses | In progress | |
| Disconnect a device | Pass if device is successfully disconected | In progress |