Uploaded image for project: 'mdsal'
  1. mdsal
  2. MDSAL-283

Action support in MDSAL DOM

    XMLWordPrintable

Details

    • New Feature
    • Status: Resolved
    • Resolution: Done
    • None
    • Fluorine
    • DOM API, DOM runtime
    • None

    • Operating System: All
      Platform: All

    Description

      We need to start from yang-model-api OperationDefinition and provide Action support in binding independant world of MDSAL

      Attachments

        Issue Links

          blocks

          New Feature - A new feature of the product, which has yet to be developed. MDSAL-284 Support Actions in Binding v2 runtime

          • Resolved

          New Feature - A new feature of the product, which has yet to be developed. NETCONF-448 Add support for YANG1.1 actions

          • Highest - This problem will block progress.
          • Resolved
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDSAL-229 mdsal-dom-api: get rid of CheckedFuture

          • Medium - Has the potential to affect progress.
          • Resolved
          # Subject Branch Project Status CR V
          74187,2 Disallow DOMOperationInstance wildcards master mdsal Status: MERGED +2 +1
          74188,2 Harden DOMRpcRouter shutdown master mdsal Status: MERGED +2 +1
          74207,2 Shutdown DOMRpcRouter master mdsal Status: MERGED +2 +1
          74208,2 Remove DOMRpcRoutingTable.invoke() master mdsal Status: MERGED +2 +1
          74209,8 Move DOMRpcRouter implementation methods master mdsal Status: MERGED +2 +1
          74596,6 Simplify DOMOperationService API master mdsal Status: MERGED +2 +1
          74609,3 Add (DOM)Action(Provider) bridges master controller Status: MERGED +2 +1

          Activity

            People

              rovarga Robert Varga
              martin.ciglan Martin Ciglan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 weeks
                  3w