Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Controller needs to be identified in body of notifications #7

Open
openBackhaul opened this issue Aug 9, 2023 · 1 comment
Open
Assignees
Labels

Comments

@openBackhaul
Copy link
Owner

It is assumed that multiple controllers are operating in parallel.
Consequently, the instance of controller needs to be identified inside controller related notifications.

Potential solution:
The ControllerIdentifier is added in front of the object-id-ref.

But, where is this information coming from?

@openBackhaul openBackhaul added the help wanted Extra attention is needed label Aug 9, 2023
@openBackhaul openBackhaul self-assigned this Aug 9, 2023
@openBackhaul
Copy link
Owner Author

It is assumed that a controller-id attribute will be added.

  example:
    urn-ietf-params-xml-ns-netconf-notification-1.0:notification:
      controller-id: 'odl-1'
      event-time: '2023-07-11T08:21:50.526721696Z'
      urn-opendaylight-params-xml-ns-yang-controller-md-sal-remote:data-changed-notification:
        data-change-event:
          - store: 'operation'
            path: '/urn-TBD-p ... ection-status'
            operation: 'updated'
            data:
              netconf-node-topology:connection-status: 'connecting'

Zia got asked to inform, if different solution would be agreed or implemented.

@openBackhaul openBackhaul added wontfix This will not be worked on on-hold and removed wontfix This will not be worked on help wanted Extra attention is needed labels Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant