16:09:43 <edwarnicke> #startmeeting MD-SAL call
16:09:43 <odl_meetbot> Meeting started Tue May 13 16:09:43 2014 UTC.  The chair is edwarnicke. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:09:43 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:09:43 <odl_meetbot> The meeting name has been set to 'md_sal_call'
16:09:48 <edwarnicke> #chair alagalah
16:09:48 <odl_meetbot> Current chairs: alagalah edwarnicke
16:09:52 <edwarnicke> #chair regXboi
16:09:52 <odl_meetbot> Current chairs: alagalah edwarnicke regXboi
16:10:25 <regXboi> #info md_sal_call on 5/13/14
16:11:03 <regXboi> #info agenda is to discuss how to support models using different versions of yang?
16:11:10 <regXboi> did I get that right?
16:12:19 <alagalah> regXboi: I think it might be about the versioning semantics  / mechanics
16:12:26 <alagalah> regXboi: (also)
16:13:47 <moizer> too much echo on webex
16:14:47 <moizer> https://git.opendaylight.org/gerrit/#/c/6399/
16:15:00 <ttkacik> https://git.opendaylight.org/gerrit/#/c/6399/
16:15:22 <regXboi> #link https://git.opendaylight.org/gerrit/#/c/6399/ link for gerrit patch that lead to the conversation
16:19:35 <regXboi> #link https://bugs.opendaylight.org/show_bug.cgi?id=735 is the bug filed that started this
16:21:53 <regXboi> #info question about whether the bug is helium only or backport to hydrogen?
16:22:02 <regXboi> #info answer is that it is helium onlyu
16:22:10 <alagalah> #info Bug has 3 options (see comment from Mathieu Lemay in above bug) on Pathset 2
16:22:17 <regXboi> #info answer is that it is helium only
16:23:59 <abhijitkumbhare> Is this call being recorded?
16:24:04 <regXboi> yes
16:24:10 <abhijitkumbhare> ok -thx
16:24:16 <regXboi> and we are *trying* to collect minutes here
16:24:31 <regXboi> although I admit to not even getting how I get from the defect link to the solutions
16:24:45 <regXboi> the discussion seems to be missing some pieces
16:25:59 <regXboi> #info discussion of the various options
16:26:29 <regXboi> #info question about the root cause
16:27:02 <regXboi> #info statement that the problem is how to evolve the model when it can't be extended
16:27:44 <regXboi> #info question about why we need to do something different with auto generated code than in hand written code
16:30:17 <regXboi> #info point that model updates are supposed to be backwards compatible per RFC 6022
16:33:50 <alagalah> #info regXboi points out that there isn't a lot of backstory in the bug/comments, and we need that information else it seems opaque
16:33:56 <alagalah> regXboi: +1
16:35:29 <regXboi> #info levelset - in trying to fix defect, required an update of ietf-restconf.yang
16:35:46 <regXboi> #info that required update of ietf-yang-types
16:37:09 <regXboi> #info now the question is what is the proper way of upgrading ietf-yang-types (or any yang model) in ODL
16:37:31 <alagalah> I also have a question... which can be addressed at the approp
16:37:49 <alagalah> riate juncture, but the crux is, we have a YANG model for our project, what does this whole discussion mean to me?
16:38:55 <regXboi> #info and this is important because any project that has a YANG model will need to deal with this issue when they update it
16:39:05 <alagalah> regXboi: you clipped
16:39:21 <alagalah> Ack the info
16:41:49 <alagalah> Ok, I have a Q: Does this mean that if you change the yang-tools, is there any chance that my Yang model will generate different APIs than it did say "yesterday" ?
16:44:23 <raghu67_> <alagalah>  If we assume Yang Tools is bug free and the Yang to Java Binding specification is stable, the APIs will not change. But that assumption may not always be true
16:45:01 <alagalah> raghu67_: thanks sir!
16:46:16 <regXboi> #info question if option 3 removes typing and leaving a pure DOM approach
16:46:26 <regXboi> #info answer: it very well could
16:49:12 <alagalah> regXboi: edwarnicke I'm not following this, so unable to scribe this part...
16:49:40 <regXboi> #info continued discussion of option 3 and how it relates to binding
16:49:41 <edwarnicke> #info question is whether or not to deprecate java bindings... moves issues from built time to runtime
16:51:09 <regXboi> #info problem with the current patch is that it will cause explosion in number of dependent classes
16:52:11 <regXboi> #info question about changes being kept "backwards-compatible"
16:52:43 <regXboi> #info answer is that the system treats changing versions as not backwards compatible but with close on failure
16:54:57 <regXboi> #info 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
16:55:33 <regXboi> #info answer it is more how applications access to the APIs and how to handle the backward compatibility from within OSGi
16:58:40 <dbainbri> -1 short terms & long term approach.
16:58:49 <dbainbri> lets do this change once and correct.
17:00:59 <regXboi> #info regXboi had to leave - can't scribe any more
17:01:16 <edwarnicke> #info question: could this be split into two problems: how do you get information about version of things?  how do you manage multiple versions?
17:01:48 <edwarnicke> dbainbri: Would very much like your thoughts on splitting the question as you have expressed opposition?
17:03:27 <kwatsen> 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")
17:03:48 <edwarnicke> #info tentative agreement to split the question and expose the model versions to get unblocked immediately
17:04:14 <edwarnicke> kwatsen: Could you #info your suggestion in?
17:04:38 <kwatsen> #info 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")
17:05:52 <alagalah> edwarnicke: The list being? controller-dev ? discuss ?
17:06:13 <edwarnicke> alagalah: Those two sound good :)
17:06:20 <alagalah> :)
17:06:56 <kwatsen> #info consider the problem similar to what an NMS would need to do to support devices having different software image versions installed
18:15:58 <edwarnicke> #stopmeeting
18:16:05 <edwarnicke> #endmeeting