[INTTEST-18] Enhance NETCONF userfeatures test to not utilize odl-netconf-connector-ssh Created: 12/Oct/16  Updated: 19/Oct/17  Resolved: 19/Jan/17

Status: Resolved
Project: integration-test
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Ryan Goulding Assignee: Peter Gubka
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All



 Description   

Since Beryllium, we have suggested that users use the odl-netconf-

{clustered-|}

topology feature instead of odl-netconf-connector-ssh, since NETCONF has moved towards spawning connectors via the network-topology model. The NETCONF userfeatures tests currently rely on the controller loopback ("controller-config") which is provided by installing odl-netconf-connector-ssh. Since we are moving away from odl-netconf-connector-ssh feature, we should modify tests to not install the odl-netconf-connector-ssh feature, and find a new way to determine whether NETCONF is "up".



 Comments   
Comment by Vratko Polak [ 13/Oct/16 ]

This also applies to other Netconf CSIT jobs, and also jobs for other projects, especially Bgpcep.

Comment by Luis Gomez [ 29/Nov/16 ]

As first step, with this patch people can use public test when loading odl-netconf-clustered-topology:

https://git.opendaylight.org/gerrit/#/c/48758

BR/Luis

Comment by Luis Gomez [ 30/Nov/16 ]

New patch from Peter on this direction:

https://git.opendaylight.org/gerrit/#/c/48786

BR/Luis

Comment by Peter Gubka [ 19/Jan/17 ]

The last change was done by https://git.opendaylight.org/gerrit/#/c/50364/
Now no netconf nor bgpcep jobs dont contain netconf connector feature as a boot feature in carbon stream.

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