[NETCONF-758] Fix functionality of the test tool Created: 15/Feb/21  Updated: 14/Feb/22  Resolved: 02/Feb/22

Status: Resolved
Project: netconf
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0.13

Type: Task Priority: Medium
Reporter: Oleksii Mozghovyi Assignee: Dominik Vrbovský
Resolution: Done Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to NETCONF-797 Fix rest-perf-client for RFC 8040 Resolved
split to NETCONF-798 Fix scale-util for RFC 8040 Resolved
split to NETCONF-796 Fix netconf-testool device registrati... Resolved

 Description   

The testool under netconf/tools/netconf-testtool consists of multiple parts
which need to be updated.

1. netconf-testool
The automatic bulk registration of devices on the controller via RESTCONF is broken.
The tool also uses old draft-bierman-netconf-restconf-02 paths - we would like to update to RFC 8040 paths.

2. rest-perf-client
The tool is using old draft-bierman-netconf-restconf-02 paths.
To update to RFC 8040 the tool is missing proper authorization of requests.

3. scale-util
The tool has multiple issues. It cannot correctly stop and start Karaf container.
In addition it is still using draft-bierman-netconf-restconf-02 noauth feature.
To update to RFC 8040 feature a proper authorization needs to be implemented in the tool.

4. stress-client
This tool is working with NETCONF protocol and works as expected.

In general the code of all tools can/should be refactored because it contains a lot
of duplicate logic.

 Comments   
Comment by Rohini Ambika [ 25/Jan/22 ]

what is the max connection batch size  a netconftest tool(v1.13.x) can simulate and connect to controller in one go?

Comment by Ivan Hrasko [ 26/Jan/22 ]

That depends on the machine you have. You can be also limited by the number of ports available.

Comment by Rohini Ambika [ 27/Jan/22 ]

With 2GB heap size how many devices we can simulate and connect to controller with netconftesttool version 1.13.x

eg : java -jar netconf-testtool-2.0.13-SNAPSHOT --controller-ip 127.0.0.1 --controller-port 8181 --device-count 5000 --debug true

When I have tested, the tool is behaving differently, sometimes its connecting 1k devices with v1.13.7 and sometimes 5k with v1.13.5 with a total device count 5K as specified in the above command.

Not sure if I am using the tool in correct way. Please help

Comment by Rohini Ambika [ 27/Jan/22 ]

Seeing the below exception in ODL logs for some ports:

An exception was thrown by org.opendaylight.netconf.nettyutil.handler.ssh.client.AsyncSshHandler$$Lambda$1831/0x00000001014e5040.operationComplete()
java.lang.IllegalStateException: complete already: AbstractBootstrap$PendingRegistrationPromise@7e9d9099(failure: org.opendaylight.netconf.shaded.sshd.common.SshException: DefaultConnectFuture[admin@/127.0.0.1:22759]: Failed (ConnectException) to execute: Connection refused)

Generated at Wed Feb 07 20:15:49 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.