#opendaylight-meeting: MD-SAL Interest Call

Meeting started by colindixon at 16:00:15 UTC (full logs).

Meeting summary

  1. agenda bashing (colindixon, 16:00:18)
    1. Moiz says so far he’s seen very little assigning of bugs during this meeting, mostly just discussing bugs (colindixon, 16:01:36)
    2. catohornet says she agrees, but she doesn’t have a good idea how to get more participants (colindixon, 16:02:10)
    3. ttkacik_mobile says that his approach is to do some hand-holding, but we’re not getting the attendance here (colindixon, 16:03:50)
    4. ACTION: colindixon to work with phrobb to try to get newcomers to attend this meeting to get involved (colindixon, 16:06:36)
    5. https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan the lithium release plan for dates (colindixon, 16:06:56)
    6. colindixon says that in theory, anything can be fixed for the next 4 weeks, the formal release is on 6/25 (colindixon, 16:07:59)
    7. pantelis asks if we should start to push some of these bugs to “not imporant enough to be fixed in Lithium” (colindixon, 16:08:48)
    8. catohornet says she’d love to see that prioritization, but doesn’t have any great ideas there, it’s the right question though (colindixon, 16:09:50)
    9. it seems like this bug scrub is sort of the catch-all place because the critical bugs are usually already triaged and being worked on by the “core” developers (colindixon, 16:11:28)
    10. bugs that make it to this meeting are (1) low-priority bugs that the “core” team hasn’t assigned yet, (2) possibly high-priority bugs that have slipped through the cracks (colindixon, 16:14:41)
    11. there are other bugs that don’t have a target-milestone which need to be scrubbed and give one so that our current queries, e.g., 3160 and 3155 (colindixon, 16:17:21)
    12. there is a suggestion to attack things in this order: (1) unassiged bugs that are in our query, (2) critical bugs in the query just to make sure, (3) the list of bugs that don’t have a milestones set (colindixon, 16:20:27)

  2. bug scrub (colindixon, 16:20:32)
    1. it appears as the only non-clustering, uassigned bug is the upgrade bug (3160) (colindixon, 16:20:58)
    2. https://bugs.opendaylight.org/show_bug.cgi?id=3160 this is the preserving user-config upgrade bug (colindixon, 16:21:27)
    3. pantelis has been working on part of this and testing Maros’s patch for bug 2976 (colindixon, 16:23:04)
    4. https://bugs.opendaylight.org/show_bug.cgi?id=2976 the bug specific to dealing with netconf connector config (colindixon, 16:23:18)
    5. pantelis gives a lot of detail about what he’s done (colindixon, 16:25:03)
    6. https://github.com/nilok/odlutils (colindixon, 16:30:38)
    7. pantelis: can project team leads if they have changed their yang model (catohornet, 16:32:42)
    8. colindixon: Ask projects to provide Data compatibility between beryllium and lithium (catohornet, 16:34:37)
    9. we don’t have a good story about migrating data back and forth (colindixon, 16:34:47)
    10. ttkacik1 says that RESTCONF can’t handle revisions, it always usese the new revisions which has some issues meaning that you can’t migrate dara via RESTCONF (colindixon, 16:36:29)
    11. ACTION: colindixon to produce a script to catalog how models have changed since helium (colindixon, 16:38:14)
    12. moiz asks if the migration code should be part of the app or separate, ttkacik1 argues separate because we should avoid using it at all for clean Ltihium installs (colindixon, 16:39:22)
    13. moiz’s idea was to launch the controller in a “migration” mode, which upgrades all the data, then shuts down and relaunches with clean Lithium (colindixon, 16:40:01)

  3. more config migration discussion (colindixon, 16:51:48)
    1. ttkacik1 notes that we tried to make changes to config yang backward compatible, but they might load the old versions of services even if they are “compatible" (colindixon, 16:52:11)
    2. pantelis agrees and says we probably want to enoucrage most people to blow away most of the config so that they get the new services and wiring (colindixon, 16:52:50)
    3. pantelis argues that we should separate config from wiring as we move forward (colindixon, 16:53:07)
    4. ttkacik says we should discuss mdsal plans for the beryllium release (catohornet, 16:56:13)
    5. there’s a Beryllium target milestone to start opening bugs (colindixon, 16:58:31)
    6. colindixon lists topic we need to think about for beryllium. Example Tooling. We should start a list of Beryllium focus areas and start discussing them. (catohornet, 16:58:38)
    7. colindixon has some ideas around focus areas, we can keep them (colindixon, 16:58:47)
    8. odl-casey says we really need to focus on making sure we can get source for third-party packages (colindixon, 16:59:19)
    9. casey cain says working with 3rd party packages need to be built with src jar files. (catohornet, 16:59:34)
    10. https://docs.google.com/spreadsheets/d/1q_vxUjo4gIxpyAGq43Yiu77o1GHdLaSlxVMysd6G5bQ/edit?usp=sharing (odl-casey, 17:01:04)

  4. talking about 3rd party libarires and source (colindixon, 17:06:03)
    1. everyone can leave at this point since it’s not an MD-SAL topic (colindixon, 17:06:29)
    2. ACTION: colindixon to make sure that the no 3rd-party librarires for Beryllium have the source or else projects will be dropped (colindixon, 17:07:27)
    3. ttkacik1 says the trick is to do use the CLM process to at least start this (colindixon, 17:08:00)
    4. colindixon Better tooling would help this effort. (catohornet, 17:09:40)
    5. ACTION: colindixon to e-mail odl-casey, ttkacik1, zxiiro, and phrobb about 3rd-party source, the last thing to do is to open blocker bugs against projects that use them (colindixon, 17:15:02)
    6. https://docs.google.com/spreadsheets/d/1q_vxUjo4gIxpyAGq43Yiu77o1GHdLaSlxVMysd6G5bQ/edit?usp=sharing this is a list fo what is missing in both our local repo and in maven central (colindixon, 17:16:12)
    7. this list came from zxiiro and we’re going to produce a more accurate list tomorrow (colindixon, 17:16:38)
    8. zxiiro is working the orbit and and eclipse jars (colindixon, 17:18:35)
    9. odl-casey says the two bigs ones he can’t find are: com.sun:tools:jar:sources:1.5.0:system and xom:xom:jar:sources:1.0:test (colindixon, 17:19:09)
    10. https://drive.google.com/a/linuxfoundation.org/file/d/0B1vn4mVLKKmfaU9Zdl9ZdlVyTjA/view?usp=sharing (odl-casey, 17:20:05)
    11. https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Lessons_from_Hydrogen.2C_Helium_and_Lithium_for_future_releases (colindixon, 17:23:50)
    12. https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Project_Status (colindixon, 17:24:25)
    13. https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan#Lessons_from_Hydrogen.2C_Helium_and_Lithium_for_future_releases this is where we can start to catalog what needs to change strategically (colindixon, 17:30:47)
    14. https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=676729675 this is where to track tactical issues (colindixon, 17:31:08)


Meeting ended at 17:32:18 UTC (full logs).

Action items

  1. colindixon to work with phrobb to try to get newcomers to attend this meeting to get involved
  2. colindixon to produce a script to catalog how models have changed since helium
  3. colindixon to make sure that the no 3rd-party librarires for Beryllium have the source or else projects will be dropped
  4. colindixon to e-mail odl-casey, ttkacik1, zxiiro, and phrobb about 3rd-party source, the last thing to do is to open blocker bugs against projects that use them


Action items, by person

  1. colindixon
    1. colindixon to work with phrobb to try to get newcomers to attend this meeting to get involved
    2. colindixon to produce a script to catalog how models have changed since helium
    3. colindixon to make sure that the no 3rd-party librarires for Beryllium have the source or else projects will be dropped
    4. colindixon to e-mail odl-casey, ttkacik1, zxiiro, and phrobb about 3rd-party source, the last thing to do is to open blocker bugs against projects that use them
  2. odl-casey
    1. colindixon to e-mail odl-casey, ttkacik1, zxiiro, and phrobb about 3rd-party source, the last thing to do is to open blocker bugs against projects that use them
  3. ttkacik1
    1. colindixon to e-mail odl-casey, ttkacik1, zxiiro, and phrobb about 3rd-party source, the last thing to do is to open blocker bugs against projects that use them
  4. zxiiro
    1. colindixon to e-mail odl-casey, ttkacik1, zxiiro, and phrobb about 3rd-party source, the last thing to do is to open blocker bugs against projects that use them


People present (lines said)

  1. colindixon (52)
  2. catohornet (7)
  3. odl_meetbot (5)
  4. zxiiro (4)
  5. odl-casey (3)
  6. ttkacik1 (0)


Generated by MeetBot 0.1.4.