#opendaylight-meeting: tsc

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

Meeting summary

  1. agenda bashing and roll call (colindixon, 17:00:39)
    1. colindixon (colindixon, 17:00:44)
    2. https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=46153#Agenda today's agenda (colindixon, 17:00:49)
    3. Chris Price (ChrisPriceAB, 17:00:58)
    4. https://meetings.opendaylight.org/opendaylight-meeting/2016/tsc/opendaylight-meeting-tsc.2016-05-05-17.00.html last week's meeting minutes (colindixon, 17:01:00)
    5. gkaempfer (gkaempfer, 17:01:14)
    6. vishnoianil (vishnoianil, 17:02:05)
    7. edwarnicke (edwarnicke, 17:02:47)
    8. Daniel Farrell (dfarrell07, 17:03:02)
    9. abhijitkumbhare (abhijitkumbhare, 17:03:19)
    10. mohnish anumala (mohnish_, 17:03:29)
    11. ACTION: colindixon to test signing gerrit commits per tykeal's instructions (colindixon, 17:03:42)
    12. ACTION: colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron? (colindixon, 17:03:46)
    13. ACTION: colindixon to drive the MPLS-TP creation reviews to conclusion (colindixon, 17:03:53)
    14. https://lists.opendaylight.org/pipermail/release/2016-May/006524.html colindixon asked if offset 0 projects could have stable features (colindixon, 17:04:17)
    15. tony tkacik (ttkacik_mobile, 17:04:47)
    16. ACTION: dfarrell07 to drive forward tooling and planning for the next TSC election (colindixon, 17:04:50)

  2. TSC mailing list discussions and votes (colindixon, 17:06:00)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-March/004956.html MPLS-TP Service creation review (colindixon, 17:06:15)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-April/005033.html MPLS-TP Solution creation review (colindixon, 17:06:42)
    3. colindixon and vishnoianil say this might point toward eventually having nonsense words as project names (colindixon, 17:08:15)
    4. https://lists.opendaylight.org/pipermail/tsc/2016-May/005149.html split-out projects and lifecycle states (colindixon, 17:09:39)
    5. the consensus there seemed to be that split-out projects should go through a graduation review if they want to be mature, that should be copy and pasting if it's really just a mature component of the prior one (colindixon, 17:12:10)
    6. abhijitkumbhare points out that he'd like to see the rought age of the part being spinning out, that would help (colindixon, 17:12:56)
    7. ChrisPriceAB asks how committers on the new project should work (colindixon, 17:13:50)
    8. edwarnicke says his take is that people on the new project should be the people with a history of contributions on that part, and thus would be most comfortable maintaining it, that means they might be new committers, and might only contain a subset of the old ones (colindixon, 17:15:05)
    9. colindixon says in the past, he's just asked people to provide the principle and reasons behind thier committer list and then evaluate it from there (colindixon, 17:16:31)
    10. ACTION: colindixon to try to collate the notes and expectations about split-out projects and record them somewhere if we have consensus (colindixon, 17:19:14)
    11. vishnoianil asks if we could have a template for split-outs to make this easy to figure out if we need discussion or not (colindixon, 17:20:07)
    12. people note that depending what's going to change, they might have different feelings on if a split-out should be mature. colindixon notes if they weren't splitting out, this question likely wouldn't come up. (colindixon, 17:22:18)
    13. ChrisPriceAB notes that the mature state is at least as much about the team and people as well as the code. colindixon agrees and notes these two axes are the source of a lot of the problems we have. (colindixon, 17:23:06)
    14. mohnish_ asks if it would thus make sense to wait a release, or if it can really be done immediately after the split-out (colindixon, 17:23:32)
    15. abhijitkumbhare notes that his take is any project can ask for any review any time, the TSC can decline to approve it or not without needing hard rules about it (colindixon, 17:24:04)
    16. ChrisPriceAB notes that he things just saying that "if you are a mature project and you split-out a project, it may or may not be able to become a mature project based on TSC input" (colindixon, 17:27:04)
    17. edwarnicke adds he's happy with that as long as it ends with "...but it can have a combined creation review and graduation review" (colindixon, 17:27:22)

  3. events (colindixon, 17:27:24)
    1. https://www.opendaylight.org/global-events (colindixon, 17:27:37)
    2. https://lists.opendaylight.org/pipermail/tsc/2016-May/005201.html the hackfest will be 6/29-30 (colindixon, 17:28:20)
    3. https://www.opendaylight.org/events/2016-09-27-000000-2016-09-29-000000/opendaylight-summit-2016 CFP for the ODL summit closes TODAY (colindixon, 17:28:38)
    4. dfarrell07 is at the OPNFV plugfest representing ODL, going well (dfarrell07, 17:28:53)
    5. https://www.opendaylight.org/events/2016-06-21-000000/opendaylight-european-mini-summit ODL mini-summit with the OPNFV summit 6/21 (colindixon, 17:29:10)

  4. boron (colindixon, 17:29:21)
    1. ODLPARENT team is planning to merge the patch for upgrading Karaf to 3.0.6 this week or soon. (anipbu, 17:29:36)
    2. https://git.opendaylight.org/gerrit/#/c/26323/ <---- Patch to be merged for Karaf 3.0.6 (anipbu, 17:29:43)
    3. The Boron Autorelease job failed to build aaa-authz-service. We are currently working with their team to identify the root cause. (anipbu, 17:29:54)
    4. https://lists.opendaylight.org/pipermail/aaa-dev/2016-May/000919.html <--- Email Thread discussing AAA Boron Autorelease Breaking (anipbu, 17:29:58)
    5. https://jenkins.opendaylight.org/releng/view/autorelease/job/autorelease-release-boron/119/org.opendaylight.aaa$aaa-authz-service/console <--- AAA Boron Autorelease Breaking (anipbu, 17:30:02)
    6. If want to have stable features and stable distribution, we will need offset 0 projects to graduate to mature and satisfy other stable feature requirements. (anipbu, 17:30:41)
    7. anipbu asks when we need a drop-dead date for when we need to have a stable distribution (colindixon, 17:30:45)
    8. https://lists.opendaylight.org/pipermail/release/2016-May/006524.html <---- Colin's Email regarding Stables Feature in Offset 0 (anipbu, 17:30:46)
    9. https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan#Stable_and_Extended_Features <---- Boron Stable Feature Requirements (anipbu, 17:30:51)
    10. colindixon asks what a reasonable line in the sand would be for when we would need stable features to meaningfully have a stable distribution (colindixon, 17:33:19)
    11. vratko says there are lots of tests: longevity, cluster, scale, etc. (colindixon, 17:33:39)
    12. colindixon points out that he things the openflow plugin testing covers a lot of the offset 0 projects, e.g., RESTONF, MD-SAL, YANG tools, etc. (colindixon, 17:34:58)
    13. vratko points out the config subsytem probably isn't there (colindixon, 17:35:08)
    14. LuisGomez says the integration team should look at this and prepare a set of gaps (colindixon, 17:35:26)
    15. rovarga says his main concern is that the APIs have enough leeway to change behavior if need be, so that they can maintain it (colindixon, 17:35:59)
    16. ACTION: rovarga to follow up with an e-mail about his concerns about the stable feature requirements (colindixon, 17:38:16)
    17. anipbu asks if RC0 woudl be too late, colindixon says he things M5 is likely as late as we could go (colindixon, 17:38:32)
    18. dfarrell07 asks if vratko can give his opinion, vratko says M3 offset 2 is the curent line in the sand, but if we want to push it out, we could (colindixon, 17:39:02)
    19. vratko says M3 would make him happier, but M5 would be doable (colindixon, 17:39:35)
    20. ACTION: LuisGomez and Vratko to check with the integration team about finding the gaps we have in our current testing (colindixon, 17:40:24)

  5. boron documentation review subgroup (colindixon, 17:41:35)
    1. colindixon would love help reading boron docs for sanity, asks for volunteers (colindixon, 17:41:53)
    2. abhijitkumbhare and ChrisPriceAB speak up (colindixon, 17:42:02)
    3. ACTION: colindixon to send a mail about a documentation review subgroup (colindixon, 17:42:16)
    4. dfarrell07 also speaks up (colindixon, 17:42:21)
    5. it should be noted that dfarrell07 and ChrisPriceAB say that they might not have many cycles (colindixon, 17:42:46)
    6. ACTION: colindixon to send e-mail about possibly docuemntation moving readthedocs, sphinx, and ReStructuredText, as opposed to using asciidoctor, and asciidoc which have caused us some pain (colindixon, 17:46:56)
    7. ACTION: colindixon to schedule a TWS on documentation structure, toolchains and needs (colindixon, 17:52:23)
    8. rovaraga notes that his worry is less conversion than training developers and maintaining docs (colindixon, 17:54:00)
    9. colindixon notes the there is a PoC (from zxiiro) which has the getting started guide into the new format, and ane examle that pulls in the releng docs as well (colindixon, 17:55:05)
    10. ttkacik_mobile notes that we need to integration with javadocs no matter what we do (colindixon, 17:55:52)

  6. stable/beryllium (colindixon, 17:56:57)
    1. Beryllium SR2 has been approved to release: https://lists.opendaylight.org/pipermail/tsc/2016-May/005225.html (anipbu, 17:57:00)
    2. https://wiki.opendaylight.org/view/Simultaneous_Release:Beryllium_Release_Plan#Beryllium_SR2_Download <--- Download Beryllium SR2 at this Link (anipbu, 17:57:01)
    3. https://wiki.opendaylight.org/view/Simultaneous_Release/Beryllium/SR2/Status <--- Beryllium SR2 Status (anipbu, 17:57:05)
    4. https://lists.opendaylight.org/pipermail/release/2016-April/006299.html Autorelease Workflow Idea (zxiiro, 17:57:08)

  7. system integration and test (colindixon, 17:58:46)
    1. sys/int/test update is that we are removing all CSIT jobs from distribution-test (thats the job that gates our release) unless the csit jobs meet our system test expectations. this will allow for consumers to know (more easily) if the distribution is up to snuff or not. risk is we lose test coverage, but it's too unwieldy to continue as is. LuisGomez can comment further if needed. (colindixon, 17:58:56)
    2. this is basically to have a set of tests that passes with high probability without random failures, so that we can not have to have projects sign off on random test failrues every time we run a test (colindixon, 18:00:08)
    3. ACTION: jamoluhrsen to send mail about this moving of non-compliant tests out of distribution-test (colindixon, 18:00:29)

  8. infrastructure (colindixon, 18:00:59)
    1. trying to move sandbox to the private cloud, waiting on rackspace (colindixon, 18:01:34)

  9. TSC chair elections (colindixon, 18:01:39)
    1. https://lists.opendaylight.org/pipermail/tsc/2016-May/005242.html call for nominations here (colindixon, 18:01:45)

  10. cookies (colindixon, 18:02:14)


Meeting ended at 18:02:17 UTC (full logs).

Action items

  1. colindixon to test signing gerrit commits per tykeal's instructions
  2. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
  3. colindixon to drive the MPLS-TP creation reviews to conclusion
  4. dfarrell07 to drive forward tooling and planning for the next TSC election
  5. colindixon to try to collate the notes and expectations about split-out projects and record them somewhere if we have consensus
  6. rovarga to follow up with an e-mail about his concerns about the stable feature requirements
  7. LuisGomez and Vratko to check with the integration team about finding the gaps we have in our current testing
  8. colindixon to send a mail about a documentation review subgroup
  9. colindixon to send e-mail about possibly docuemntation moving readthedocs, sphinx, and ReStructuredText, as opposed to using asciidoctor, and asciidoc which have caused us some pain
  10. colindixon to schedule a TWS on documentation structure, toolchains and needs
  11. jamoluhrsen to send mail about this moving of non-compliant tests out of distribution-test


Action items, by person

  1. colindixon
    1. colindixon to test signing gerrit commits per tykeal's instructions
    2. colindixon to try to find somebody to help with documenting the general procedure for the platform upgrade to Boron?
    3. colindixon to drive the MPLS-TP creation reviews to conclusion
    4. colindixon to try to collate the notes and expectations about split-out projects and record them somewhere if we have consensus
    5. colindixon to send a mail about a documentation review subgroup
    6. colindixon to send e-mail about possibly docuemntation moving readthedocs, sphinx, and ReStructuredText, as opposed to using asciidoctor, and asciidoc which have caused us some pain
    7. colindixon to schedule a TWS on documentation structure, toolchains and needs
  2. dfarrell07
    1. dfarrell07 to drive forward tooling and planning for the next TSC election
  3. jamoluhrsen
    1. jamoluhrsen to send mail about this moving of non-compliant tests out of distribution-test
  4. LuisGomez
    1. LuisGomez and Vratko to check with the integration team about finding the gaps we have in our current testing
  5. tykeal
    1. colindixon to test signing gerrit commits per tykeal's instructions


People present (lines said)

  1. colindixon (72)
  2. anipbu (11)
  3. tykeal (5)
  4. ChrisPriceAB (5)
  5. dfarrell07 (4)
  6. abhijitkumbhare (4)
  7. edwarnicke (3)
  8. odl_meetbot (3)
  9. zxiiro (3)
  10. jamoluhrsen (2)
  11. vishnoianil (2)
  12. gkaempfer (1)
  13. LuisGomez (1)
  14. ttkacik_mobile (1)
  15. mohnish_ (1)


Generated by MeetBot 0.1.4.