| Jeremy | fc567ca | 2016-02-16 15:08:25 -0800 | [diff] [blame] | 1 | Summary: |
| 2 | This test suite consists of generic NETCONF protocol testing within ONOS |
| 3 | using OF-Config to translate NETCONF requests for OVSDB. |
| 4 | The following is an overview of how the NETCONF protocol is tested |
| 5 | Steps: |
| 6 | - Start NETCONF App in all currently running nodes |
| 7 | - Start OF-Config server on device to be configured |
| 8 | - Create configuration file |
| 9 | - Upload the configuration file to the device to be configured |
| 10 | - Verify that the device was configured successfully |
| 11 | |
| 12 | Required: |
| 13 | Make sure that OF-Config, https://github.com/openvswitch/of-config, is |
| 14 | installed on the device that is to be configured, the test assumes this |
| 15 | device is the machine running TestON. |
| 16 | Ensure that <cfgName> and <cfgPass> in the params file are the username |
| 17 | and password required to ssh into the desired machine and account that |
| 18 | of-config is to be run on. |
| 19 | The netconfConfig.json file contains the configuration that was |
| 20 | generated by the test. The test also relies on the existence of this |
| 21 | file and will missbehave if it is removed entirely. The contents of the |
| 22 | file are overwritten everytime the test suite runs through Test Case 200 |
| 23 | |
| 24 | TODO: |
| 25 | Extend configuration to allow for specification of |
| 26 | - Vendor name |
| 27 | - Hardware version |
| 28 | - Software version |
| 29 | - Serial Number |