Total Statistics | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
|---|---|---|---|---|---|---|
| All Tests | 8 | 3 | 5 | 0 | 00:01:14 |
Statistics by Tag | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
|---|---|---|---|---|---|---|
| 1node | 8 | 3 | 5 | 0 | 00:01:14 | |
| critical | 8 | 3 | 5 | 0 | 00:01:14 | |
| netconf | 8 | 3 | 5 | 0 | 00:01:14 |
Statistics by Suite | Total | Pass | Fail | Skip | Elapsed | Pass / Fail / Skip |
|---|---|---|---|---|---|---|
| 8 | 3 | 5 | 0 | 00:01:22 |
| Full Name: | netconf-clustering-scale.txt |
|---|---|
| Documentation: | netconf-restperfclient update performance test suite (clustered setup). Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html Perform given count of update operations on device data mounted onto a netconf connector (using the netconf-testtool-restperfclient tool) and see how much time it took. More exactly, it sends the data to a restconf mountpoint of the netconf connector belonging to the device, which turns out to turn the first request sent to a "create" request and the remaining requests to "update" requests (due to how the testtool device behavior is implemented). The difference from the "single node" test suite (see ../scale/performance.robot) is that the device is configured and the data on it created using one node in the cluster and the update operations are issued on a different node. This forces the cluster nodes to communicate with each other about the data to be sent to the device. |
| Source: | /w/workspace/netconf-csit-3node-clustering-scale-only-titanium/test/csit/suites/netconf/clusteringscale/performance.robot |
| Start / End / Elapsed: | 20250329 23:14:03.663 / 20250329 23:15:25.369 / 00:01:21.706 |
| Status: | 8 tests total, 3 passed, 5 failed, 0 skipped |
| Documentation: | Setup everything needed for the test cases. |
|---|---|
| Start / End / Elapsed: | 20250329 23:14:04.204 / 20250329 23:14:11.490 / 00:00:07.286 |
| Documentation: | Teardown the test infrastructure, perform cleanup and release all resources. |
|---|---|
| Start / End / Elapsed: | 20250329 23:15:25.019 / 20250329 23:15:25.369 / 00:00:00.350 |
| Full Name: | netconf-clustering-scale.txt.Start_Testtool |
|---|---|
| Documentation: | Deploy and start test tool, then wait for all its devices to become online. |
| Tags: | 1node, critical, netconf |
| Start / End / Elapsed: | 20250329 23:14:11.489 / 20250329 23:14:18.515 / 00:00:07.026 |
| Status: | PASS |
| Full Name: | netconf-clustering-scale.txt.Configure_Device_On_Netconf |
|---|---|
| Documentation: | Configure the testtool device on Netconf connector, using node 1. |
| Tags: | 1node, critical, netconf |
| Start / End / Elapsed: | 20250329 23:14:18.516 / 20250329 23:14:19.949 / 00:00:01.433 |
| Status: | PASS |
| Full Name: | netconf-clustering-scale.txt.Wait_For_Device_To_Become_Connected |
|---|---|
| Documentation: | Wait until the device becomes available through Netconf on node 1. |
| Tags: | 1node, critical, netconf |
| Start / End / Elapsed: | 20250329 23:14:19.949 / 20250329 23:14:23.590 / 00:00:03.641 |
| Status: | PASS |
| Full Name: | netconf-clustering-scale.txt.Wait_For_Device_Data_To_Be_Seen |
|---|---|
| Documentation: | Wait until the device data show up at node 2. |
| Tags: | 1node, critical, netconf |
| Start / End / Elapsed: | 20250329 23:14:23.590 / 20250329 23:15:24.721 / 00:01:01.131 |
| Status: | FAIL |
| Message: |
| Documentation: | Test case setup which skips on previous failure. If not, logs test case name to Karaf log. Recommended to be used as the default test case setup. |
|---|---|
| Start / End / Elapsed: | 20250329 23:14:23.590 / 20250329 23:14:23.867 / 00:00:00.277 |
| Documentation: | Runs the specified keyword and retries if it fails. |
|---|---|
| Start / End / Elapsed: | 20250329 23:14:23.868 / 20250329 23:15:24.701 / 00:01:00.833 |
| Message: |
| Full Name: | netconf-clustering-scale.txt.Create_Device_Data |
|---|---|
| Documentation: | Send some sample test data into the device through node 2 and check that the request went OK. |
| Tags: | 1node, critical, netconf |
| Start / End / Elapsed: | 20250329 23:15:24.721 / 20250329 23:15:24.734 / 00:00:00.013 |
| Status: | FAIL |
| Message: |
| Full Name: | netconf-clustering-scale.txt.Run_Restperfclient |
|---|---|
| Documentation: | Deploy and execute restperfclient, asking it to send the specified amount of requests to the netconf connector of the device through node 3. The duration of this test case is the main performance metric. |
| Tags: | 1node, critical, netconf |
| Start / End / Elapsed: | 20250329 23:15:24.734 / 20250329 23:15:24.747 / 00:00:00.013 |
| Status: | FAIL |
| Message: |
| Full Name: | netconf-clustering-scale.txt.Check_For_Failed_Requests |
|---|---|
| Documentation: | Make sure there are no failed requests in the restperfclient log. This is a separate test case to distinguish between restperfclient failure and failed requests. Failed requests are rejected because we don't want to test performance of ODL rejecting our requests. If this test case fails, then the duration of Run_Restperfclient cannot be trusted to show the real performance of the cluster. |
| Tags: | 1node, critical, netconf |
| Start / End / Elapsed: | 20250329 23:15:24.747 / 20250329 23:15:24.760 / 00:00:00.013 |
| Status: | FAIL |
| Message: |
| Full Name: | netconf-clustering-scale.txt.Cleanup_And_Collect |
|---|---|
| Documentation: | Deconfigure the testtool device on Netconf connector using node 1. |
| Tags: | 1node, critical, netconf |
| Start / End / Elapsed: | 20250329 23:15:24.760 / 20250329 23:15:25.018 / 00:00:00.258 |
| Status: | FAIL |
| Message: |