This page supports the discussion about the solution as started by Brian Freeman
Invited Robert Varga and other...
Target: No changes needed on OpenDaylight itself
O-RAN-SCHow to implement non-permanent NetConf sessions using ODL OpenDaylight Network ODL NetConf Client ODL NetConf Client Customer NetConf Adapter Customer NetConf Adapter NetConf Server NetConf Server Target subject of the discussion non-permanent NetConf Session permanent NetConf Session The adapter keeps the SSH TLS session to ODL,identifiies ODL-NetConf-KeepAlives and anwers them.Consequence:- From ODL point of view the MountPoint is the Adapter.- Details about port ranges and Handover to another "master"of the NetConf session in an ODL cluster to be discussed.- Is the Adapter instanciated per MountPoint or does theAdapter terminate more than one NetConf session?- How are the TLS certificates, private keys handled betweenNetConf-Server, Adapter, NetConf Client? Details starting from NO CONNECTION Establish SSH/TLS Establish SSH/TLS [010]Hello Message [020]Hello Message [030]Capabilites [040]Capabilites [050]Close session - Terminate NetConf/TLS/SSH loop[every 120s] [060]NetConf keep-alive request [070]NetConf keep-alive response [080]<rpc> request [090]Establish SSH/TLS [100]Hello Message [110]Capabilites [120]Analyse capability changes [130]inform in case of capability changes [140]<rpc> request [150]<rpc> response [160]<rpc> response [170]Close session - Terminate NetConf/TLS/SSH loop[every 120s] [180]NetConf keep-alive request [190]NetConf keep-alive response [200]Close session - Terminate NetConf/TLS/SSHLicenseApache 2.0Thanks to plantUml!2019-07-16 | o-ran-sc.org
