#opendaylight-meeting: tsc

Meeting started by colindixon at 17:59:19 UTC (full logs).

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:59:29)
    1. regXboi (irc so far) (regXboi, 18:00:21)
    2. https://wiki.opendaylight.org/view/TSC:Main#Agenda the agenda in the usual place (colindixon, 18:00:40)
    3. regXboi (the audio half now) (regXboi, 18:00:58)
    4. kwatsen (kwatsen, 18:01:23)
    5. jmedved (jmedved, 18:03:07)
    6. colindixon (colindixon, 18:03:17)
    7. edwarnicke (edwarnicke, 18:03:26)
    8. LuisGomez (LuisGomez, 18:03:31)
    9. ACTION: gzhao and edwarnicke to continue to work on getting Lithium auto-build to work (colindixon, 18:03:38)
    10. ACTION: phrobb to start email thread on dates/times/activities for hackfest and integration-togetherness (colindixon, 18:03:52)
    11. opinion: regXboi +1s the concept of a distributed hackfest (regXboi, 18:05:26)
    12. the action from dlenrow, mohnish and mlemay to work on gathering and acrhiving use cases, I will assume that they’ll let us know when they want more time on the TSC (colindixon, 18:05:36)
    13. Youcef Laribi (Youcef, 18:05:37)
    14. Chris Wright (cdub, 18:05:40)
    15. ACTION: mlemay to Investigate usage of repotool manifest for inter-repo + tags management with zxiiro (colindixon, 18:06:29)
    16. mohnish (mohnish, 18:06:48)
    17. ACTION: colindixon to put together pieces for the Helium-SR1 release (colindixon, 18:06:49)

  2. Canceling Upcoming TSC Meetings (tbachman, 18:07:05)
    1. https://wiki.opendaylight.org/view/OpenDaylight_Controller:Pulling,_Hacking,_and_Pushing_the_Code_from_the_CLI For alagalah action item (alagalah_, 18:07:30)
    2. colindixon sent email to the list to cancel TSC meetings over the Thanksgiving, Christmas, and New Year breaks (tbachman, 18:08:19)
    3. AGREED: TSC Meetings on Thanksgiving, Christmas, and New Years are all cancelled (phrobb, 18:08:46)

  3. Updates (tbachman, 18:08:48)
    1. phrobb says that there’s nothing new on the board elections, but reminds committers to feel free to join the non-profit and vote (tbachman, 18:09:25)
    2. Board election closes November 18th (tbachman, 18:09:45)
    3. currently there are 30/142 committers that have signed up (tbachman, 18:09:59)
    4. https://wiki.opendaylight.org/view/Committer_Members_Board_Representation (cdub, 18:10:32)
    5. https://wiki.opendaylight.org/view/Committer_Members_Board_Representation wiki detailing ODL committer board (dfarrell07, 18:10:36)
    6. https://linuxfoundation.echosign.com/public/hostedForm?formid=AI3XA256U2H44Y (alagalah_, 18:10:55)
    7. colindixon asks TSC members to reach out to committers to encourage signing up (tbachman, 18:10:59)
    8. chris price (is late) (ChrisPriceAB, 18:11:04)
    9. phrobb says that there are no large events in near future; looking at events for the new year (tbachman, 18:12:49)
    10. phrobb says ODL Summit Call For Papers is anticipated to open in January (edwarnicke, 18:13:12)
    11. phrobb say ODL Summit Call for Papers likely to close in Feb (edwarnicke, 18:13:30)
    12. jmedved asks if we have release notes for stable/helum (tbachman, 18:14:13)
    13. stable/helium isn’t currently building, due to outstanding patches (tbachman, 18:14:50)
    14. https://docs.google.com/spreadsheets/d/1PYxjiSYEks44uJByVO1P44rnI5xTJRulpKyrSsDQF9g/edit#gid=383947003 Spreadsheet for tracking stable/helium (tbachman, 18:15:13)
    15. https://docs.google.com/spreadsheets/d/1TRYposNDFPaKcySlvwkOXvfR6Anx2EFujlIjoTthhRY/edit#gid=829479065 (gzhao, 18:15:28)
    16. dlenrow (dlenrow, 18:15:53)
    17. LuisGomez asks how we can improve our process/automation around release/version-bump because there is 2 weeks of disruption currently when doing this (phrobb, 18:17:12)
    18. tykeal says that the hope is that the autorelease job set will do the tagging, etc. automatically (tbachman, 18:17:18)
    19. right now there’s a bit of “hand-crafting” to do version bumping due to project dependencies (tbachman, 18:18:09)

  4. Infrastructure (phrobb, 18:20:02)
    1. tykeal says that all silos are now in rackspace (tbachman, 18:20:05)
    2. congratulations to tykeal for getting all the silos into rackspace (edwarnicke, 18:20:16)
    3. gerrit didn’t get moved into rackspace last week, but that will be worked on tomorrow evening, with email sent to the list (tbachman, 18:20:33)
    4. tykeal says that all projects should be publishing to jenkins email list, rather than having this done per-project (tbachman, 18:21:33)
    5. tykeal says for projects that have dedicated jenkins email aliases, he will inject ~2 weeks a notification that the list will be decommissioned, and will remove the lists in January. (tbachman, 18:22:21)
    6. AGREED: baring any unforseen reasons, the project specific bug/jenkins/gerrit mailing lists will be decommissioned in January (phrobb, 18:24:17)

  5. Creation Review for SXP Project (tbachman, 18:24:46)
    1. https://wiki.opendaylight.org/view/Project_Proposals:SXP Project Proposal (tbachman, 18:25:06)
    2. https://wiki.opendaylight.org/images/5/5a/SXP_Specification_and_Architecture_v00.docx Specification and Architecture (tbachman, 18:25:48)
    3. https://wiki.opendaylight.org/images/d/d2/Sxp-odl-plugin.pdf Plugin proposal (pdf form) (tbachman, 18:26:17)
    4. the above link is the presentation that Miloslav is presenting (colindixon, 18:26:52)
    5. abhijitkumbhare asks if miroslav can describe the SXP protocol (tbachman, 18:30:05)
    6. SXP is a security protocol dedicated for delivery of security data (tbachman, 18:30:19)
    7. security data consists of security groups, with each group having multiple users registered (tbachman, 18:30:41)
    8. it delivers IP address bindings to security groups (tbachman, 18:30:59)
    9. The attached router/switch advertises these security bindings into the network (tbachman, 18:31:18)
    10. https://datatracker.ietf.org/doc/draft-smith-kandula-sxp/ (edwarnicke, 18:31:33)
    11. This will be something similar to BGP route reflection (tbachman, 18:31:34)
    12. devices can then act on this security information (tbachman, 18:32:14)
    13. jmedved says this would be very useful as a renderer in groupbasedpolicy (tbachman, 18:32:38)
    14. colindixon asks how this would relate to opflex (tbachman, 18:32:44)
    15. jmedved says this doesn’t relate to opflex, but could be one of the renderers used in groupbasedpolicy (tbachman, 18:33:00)
    16. jmedved this just implements the protocol and the bindings database (tbachman, 18:33:34)
    17. LuisGomez asks if there will be REST APIs to connect this (tbachman, 18:34:58)
    18. colindixon notes that since there is an MD-SAL data store, the REST APIs will be present (tbachman, 18:35:14)
    19. kwatsen asks if SXP has been implemented by any other vendors than Cisco (tbachman, 18:37:37)
    20. jmedved says he’s not sure, but there is interest from academia (e.g. Rice University) (tbachman, 18:38:00)
    21. colindixon says that it should be clarified that the scope is only things related to the SXP protocol (tbachman, 18:38:45)
    22. colindixon notes that there’s only a single committer on the intial committer list, and asks if that’s intentional? (tbachman, 18:39:16)
    23. miroslav says that there are 4 committers, but they are working out the details (tbachman, 18:39:52)
    24. regXboi and colindixon say it’s much easier to approve if there’s a full list of committers (tbachman, 18:40:46)
    25. edwarnicke says he’d like to see a link to the SXP IETF draft in the proposal (tbachman, 18:41:21)
    26. colindixon says there is a link to the IETF draft in the proposal (tbachman, 18:41:40)
    27. ACTION: miroslav to clarfiy the scope of the SXP proposal, add link to IETF doc-tracker, and provide full list of committers (tbachman, 18:44:49)
    28. link to datatracker is already on first line of proposal description https://wiki.opendaylight.org/view/Project_Proposals:SXP#Description (phrobb, 18:48:13)
    29. mohnish asks how you would verify the functionality (i.e. against a device)? (tbachman, 18:49:21)
    30. miroslav says this has only been tested against Cisco equipment (tbachman, 18:49:51)
    31. edwarnicke points out that with the openflowplugin, every time we test against other vendors, we run into interoperability/standardization issues (tbachman, 18:50:53)
    32. jmedved adds that there are actually committers, but they just weren’t listed in the proposal (tbachman, 18:51:22)
    33. in particular, the list of “resoruces committed” (4 people) should also be initial comitters (colindixon, 18:53:42)
    34. VOTE: Voted on "Shall the TSC approve the SXP project to the Incubation state within OpenDaylight provisional to adding the full list of initial committers and the scope to be made clear as tied to the SXP protocol, and a trademark name search being satisfactorily completed?" Results are, +1: 9 (phrobb, 18:56:33)
    35. kwatsen expresses concern about project proliferation for protocols that are only supported by a single vendor (tbachman, 18:57:38)
    36. note that the above vote was to merely move the 4 resources committed to also be initial committers, not a blank check for initial committers (colindixon, 18:57:42)
    37. cdub agrees, and says that odlforge could help here, but this all requires wider discussion (tbachman, 18:58:19)

  6. Code Maturity and Lifecycle Issues (tbachman, 18:58:35)
  7. Summer Intern Program (tbachman, 18:59:53)
    1. phrobb says that Summer Interns lock down their plans right around the end of the calendar year (tbachman, 19:01:39)
    2. ODL needs to start coming up with projects/topics, and identifying mentors for the program (tbachman, 19:02:39)
    3. The program would start May 19th, and end about the 3rd week of August (tbachman, 19:02:54)
    4. colindixon asks if there’s a wiki page for the program this year? (tbachman, 19:04:34)
    5. phrobb says he’ll be working on the wiki page this week (tbachman, 19:04:43)
    6. ACTION: phrobb will create a wiki page by next week’s TSC meeting where we can put projects and mentors (colindixon, 19:04:55)

  8. Certificate Authorities (tbachman, 19:06:56)
    1. jmedved says when you try doing builds from the MAC and pulling artifacts from nexus, it requires certificates (tbachman, 19:07:51)
    2. jmedved says that you need to manually install the certificates into your JDK/JVM, as the manuals on startcom are insufficient, and not as widespread as other certificate authorities (tbachman, 19:08:28)
    3. jmedved asks if we can use a more wider known certificate authority for our nexus? (tbachman, 19:08:45)
    4. jmedved says this is a MAC-specific problem (but hasn’t tried windows — works on Linux) (tbachman, 19:09:16)
    5. tykeal says that he as an admin has no ability to change the certificate authority that the LF uses (tbachman, 19:10:11)
    6. ACTION: phrobb and tykeal to work with the LF staff to identify this as a problem that the LF has and start to investigate alternatives (i.e. raise this as a potential problem) (tbachman, 19:10:53)
    7. the issue is that downloading the archetype index, it points you to https (tbachman, 19:13:06)
    8. rovarga asks if this is an issue with the JVM distributed by apple (tbachman, 19:13:59)
    9. ACTION: rovarga, jmedved, edwarnicke, tykeal, and phrobb will work on finding solution (colindixon, 19:15:54)

  9. Progress on Technical Debt and pom files (tbachman, 19:16:50)
    1. https://wiki.opendaylight.org/view/CrossProject:HouseKeeping_Best_Practices_Group:Project_layout (rovarga, 19:17:22)
    2. rovarga says that the idea is to introduce a general best practices for both project layout and what stuff goes into which pom file and why (tbachman, 19:18:27)
    3. The current wiki page provided in the link is WIP (tbachman, 19:19:20)
    4. colindixon says that the pom changes will facilitate version bumping between releases (tbachman, 19:20:38)
    5. ACTION: rovarga to email alagalah to do a TWS on this topic (tbachman, 19:22:01)

  10. Code Maturity and Lifecycle Issues (tbachman, 19:22:44)
    1. colindixon asks if we’re willing to have principals on things such as how long we’ll support releases (tbachman, 19:23:25)
    2. colindixon would also like to discuss ODLForge (tbachman, 19:23:37)
    3. colindixon would also like to discuss the project promotion process (tbachman, 19:23:59)

  11. ODLForge (tbachman, 19:24:49)
    1. https://pad.opendaylight.org/public/odlforge -- etherpad high-level ideas around ODLForge (tykeal, 19:25:04)
    2. cdub says it would be beneficial to have a space to do collaborative development to bring developers into the fold for the purpose of building up a project (tbachman, 19:25:25)
    3. cdub feels that many of the projects proposals are too empty, and that having code might help here (tbachman, 19:25:46)
    4. regXboi asks how are we talking about changing the project review process (tbachman, 19:27:36)
    5. cdub ODLForge and project reviews don’t have to be coupled (tbachman, 19:27:55)
    6. ACTION: regXboi to attempt to not be human (regXboi, 19:28:58)
    7. regXboi doubts he'll be able to succeed in that action items (regXboi, 19:29:27)
    8. tykeal says that the jenkins side would use Jenkins Job Builder as a separte silo (tbachman, 19:30:18)
    9. The projects that come in would get repositories under an ODL namespace, similar to how releng has theirs in a separate namespace (tbachman, 19:30:44)
    10. projects would be able to publish to their own place in the nexus repo (tbachman, 19:31:00)
    11. tykeal says building out that infra would make it quicker to bring new projects online (tbachman, 19:31:23)
    12. tykeal says that setting up this infra isn’t that hard (could even do by next week’s TSC) (tbachman, 19:32:22)
    13. edwarnicke asks if it would be possible to set up something separately, in order to have a clear distinction (tbachman, 19:32:59)
    14. tykeal says they’ve refused import of history from outside repos, b/c they have no way of handling identity linkage from outside entities (tbachman, 19:33:31)
    15. tykeal says that openstack also has their stackforge on their primary system (tbachman, 19:34:06)
    16. edwarnicke would like to have a clearly separated (by name — DNS) nexus server (tbachman, 19:35:41)
    17. edwarnicke would like to have the governance issues worked out, so that ODL projects don’t have dependencies on ODL Forge artifacts (tbachman, 19:36:19)
    18. https://pad.opendaylight.org/public/odlforge <-- current proposal (cdub, 19:47:46)
    19. ACTION: edwarnicke cdub tykeal and others to come up with concrete plan for next week’s TSC on how to make ODL Forge amenable to all (tbachman, 19:48:05)

  12. singularity clause (tbachman, 19:53:29)
    1. http://www.opendaylight.org/project/tsc/tsc-policy (colindixon, 19:53:36)
    2. http://en.wikipedia.org/wiki/Technological_singularity (alagalah, 19:53:38)
    3. http://blogs.westword.com/showandtell/05shark.jpg (tykeal, 19:55:40)
    4. cdub, colindixon and edwarnicke talk about how we can encourage (and later require) projects to move though the lifecycle process (colindixon, 20:00:46)


Meeting ended at 20:01:48 UTC (full logs).

Action items

  1. gzhao and edwarnicke to continue to work on getting Lithium auto-build to work
  2. phrobb to start email thread on dates/times/activities for hackfest and integration-togetherness
  3. mlemay to Investigate usage of repotool manifest for inter-repo + tags management with zxiiro
  4. colindixon to put together pieces for the Helium-SR1 release
  5. miroslav to clarfiy the scope of the SXP proposal, add link to IETF doc-tracker, and provide full list of committers
  6. phrobb will create a wiki page by next week’s TSC meeting where we can put projects and mentors
  7. phrobb and tykeal to work with the LF staff to identify this as a problem that the LF has and start to investigate alternatives (i.e. raise this as a potential problem)
  8. rovarga, jmedved, edwarnicke, tykeal, and phrobb will work on finding solution
  9. rovarga to email alagalah to do a TWS on this topic
  10. regXboi to attempt to not be human
  11. edwarnicke cdub tykeal and others to come up with concrete plan for next week’s TSC on how to make ODL Forge amenable to all


Action items, by person

  1. alagalah
    1. rovarga to email alagalah to do a TWS on this topic
  2. cdub
    1. edwarnicke cdub tykeal and others to come up with concrete plan for next week’s TSC on how to make ODL Forge amenable to all
  3. colindixon
    1. colindixon to put together pieces for the Helium-SR1 release
  4. edwarnicke
    1. gzhao and edwarnicke to continue to work on getting Lithium auto-build to work
    2. rovarga, jmedved, edwarnicke, tykeal, and phrobb will work on finding solution
    3. edwarnicke cdub tykeal and others to come up with concrete plan for next week’s TSC on how to make ODL Forge amenable to all
  5. gzhao
    1. gzhao and edwarnicke to continue to work on getting Lithium auto-build to work
  6. jmedved
    1. rovarga, jmedved, edwarnicke, tykeal, and phrobb will work on finding solution
  7. mlemay
    1. mlemay to Investigate usage of repotool manifest for inter-repo + tags management with zxiiro
  8. phrobb
    1. phrobb to start email thread on dates/times/activities for hackfest and integration-togetherness
    2. phrobb will create a wiki page by next week’s TSC meeting where we can put projects and mentors
    3. phrobb and tykeal to work with the LF staff to identify this as a problem that the LF has and start to investigate alternatives (i.e. raise this as a potential problem)
    4. rovarga, jmedved, edwarnicke, tykeal, and phrobb will work on finding solution
  9. regXboi
    1. regXboi to attempt to not be human
  10. rovarga
    1. rovarga, jmedved, edwarnicke, tykeal, and phrobb will work on finding solution
    2. rovarga to email alagalah to do a TWS on this topic
  11. tykeal
    1. phrobb and tykeal to work with the LF staff to identify this as a problem that the LF has and start to investigate alternatives (i.e. raise this as a potential problem)
    2. rovarga, jmedved, edwarnicke, tykeal, and phrobb will work on finding solution
    3. edwarnicke cdub tykeal and others to come up with concrete plan for next week’s TSC on how to make ODL Forge amenable to all


People present (lines said)

  1. tbachman (139)
  2. colindixon (30)
  3. cdub (26)
  4. edwarnicke (24)
  5. regXboi (19)
  6. odl_meetbot (15)
  7. alagalah (12)
  8. tykeal (10)
  9. phrobb (8)
  10. dfarrell07 (6)
  11. rovarga (5)
  12. alagalah_ (5)
  13. dlenrow (4)
  14. ChrisPriceAB (4)
  15. mohnish (4)
  16. gzhao (3)
  17. LuisGomez (2)
  18. kwatsen (2)
  19. Youcef (2)
  20. abhijitkumbhare (1)
  21. mlemay (1)
  22. jmedved (1)


Generated by MeetBot 0.1.4.