[CONTROLLER-1869] DOMMountPointService needs to perform deeper proxying Created: 06/Nov/18  Updated: 22/Nov/18  Resolved: 22/Nov/18

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: None
Fix Version/s: Neon, Fluorine SR2

Type: Bug Priority: Medium
Reporter: Robert Varga Assignee: Robert Varga
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by NETCONF-573 Mountpoint created using mdsal DOM AP... Resolved

 Description   

As noted during migration of restconf to MD-SAL APIs, we have a slight issue when accessing mount points between users of Controller and MD-SAL APIs.

While the mount points themselves work okay, their services are incompatible: if the mount point registers an MD-SAL DOMDataBroker, users of the controller API will not be able to resolve the corresponding service and vice-versa.

This leads to a breakage if we migrate NETCONF or RESTCONF only - suddenly RESTCONF won't be able to route the requests properly.

The proper fix is to instantiate proxy services providing two-way translation, so that both MD-SAL and Controller services are available from point points accessed via the controller API.



 Comments   
Comment by Jakub Morvay [ 06/Nov/18 ]

WIP patch https://git.opendaylight.org/gerrit/#/c/77562/ for following direction:

registering MD-SAL montpoint with MD-SAL services -> retrieving controller sal mountpoint and controller sal services

Generated at Wed Feb 07 19:56:39 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.