#opendaylight-meeting: tsc

Meeting started by colindixon at 18:00:29 UTC (full logs).

Meeting summary

  1. roll call and agenda bashing (colindixon, 18:00:35)
    1. colindixon (colindixon, 18:00:36)
    2. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=38148#Agenda agenda in it's usaul place (colindixon, 18:00:51)
    3. https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-10-22-17.00.html last week's minutes (colindixon, 18:01:37)
    4. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade from Helium to Lithium (for SR3) https://bugs.opendaylight.org/show_bug.cgi?id=3160 (colindixon, 18:02:01)
    5. jmedved (jmedved, 18:02:07)
    6. ACTION: ttcacik and zxiiro to work on getting feature-level code coverage numbers (colindixon, 18:02:28)
    7. dlenrow (dlenrow, 18:03:05)
    8. https://bugs.opendaylight.org/show_bug.cgi?id=4519 the bug to get dsbenchmark out of coretutorials by offset 2 M4 (colindixon, 18:03:16)
    9. LuisGomez (LuisGomez, 18:03:19)
    10. ACTION: jmedved to talk to ttkacik about how to get the benchmarks into controller by offset 2 M4 (tracked by https://bugs.opendaylight.org/show_bug.cgi?id=4519) (colindixon, 18:03:30)
    11. mohnish anumala (mohnish_, 18:04:00)
    12. ACTION: rovarga, alagalah, mohnish, ttkacik, vishnoianil, ebrjohn, RPenno, abhijitkumbhare will try to draft a paragraph around the best practices including this discussion and feedback (to be gotten) from PTLS, they should also feel free to provide feedback around tools and technical solutions to help with upstream/downstream breakages (colindixon, 18:04:38)
    13. edwarnicke (edwarnicke, 18:05:42)

  2. events (colindixon, 18:06:26)
    1. Daniel Farrell (dfarrell07, 18:06:42)
    2. https://www.opendaylight.org/global-events upcoming events (colindixon, 18:06:57)
    3. hackfest on Monday/Tuesday of next week, register if you haven't (colindixon, 18:07:14)
    4. https://wiki.opendaylight.org/view/Events/Beryllium_HackFest#Topics please add your attendance and/or topics here (colindixon, 18:07:28)
    5. https://www.regonline.com/Register/Checkin.aspx?EventID=1761135 register here if you haven't (it's free, but might run out of space) (colindixon, 18:07:59)
    6. phrobb says that there will be obviously some unconfernece topics too (colindixon, 18:08:29)
    7. there will be some remote participation, but phrobb suggests that we maybe use hangouts for smaller groups as it might work better (colindixon, 18:08:46)
    8. colindixon and phrobb give a summary of OpenStack tokyo, we had no talks, there was a huge attendance at the demo we gave, we should aim to have more talks in Austin (colindixon, 18:11:55)

  3. TSC mailing list votes and discussions (colindixon, 18:13:29)
    1. https://lists.opendaylight.org/pipermail/tsc/2015-October/004026.html at-large election bylaw waiver discussion (colindixon, 18:13:45)
    2. https://lists.opendaylight.org/pipermail/tsc/2015-October/004021.html requirement to be in the release (colindixon, 18:14:13)
    3. https://lists.opendaylight.org/pipermail/tsc/2015-November/004098.html meeting next week despite the OPNFV summit (colindixon, 18:14:49)
    4. ACTION: phrobb to try to find a room for the TSC call under the assumption it's still happen (colindixon, 18:16:00)

  4. TSC at-large elections (colindixon, 18:16:48)
    1. phrobb says that the discussion of how to avoid needing a permament exception to leave platinum designates in place has stalled a bit, and we still need to close on that (colindixon, 18:17:59)
    2. dfarrell07 says he wished that there were experts that could help us with governance and election design (colindixon, 18:20:32)
    3. colindixon and edwarnicke say that desiging good governance is hard and a contenttious/open problem (colindixon, 18:20:57)

  5. beryllium (colindixon, 18:21:09)
    1. we're still wating on 5 projects to get M3 updates, they've been notified (colindixon, 18:21:37)
    2. we have several projects with action items that are being tracked (colindixon, 18:21:57)
    3. we have 8 projects that aren't in integration/distribution, they have also been notified (colindixon, 18:22:15)
    4. beryllium autorelease is currently blocking on NetIDE using an old version of config-parent, it will be adressed soon or they'll be dropped, also being blocked by dsbenchmark which is planned to be moved by offset 2 M4 (colindixon, 18:23:03)
    5. https://docs.google.com/spreadsheets/d/1Kfp5HVQGydNegEjp6dD2V3XsUnqpice0bysWbdxABA4/edit#gid=1817245674 (anipbu, 18:23:33)
    6. dfarrell07 asks if we can keep stats about missed deadlines for fugture needs (colindixon, 18:23:42)
    7. https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=1241552017 (colindixon, 18:24:11)
    8. colindixon and anipbu say we track how late milestone readouts are, but don't track deep on timeness of internal deliverables (colindixon, 18:25:30)
    9. anipbu says he'll track when a project is 100% complete with a milestone starting with M4, to get better information (colindixon, 18:26:52)
    10. edwarnicke says this is incredibly helpful and he can't overstate how important what anipbu is doing and how it's doing (colindixon, 18:27:22)
    11. colindixon, abhijitkumbhare, dfarrell07 (and presumably many ohters) offer hearty +1s (colindixon, 18:27:41)
    12. https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan#Project_Status the projecct tracking sheet is linked from teh main release plan here (colindixon, 18:28:06)
    13. https://docs.google.com/spreadsheets/d/1Kfp5HVQGydNegEjp6dD2V3XsUnqpice0bysWbdxABA4/edit#gid=1862710416 the actual sheet with the auto-computed milestone completely summary (colindixon, 18:28:28)
    14. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=2030147923 (anipbu, 18:28:54)
    15. https://wiki.opendaylight.org/view/Weather#Beryllium_Blocking_Bugs cross-project issues and blocking bugs are tracked in this sheet (linked from weather page) (colindixon, 18:29:27)
    16. https://wiki.opendaylight.org/view/Weather (colindixon, 18:29:54)
    17. we tried to merge the jersey/jaxrs patch last week, it turned to break a lot of people and we've reverted it (colindixon, 18:30:23)
    18. the structural container patch was merged, there was a controller bug, but it was fixed and remains in (colindixon, 18:30:42)
    19. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1368787047 <-- JDK8 tracking (anipbu, 18:38:23)
    20. we're working on getting JDK8 to work at least for building and verify jobs, there are patches for all be 2-3 projects that get them to build with JDK8 onmaster, 2-3 of them seem to fail with non-JDK8 issues on master (colindixon, 18:39:02)
    21. anipbu has been tracking this and tracking it well (colindixon, 18:39:11)
    22. it remains to be seen if we can get JDK8 and JDK7 autorelease to build for autorelease (colindixon, 18:39:49)
    23. rovarga says his goal is to have Beryllium be compatible with both JDK7 adn JDK8 and then move to JDK8-only in Boron, which seems within grasp (colindixon, 18:41:28)
    24. rovarga says that's in part because YANG Tools would like to be able to use Jave 8 only features for YANG 1.1 java binding (colindixon, 18:41:50)

  6. stable/lithium (colindixon, 18:42:07)
    1. the next SR is in two weeks with a cutoff of 11/15 for patches (colindixon, 18:42:18)

  7. system integration and test (colindixon, 18:42:36)
    1. jamoluhrsen says that there are missing system test templates that they're still waiting on (colindixon, 18:43:09)

  8. infrastructure (colindixon, 18:43:34)
    1. we had reboots of infra that happened last week due to rackspace host upgrated, caused angst on master jenkins, but it's fixed now (colindixon, 18:44:08)
    2. we now have more than 1000 jobs in a jenkins master (tykeal notes that OpenStack has more than 3000), restarts to jenkins now take a long time, just from starting jenkins to consider processing jobs takes 30 minutes, in total it takes 1-2 hours for jenkins restarts (colindixon, 18:45:13)
    3. some of these issues will go away as we move to nodepool and xuul (colindixon, 18:45:59)
    4. https://lists.opendaylight.org/pipermail/dev/2015-October/001325.html GPG keysigning info at the Beryllium Hackfest (tykeal, 18:46:18)

  9. DIDM feature names (colindixon, 18:47:11)
    1. https://lists.opendaylight.org/pipermail/tsc/2015-October/003946.html mail thread (colindixon, 18:47:34)
    2. https://github.com/opendaylight/openflowplugin/search?utf8=%E2%9C%93&q=nicira it's worth noting that we have other features, the nicira extensions here (colindixon, 18:49:01)
    3. phrobb says that this isn't a legal question, because it will fall under fair use, but we have avoided having trademark names in project names from business reasons, thus would also logically apply here (colindixon, 18:49:43)
    4. the consensus seems to be tending toward the naming is fine as long as it's really about a vendor product, not naming things that would would be confusing (colindixon, 18:51:25)
    5. cdub says that the general best practice is to use obvious name without obfuscation for vague business reasons, and it's different between being a low-level (driver-level) than a higher-level API or feature (colindixon, 18:54:38)
    6. edwarnicke, colindixon, and dlenrow all say +1 (colindixon, 18:55:06)
    7. it seems everyone agrees it would be different if the vendor-specific name was further up in the stack (colindixon, 18:58:40)
    8. mohnish_ says also, it would be really important for PTLs to separate vendor-specific code from vendor-agnositc code (colindixon, 18:59:48)

  10. wiki revamp (colindixon, 19:01:17)
    1. https://wikistg.opendaylight.org/view/Main_Page odl-casey has been trying to do a bit of a visual and some content revamp of the wiki (username: daylight, password: ODLStageSiteAccess!) (colindixon, 19:02:45)
    2. it has a new theme, that's a bit cleaner (colindixon, 19:02:56)
    3. the links of the main page have beeen grouped into "user", "developer" and "community" generally to make it easier for people to find what they need, epsecially for users (not ODL developers) who often end up and are confused by our wiki (colindixon, 19:03:54)
    4. odl-casey would love feedback, colindixon will start a thread (colindixon, 19:04:15)
    5. ACTION: colindixon to start a thread on the wiki revamp (colindixon, 19:04:40)

  11. cookies (colindixon, 19:08:20)


Meeting ended at 19:08:38 UTC (full logs).

Action items

  1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade from Helium to Lithium (for SR3) https://bugs.opendaylight.org/show_bug.cgi?id=3160
  2. ttcacik and zxiiro to work on getting feature-level code coverage numbers
  3. jmedved to talk to ttkacik about how to get the benchmarks into controller by offset 2 M4 (tracked by https://bugs.opendaylight.org/show_bug.cgi?id=4519)
  4. rovarga, alagalah, mohnish, ttkacik, vishnoianil, ebrjohn, RPenno, abhijitkumbhare will try to draft a paragraph around the best practices including this discussion and feedback (to be gotten) from PTLS, they should also feel free to provide feedback around tools and technical solutions to help with upstream/downstream breakages
  5. phrobb to try to find a room for the TSC call under the assumption it's still happen
  6. colindixon to start a thread on the wiki revamp


Action items, by person

  1. abhijitkumbhare
    1. rovarga, alagalah, mohnish, ttkacik, vishnoianil, ebrjohn, RPenno, abhijitkumbhare will try to draft a paragraph around the best practices including this discussion and feedback (to be gotten) from PTLS, they should also feel free to provide feedback around tools and technical solutions to help with upstream/downstream breakages
  2. alagalah
    1. rovarga, alagalah, mohnish, ttkacik, vishnoianil, ebrjohn, RPenno, abhijitkumbhare will try to draft a paragraph around the best practices including this discussion and feedback (to be gotten) from PTLS, they should also feel free to provide feedback around tools and technical solutions to help with upstream/downstream breakages
  3. colindixon
    1. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade from Helium to Lithium (for SR3) https://bugs.opendaylight.org/show_bug.cgi?id=3160
    2. colindixon to start a thread on the wiki revamp
  4. jmedved
    1. jmedved to talk to ttkacik about how to get the benchmarks into controller by offset 2 M4 (tracked by https://bugs.opendaylight.org/show_bug.cgi?id=4519)
  5. phrobb
    1. phrobb to try to find a room for the TSC call under the assumption it's still happen


People present (lines said)

  1. colindixon (75)
  2. dlenrow (6)
  3. edwarnicke (5)
  4. odl_meetbot (4)
  5. abhijitkumbhare (4)
  6. dfarrell07 (3)
  7. anipbu (3)
  8. alagalah (2)
  9. mohnish_ (2)
  10. tykeal (2)
  11. jmedved (1)
  12. djx (1)
  13. LuisGomez (1)
  14. odl-casey (1)
  15. phrobb_ (1)
  16. phrobb (0)


Generated by MeetBot 0.1.4.