#opendaylight-meeting: MDSAL Hackers

Meeting started by alagalah at 16:05:58 UTC (full logs).

Meeting summary

  1. agenda bashing (tbachman, 16:06:22)
    1. 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 (tbachman, 16:07:41)
    2. https://wiki.opendaylight.org/view/Controller_Core_Functionality_Tutorials:Project_proposal (alagalah, 16:11:43)
    3. alagalah provided the project proposal for the Tutorials project (tbachman, 16:12:27)
    4. jmedved says for scope, we should add netconf/restconf as well (tbachman, 16:15:12)
    5. jmedved says we should indicate the the project facilitates best practices in coding patterns and reusable pieces of code (tbachman, 16:18:51)
    6. uchau asks if the openflowplugin and openflowjava are considered offset 0 projects (tbachman, 16:19:25)
    7. alagalah asks if there are alternative ways to address that without confusing the scope (tbachman, 16:19:47)
    8. uchau asks if we have to specify the offset (tbachman, 16:20:05)
    9. ttkacik_ says if we specify offset 0, we will likely not have the openflowplugin or openflowjava (tbachman, 16:21:00)
    10. ttkacik_ says if we go with offset 1, we will get the openflowplugin (tbachman, 16:21:05)
    11. alagalah asks if the list in the current proposal captures the scope (tbachman, 16:21:42)
    12. ttkacik_ asks if the tutorials is meant to encompass 3rd parties (tbachman, 16:22:05)
    13. alagalah says he needs to think about it, but is skeptical that this could be addressed in the Lithium time frame (tbachman, 16:22:25)
    14. ttkacik_ asks if the on-boarding for the java apis and java tutorials is mean to address private app development (tbachman, 16:22:59)
    15. alagalah asks if we can put a “phased approach” into the project proposal (tbachman, 16:23:26)
    16. ttkacik_ says that you can make it so that some parts of the tutorial are optional (tbachman, 16:24:04)
    17. jmedved recommends that folks think about the existing proposal (tbachman, 16:26:31)
    18. alagalah asks colindixon if it’s okay to rename scope to desription and scope (tbachman, 16:26:52)
    19. 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" (tbachman, 16:27:42)
    20. alagalah asks when the deadline is to put this up in order to make Lithium (tbachman, 16:28:01)
    21. colindixon says this could be an offset 2 project, in which case the deadline isn’t until 12/25 (tbachman, 16:28:16)
    22. colindixon says if you email proposals mailing list by christmas, it’s fine (tbachman, 16:28:46)

  2. project template proposal (tbachman, 16:29:16)
    1. 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 (tbachman, 16:30:01)
    2. https://wiki.opendaylight.org/view/YANG_Tools:Issue_Tracking (ttkacik_, 16:30:29)
    3. jmedved asks why this is under yangtools on the wiki (tbachman, 16:32:31)
    4. ttkacik_ says it was started under yangtools, but we can move to a cross-project/best-practices (tbachman, 16:32:53)
    5. colindixon recommends moving it to best-practices (tbachman, 16:33:02)
    6. colindixon says that the opendaylight bugs page would be a good place to link it (tbachman, 16:33:39)
    7. https://wiki.opendaylight.org/view/OpenDaylight_Bugs OpenDaylight bugs wiki page (tbachman, 16:34:11)
    8. colindixon wonders if we should have temporary good links, and try to put them into some structure later (tbachman, 16:34:31)
    9. colindixon says it would be good to have ttkacik_ walk through this process on a TWS (tbachman, 16:36:15)
    10. http://bit.ly/mdsal-dev-links (ttkacik_, 16:38:50)
    11. 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 (tbachman, 16:44:16)
    12. https://wiki.opendaylight.org/view/OpenDaylight_Controller:Config:Main#Overview the overview of the config subsystem (colindixon, 16:46:33)
    13. colindixon says that others may be able to fill in the dependency resolution section better (tbachman, 16:47:24)
    14. https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:MD-SAL_Document_Review:Config_SubSystem <- Maros documentation on ConfigSubsystem (alagalah, 16:47:38)
    15. ttkacik_ says that in Helium, we allow for runtime reconfiguration of dependencies (e.g. clustering — reconfigures MD-SAL) (tbachman, 16:48:41)
    16. colindixon says that in OSGI you could do the same thing by taking down a dependency and bringing the dependency back up (tbachman, 16:49:29)
    17. 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 (tbachman, 16:49:50)
    18. ttkacik_ says with the config subsystem,it’s external to the application, (tbachman, 16:50:13)
    19. colindixon says it lets you put constraints on the valid implementations you’re willing to accept (tbachman, 16:50:36)
    20. ACTION: colindixon to expand the dependency resolution section (tbachman, 16:51:02)
    21. ACTION: alagalah to read the config subsystem portion of the wiki page to see if it makes sense (tbachman, 16:51:30)
    22. https://www.youtube.com/watch?v=bpLBUvTNW8I 5 minute config files from edwarnicke (colindixon, 16:52:01)
    23. ACTION: colindixon to fold the 5 minute youtube videos into the wiki page (tbachman, 16:53:36)
    24. colindixon asks where this overview should live (tbachman, 16:54:07)
    25. jmedved says the config subsystem is okay where it is; do we want to update the architecture overview (tbachman, 16:54:21)
    26. https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:MD-SAL_Document_Review:Architecture (jmedved, 16:54:45)
    27. ACTION: colindixon to review the MD-SAL Document Review: architecture wiki page (tbachman, 16:55:13)
    28. jmedved says he’d like to see similar pages for karaf, clustering, etc. (tbachman, 16:55:40)
    29. ACTION: jmedved to send out invites for this week’s 7-am PST meetings (tbachman, 16:57:08)


Meeting ended at 16:57:58 UTC (full logs).

Action items

  1. 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
  2. ttkacik_ to move the Issue Tracking to either the best practices or cross project wiki, and provide a link in the OpenDaylight bugs page
  3. colindixon to expand the dependency resolution section
  4. alagalah to read the config subsystem portion of the wiki page to see if it makes sense
  5. colindixon to fold the 5 minute youtube videos into the wiki page
  6. colindixon to review the MD-SAL Document Review: architecture wiki page
  7. jmedved to send out invites for this week’s 7-am PST meetings


Action items, by person

  1. alagalah
    1. alagalah to read the config subsystem portion of the wiki page to see if it makes sense
  2. colindixon
    1. colindixon to expand the dependency resolution section
    2. colindixon to fold the 5 minute youtube videos into the wiki page
    3. colindixon to review the MD-SAL Document Review: architecture wiki page
  3. jmedved
    1. jmedved to send out invites for this week’s 7-am PST meetings
  4. ttkacik_
    1. ttkacik_ to move the Issue Tracking to either the best practices or cross project wiki, and provide a link in the OpenDaylight bugs page


People present (lines said)

  1. tbachman (66)
  2. odl_meetbot (6)
  3. alagalah (6)
  4. colindixon (5)
  5. ttkacik_ (2)
  6. jmedved (1)


Generated by MeetBot 0.1.4.