16:00:10 <colindixon> #startmeeting MD-SAL interest call
16:00:10 <odl_meetbot> Meeting started Tue Jul 21 16:00:10 2015 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:00:10 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:10 <odl_meetbot> The meeting name has been set to 'md_sal_interest_call'
16:00:14 <colindixon> #topic agenda bashing
16:00:32 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2015/md_sal_ineterest_call/opendaylight-meeting-md_sal_ineterest_call.2015-07-14-16.05.html last week’s minutes
16:02:31 <colindixon> #link https://lists.opendaylight.org/pipermail/controller-dev/2015-July/009902.html the e-mail thead after last weeks meeting on the proposed new data store APIs
16:02:48 <colindixon> #link http://gist.asciidoctor.org/?c5f1027c657cda428a5d the proposed new data store APIs themselves
16:03:08 <colindixon> #info from last week, we had planned to talk about what we would do with the developer design forum time
16:03:32 <colindixon> #link https://wiki.opendaylight.org/view/Events:Be_Dev_Forum potential topics for the developer deisgn forum are here
16:06:26 <colindixon> #Info TomP says they covered a bit about the new DataTree APIs at the end of the last meeting and agreed to talk about it more in person at the summit next week
16:07:09 <colindixon> #link https://wiki.opendaylight.org/view/Events:Be_Dev_Forum#Clustering_enhancements this will be discussed under this topic for those who are interested
16:07:42 * tbachman wanders into the webex/room
16:07:48 <colindixon> #topic how can we best use our time at the summit?
16:08:45 <colindixon> #info ttkacik shows the topics from the above link
16:09:21 <colindixon> #info ttkacik and moiz say that there is likely one long topic (clustering enhancement) listed above
16:09:46 <colindixon> #info ttkacik says there are also protocol-specific clustering topics, e.g., NETCONF and OpenFlow clustering
16:10:23 <colindixon> #info ttkacik another topic on upgrading the MD-SAL and migration from one version to another version (supporting multiple YANG model revisions)
16:10:27 <tbachman> #info colindixon notes that we don’t support multiple YANG model revisions via RESTCONF
16:10:35 <tbachman> 3Undo
16:10:38 <tbachman> oops
16:10:42 <tbachman> not a chair, either
16:10:46 * tbachman is way too slow
16:11:07 <colindixon> #chair tbachman
16:11:07 <odl_meetbot> Current chairs: colindixon tbachman
16:11:09 <tbachman> colindixon: :)
16:11:32 <tbachman> #info colindixon asks whether transactionality in NETCONF is also a topic of interest
16:12:01 <tbachman> #info ttkacik says it’s of interest, but NETCONF already does 2-phase commits, and has done so since Hydrogen (if device supports it)
16:12:04 <colindixon> #info cross-data-center clustering may also be interesting to people
16:12:28 <tbachman> #info colindixon asks if we want to write code during the dev summit or are we just white-boarding?
16:12:50 <tbachman> #info ttkacik says we’re probably more interested in discussing cross-project concerns
16:13:28 <tbachman> #info moizer says we should add a topic for application clustering requirements discussion
16:14:37 <tbachman> #info ttkacik says application level clustering is an important topic and recommends it being its own topic
16:15:28 <tbachman> #info moizer will lead the application level clustering topic session
16:16:02 <tbachman> pantelis: jump in man! :)
16:16:53 <tbachman> #info pantelis asks how long each session is
16:17:38 <tbachman> #info ttkacik says phrobb was going to look at the possible topics and attendees, and to try and schedule the sessions so that similar subjects don’t overlap — this might affect how long the sessions are scheduled for
16:18:56 <tbachman> #info colindixon asks phrobb how long the topics are going to be — should we be estimating lengths?
16:19:27 <tbachman> #info phrobb recommends estimating a length — also a relative number (e.g. base clustering session before application level clustering)
16:20:21 <tbachman> #info pantelis asks if we should combine openflow and NETCONF
16:20:34 <tbachman> #info ttkacik says he’d like to keep the openflow and HA clustering separate — is a big topic
16:20:57 * tbachman will atttend that session
16:21:49 <tbachman> #info moizer says we’ll first be discussing the use cases, and once we’ve done that, then we can talk about clustering enhancements, then finally applications
16:22:31 <tbachman> #link https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Usage_Pattern_Questionare wiki page for clustering usage questionaire from ttkacik
16:33:35 <tbachman> #info phrobb says we have 12 hours for the sessions
16:36:14 <colindixon> tbachman: sorry for wandering off
16:36:21 <tbachman> colindixon: no worries
16:36:25 <tbachman> mostly wiki page editing :)
16:38:28 <tbachman> #info colindixon would like to see a log normalization session — how to make log messages more uniform across projects
16:38:42 * tbachman notes rovarga created a good wiki page for recommendations once
16:38:54 <tbachman> machine-learning on log messages
16:41:49 <colindixon> https://meetings.opendaylight.org/opendaylight-meeting/2015/tws/opendaylight-meeting-tws.2015-07-13-17.01.html
16:43:03 <colindixon> #link https://meetings.opendaylight.org/opendaylight-meeting/2015/tws/opendaylight-meeting-tws.2015-07-13-17.01.html at last week’s TWS call the SDN App SDK project presented a much more cut down version with just log aggregation analysis
16:43:35 <tbachman> #info phrobb is going to put things into an agenda format now — last call for topics!
16:43:41 <colindixon> tbachman: beats me
16:44:14 <colindixon> #chair ttkacik
16:44:14 <odl_meetbot> Current chairs: colindixon tbachman ttkacik
16:44:33 <colindixon> #info moizer asks what will come out of these topics? bugs/enhancements?
16:44:52 <colindixon> #info ttkacik says modifications to release plans would be ideal
16:45:06 <colindixon> #info for controller/netconf/yangtools/mdsal would likely be enhancement bugs
16:45:07 <tbachman> colindixon: thx
16:45:13 <colindixon> #info for other projects, who knows
16:45:22 <colindixon> #info colindixon says that design documents also seem to make sense
16:45:35 <tbachman> #info moizer says that the specific work items are going to be bugs — so by the end, we should have the bugs on the release plan updated
16:49:21 <colindixon> #topic inventory vs. topology models
16:49:46 <colindixon> #info as long as we have backward compatibility for all apps in Beryllium and deprecate the inventory model in Beryllium, we’re happy
16:51:47 <colindixon> #info colindixon says that you can eliminate so much code if you allow flow programming via topology instead of having to use both inventory and topology
16:52:09 <colindixon> #info colindixon and moizer both say that we should deprecate inventory in Be and remove it in B
16:52:43 <colindixon> #action ttkacik and colindixon to talk to Keith about scheduling time on the TWS
16:53:10 <colindixon> #info TomP asks if we can deprecate a YANG model, ttkacik says yes, but he’s not sure that we pass it to the binding APIs, but if not we’ll add it
16:53:26 <colindixon> #info RESTCONF has no real way to signal deprecation
16:55:54 <colindixon> #topic release plans
16:56:20 <colindixon> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan#Offset_0_Projects release plans for offset 0 projects are listed as drafts here
16:56:27 <colindixon> #info thanks to ttkacik for posting those
16:58:08 <tbachman> colindixon: you want to endmeeting, or shall I?
20:06:53 <colindixon> #endmeeting