Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Non TSC Attendees

  • Add as needed

...

TimeItemWhoNotes
5 min

Meeting Admin


5 min

Announcements

  •  Fall Technical Event - Not the same week as ONES!
    • Start Oct 13 or 14, run 3 days with less time each day
    • Topic Submission Status????
    • Volunteers to represent OPNFV in event:
    • Lincoln Lavoie and Sridhar Rao will represent us
  •  Volunteer(s) needed to run the OPNFV Weekly Technical Discussion meetings: ASAP - rotating chairs, see right-hand column

Sept - Sridhar Rao

Oct - Emma Foley

Nov -

Dec -


10 min
  •  Docker image retention policy
    • Weekly Tech Discuss IRC minutes
    • The rate of Pulls may be the biggest problem,
    • collect data for most active projects,
    • inform TAC and LF IT to deal with this issue LFN-wide.

 Tech Discuss meeting

5 min
  •  TAC Feedback
Al Morton
5 min

OPNFV Release Process

  •  Status
    • Requirements Work Group using the Release meeting time
      • THIS WEEK we focus on performance and telemetry requirements
      • determine the make-up of the JERMA Release
      • Need PTL Participation
    • Key conclusions so far, regarding JERMA and CNTT Baldy
      • Security requirements being revised (out of JERMA scope)
      • Functional tests will refer to CNTT RC-1 for requirements
      • Testing in other areas must reach past RC-1 to RA-1 in order to help CNTT stakeholders.
    • Documentation: Jerma Requirements Working Group Assessment
    • Overhauling OPNFV Docs Sofia Wallin
    • Meeting Logistics
  •  Self-Release Naming: Use of OPNFV Release names in the future.

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



10 min

CNTT Engagement status updates


10 min
  •  2021 Budget
  • Need to know requirements for coming year
  • Marketing and HW buckets, CAPEX, LF Staffing
  • SLIDES !!  Like last year, increase or decrease, or just right!
  • #agree ???
10 Min
  •  Recording for the purpose of audio transcript only. (defer to  )

DEFER  

5 min

OVP Engagement status update

  •  Performance testing discussion status update
  •  RC-2 and OVP 2.0 discussions
    • Performance terms adopted in terminology (no acceptance thresholds)
  • 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?)
  • General acceptance at CVC meeting but need to prusue RC-2 adoption of latest text.
2 min

OPNFV Project Reviews

  •  Projects:
    • ovn4nfv at future meeting

Trevor Cooper Project code being used in Akraino and another project. PTL not responding. Some interest in moving the repo to Akraino

10 min

Status Updates

  •  OPNFV Linux Foundation Lab (Portland) hardware upgrade status
  •  LF IT/Infra update: (Aric GardnerTrevor Bramwell)

5 min

Future Topics

  •  Future Topic: new template for staffing task & requirement evaluation - similar to Intern projects Mark Beierl
  •  Future Topic: Yardstick's future??  HA test cases.  Bottlenecks' Stress test spawns VMs till it breaks in OVP

  • new template concept is on hold

...