#opendaylight-meeting: tsc

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

Meeting summary

  1. agenda bashing and roll call (colindixon, 18:00:17)
    1. colindixon (colindixon, 18:00:20)
    2. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-01-21-18.00.html last week's meeting minuts (colindixon, 18:00:32)
    3. Daniel Farrell (dfarrell07, 18:00:51)
    4. Chris Price (ChrisPriceAB, 18:00:57)
    5. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=40650#Agenda the agenda in it's usual place (colindixon, 18:01:06)
    6. ACTION: colindixon to keep boron planning on our minds (colindixon, 18:02:13)
    7. jmedved (jmedved, 18:02:18)
    8. mohnish anumala (mohnish_, 18:02:19)
    9. ACTION: colindixon to send a reminder e-mail about TWS on boron planning on monday (colindixon, 18:02:27)
    10. edwarnicke (edwarnicke, 18:02:55)
    11. LuisGomez (LuisGomez, 18:03:12)
    12. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 18:04:54)
    13. 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:05:14)

  2. events (colindixon, 18:06:11)
    1. https://www.opendaylight.org/global-events (colindixon, 18:06:25)
    2. https://www.opendaylight.org/events/2016-01-31-000000-2016-02-01-000000/open-networking-india-symposium-2016 open networking india sunday/monday of this week phrobb will be there (colindixon, 18:06:51)
    3. https://www.opendaylight.org/events/2016-02-15-000000-2016-02-19-000000/cisco-live-berlin Cisco Live Berlin, phrobb and ChrisPriceAB will be on a panel there (colindixon, 18:07:05)
    4. https://www.opendaylight.org/events/2016-02-29-000000-2016-03-01-000000/opendaylight-developer-design-forum develper design forum 2/29 and 3/1, you can submit ideas and topics there if you want, there will be some unconference (colindixon, 18:07:30)
    5. many other events upcoming (colindixon, 18:08:02)
    6. notifications about the acceptances to ONS should be going out over the next bit, PC meetings should be over on Friday, some acceptances have already gone out (colindixon, 18:08:38)
    7. CFP for OpenStack closes on Monday (2/1) submit NOW (colindixon, 18:09:14)
    8. there is a mini-summit going on at ONS, there's CFP open now, having 6-8 slots, it will happen on Monday, 3/14, please submit now, you should have an e-mail, deadline is a week from Friday (colindixon, 18:10:36)
    9. there will be ONOS, ODL, and OPNFV mini-summits at least (colindixon, 18:10:48)
    10. LuisGomez expresses concern about the density of events and attending, e.g., both the dev design forum and the mini-summit at ONS (colindixon, 18:11:24)
    11. ACTION: phrobb will make sure the mini-summit is on the events page (colindixon, 18:11:45)

  3. boron (colindixon, 18:12:41)
    1. zxiiro says there are patches to switch to JDK8 for building. some projectss still need to do that (colindixon, 18:13:11)
    2. rovarga says there are also a bunch of patches to move to equinox 3.9, please merge those too (colindixon, 18:13:28)
    3. https://git.opendaylight.org/gerrit/#/q/status:open+project:releng/builder+branch:master+topic:jdk8only jdk8 patches (zxiiro, 18:13:52)
    4. equinox upgrade: https://git.opendaylight.org/gerrit/#/q/topic:java8equinox (rovarga, 18:14:31)
    5. ACTION: colindixon to bring up jdk8 and equinox next week so see if we're tracking (colindixon, 18:14:33)
    6. https://git.opendaylight.org/gerrit/#/q/topic:java8equinox (rovarga, 18:14:39)

  4. beryllium (colindixon, 18:14:46)
    1. we've had isseus with tests in RC0 and nearly no projects reported system test results (colindixon, 18:15:05)
    2. anipbu will be more aggresive to report things for RC1 to make sure we get better data (colindixon, 18:15:21)
    3. anipbu notes that build time for beryllium autorelease has gone up, zxiiro is investigating, on 1/21 it took 7 hours to build, on 1/22 it went up to 11 hours (colindixon, 18:16:00)
    4. zxiiro asks anyone who might know why, to let him know (colindixon, 18:16:09)
    5. there were some issues with merging the fix to BUG4295, but they've been fixed now (colindixon, 18:16:28)
    6. https://wiki.opendaylight.org/view/Weather#Current_Weather_Report (colindixon, 18:17:15)
    7. anipbu says that there are some blocker bugs in Beryllium, anipbu has reached out to ask if they're actually blockers, if they'll be fixed, and/or if they can be downgraded (colindixon, 18:17:40)

  5. system integration and test (colindixon, 18:18:04)
    1. projects please, Please, PLEASE report system test status for RC1 (colindixon, 18:18:18)

  6. infrastructure (colindixon, 18:18:38)
    1. we've had issues with dead ports and how quickly we can reap them, they are now running that script every 4 hours now, that should help (colindixon, 18:18:50)

  7. Group Based Poilcy graduation review (colindixon, 18:19:23)
    1. https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Mature_Project_Proposal GBP Mature Project graduation proposal (alagalah, 18:19:39)
    2. one highlight is cooperating with SFC which was the first peer-to-peer example of that according LuisGomez (colindixon, 18:21:03)
    3. colindixon goes through what's on the proposal and comments briefly, it all seems to look good to him (colindixon, 18:24:23)
    4. mohnish_ asks how far they are into the boron planning and how much churn/change we can expect (colindixon, 18:24:48)
    5. alagalah says there's at least four tnew things they want to do, he's going to europe tomorrow to help scope those out internally and then bring it forward later (colindixon, 18:25:21)
    6. vrpolak notes some parts of BGP+SFC demo are running as CSIT jobs, for example https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-6node-all-stable-lithium/ (colindixon, 18:25:51)
    7. alagalah says in GBP (and perhaps more broadly) we don't tend to give people informaiton about things past the next release, that information might be useful for the AG (colindixon, 18:26:21)
    8. these are all good examples of projects cooperation that we want to see more going forward. (LuisGomez, 18:26:39)
    9. VOTE: Voted on "shall the TSC move the Group Based Policy project to mature?" Results are, +1: 6 (colindixon, 18:28:39)
    10. note that edwarnicke also votes +1 (colindixon, 18:28:40)
    11. AGREED: the Group Based Policy project is now a mature project in OpenDaylight (colindixon, 18:29:08)

  8. committer promotions on OVSDB (colindixon, 18:29:51)
    1. https://lists.opendaylight.org/pipermail/ovsdb-dev/2016-January/002472.html Vishal Thapar as committer on OVSDB (colindixon, 18:30:01)
    2. https://lists.opendaylight.org/pipermail/ovsdb-dev/2016-January/002470.html Stephen Kitt as OVSDB Committer (colindixon, 18:30:18)
    3. https://git.opendaylight.org/gerrit/#/q/project:ovsdb+owner:%22Stephen+Kitt+%253Cskitt%2540redhat.com%253E%22+status:merged merged patches from Stephen in OVSDB (colindixon, 18:30:50)
    4. https://git.opendaylight.org/gerrit/#/q/project:ovsdb+status:merged+owner:%22Vishal+Thapar+%253Cvishal.thapar%2540ericsson.com%253E%22 meged patches from Vishal in OVSDB (colindixon, 18:31:36)
    5. VOTE: Voted on "shall the TSC move Stephen Kitt to being a committer on OVSDB?" Results are, +1: 6 (colindixon, 18:32:52)
    6. ChrisPriceAB also votes +1 (colindixon, 18:33:00)
    7. VOTE: Voted on "shall the TSC move Vishal to being a comitter on OVSDB?" Results are, +1: 7 (colindixon, 18:33:42)
    8. AGREED: both Stephen Kitt and Vishal Thapar are now committers on OVSDB (colindixon, 18:34:00)

  9. OpenFlow plugin graduation reviews (colindixon, 18:35:50)
    1. colindixon asks if we're ready to review this given the current situation (colindixon, 18:36:00)
    2. abhijitkumbhare says sure, rovarga says he's worried about the current situation and without a plan it's hard to endorse the project as mature (colindixon, 18:36:32)
    3. ChrisPriceAB says that he feels like we have a plan and so, he's OK proceding with the discussion (colindixon, 18:37:00)
    4. dfarrell07 is concerned about flux in OFPlugin, would expect a more stable design from a Mature project (dfarrell07, 18:37:08)
    5. rovarga notes that there was a failure of communcation to figure out how how and when projects could migration, abhijitkumbhare says the plan has always been to migrate people in boron, it was people that hadn't asked migrating to the LIthium plugin that caused issues (colindixon, 18:37:49)
    6. LuisGomez says his take was that the release committments were met by the OpenFlow plugin (colindixon, 18:39:12)
    7. rovarga notes that it's not that he doesn't feel that this review shouldn't happen, but he'd like to understand what the plan is to go forward (colindixon, 18:40:31)
    8. dfarrell07 also expects Mature projects to communicate during the Mature Release Process very well, isn't sure the design changes were up to that quality standard (dfarrell07, 18:40:32)
    9. hideyuki notes at the begining of the Beyrllium, we (VTN project) had a conversation with OFP project guys about the plan of the bouth OFP-Lithium and OFP-Helium. And, at that time, we heard that they were going to work on both plugins for Beryllium (colindixon, 18:40:46)
    10. phrobb note that in the release plan does not note needing to move between features (colindixon, 18:41:44)
    11. dfarrell07 is concerned about lack of docs about this change (which seems to be an API change) in Be release plan, isn't sure that's "following the Mature Release process" (dfarrell07, 18:43:30)
    12. phrobb also notes that there are no API changes, but there were actually some API changes for the new plugin (colindixon, 18:43:40)
    13. ChrisPriceAB notes that if the plan was always to deliver both, then there wasn't an API change in Beryllium, just two versions with compatibility concerns (colindixon, 18:46:11)
    14. colindixon notes that actually vishnoianil (and the broader openflowplugin team) did manage to fix the old design to ensure that it worked for everyone in the release to avoid delaying or blocking the release, while it was ugly, in the end they dealt with the hardship (colindixon, 18:46:51)
    15. abhijitkumbhare says that they do plan to move to one implementation in boron (colindixon, 18:47:18)
    16. colindixon asks if there are APIs that need to be deprecated NOW so that they could be removed in Boron (would we allow that) (colindixon, 18:47:55)
    17. https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Graduation_Proposal (colindixon, 18:48:40)
    18. mohnish_ says as it stands in Beryllium, no project is using the new plugin by default, so that does ask about what "working code base" means in this context if the plan is to move to the new design (colindixon, 18:50:31)
    19. dfarrell07 and rovarga think the point of 'following the mature release process' is making sure the need for end-of-release heroics is virtually eliminated (dfarrell07, 18:50:38)
    20. dfarrell07 notes that he's on the record (TSC mailing list) as arguing for a more expansive interpretation of "following the Mature Release process" (dfarrell07, 18:55:31)
    21. as written, I don't think the governance makes any distinctions among offset-0,1,2 (edwarnicke, 18:59:25)
    22. VOTE: Voted on "shall the TSC move the OpenFlow Plugin project to mature?" Results are, 0: 2, +1: 3, -1: 2 (colindixon, 19:04:58)
    23. at least for now the resolution fails, there are several people who would like more information and might change there vote (notably edwarnicke mohnish_) (colindixon, 19:05:32)
    24. abhijitkumbhare asks when openflowplugin could come back to ask again, dfarrell07 says he'd like to see people come back after the Boron release (colindixon, 19:07:16)
    25. colindixon says he doesn't think there are mechanics that stop you from coming back to ask for another vote immediataly (colindixon, 19:09:00)
    26. colindixon, edwarnicke, dfarrell07 and others say there's another part that is when the TSC would feel like it would make sense (colindixon, 19:09:31)
    27. rovarga says maybe right after the Beryllum release would be another option (colindixon, 19:09:46)
    28. I meant after next Release Review (which is Beryllium at this moment) (rovarga, 19:10:26)
    29. colindixon throws out Be-SR1 as another target (colindixon, 19:10:43)
    30. jmedved says all of those sounded like good candidates (colindixon, 19:10:53)

  10. cookies (colindixon, 19:11:00)
    1. I do not thinkk SR1 has Releaseds Reviews (rovarga, 19:11:00)
    2. rovarga is correct only at formal release (colindixon, 19:11:20)


Meeting ended at 19:11:23 UTC (full logs).

Action items

  1. colindixon to keep boron planning on our minds
  2. colindixon to send a reminder e-mail about TWS on boron planning on monday
  3. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  4. colindixon to follow this issue to figure out lessons learned and how to avoid the two diffenent openflow plugin in the future
  5. phrobb will make sure the mini-summit is on the events page
  6. colindixon to bring up jdk8 and equinox next week so see if we're tracking


Action items, by person

  1. colindixon
    1. colindixon to keep boron planning on our minds
    2. colindixon to send a reminder e-mail about TWS on boron planning on monday
    3. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    4. colindixon to follow this issue to figure out lessons learned and how to avoid the two diffenent openflow plugin in the future
    5. colindixon to bring up jdk8 and equinox next week so see if we're tracking
  2. phrobb
    1. phrobb will make sure the mini-summit is on the events page


People present (lines said)

  1. colindixon (98)
  2. odl_meetbot (23)
  3. dfarrell07 (16)
  4. ChrisPriceAB (10)
  5. LuisGomez (9)
  6. edwarnicke (7)
  7. mohnish_ (7)
  8. rovarga (6)
  9. jmedved (6)
  10. alagalah (4)
  11. Prem_ (2)
  12. abhijitkumbhare (2)
  13. ttkacik1 (1)
  14. vrpolak (1)
  15. anipbu (1)
  16. zxiiro (1)
  17. shague (1)
  18. hideyuki (1)
  19. jamoluhrsen (1)
  20. phrobb (0)
  21. phrobb- (0)


Generated by MeetBot 0.1.4.