#opendaylight-meeting: tsc

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

Meeting summary

  1. agenda bashing and roll call (colindixon, 18:00:42)
    1. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=41044 the agenda in it's usual place (colindixon, 18:01:07)
    2. mohnish anumala (mohnish_, 18:01:11)
    3. ttkacik as stand-in for eaw (ttkacik, 18:01:17)
    4. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-01-28-18.00.html last week's meeting minutes (colindixon, 18:01:23)
    5. colindixon (colindixon, 18:01:29)
    6. abhijitkumbhare stand-in for ChrisPriceAB (abhijitkumbhare, 18:01:34)
    7. ACTION: colindixon to keep boron planning on our minds (colindixon, 18:01:56)
    8. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 18:01:56)
    9. ACTION: colindixon to follow this issue to figure out lessons learned and how to avoid the two diffenent openflow plugin in the future (colindixon, 18:01:57)
    10. LuisGomez (LuisGomez, 18:02:49)
    11. colindixon asks about jdk8 and equinox, rovarga says that there are still 4-5 projects to move (colindixon, 18:03:04)
    12. rovarga for jmedved (rovarga, 18:03:06)
    13. Daniel Farrell (dfarrell07, 18:03:10)
    14. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1156234389 (anipbu, 18:03:15)
    15. rovarga says we already merged the move to jdk8 so they can merge their patfches then, anipbu is tracking that and says it only 3 projects now (colindixon, 18:03:38)
    16. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1156234389 this tracks jd8 progrees (column E tracks the equinox part) (colindixon, 18:04:12)
    17. rovarga says that jdk8 update 40 is required to get things to work with Boron builds and running (colindixon, 18:04:36)
    18. ACTION: phrobb will make sure the mini-summit is on the events page (as more than just something hidden on the ONS page) (colindixon, 18:05:07)

  2. tsc mailing list votes and discussion (colindixon, 18:06:12)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-February/004631.html updated best practices paragraph for avoid cross-project breakages (colindixon, 18:06:29)
    2. VOTE: Voted on "shal the tsc adopt the following best practices for preventing/handling cross-project breakages https://lists.opendaylight.org/pipermail/tsc/2016-February/004631.html?" Results are, +1: 7 (colindixon, 18:08:03)
    3. AGREED: this is the TSC-endorsed best practices for preventing/handling cross-project breakages https://lists.opendaylight.org/pipermail/tsc/2016-February/004631.html (colindixon, 18:08:24)

  3. TSC Elections (colindixon, 18:08:39)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-February/004633.html colin's asks for votes questions around the election (colindixon, 18:09:10)
    2. edwarnicke and dfarrell07 felt we could vote #1 (the framework), but hesitant to vote on #2 or #3 (colindixon, 18:09:36)
    3. dfarrell07 says there are still some details, but the framework seems sane (colindixon, 18:09:57)
    4. dfarrell07 would like some preliminary endorsement to go off to figure out how the voting will mechanically work (colindixon, 18:10:17)
    5. https://wiki.opendaylight.org/view/TSC:Election_Proposal this is the framework (well really everything up to Represented Group Proposals) (colindixon, 18:10:48)
    6. colindixon says we are required to have annual elections by our charter, the last election was in October of 2014, so we're at ~16 months (colindixon, 18:11:59)
    7. colindixon asks if it's reasonable to work out the details now and go for it or wait until next time and have normal elections now (colindixon, 18:12:21)
    8. VOTE: Voted on "shall the TSC preliminarily adopt the new framework for TSC elections (see https://wiki.opendaylight.org/view/TSC:Election_Proposal ) either for this election or the one after, which does address the board request?" Results are, +1: 7 (colindixon, 18:17:07)
    9. #info we can take this to the board to get the waiver to run this election as we see fit new style or old style, the next election must be some new style, we will vote later what we want this election to be (colindixon, 18:17:19)
    10. AGREED: the TSC preliminarily adopts the new framework for TSC elections (see https://wiki.opendaylight.org/view/TSC:Election_Proposal ) either for this election or the one after, which does address the board request (colindixon, 18:17:42)
    11. ACTION: phrobb- to take the vote about new election styles to the board to enable renewal of the platinum designate waiver (via e-mail) (colindixon, 18:18:19)

  4. events (colindixon, 18:18:55)
    1. https://www.opendaylight.org/global-events (colindixon, 18:19:02)
    2. https://www.opendaylight.org/events/2016-02-29-000000-2016-03-01-000000/opendaylight-developer-design-forum developer design form on 2/29-3/1, CFP is out, please submit (colindixon, 18:19:50)
    3. phrobb- will make a wiki page of the topics after that closes for us to plan (colindixon, 18:20:02)
    4. there will also be room for un-conference topics (colindixon, 18:20:11)
    5. there is an intent/policy/NB abstraction topic that might get it's own room for most of the time, dlenrow is going to be using a it as a semi-workshop on the topic (colindixon, 18:20:50)
    6. https://www.opendaylight.org/events/2016-03-13-000000-2016-03-17-000000/open-networking-summit our mini-sumit at ONS has a CFP closes Friday 2/5 (colindixon, 18:21:16)
    7. https://www.opendaylight.org/events/2016-04-25-000000-2016-04-29-000000/openstack-summit is in April in Austin, the CFP closed on Monday 2/1 (colindixon, 18:22:13)
    8. see other events on the events page above (colindixon, 18:22:20)

  5. boron (colindixon, 18:22:54)
    1. anipbu beyond jdk8 stuff above, we're good (colindixon, 18:23:07)

  6. beryllium (colindixon, 18:23:10)
    1. anipbu says there was a recent weather item about extra routes not being provided in neutron, the patch affected OVSDB, VPNservice, and GBP and it broke autorelease (colindixon, 18:23:45)
    2. this issue must be resolved in order to avoid blocking RC2 tonight at UTC 23:59:59 (colindixon, 18:24:25)
    3. anipbu say that the affected projects have merged their patches and it should mean autorelease will build successfully (colindixon, 18:24:56)
    4. there is a concern about VTN being aware of and/or affected by this as well, anipbu has reached (colindixon, 18:25:22)
    5. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=1798258463 issues with RC 1 (colindixon, 18:26:06)
    6. we're tracking the issues and trying to fix them by RC2 which is the final test buidl (colindixon, 18:26:36)
    7. RC3 will be the actual release candidate and will be released the week after unless there are no issues (colindixon, 18:26:57)
    8. https://docs.google.com/spreadsheets/d/1hci5TMUPyB6PX8Al-fwfVqvs5SQVa2wZLja_7rKWN6o/edit#gid=45904332 <-- Sign up for Release Review (anipbu, 18:27:11)
    9. colindixon says it would be really good if we think we fixed all the issues we saw in RC1 in RC2 before we cut it, worst-case we can cut an RC2.1 to evaluate that (colindixon, 18:28:22)
    10. zxiiro notes that autorelease run daily, so we will have RC2.1 even if we dont' call it that (colindixon, 18:29:18)

  7. stable/lithium (colindixon, 18:29:33)
    1. nothing this week (colindixon, 18:29:36)

  8. system integration and test (colindixon, 18:29:44)
    1. jamoluhrsen says that there are 23 projects that don't have system test waivers yet arent' reporting system test results (colindixon, 18:30:29)
    2. ACTION: jamoluhrsen to produce a list of which projects do not have system tests but promised to do so, so that it can be understood for future tasks, e.g., graduation reviews (colindixon, 18:31:30)
    3. ACTION: anipbu to remind people that Lithium-SR4 build is soon (with the actual date) (colindixon, 18:31:47)

  9. infrastructure (colindixon, 18:32:09)
    1. zxiiro says not much to report, the port issues with rackspace have seemed to go away now that they reap broken ports every 4 hours (colindixon, 18:32:34)

  10. Tomas Cere as a commiter on NETCONF (colindixon, 18:32:53)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-February/004622.html request to the TSC (colindixon, 18:33:04)
    2. https://lists.opendaylight.org/pipermail/netconf-dev/2016-February/000236.html two +1s which is a majority (colindixon, 18:33:19)
    3. https://git.opendaylight.org/gerrit/#/q/owner:%22Tomas+Cere+%253Ctcere%2540cisco.com%253E%22+project:netconf patches (colindixon, 18:33:32)
    4. VOTE: Voted on "shall the TSC approve Tomas Cere on the NETCONF project?" Results are, +1: 7 (colindixon, 18:35:43)
    5. AGREED: Tomas Cere is now a comitter on NETCONF (colindixon, 18:36:01)

  11. VTN graduation review (colindixon, 18:36:16)
    1. https://wiki.opendaylight.org/view/VTN:Graduation_Review the graduation review proposal (colindixon, 18:36:32)
    2. https://lists.opendaylight.org/pipermail/project-proposals/2015-December/000388.html requested on 12/29/2016 (colindixon, 18:36:49)
    3. VTN has been part of ODL since Hydrogen really the beginning (colindixon, 18:37:55)
    4. colindixon can confirm that the docuemntation for VTN is consistently the most up-to-date and thorough (colindixon, 18:38:44)
    5. LuisGomez and dfarrell07 say VTN system tests are good (dfarrell07, 18:38:48)
    6. VTN tests overall rock, they caught a very elusive YT bug ;-) (rovarga, 18:39:12)
    7. colindixon notes that they are good a hitting deadlines (even removing their dependency on the MD-SAL) and communicate well in advance if they might miss one (colindixon, 18:40:26)
    8. hideyuki reminds colindixon that VTN is used by NIC and so is not a leaf project (colindixon, 18:40:40)
    9. rovarga notes that he doesn't think we have another project of this scope with this carefully controlled and understood sonar issues (colindixon, 18:41:24)
    10. VOTE: Voted on "shall the TSC graduate the VTN being mature?" Results are, +1: 7 (colindixon, 18:42:08)
    11. AGREED: the VTN project is now mature (colindixon, 18:42:19)
    12. ACTION: hideyuki to update the relevant wiki pages (project facts temple and the graduation review template) (colindixon, 18:42:41)
    13. ACTION: colindixon to make sure we have an accurate list of oustanding project proposals (colindixon, 18:44:02)

  12. beryllium release mechanics (colindixon, 18:44:56)
    1. we will vote go/no-go on 2/18, the PR launch with LF marketing will be on Monday, 2/22 (colindixon, 18:45:29)
    2. assuming that things go well on 1/18 (colindixon, 18:45:39)

  13. Boron Planning Summary (colindixon, 18:46:10)
    1. rovarga says he's not sure we have a large scale update (colindixon, 18:46:17)
    2. the discussion is looking at both shortening the development cycle and trying to decouple development between the different offsets to reduce transient failures (colindixon, 18:46:45)
    3. https://lists.opendaylight.org/pipermail/discuss/2016-February/006140.html most recent mailing list thread (colindixon, 18:46:57)
    4. https://meetings.opendaylight.org/opendaylight-meeting/2016/tws/opendaylight-meeting-tws.2016-01-11-18.27.html TWS meeting 1 (colindixon, 18:47:05)
    5. https://meetings.opendaylight.org/opendaylight-meeting/2016/tws/opendaylight-meeting-tws.2016-01-25-18.00.html TWS meeting 2 (colindixon, 18:47:12)
    6. https://meetings.opendaylight.org/opendaylight-meeting/2016/tws/opendaylight-meeting-tws.2016-02-01-18.02.html TWS meeting 3 (colindixon, 18:47:20)
    7. rovarga says that there seems to be some consensus that 6 months is too long and causing us some issues with too much time to drift apart before syncing (colindixon, 18:48:12)
    8. rovarga says the current theory would be having harder syncs every 2-4 months to try ot reduce drift while still preventing transient breakages (colindixon, 18:48:42)
    9. rovarga says he thinks there's still work to be done to figure out if we could really adopt this in Boron (colindixon, 18:49:03)
    10. Boron, Carbon, Nitrogen are the next three (rovarga, 18:49:46)
    11. https://wiki.opendaylight.org/view/New_workflow_proposal new workflow from skitt and rovarga (colindixon, 18:50:08)
    12. https://wiki.opendaylight.org/view/Semantic_Versioning semantic versioning which goes along with it (colindixon, 18:50:18)
    13. https://lists.opendaylight.org/pipermail/tsc/2016-January/004565.html Advisory Requests for Boron (colindixon, 18:50:39)
    14. rovarga says we don't have a target date for the Boron release (colindixon, 18:51:07)
    15. abhijitkumbhare says shouldn't we try to hit before the OpenDaylight summit on 9/27 (colindixon, 18:51:20)
    16. phrobb- says we targeted the summit to match a likely Boron release, but that it's not required (colindixon, 18:51:45)
    17. rovarga says we should pick that target and work from there (colindixon, 18:51:52)
    18. ACTION: colindixon to draft up a Boron release plan that looks like Beryllium and hits before the ODL Summit just in case (colindixon, 18:52:26)
    19. ACTION: rovarga to follow up with a counter-proposal with the new workflow ;-) (rovarga, 18:53:27)
    20. The way the current fast release proposal works, it would be an 2 months + 2 months * offset, so we may have time to bail out if a new plan seems to be failing (dfarrell07, 18:53:49)
    21. The way the current fast release proposal works, it would be an 2 months + 2 months * offset, so we may have time to bail out if a new plan seems to be failing, says colindixon (dfarrell07, 18:54:07)

  14. cookies (colindixon, 18:55:04)


Meeting ended at 18:55:07 UTC (full logs).

Action items

  1. colindixon to keep boron planning on our minds
  2. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  3. colindixon to follow this issue to figure out lessons learned and how to avoid the two diffenent openflow plugin in the future
  4. phrobb will make sure the mini-summit is on the events page (as more than just something hidden on the ONS page)
  5. phrobb- to take the vote about new election styles to the board to enable renewal of the platinum designate waiver (via e-mail)
  6. jamoluhrsen to produce a list of which projects do not have system tests but promised to do so, so that it can be understood for future tasks, e.g., graduation reviews
  7. anipbu to remind people that Lithium-SR4 build is soon (with the actual date)
  8. hideyuki to update the relevant wiki pages (project facts temple and the graduation review template)
  9. colindixon to make sure we have an accurate list of oustanding project proposals
  10. colindixon to draft up a Boron release plan that looks like Beryllium and hits before the ODL Summit just in case
  11. rovarga to follow up with a counter-proposal with the new workflow ;-)


Action items, by person

  1. anipbu
    1. anipbu to remind people that Lithium-SR4 build is soon (with the actual date)
  2. colindixon
    1. colindixon to keep boron planning on our minds
    2. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    3. colindixon to follow this issue to figure out lessons learned and how to avoid the two diffenent openflow plugin in the future
    4. colindixon to make sure we have an accurate list of oustanding project proposals
    5. colindixon to draft up a Boron release plan that looks like Beryllium and hits before the ODL Summit just in case
  3. hideyuki
    1. hideyuki to update the relevant wiki pages (project facts temple and the graduation review template)
  4. jamoluhrsen
    1. jamoluhrsen to produce a list of which projects do not have system tests but promised to do so, so that it can be understood for future tasks, e.g., graduation reviews
  5. rovarga
    1. rovarga to follow up with a counter-proposal with the new workflow ;-)
  6. UNASSIGNED
    1. phrobb will make sure the mini-summit is on the events page (as more than just something hidden on the ONS page)
    2. phrobb- to take the vote about new election styles to the board to enable renewal of the platinum designate waiver (via e-mail)


People present (lines said)

  1. colindixon (113)
  2. odl_meetbot (21)
  3. dfarrell07 (14)
  4. rovarga (9)
  5. abhijitkumbhare (7)
  6. LuisGomez (6)
  7. mohnish_ (6)
  8. ttkacik (5)
  9. anipbu (3)
  10. jamoluhrsen (1)
  11. hideyuki (1)
  12. phrobb- (0)


Generated by MeetBot 0.1.4.