#opnfv-meeting: Weekly Technical Discussion 152

Meeting started by bh526r at 13:00:48 UTC (full logs).

Meeting summary

    1. Roll Call (bh526r, 13:00:58)

  2. Roll Call (bh526r, 13:01:05)
    1. Bin Hu (bh526r, 13:01:12)
    2. Mike Fix (bh526r, 13:02:32)
    3. Dan Xu (bh526r, 13:02:39)
    4. Al Morton (bh526r, 13:02:52)
    5. Sridhar Rao (bh526r, 13:05:19)

  3. Continue to Discuss New Project Proposal CNTT-RI (bh526r, 13:07:56)
    1. https://wiki.opnfv.org/download/attachments/2925877/20190909_CNTT_RI_Proj_Proposal_OPNFV_Community_Review.pptx?version=1&modificationDate=1568084377000&api=v2 (bh526r, 13:08:14)
    2. https://wiki.opnfv.org/display/PROJ/Project+Proposals%3A+CNTT-RI (bh526r, 13:08:35)
    3. Mike summarized what has been discussed in email (bh526r, 13:08:58)
    4. One comment was about developing tools, and it was clarified that it will reuse existing test tools as much as it can, and collaborate with test projects for test tools (bh526r, 13:12:23)
    5. Most of comments are clarifications, and are clarified in email (bh526r, 13:12:58)
    6. Al also revised wiki site for those clarifications (bh526r, 13:13:18)
    7. One last comments was about project type, i.e. feature project or requirement project. (bh526r, 13:13:42)
    8. It was clarified that according to the project scope and deliverables, feature project type is more appropriate because the focus is not to close the gaps in upstream which is a byproduct of the project. (bh526r, 13:15:12)
    9. Al Morton (acmacm, 13:15:29)
    10. Sunku Ranganath (bh526r, 13:17:09)
    11. Mark Shostak (bh526r, 13:17:26)
    12. Murtuza Khan (bh526r, 13:17:39)
    13. Sridhar Rao (SRao, 13:18:22)
    14. Other comments include meeting frequency, issues handling, repo, and how to align with OPNFV releases etc. (bh526r, 13:20:45)
    15. Those comments are clarified in wiki and mailing list. Those are logistics and execution details after project is approved. (bh526r, 13:21:57)
    16. project odes not intend to join IRUYA release - fiirst RI in January (acmacm, 13:22:28)
    17. Sridhar asked since the project CNTT-RI, should it be accepted in CNTT RM Chapter 8? (bh526r, 13:24:11)
    18. Mike clarified that Chapter 8 has an Annex that gives all current test cases. New test cases will be developed from this CNTT-RI project by collaborating with other test projects. So CNTT-RI is a superset of Chapter 8. (bh526r, 13:25:20)
    19. Bin asked everyone on the meeting if we feel that all comments have been resolved in email discussion and wiki clarification, and group can achieve consensus to move forward for TSC Creation Review. (bh526r, 13:29:30)
    20. Al agreed that we can bring it to TSC. TSC may have additional comments, questions etc. during Creation Review. (bh526r, 13:30:29)
    21. All agreed that group achieved consensus to recommend this CNTT-RI project proposal for TSC Creation Review. (bh526r, 13:31:40)

  4. AOB (bh526r, 13:35:45)
    1. Mike asked that many people will travel to Antwerp next week, and most will miss Monday's meeting (bh526r, 13:37:11)
    2. All agreed that we can cancel next week's technical discussion on Monday 9/23 unless there is an urgent topic (bh526r, 13:37:49)
    3. Bin will ask community and recommend to cancel the meeting on 9/23 (bh526r, 13:38:58)
    4. Al had general questions to CNTT authors. There are performance metrics in Chapter 4. Those are describing infrastructure performance, i.e. "Internal" in Chapter 4. (bh526r, 13:43:40)
    5. Al and Mark will discuss more in Antwerp next week regarding testing performance metrics (bh526r, 13:50:56)
    6. Sridhar, PTL, will also join the discussion (bh526r, 13:52:05)
    7. No other comments and meeting adjourned (bh526r, 13:55:04)


Meeting ended at 13:55:08 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. bh526r (36)
  2. collabot` (3)
  3. acmacm (2)
  4. SRao (1)


Generated by MeetBot 0.1.4.