16:03:18 <colindixon> #startmeeting MD-SAL interest call
16:03:18 <odl_meetbot> Meeting started Tue Sep 22 16:03:18 2015 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
16:03:18 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:03:18 <odl_meetbot> The meeting name has been set to 'md_sal_interest_call'
16:03:23 <colindixon> #topic agenda bashing
16:03:33 <colindixon> #link https://wiki.opendaylight.org/view/MD-SAL_Weekly_Call#Upcoming_Agenda_Topics
16:04:03 <colindixon> rovarga: you coming?
16:04:29 <colindixon> #info the only topic we have scheduled for today is to talk about the migration to jersey 2
16:05:33 <colindixon> #link https://git.opendaylight.org/gerrit/#/c/27052 TomP would like to discuss the design proposal here
16:06:33 <colindixon> #topic things coming down the pipe
16:07:52 <colindixon> #link https://git.opendaylight.org/gerrit/#/q/topic:bug2399 the last patch of a series to fix BUG-2399
16:08:03 <colindixon> #link https://bugs.opendaylight.org/show_bug.cgi?id=2399 the bug
16:08:54 <colindixon> #info the last patch is still being tested and is close to being merged, it has to do with automatic creation and removal of containers when there are no more leaves
16:09:47 <colindixon> #info there is also a new parser coming in, which has been in development since early Lithium
16:10:53 <colindixon> https://github.com/opendaylight/yangtools/tree/master/yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/impl
16:12:04 <colindixon> #info it replaces the old parser with a new one that is more focused on providing better extensibility, e.g., even the YANG natifve stuff is treated as an extions
16:12:29 <colindixon> #action ttkacik to send out links to the exact packages for the new vs. the old parser
16:12:41 <colindixon> #link https://github.com/opendaylight/yangtools/tree/master/yang/yang-parser-impl/src/main/java/org/opendaylight/yangtools/yang/parser/impl I think both implementations are here
16:15:28 <colindixon> #topic jersey 2
16:15:46 <colindixon> #link https://git.opendaylight.org/gerrit/#/q/status:open+project:controller+branch:master+topic:jersey2-migration jersey 2 patches
16:15:54 <colindixon> #link https://lists.opendaylight.org/pipermail/controller-dev/2015-September/010376.html mailing list thread
16:16:11 <colindixon> #link https://bugs.opendaylight.org/show_bug.cgi?id=2515 the bug in question
16:16:51 <colindixon> #info ryan goulding says that he needs support for jersey 2 for AAA, he’s just curious what the state is
16:17:33 <colindixon> #info ttkacik says that the patches need to be picked up and updated
16:17:41 <colindixon> #info Ryan asks if he can help out
16:18:13 <colindixon> #info ttkacik says that he’d love to see help in getting these patches working in the NETCONF project
16:18:56 <colindixon> #info colindixon asks if there are any problems we should expect
16:19:14 <colindixon> #info ttkacik and ryan say that neutron might be a pain, but it should be mostly easy
16:20:52 <colindixon> #topic NETCONF clustering
16:21:22 <colindixon> #link https://git.opendaylight.org/gerrit/#/c/27052 this is the NETCONF clustering design docs
16:25:37 <colindixon> #info essentially, there is a move to put the NETCONF configuration data and things in the config data store instead of the config subsystem so that it will be replicated
16:26:40 <colindixon> #info this will use the entity ownership service to establish who is supposed to talk to a given NETCONF device
16:27:55 <colindixon> #info the idea is that there is a global topology manager which manages the high-level stuff, then the node manager runs one per NETCONF device and deal with per-device issues
16:28:19 <colindixon> #info NETCONF call home (device to controller connections) is discussed, but not planned in Beryllium
16:33:29 <colindixon> #info there will be no clustering support for config-subsystem managed NETCONF devices
16:34:07 <colindixon> #info there will be no support for clustering the controller-config NETCONF device (e.g., NETCONF NB) because it would be a diffferent devices on every node as it’s a loopback interface in some sense
16:34:34 <colindixon> #info the hope is to abstract out the netconf details and maybe make it usable for others
16:40:23 <colindixon> #info tom pantelis asks if there’s a way to migrate existing config-subsystem configured NETCONF connections to this
16:41:00 <colindixon> #info ttkacik says yes, we could write an adaptor but he recommends that it be opt-in, not opt-out
16:41:53 <colindixon> #info in particular that’s to avoid the interactions between clustering and the NETCONF NB which the controller exports and mounts as a loopback
16:44:37 <colindixon> #info TomP asks about how we will migrate an installation of OpenDaylight with old-style config-subsystem-based NETCONF connected devices
16:45:03 <colindixon> #Info rovarga basically says we can’t think about this until we have a broader upgrade process worked out
16:46:30 <colindixon> #info colindixon asks if moving the config file XML to the data store would literally be copying XML snippets and pasting them
16:46:44 <colindixon> #info rovarga says no, it’s likely going to involve some transform
16:47:15 <colindixon> #info ttkacik says that it should be pretty easy to write a script that copies the 4-5 fields crom one place to another
16:51:37 <colindixon> #topic MD-SAL project migration
16:52:11 <colindixon> #info ttkacik says that the only thing that needs to happen is to do some ping-pong work between the MD-SAL and the controller project to keep the older APIs in place
16:52:40 <colindixon> #info ttkacik says that most of the code won’t be removed from the controller (except DOMBrokerImpl and BindingBroker)
16:53:06 <colindixon> #info it’s more complicated than the NETCONF which had no public Java APIs
16:53:45 <colindixon> #info TomP asks are we moving sal-common-api? when are we going to? how can TomP help? TomP needs it for the entity ownership service
16:54:00 <colindixon> #action TomP and ttkacik to work together on when to merge that
16:54:15 <colindixon> #info anipbu says that there are four projects still that haven’t merged the MD-SAL migration patches
16:55:31 <colindixon> #endmeeting