13:00:48 <bh526r> #startmeeting Weekly Technical Discussion 152
13:00:48 <collabot`> Meeting started Mon Sep 16 13:00:48 2019 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:48 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:00:48 <collabot`> The meeting name has been set to 'weekly_technical_discussion_152'
13:00:58 <bh526r> #info Roll Call
13:01:05 <bh526r> #topic Roll Call
13:01:12 <bh526r> #info Bin Hu
13:02:32 <bh526r> #info Mike Fix
13:02:39 <bh526r> #info Dan Xu
13:02:52 <bh526r> #info Al Morton
13:05:19 <bh526r> #info Sridhar Rao
13:07:56 <bh526r> #topic Continue to Discuss New Project Proposal CNTT-RI
13:08:14 <bh526r> #link https://wiki.opnfv.org/download/attachments/2925877/20190909_CNTT_RI_Proj_Proposal_OPNFV_Community_Review.pptx?version=1&modificationDate=1568084377000&api=v2
13:08:35 <bh526r> #link https://wiki.opnfv.org/display/PROJ/Project+Proposals%3A+CNTT-RI
13:08:58 <bh526r> #info Mike summarized what has been discussed in email
13:12:23 <bh526r> #info 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
13:12:58 <bh526r> #info Most of comments are clarifications, and are clarified in email
13:13:18 <bh526r> #info Al also revised wiki site for those clarifications
13:13:42 <bh526r> #info One last comments was about project type, i.e. feature project or requirement project.
13:15:12 <bh526r> #info 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.
13:15:29 <acmacm> #info Al Morton
13:17:09 <bh526r> #info Sunku Ranganath
13:17:26 <bh526r> #info Mark Shostak
13:17:39 <bh526r> #info Murtuza Khan
13:18:22 <SRao> #info Sridhar Rao
13:20:45 <bh526r> #info Other comments include meeting frequency, issues handling, repo, and how to align with OPNFV releases etc.
13:21:57 <bh526r> #info Those comments are clarified in wiki and mailing list. Those are logistics and execution details after project is approved.
13:22:28 <acmacm> #info project odes not intend to join IRUYA release - fiirst RI in January
13:24:11 <bh526r> #info Sridhar asked since the project CNTT-RI, should it be accepted in CNTT RM Chapter 8?
13:25:20 <bh526r> #info 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.
13:29:30 <bh526r> #info 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.
13:30:29 <bh526r> #info Al agreed that we can bring it to TSC. TSC may have additional comments, questions etc. during Creation Review.
13:31:40 <bh526r> #info All agreed that group achieved consensus to recommend this CNTT-RI project proposal for TSC Creation Review.
13:35:45 <bh526r> #topic AOB
13:37:11 <bh526r> #info Mike asked that many people will travel to Antwerp next week, and most will miss Monday's meeting
13:37:49 <bh526r> #info All agreed that we can cancel next week's technical discussion on Monday 9/23 unless there is an urgent topic
13:38:58 <bh526r> #info Bin will ask community and recommend to cancel the meeting on 9/23
13:43:40 <bh526r> #info 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.
13:50:56 <bh526r> #info Al and Mark will discuss more in Antwerp next week regarding testing performance metrics
13:52:05 <bh526r> #info Sridhar, PTL, will also join the discussion
13:55:04 <bh526r> #info No other comments and meeting adjourned
13:55:08 <bh526r> #endmeeting