-
Bug
-
Resolution: Unresolved
-
None
-
Operating System: All
Platform: All
-
7069
-
Normal
In my testing, ODL is always generating NETCONF <edit-config> requests with operation "replace". According to IETF Draft IETF NETCONF RESTCONF the following is expected:
-------------------------------------------------------+
| RESTCONF | NETCONF |
-------------------------------------------------------+
| OPTIONS | none |
| HEAD | none |
| GET | <get-config>, <get> |
| POST | <edit-config> (nc:operation="create") |
| POST | invoke an RPC operation |
| PUT | <edit-config> (nc:operation="create/replace") |
| PATCH | <edit-config> (nc:operation="merge") |
| DELETE | <edit-config> (nc:operation="delete") |
-------------------------------------------------------+
REFERENCE https://tools.ietf.org/html/draft-ietf-netconf-restconf
As a matter of consequence ODL is currently running into issues, for vendors who have not yet implemented the "replace" operation.
Somehow I believe, this is caused by an incomplete implementation. OpenDaylight already has the "checkItemDoesNotExists()" method implemented. So it should use this information to decide about using the "create" or "replace" method based on using POST or PUT.
- relates to
-
NETCONF-706 Add support of new a NetconfDataTreeService in clustered netconf
-
- Resolved
-
