#opendaylight-meeting: tsc

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

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:00:18)
    1. colindixon (colindixon, 17:00:32)
    2. gkaempfer (gkaempfer, 17:00:33)
    3. rovarga for jmedved (rovarga, 17:00:58)
    4. Chris Luke (Chrisy, 17:00:59)
    5. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47673 agenda (colindixon, 17:01:00)
    6. abhijitkumbhare (abhijitkumbhare, 17:01:07)
    7. mohnish anumala (mohnish__, 17:01:13)
    8. Chrisy is here for edwarnicke (colindixon, 17:01:15)
    9. Anil Vishnoi (vishnoianil, 17:01:56)
    10. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-07-07-17.00.html last week's meeting minutes (colindixon, 17:01:58)
    11. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47673#Committer_promotion_process_for_contributors is no longer a draft per last week's meeting minutes (colindixon, 17:02:38)
    12. Jamo Luhrsen (for Daniel Farrell) (jamoluhrsen, 17:02:39)
    13. ACTION: vishnoianil, phrobb and abhijitkumbhare to schedule a meeting to discussion the project categorization, so that it can be helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope. (colindixon, 17:03:13)
    14. ACTION: phrobb to work on having a policy for how attendance to design forums works going forward with community involvement (colindixon, 17:03:22)
    15. https://lists.opendaylight.org/pipermail/tsc/2016-July/005593.html we have a revision to the ODL summit registration where you can attend the DDF without having to have a gerrit patch (colindixon, 17:04:01)
    16. https://lists.opendaylight.org/pipermail/tsc/attachments/20160714/658d5edf/attachment-0001.png (colindixon, 17:04:12)
    17. ACTION: phrobb to create a wiki page with topics for the September DDF (colindixon, 17:04:43)
    18. ACTION: skitt or colindixon to work on removing the ancient org.eclipse dependencies in controller (and elsewhere?) (colindixon, 17:04:54)
    19. ACTION: phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election (TWS?) (colindixon, 17:05:01)
    20. ACTION: colindixon and phrobb to set up a poll of committers, PTLs and TSC members to see if there's a desire to have one TSC meeting a month at an APAC-friendly time (colindixon, 17:05:29)
    21. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 17:05:49)
    22. abhijitkumbhare wants to talk about openflowplugin staffing (colindixon, 17:06:48)

  2. tsc mailing list discussion and votes (colindixon, 17:07:17)
    1. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=47673#Agenda find them here (colindixon, 17:07:33)
    2. vishnoianil asks people to please chime in on those topics (colindixon, 17:08:54)

  3. events (colindixon, 17:08:58)
    1. https://www.opendaylight.org/global-events (colindixon, 17:09:04)
    2. linuxcon japan is now in Tokyo (colindixon, 17:09:18)
    3. we are (for the first time) doing stuff around openstack days (both east on 8/23 and silicon valley 8/9) (colindixon, 17:09:58)
    4. CFP for OpenStack closed yesterday (colindixon, 17:10:20)
    5. CFP will be coming for OpenDayilght Forum India (colindixon, 17:10:51)

  4. boron (colindixon, 17:11:02)
    1. The IETF Types Migration Effort has completed successfully with 35 patches merged, 1 patch pending (atrium), and two projects with pending issues (groupbasedpolicy and topoprocessing). (anipbu, 17:11:39)
    2. https://lists.opendaylight.org/pipermail/release/2016-July/007280.html <--- Email summarizing upgrade activity (anipbu, 17:11:42)
    3. https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=778533050 <--- Tracking patch status (anipbu, 17:11:48)
    4. Discussion and concerns related to distribution size, with feedback needed from snmp4sdn, lispflowmapping, nemp, alto, capwap, usc, groupbasedpolicy, sfc, tsdr (anipbu, 17:12:09)
    5. https://lists.opendaylight.org/pipermail/release/2016-July/007248.html <--- Email thread for distribution size (anipbu, 17:12:19)
    6. Need feedback from projects regarding their documentation for Boron release: aaa, bgpcep, didm, faas, genius, natapp, nemo, neutron, next, nic, ovsdb, persistence, sdninterfaceapp, snbi, snmp4sdn, topoprocessing, usecplugin (anipbu, 17:12:38)
    7. https://lists.opendaylight.org/pipermail/release/2016-July/007282.html <--- Email thread for documentation patches (anipbu, 17:12:45)
    8. Reminder to Offset 0 projects that code freeze was two weeks ago and we are missing M5 Status from three projects: controller, infrautils, netconf (anipbu, 17:13:35)
    9. https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-July/005492.html (abhijitkumbhare, 17:14:26)
    10. https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-July/005492.html "Jozef Bacigal and Andrej Leitner will cease their work on OpenFlow project at the end of July 2016" (colindixon, 17:15:07)
    11. abhijitkumbhare mentions this as a risk—even for Boron (colindixon, 17:15:20)
    12. LuisGomez points out that these are the people who brought the new plugin in this release and know it best (colindixon, 17:15:57)
    13. ACTION: colindixon to reach out to them about whether we could at least keep them through the Boron release (colindixon, 17:16:15)
    14. the July 21st meeting of OFP will be a bug scrub, so please come if you want to contribute or pick up bugs (colindixon, 17:17:36)

  5. stable/beryllium (colindixon, 17:19:10)
    1. Autorelease Build is successful. Reminder for projects that the cutoff is in one week and half on July 24 with a release on July 28. (anipbu, 17:19:22)
    2. cutoff is in 1.5 weeks for SR3 (colindixon, 17:19:38)

  6. system integration and test (colindixon, 17:19:51)
    1. all of the boron system test has been moot starting the last week b/c of distribution size, pay attention as we get it going again now (colindixon, 17:20:18)
    2. ACTION: colindixon to follow up on distribution size issues (colindixon, 17:20:29)
    3. rovarga says unless they start pulling in more artifacts or more stuff, it should be fine for Boron (in that it stays under the 512 MB limit), but that's maybe still bad only because of size (colindixon, 17:21:34)

  7. infrastructure (colindixon, 17:22:03)
    1. there was an issue this morning where Jenkins was in shutdown mode (for reasons tykeal and zxiiro don't understand), when they fixed it, it cause a Jenkins reboot (colindixon, 17:22:54)
    2. they're investigating ways to move away from "matrix" jobs, which seem to be some source of problems (colindixon, 17:23:17)
    3. we've fixed our JJB so that we can more easily have per-project (and per-job) VM sizing, which should help some of the problems we saw in the migration to private cloud (colindixon, 17:24:12)
    4. as part of moving away from "matrix" jobs, we'll also be moving away from the maven job type in Jenkins (this will help because it hasn't been updated in >2 years, but will remove the blue bubble per "artifact" in maven jobs) (colindixon, 17:25:02)
    5. this will also speed things up by not archiving artifacts even if we tell them not to and avoiding storying md5sums of all artifacts (called fingerprints), which slows down the boot of Jenkins (colindixon, 17:25:44)
    6. Jenkins with no fingerprints takes about 2 minutes, took 10 minutes today, took 40 minutes before we migrated to the private cloud (colindixon, 17:26:24)
    7. zxiiro hopes that doing this will speed up builds and effectively giving us more resources (colindixon, 17:26:42)
    8. tykeal says, from his view, we're holding the line in the private cloud, but we are aware that we are somewhat more constrained than before (colindixon, 17:27:17)
    9. ACTION: zxiiro to create a thread outlining the planned JJB changes in infra (zxiiro, 17:27:26)
    10. tykeal is hoping (with help from rackspace) to have a way for CSIT jobs to run in the public cloud, but he can't promise (colindixon, 17:27:53)
    11. tykeal says the current theory with Nexus issues is that it's the latency to Oregon from Rackspace, they're creating a replica of the authentication in Rackspace to fix it, if not... (colindixon, 17:29:02)
    12. vishnoianil notes that we're expecting a lot more load as we move toward RCs, tykeal notes that's a bunch of the reason to look at the public cloud (colindixon, 17:31:01)
    13. ACTION: vishnoianil and anipbu to work out if and how we can poll projects about how they're doing on their timelines and how that might impact the boron release and infrastructure issues (colindixon, 17:32:24)

  8. committer promotions (colindixon, 17:33:05)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-July/005592.html Thanh Ha on Documentation (colindixon, 17:33:23)
    2. https://git.opendaylight.org/gerrit/#/q/project:docs+owner:%22Thanh+Ha+%253Cthanh.ha%2540linuxfoundation.org%253E%22+status:merged+branch:master lots of merged commits (colindixon, 17:33:41)
    3. two +1s and no -1s in 8 days (colindixon, 17:34:05)
    4. http://docs.opendaylight.org/en/latest/ he's been instrumental in getting this up and working (colindixon, 17:34:43)
    5. VOTE: Voted on "shall the TSC approve Thanh Ha as a committer on docs?" Results are, +1: 8 (colindixon, 17:35:13)
    6. AGREED: Thanh is a committer on docs (colindixon, 17:35:27)

  9. fast and/or phased release schedule in carbon (colindixon, 17:36:30)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-June/005428.html discussion (colindixon, 17:36:39)
    2. colindixon asks if we need to draw a line in the sand to incorporate fast and/or phased into Carbon? (colindixon, 17:37:33)
    3. jamoluhrsen says it feels almost too late now, there's not enough discussion to safely put it in a plan (colindixon, 17:37:59)
    4. vishnoianil points out that we need to run the pilot first and we likely can't reasonably do that before Carbon (colindixon, 17:38:33)
    5. mohnish__ agrees with vishnoianil, but asks if we know how much development time we have if we go with "fast" and have only 2 months (colindixon, 17:39:21)
    6. rovarga says that one thing that might help is if you had experimental features, which need not be tracked as part of a given release as they're worked on across releases (colindixon, 17:39:58)
    7. rovarga also notes that if people take 2-3 weeks off (which they do) during a 2-month release with only 6 weeks of coding, that can trash a release (colindixon, 17:40:45)
    8. https://lists.opendaylight.org/pipermail/tsc/2016-July/005588.html this is the "pilot" vishnoianil referenced (colindixon, 17:41:29)
    9. the idea would be to do it sometime on the side during Carbon (colindixon, 17:42:06)
    10. colindixon suggests maybe we should wait until edwarnicke comes back, but Chrisy notes he's out for 3 weeks (colindixon, 17:44:22)
    11. rovarga agrees that we don't really have any of the scripts and tooling around, and that we can't have any real hope of getting to it in Carbon (colindixon, 17:45:04)
    12. rovarga suggests having a hackfest during Carbon working on this (colindixon, 17:45:13)
    13. VOTE: Voted on "shall the TSC put together a 6-month release (like Boron) that will start shortly after Boron?" Results are (colindixon, 17:49:29)
    14. the consensus on the call (without edwarnicke) is that we really don't enough runway to make an drastic changes to the Carbon release, e.g., fast and/or phased (colindixon, 17:50:44)
    15. vishnoianil asks if we should have a parallel pilot with a few projects on a topic branch during carbon, colindixon thinks that's right (colindixon, 17:51:38)
    16. vishnoianil points out (and colindixon and phrobb agrees vehemently) that would give projects clarity that we will have a normal, 6-month release in Carbon, at the same time as giving us experience (colindixon, 17:52:10)
    17. phrobb suggests that as part of the Carbon release plan which projects would be part of the pilot and how they'd do it, e.g., topic branches (colindixon, 17:53:43)
    18. ACTION: phrobb to put out a sample Carbon release plan based on Boron, which we could then iterate on (colindixon, 17:55:21)
    19. ACTION: Chrisy to reach to to edwarnicke about fast and/phased carbon (colindixon, 17:56:35)
    20. ACTION: colindixon will try to get us to some clarity by next week's TSC call, not to rush things, but to make sure that we give projects clarity, especially new ones (colindixon, 17:58:09)
    21. VOTE: Voted on "shall the TSC commit to having the basic outline of the main Carbon release, e.g., approx length and milestones w/approx dates, by 7/28?" Results are, +1: 8 (colindixon, 18:03:26)
    22. AGREED: the TSC commits to having the basic outline of the main Carbon release, e.g., approx length and milestones w/approx dates, by 7/28 (colindixon, 18:03:50)
    23. ACTION: colindixon to bring the commitment to a outline of a Carbon release plan up on the TSC mailing list (colindixon, 18:04:16)

  10. cookies (colindixon, 18:04:22)


Meeting ended at 18:04:31 UTC (full logs).

Action items

  1. vishnoianil, phrobb and abhijitkumbhare to schedule a meeting to discussion the project categorization, so that it can be helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope.
  2. phrobb to work on having a policy for how attendance to design forums works going forward with community involvement
  3. phrobb to create a wiki page with topics for the September DDF
  4. skitt or colindixon to work on removing the ancient org.eclipse dependencies in controller (and elsewhere?)
  5. phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election (TWS?)
  6. colindixon and phrobb to set up a poll of committers, PTLs and TSC members to see if there's a desire to have one TSC meeting a month at an APAC-friendly time
  7. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  8. colindixon to reach out to them about whether we could at least keep them through the Boron release
  9. colindixon to follow up on distribution size issues
  10. zxiiro to create a thread outlining the planned JJB changes in infra
  11. vishnoianil and anipbu to work out if and how we can poll projects about how they're doing on their timelines and how that might impact the boron release and infrastructure issues
  12. phrobb to put out a sample Carbon release plan based on Boron, which we could then iterate on
  13. Chrisy to reach to to edwarnicke about fast and/phased carbon
  14. colindixon will try to get us to some clarity by next week's TSC call, not to rush things, but to make sure that we give projects clarity, especially new ones
  15. colindixon to bring the commitment to a outline of a Carbon release plan up on the TSC mailing list


Action items, by person

  1. abhijitkumbhare
    1. vishnoianil, phrobb and abhijitkumbhare to schedule a meeting to discussion the project categorization, so that it can be helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope.
  2. anipbu
    1. vishnoianil and anipbu to work out if and how we can poll projects about how they're doing on their timelines and how that might impact the boron release and infrastructure issues
  3. Chrisy
    1. Chrisy to reach to to edwarnicke about fast and/phased carbon
  4. colindixon
    1. skitt or colindixon to work on removing the ancient org.eclipse dependencies in controller (and elsewhere?)
    2. colindixon and phrobb to set up a poll of committers, PTLs and TSC members to see if there's a desire to have one TSC meeting a month at an APAC-friendly time
    3. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    4. colindixon to reach out to them about whether we could at least keep them through the Boron release
    5. colindixon to follow up on distribution size issues
    6. colindixon will try to get us to some clarity by next week's TSC call, not to rush things, but to make sure that we give projects clarity, especially new ones
    7. colindixon to bring the commitment to a outline of a Carbon release plan up on the TSC mailing list
  5. phrobb
    1. vishnoianil, phrobb and abhijitkumbhare to schedule a meeting to discussion the project categorization, so that it can be helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope.
    2. phrobb to work on having a policy for how attendance to design forums works going forward with community involvement
    3. phrobb to create a wiki page with topics for the September DDF
    4. phrobb and dfarrell07 to drive forward tooling and planning for the next TSC election (TWS?)
    5. colindixon and phrobb to set up a poll of committers, PTLs and TSC members to see if there's a desire to have one TSC meeting a month at an APAC-friendly time
    6. phrobb to put out a sample Carbon release plan based on Boron, which we could then iterate on
  6. vishnoianil
    1. vishnoianil, phrobb and abhijitkumbhare to schedule a meeting to discussion the project categorization, so that it can be helpful for users who wants to propose a project proposal and looking for all the relevant projects in that scope.
    2. vishnoianil and anipbu to work out if and how we can poll projects about how they're doing on their timelines and how that might impact the boron release and infrastructure issues
  7. zxiiro
    1. zxiiro to create a thread outlining the planned JJB changes in infra


People present (lines said)

  1. colindixon (94)
  2. odl_meetbot (16)
  3. anipbu (11)
  4. jamoluhrsen (7)
  5. abhijitkumbhare (6)
  6. rovarga (5)
  7. mohnish__ (4)
  8. Chrisy (4)
  9. vishnoianil (4)
  10. gkaempfer (3)
  11. zxiiro (1)
  12. phrobb (0)


Generated by MeetBot 0.1.4.