[NETCONF-925] Rework optional reconnect logic Created: 06/Dec/22  Updated: 28/Oct/23

Status: Confirmed
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: 7.0.0

Type: New Feature Priority: Medium
Reporter: Robert Varga Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: pt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
is blocked by NETCONF-1070 Rework client reconnection logic Resolved
Issue split
split from NETCONF-669 Separate out schemaless mountpoints Resolved
Relates
relates to NETCONF-1192 Duplicate 'ignore-missing-schema-sour... Resolved

 Description   

Reconnection logic introduced in NETCONF-611 is rather ugly, as it modifies lifecycle rather thoroughly and relies on datastore overwrites.

Migrate the logic into AbstractNetworkTopology, where it should react to RemoteDeviceHandler.onDeviceDisconnected() – which it is in control of, as it is passing the object it creates via createSalFacade().

Perhaps we should be triggering onDeviceFailed() and propagate the schema resolution exception, though – this needs some thought.

At any rate, NetconfDeviceBuilder should lose setNode(), as it should not be needed.


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