[CONTROLLER-662] Datastore: expose AsyncConfigurationCommitCohort into DataBroker Created: 05/Aug/14  Updated: 19/Mar/15  Due: 30/Nov/14  Resolved: 19/Mar/15

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: Helium
Fix Version/s: None

Type: Improvement
Reporter: Robert Varga Assignee: Tony Tkacik
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Duplicate
duplicates MDSAL-41 Provide support for custom Commit Coh... Resolved

 Description   

With the new APIs we inadvertently lost the ability for BA applications to prevent prevent writes into the config store.

This will be needed by BUG-1484, where FRM needs to stop users from injecting flow cookies (as those will not be honored anyway). While it does not gate implementation, not having this ability will lead to surprising behavior.

Expose the cohort into binding APIs and the machinery needed to make it work.

 Comments   
Comment by Reinaldo Penno [ 27/Oct/14 ]

It would be very useful if the callback could indicate whether the client trying change the datastore is RESTconf vs. Internal Databroker. it could be some form of client ID.

Comment by Reinaldo Penno [ 29/Oct/14 ]

Requirements:

  • I would like to attach a CommitHandler much like a data listener (to a specific leaf , subtree, etc). This is because certain portions of the tree will have different business logic associated with them. Some I will have to contact another external server, some will be just a matter of validating some of the input.
  • I would like to define the error code and reason phrase RESTconf will send back. I do not want all errors to be 401. Based on the business logic output I will decide on the appropriate error. Of course if no error is passed from ODL Provider, infrastructure can return a default error
  • Following up on above, I would like to be able to return 3XX code with appropriate payload. The reasons are many: Load-balancing, redirection to appropriate ODL or server instance that should handle resource, etc. This has been a long requirement since it is heavily used by business apps. This could be done with a Yang metadata data. A metadata-tag that we can change run-time with the URI to be used for redirection.
Comment by Reinaldo Penno [ 06/Nov/14 ]

Hi folks,

any update on this functionality?

thanks,

Comment by Tony Tkacik [ 07/Nov/14 ]

Started on defining low level APIs required for user created validation tools.
API Draft / patchsets should start be published in course of few next days.

Comment by Reinaldo Penno [ 20/Nov/14 ]

Hi Folks,

any progress on this bug? If there are any patches in gerrit, let me know so I can take a look as well.

thanks,

Comment by Reinaldo Penno [ 19/Jan/15 ]

Any progress?

Comment by Tony Tkacik [ 19/Mar/15 ]

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

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