16:44:00 #startmeeting md-sal interest call 16:44:00 Meeting started Tue Oct 13 16:44:00 2015 UTC. The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html. 16:44:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:44:00 The meeting name has been set to 'md_sal_interest_call' 16:44:07 #topic jersey migration 16:45:14 #info rgoulding_ is still testing things and he hopes it will be ready by next week, it's a pain to test things becuase autorelease is broken, and we can't test version bumps without building the world 16:45:19 #topic clustering behavior 16:46:21 #info there's a *long* discussion about the semantics of different events and how we should tell apps to handle things in the MD-SAL 16:47:06 #info this ends with moiz and colindixon agreeing that they should write up a clustering best practices document 16:47:12 #topic default values in YANG 16:47:36 #info ssaxena asks are we supporting default values in various YANG constructs 16:49:41 #info rovarga says that the spec says that "the system should behave as though the default value exists when unspecified", but not that the node actually has to exist 16:50:29 #link https://tools.ietf.org/html/rfc6020#section-7.6.1 16:52:35 #info rovarga says the current appraoch is that applications to provide that property on their own 16:53:46 #info in essence it is the programmer's responsiblity to provide the appropriate behavior based on their out-of-band knowledge of the model 16:55:18 #info to help this, there are recent patches that provide default values for binding-aware DTOs on reads and data change notifications 16:56:25 #info rovarga notes that his reading of the spec is that the default nodes should not be returned as existing, only the behavior should change based on default values 17:04:30 #info ttkacik says that RFC 6243 spells out that there are particular functions which allow for reads with explicit rendering of the default nodes and thus implies that normal reads shoudl not render it 17:06:22 #info there is a broader issue around how to both respect the YANG spec to derive the maximum value from it, but not suffer too much from places where it makes thins counterintuitive for our developers and users 17:06:25 #endmeeting