17:01:13 <colindixon> #startmeeting tws 17:01:13 <odl_meetbot> Meeting started Mon Jun 20 17:01:13 2016 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:01:13 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:13 <odl_meetbot> The meeting name has been set to 'tws' 17:01:18 <colindixon> #topic agenda bashing 17:01:26 <colindixon> #chair anipbu phrobb CaseyODL 17:01:26 <odl_meetbot> Current chairs: CaseyODL anipbu colindixon phrobb 17:02:39 * colindixon is trying to get audio working on the WebEx, but having some issues 17:04:18 <colindixon> #info today, martin and jakub will present on the new RESTCONF draft 11 implementation 17:05:52 <colindixon> #link http://lists.opendaylight.org/pipermail/dev/attachments/20160620/fadb0c9d/attachment-0001.pptx slides 17:06:31 <colindixon> #topic RESTCONF draft 11 (which is supposedly only cosmetically different from draft 14, which is the latest) 17:06:37 <colindixon> #undo 17:06:37 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Topic object at 0x2787950> 17:06:41 <colindixon> #topic RESTCONF draft 11 17:06:51 <colindixon> #info draft 11 is supposedly only cosmetically different from draft 14, which is the latest 17:07:32 <colindixon> #undo 17:07:32 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x29d4390> 17:07:35 <colindixon> #info draft 11 is supposedly only cosmetically different from draft 13, which is the latest 17:07:42 <colindixon> #link https://datatracker.ietf.org/doc/draft-ietf-netconf-restconf/ 17:08:01 <colindixon> #info RESTCONF is a REST-like way to query YANG modeled data and get information back in XML or JSON 17:08:49 <colindixon> #info apparently, last autumn there was analysis between draft 02 (what we current implement) and draft 08 at the the time 17:09:21 <colindixon> #info when implementation started, we were at draft 11, we're now at draft 13 17:09:49 <colindixon> #link #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 17:10:10 <colindixon> #link https://wiki.opendaylight.org/view/Weather#Restconf_Draft11_upgrade_and_code_clean-up weather event tracking this effort and any eventual migration 17:11:01 <colindixon> #topic goals of the migration 17:11:38 <colindixon> #info support draft 11, there are a variety of tasks and changes that happened to do that 17:11:46 <colindixon> #info new implementation of services by scope 17:12:01 <colindixon> #info re-implementation of URI parsing (new draft uses different URI structures) 17:12:49 <colindixon> #info signletons/web.xml removal (still in progress) 17:13:17 <colindixon> #info one wrapper for both providers (old and new restconf, i.e., draft 02 and 11) 17:13:50 <colindixon> #Info general code refactor and cleanup while things are being reworked 17:15:09 <colindixon> #info re-organization of new into the project components/packages 17:15:25 <colindixon> #info hideyuki asks if there are changes needed for MD-SAL applications 17:15:48 <colindixon> #info 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 17:17:19 <colindixon> #info colindixon asks if the earliest the removal of the draft 02 would be carbon, the answer is yes 17:17:43 <colindixon> #topic detailed comparison between draft 02 and draft 11 17:18:27 <colindixon> #link https://wiki.opendaylight.org/view/File:Restconf_v2_analysis.odt as linked above, this is the document going through the changes 17:20:29 <colindixon> #Info new media type of errors added in addtion to data, operation, API and datastore, patch is now something handled outside the media type 17:20:37 <colindixon> #undo 17:20:37 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2708c90> 17:20:52 <colindixon> #Info new media type of errors added in addtion to data, operation, API and datastore, patch, patch-status and schema 17:21:33 <colindixon> #info URLs change, now config/operationation are expressed in the URL as GET parameters, not as part of the URL 17:22:09 <hideyuki> Is the RESTCONF implementation of Beryllium based on biermann-02? 17:22:14 <colindixon> #info many other small shifts 17:22:46 <colindixon> #info encoding resource identifiers into the URLs is now also different, so keys in lists... 17:23:34 <colindixon> #info new action statement invoked using POST to a given operation 17:24:34 <colindixon> #info new POST parameters include content, fields, filter, start-time, stop-time, and with-defaults 17:26:00 <colindixon> #Info the way notifications work changes, also support for notififcations is not requied to be compliant with RESTCONF 17:27:23 <colindixon> #Info code reorganization includes common, parser, rest, restful, and utils 17:28:23 <colindixon> #info 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 17:30:08 <colindixon> #info 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 17:33:43 <colindixon> #Info 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 17:35:01 <colindixon> #info 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 17:36:51 <colindixon> #info colindixon asks if we'll support anyxml? rovarga says, yes, that's the plan, but not in this release 17:37:21 <colindixon> #info colindixon also asks aobut YANG1.1, are we going to support YANG1.1 17:38:38 <colindixon> #info 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 17:38:58 <evanz> How does the content=all (config + operational) work as far as resolving conflicts? How does the data look? 17:39:36 <colindixon> evanz: thanks for the question 17:41:40 <colindixon> evanz: please feel free to ask over voice 17:43:12 <evanz> sure, thanks colindixon 17:48:04 <colindixon> #info evanz asks "How does the content=all (config + operational) work as far as resolving conflicts? How does the data look?" 17:48:10 <colindixon> #info colindixon clarifies with this: 17:48:14 <colindixon> #info For example if you have the YANG snippet: 17:48:14 <colindixon> #info 17:48:16 <colindixon> #info container person{ 17:48:17 <colindixon> #info leaf name{ 17:48:19 <colindixon> #info type string; 17:48:20 <colindixon> #info } 17:48:22 <colindixon> #info } 17:48:23 <colindixon> #info 17:48:25 <colindixon> #info Assuming in operational: name=bob 17:48:26 <colindixon> #info PUT config: name=fred 17:48:27 <colindixon> #info 17:48:28 <colindixon> #info GET config+operational: what does this return? How does it resolve the conflicts? 17:48:37 <colindixon> #info 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 17:49:53 <colindixon> #chair LuisGomez 17:49:53 <odl_meetbot> Current chairs: CaseyODL LuisGomez anipbu colindixon phrobb 17:50:17 <colindixon> LuisGomez: I'm still on audio, but I have to go afk for a second, can you take notes and/or end the meeting if need be 17:50:52 <LuisGomez> sure 17:53:34 <LuisGomez> this is being recorded anyway for people to come back and check code walkthrough 17:55:25 <LuisGomez> #info Jakub is doing demo installing restconf feature 17:56:17 <LuisGomez> #info demo is on ODL toaster application 17:59:35 <LuisGomez> #info Jakub is showing websockets notifications 18:01:22 <LuisGomez> #info colin asks about how to distinguish between restconf versions 18:01:42 <LuisGomez> #info new version has /11/ 18:03:50 <LuisGomez> #info this is in addition to /restconf in the URL 18:04:36 <LuisGomez> thanks all 18:04:40 <LuisGomez> #endmeeting