OPNFV TSC Meeting 2020-08-04

Welcome TSC for 2020-2021 !!

• Who are we? (Introductions)
• Who we are!
• How we Work: 1 hour TSC meeting per week, augmented by weekly Technical Discussion meetings, off-line Voting on Wiki with comment periods, e-mail discussions.
• Vacation Planning: Quorum Requirements, Proxy allocation policy
  

I expect more from TSC members than from the previous year: Showing-up at the TSC meeting once a week or voting on issues is just the beginning.

We need TSC members who are willing to volunteer to lead activities and participate in sub-committees to accomplish an important goal.

For anyone who participates outside the TSC meetings, that would mean reading the minutes, participating in off-line discussions and volunteering for the OPNFV activities that the TSC has agreed its members must lead.

I hope that you are all willing to affirm your active TSC membership: it’s not the same TSC anymore!

Yardstick HA Tests: Four tests result in restoration with outages more that twice the SLA (5 seconds). These are the API restoration/response results.

• Other implementations have passed these SLAs, BUT this is a trade-off between stability and restoration time. Recommendation is to include the Quantitative results as part of any statement on Exceptions (this is indicative of the general problem with threshold applicability).

vping tests: Additional log files show that the vping tests have passed (different from the log file on the Dovetail portal site).

• Would like to know the specific reasons for failure –  but Functest versions can’t be run at the moment – vacation.

Bottlenecks Stress Tests: Bottlenecks Log file shows PASS, Dovetail Log file shows FAIL.

• Apparent Dovetail issue.

Partial list of issues discussed:

1. Project Candidates: RI-2 Instantiation, VSPERF, Airship, Prox/SampleVNF, CIRV, would participate in Integration testing, need to talk about others.
2. Are the Definitions of Gates clear?
   
   1. Testing of the CNTT-selected RC Test Cases
   2.  projects must pass Gating (s 17)
   3. Gates need to be established, install without errors, simple functional tests, success of more advanced features and automated with X-testing
3. Pre-requisites, include Integration TEST project (Morgan in ONAP), test what OPNFV delivers.
4. OPNFV needs to Release and Support tests that are reliable.
   1. "Establish" items are the key steps for TSC: Requirements Vetting and Integration Test SCs

• OPNFV 2.0 on hold during CNTT FMO discussion

OVP Engagement status update

• Performance testing discussion status update
  
• RC-2 and OVP 2.0 discussions

• VDTF Session on Performance testing with OVP 2.0 went well
• Representation needed at bi-weekly CVC meeting - see notes page for more info
• current page (same as above?)

• new template concept is on hold

• OPNFV Project Reviews - schedule review for ovp4nfv