#opendaylight-meeting: tws

Meeting started by colindixon at 17:01:13 UTC (full logs).

Meeting summary

  1. agenda bashing (colindixon, 17:01:18)
    1. today, martin and jakub will present on the new RESTCONF draft 11 implementation (colindixon, 17:04:18)
    2. http://lists.opendaylight.org/pipermail/dev/attachments/20160620/fadb0c9d/attachment-0001.pptx slides (colindixon, 17:05:52)

  2. RESTCONF draft 11 (colindixon, 17:06:41)
    1. draft 11 is supposedly only cosmetically different from draft 13, which is the latest (colindixon, 17:07:35)
    2. https://datatracker.ietf.org/doc/draft-ietf-netconf-restconf/ (colindixon, 17:07:42)
    3. RESTCONF is a REST-like way to query YANG modeled data and get information back in XML or JSON (colindixon, 17:08:01)
    4. apparently, last autumn there was analysis between draft 02 (what we current implement) and draft 08 at the the time (colindixon, 17:08:49)
    5. when implementation started, we were at draft 11, we're now at draft 13 (colindixon, 17:09:21)
    6. #link https://wiki.opendaylight.org/view/File:Restconf_v2_analysis.odt this is the writeup of the analysis of the differences between draft 02 and draft 11, it's very good (colindixon, 17:09:49)
    7. https://wiki.opendaylight.org/view/Weather#Restconf_Draft11_upgrade_and_code_clean-up weather event tracking this effort and any eventual migration (colindixon, 17:10:10)

  3. goals of the migration (colindixon, 17:11:01)
    1. support draft 11, there are a variety of tasks and changes that happened to do that (colindixon, 17:11:38)
    2. new implementation of services by scope (colindixon, 17:11:46)
    3. re-implementation of URI parsing (new draft uses different URI structures) (colindixon, 17:12:01)
    4. signletons/web.xml removal (still in progress) (colindixon, 17:12:49)
    5. one wrapper for both providers (old and new restconf, i.e., draft 02 and 11) (colindixon, 17:13:17)
    6. general code refactor and cleanup while things are being reworked (colindixon, 17:13:50)
    7. re-organization of new into the project components/packages (colindixon, 17:15:09)
    8. hideyuki asks if there are changes needed for MD-SAL applications (colindixon, 17:15:25)
    9. rovarga says that if you stay inside Java and just use those APIs no changes are needed, you only need to change things that use RESTCONF (colindixon, 17:15:48)
    10. colindixon asks if the earliest the removal of the draft 02 would be carbon, the answer is yes (colindixon, 17:17:19)

  4. detailed comparison between draft 02 and draft 11 (colindixon, 17:17:43)
    1. https://wiki.opendaylight.org/view/File:Restconf_v2_analysis.odt as linked above, this is the document going through the changes (colindixon, 17:18:27)
    2. new media type of errors added in addtion to data, operation, API and datastore, patch, patch-status and schema (colindixon, 17:20:52)
    3. URLs change, now config/operationation are expressed in the URL as GET parameters, not as part of the URL (colindixon, 17:21:33)
    4. many other small shifts (colindixon, 17:22:14)
    5. encoding resource identifiers into the URLs is now also different, so keys in lists... (colindixon, 17:22:46)
    6. new action statement invoked using POST to a given operation (colindixon, 17:23:34)
    7. new POST parameters include content, fields, filter, start-time, stop-time, and with-defaults (colindixon, 17:24:34)
    8. the way notifications work changes, also support for notififcations is not requied to be compliant with RESTCONF (colindixon, 17:26:00)
    9. code reorganization includes common, parser, rest, restful, and utils (colindixon, 17:27:23)
    10. rest is just the the part that talks REST URIs and the like it's basically implemetning the RFC, restful actually handles the interaction with the MD-SAL and our implementation (colindixon, 17:28:23)
    11. colindixon asks about the parser, the parser has to not only handle yang modeled data (via the YANG tools parser), but also things that aren't YANG modeled, e.g., patch operations (colindixon, 17:30:08)
    12. colindixon asks if we could rename rest and restfu to something more intuitive, davidmichaelkarr concurs that they're a bit confusing or at least don't communicate what they mean well (colindixon, 17:33:43)
    13. colindixon asks if the plan is to implementat notifications, Jakub says that the plan is to support them both YANG notifications and data change notifications (colindixon, 17:35:01)
    14. colindixon asks if we'll support anyxml? rovarga says, yes, that's the plan, but not in this release (colindixon, 17:36:51)
    15. colindixon also asks aobut YANG1.1, are we going to support YANG1.1 (colindixon, 17:37:21)
    16. rovarga says that for whatever reason the RESTCONF spec is tied to YANG 1.1, but we don't have a YANG 1.1 parser, for now we will have RESTCONF based on YANG 1.0, which is a bit of a frankenprotocol, but with YANG1.1 support where it's reasonable (colindixon, 17:38:38)
    17. evanz asks "How does the content=all (config + operational) work as far as resolving conflicts? How does the data look?" (colindixon, 17:48:04)
    18. colindixon clarifies with this: (colindixon, 17:48:10)
    19. For example if you have the YANG snippet: (colindixon, 17:48:14)
    20. (colindixon, 17:48:14)
    21. container person{ (colindixon, 17:48:16)
    22. leaf name{ (colindixon, 17:48:17)
    23. type string; (colindixon, 17:48:19)
    24. } (colindixon, 17:48:20)
    25. } (colindixon, 17:48:22)
    26. (colindixon, 17:48:23)
    27. Assuming in operational: name=bob (colindixon, 17:48:25)
    28. PUT config: name=fred (colindixon, 17:48:26)
    29. (colindixon, 17:48:27)
    30. GET config+operational: what does this return? How does it resolve the conflicts? (colindixon, 17:48:28)
    31. the answer seems to be that we don't know how this works, we'll have to look at the spec and/or the code to figure it out (colindixon, 17:48:37)
    32. Jakub is doing demo installing restconf feature (LuisGomez, 17:55:25)
    33. demo is on ODL toaster application (LuisGomez, 17:56:17)
    34. Jakub is showing websockets notifications (LuisGomez, 17:59:35)
    35. colin asks about how to distinguish between restconf versions (LuisGomez, 18:01:22)
    36. new version has /11/ (LuisGomez, 18:01:42)
    37. this is in addition to /restconf in the URL (LuisGomez, 18:03:50)


Meeting ended at 18:04:40 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. colindixon (67)
  2. LuisGomez (10)
  3. odl_meetbot (8)
  4. evanz (2)
  5. hideyuki (1)
  6. phrobb (0)
  7. anipbu (0)
  8. CaseyODL (0)


Generated by MeetBot 0.1.4.