================================== #opendaylight-meeting: MD-SAL call ================================== Meeting started by edwarnicke at 16:09:43 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-meeting/2014/md_sal_call/opendaylight-meeting-md_sal_call.2014-05-13-16.09.log.html . Meeting summary --------------- * md_sal_call on 5/13/14 (regXboi, 16:10:25) * agenda is to discuss how to support models using different versions of yang? (regXboi, 16:11:03) * LINK: https://git.opendaylight.org/gerrit/#/c/6399/ (moizer, 16:14:47) * LINK: https://git.opendaylight.org/gerrit/#/c/6399/ (ttkacik, 16:15:00) * LINK: https://git.opendaylight.org/gerrit/#/c/6399/ link for gerrit patch that lead to the conversation (regXboi, 16:15:22) * LINK: https://bugs.opendaylight.org/show_bug.cgi?id=735 is the bug filed that started this (regXboi, 16:19:35) * question about whether the bug is helium only or backport to hydrogen? (regXboi, 16:21:53) * answer is that it is helium onlyu (regXboi, 16:22:02) * Bug has 3 options (see comment from Mathieu Lemay in above bug) on Pathset 2 (alagalah, 16:22:10) * answer is that it is helium only (regXboi, 16:22:17) * discussion of the various options (regXboi, 16:25:59) * question about the root cause (regXboi, 16:26:29) * statement that the problem is how to evolve the model when it can't be extended (regXboi, 16:27:02) * question about why we need to do something different with auto generated code than in hand written code (regXboi, 16:27:44) * point that model updates are supposed to be backwards compatible per RFC 6022 (regXboi, 16:30:17) * regXboi points out that there isn't a lot of backstory in the bug/comments, and we need that information else it seems opaque (alagalah, 16:33:50) * levelset - in trying to fix defect, required an update of ietf-restconf.yang (regXboi, 16:35:29) * that required update of ietf-yang-types (regXboi, 16:35:46) * now the question is what is the proper way of upgrading ietf-yang-types (or any yang model) in ODL (regXboi, 16:37:09) * and this is important because any project that has a YANG model will need to deal with this issue when they update it (regXboi, 16:38:55) * question if option 3 removes typing and leaving a pure DOM approach (regXboi, 16:46:16) * answer: it very well could (regXboi, 16:46:26) * continued discussion of option 3 and how it relates to binding (regXboi, 16:49:40) * question is whether or not to deprecate java bindings... moves issues from built time to runtime (edwarnicke, 16:49:41) * problem with the current patch is that it will cause explosion in number of dependent classes (regXboi, 16:51:09) * question about changes being kept "backwards-compatible" (regXboi, 16:52:11) * answer is that the system treats changing versions as not backwards compatible but with close on failure (regXboi, 16:52:43) * question that this is isomorphic to "how do you handle revisions to the API" and the proposal is to discard binding and push the problem to runtime (regXboi, 16:54:57) * answer it is more how applications access to the APIs and how to handle the backward compatibility from within OSGi (regXboi, 16:55:33) * regXboi had to leave - can't scribe any more (regXboi, 17:00:59) * question: could this be split into two problems: how do you get information about version of things? how do you manage multiple versions? (edwarnicke, 17:01:16) * tentative agreement to split the question and expose the model versions to get unblocked immediately (edwarnicke, 17:03:48) * my recommendation for the long-term: just keep the most recent bindings in memory and keep up the illusion of still supporting the old versions for legacy clients (what Ed called "adapters") (kwatsen, 17:04:38) * consider the problem similar to what an NMS would need to do to support devices having different software image versions installed (kwatsen, 17:06:56) Meeting ended at 18:16:05 UTC. People present (lines said) --------------------------- * regXboi (30) * alagalah (14) * edwarnicke (11) * odl_meetbot (5) * kwatsen (3) * dbainbri (2) * moizer (2) * abhijitkumbhare (2) * ttkacik (1) * raghu67_ (1) Generated by `MeetBot`_ 0.1.4