[MDSAL-433] Expose CONFIG/OPER-bound DataBrokers Created: 06/Apr/19  Updated: 13/Sep/19

Status: Open
Project: mdsal
Component/s: Binding runtime, DOM runtime
Affects Version/s: None
Fix Version/s: None

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


 Description   

In order to migrate users, we need to stop proliferation of DataBroker as a unified access which can span multiple datastores in a single transaction.

Rather than migrating users in one go to a new API, expose two facades with odl:type={config,oper}, each of which will be bound a specific datastore and will reject attempts to access any other datastore. This should work dynamically, based on the odl:type=default databroker currently injected.

We then can migrate users to use a specific databroker (or separate instances) and once that is done, we can start switching them to a more specific interface.


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