16:05:58 <alagalah> #startmeeting MDSAL Hackers 16:05:58 <odl_meetbot> Meeting started Mon Dec 1 16:05:58 2014 UTC. The chair is alagalah. Information about MeetBot at http://ci.openstack.org/meetbot.html. 16:05:58 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:05:58 <odl_meetbot> The meeting name has been set to 'mdsal_hackers' 16:06:05 <alagalah> #chair tbachman jmedved 16:06:05 <odl_meetbot> Current chairs: alagalah jmedved tbachman 16:06:22 <tbachman> #topic agenda bashing 16:07:14 * tbachman goes off to look for minutes 16:07:41 <tbachman> #link https://meetings.opendaylight.org/opendaylight-meeting/2014/md_sal_hackers/opendaylight-meeting-md_sal_hackers.2014-11-24-16.00.html minutes from last week’s meeting 16:11:43 <alagalah> #link https://wiki.opendaylight.org/view/Controller_Core_Functionality_Tutorials:Project_proposal 16:11:48 <tbachman> alagalah: thx! 16:11:56 * tbachman was searching for that 16:12:27 <tbachman> #info alagalah provided the project proposal for the Tutorials project 16:15:12 <tbachman> #info jmedved says for scope, we should add netconf/restconf as well 16:18:51 <tbachman> #info jmedved says we should indicate the the project facilitates best practices in coding patterns and reusable pieces of code 16:19:25 <tbachman> #info uchau asks if the openflowplugin and openflowjava are considered offset 0 projects 16:19:47 <tbachman> #info alagalah asks if there are alternative ways to address that without confusing the scope 16:20:05 <tbachman> #info uchau asks if we have to specify the offset 16:20:29 <tbachman> #info ttkacik_ says if we specify offset 0, we pretty much will not have openflow 16:20:42 <tbachman> #undo 16:20:42 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2734250> 16:21:00 <tbachman> #info ttkacik_ says if we specify offset 0, we will likely not have the openflowplugin or openflowjava 16:21:05 <tbachman> #info ttkacik_ says if we go with offset 1, we will get the openflowplugin 16:21:42 <tbachman> #info alagalah asks if the list in the current proposal captures the scope 16:22:05 <tbachman> #info ttkacik_ asks if the tutorials is meant to encompass 3rd parties 16:22:25 <tbachman> #info alagalah says he needs to think about it, but is skeptical that this could be addressed in the Lithium time frame 16:22:59 <tbachman> #info ttkacik_ asks if the on-boarding for the java apis and java tutorials is mean to address private app development 16:23:26 <tbachman> #info alagalah asks if we can put a “phased approach” into the project proposal 16:24:04 <tbachman> #info ttkacik_ says that you can make it so that some parts of the tutorial are optional 16:26:31 <tbachman> #info jmedved recommends that folks think about the existing proposal 16:26:52 <tbachman> #info alagalah asks colindixon if it’s okay to rename scope to desription and scope 16:27:42 <tbachman> #info colindixon says if the description really is the scope, then that’s fine, but just make sure the TSC understands the scope and that it’s “well-stated" 16:28:01 <tbachman> #info alagalah asks when the deadline is to put this up in order to make Lithium 16:28:16 <tbachman> #info colindixon says this could be an offset 2 project, in which case the deadline isn’t until 12/25 16:28:46 <tbachman> #info colindixon says if you email proposals mailing list by christmas, it’s fine 16:29:08 * tbachman wonders if there’s a holiday baby in the wings 16:29:09 <tbachman> lol 16:29:16 <tbachman> #topic project template proposal 16:29:28 <tbachman> anyone got a link for this? 16:30:01 <tbachman> #action ttkacik to send an email with a concrete/specific example of how bugzilla can be set up to use for automation of release planning and tracking 16:30:22 <alagalah> tbachman: I don't think we are ready for that yet... 16:30:27 <tbachman> alagalah: ack 16:30:28 <alagalah> tbachman: There's two outstanding action items 16:30:29 <ttkacik_> #info https://wiki.opendaylight.org/view/YANG_Tools:Issue_Tracking 16:30:36 <tbachman> ttkacik_: thx! 16:32:31 <tbachman> #info jmedved asks why this is under yangtools on the wiki 16:32:53 <tbachman> #info ttkacik_ says it was started under yangtools, but we can move to a cross-project/best-practices 16:33:02 <tbachman> #info colindixon recommends moving it to best-practices 16:33:39 <tbachman> #info colindixon says that the opendaylight bugs page would be a good place to link it 16:34:11 <tbachman> #link https://wiki.opendaylight.org/view/OpenDaylight_Bugs OpenDaylight bugs wiki page 16:34:31 <tbachman> #info colindixon wonders if we should have temporary good links, and try to put them into some structure later 16:36:15 <tbachman> #info colindixon says it would be good to have ttkacik_ walk through this process on a TWS 16:37:08 <tbachman> colindixon: making early xmas list ;) 16:37:23 <colindixon> tbachman: :-) 16:38:50 <ttkacik_> #link http://bit.ly/mdsal-dev-links 16:38:54 <tbachman> ttkacik_: thx! 16:40:44 <colindixon> FWIW, my patches and my reviews both work for me as long as I’m logged in before I click on the links 16:44:16 <tbachman> #action ttkacik_ to move the Issue Tracking to either the best practices or cross project wiki, and provide a link in the OpenDaylight bugs page 16:45:30 * tbachman was looking for the link as well 16:46:33 <colindixon> #link https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Main#Overview the overview of the config subsystem 16:46:36 <tbachman> colindixon: thx! 16:47:24 <tbachman> #info colindixon says that others may be able to fill in the dependency resolution section better 16:47:38 <alagalah> #link https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:MD-SAL_Document_Review:Config_SubSystem <- Maros documentation on ConfigSubsystem 16:48:41 <tbachman> #info ttkacik_ says that in Helium, we allow for runtime reconfiguration of dependencies (e.g. clustering — reconfigures MD-SAL) 16:49:29 <tbachman> #info colindixon says that in OSGI you could do the same thing by taking down a dependency and bringing the dependency back up 16:49:50 <tbachman> #info ttkacik_ says you then need code in your application that uses the Felix DM or service tracker, so then the problem is how to configure what you want 16:50:13 <tbachman> #info ttkacik_ says with the config subsystem,it’s external to the application, 16:50:36 <tbachman> #info colindixon says it lets you put constraints on the valid implementations you’re willing to accept 16:51:02 <tbachman> #action colindixon to expand the dependency resolution section 16:51:11 <tbachman> #info colindixon asks if someone who doesn 16:51:13 <tbachman> #undo 16:51:13 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x285d610> 16:51:30 <tbachman> #action alagalah to read the config subsystem portion of the wiki page to see if it makes sense 16:52:01 <colindixon> #link https://www.youtube.com/watch?v=bpLBUvTNW8I 5 minute config files from edwarnicke 16:52:22 * tbachman hears ghosts of edwarnicke present 16:53:36 <tbachman> #action colindixon to fold the 5 minute youtube videos into the wiki page 16:53:42 <colindixon> tbachman: thanks, I’m slow 16:53:46 <tbachman> colindixon: hardly ;) 16:54:07 <tbachman> #info colindixon asks where this overview should live 16:54:21 <tbachman> #info jmedved says the config subsystem is okay where it is; do we want to update the architecture overview 16:54:45 <jmedved> #info https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:MD-SAL_Document_Review:Architecture 16:55:13 <tbachman> #action colindixon to review the MD-SAL Document Review: architecture wiki page 16:55:40 <tbachman> #info jmedved says he’d like to see similar pages for karaf, clustering, etc. 16:56:06 * tbachman *thinks* he’s lb-action’ed colindixon? 16:57:08 <tbachman> #action jmedved to send out invites for this week’s 7-am PST meetings 16:57:58 <tbachman> #endmeeting