Versions Compared

Old Version 1

changes.mady.by.user Al Morton

Saved on

compared with

New Version Current

changes.mady.by.user Al Morton

Saved on

Key

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

Table of Contents

Date

 

Attendees

  • Move up from absent as needed.

...

Absent

Non TSC Attendees

...

Agenda items

TimeItemsPresenterNotes
5 min

Meeting Logistics

16
Al Morton

5 min

Announcements

Virtual Developer and Test Forum - Registration Link

Al Morton


10 min

Read-out from June Governing Board Meeting

  •  Report from last meeting
Cédric Ollivier
15 min

TSC Role and Responsibilities

  •  Review TSC Charter for clarification within the community
  •  TSC/OPNFV project review - specifically how do we address CNTT engagement
    • Where do we track CNTT requirements (or test cases required) against what projects are fulfilling them?
    • Where do we have a master plan of outstanding work?  We want to encourage new participation, but if there is no overall project plan, how do new people know what they can work on?
    • Is this master plan a feed to the release process?  Do we have a goal to pick specific items and make them actionable for the next "release"?

Al Morton

Mark Beierl

Key Points in our Mandate:

  • TSC is responsible for Technical Oversight of OPNFV projects
  • TSC can form Sub-Committees and and Working Groups
  • TSC members make contributions in many ways, and eligibility requirements reflect many dimensions.
  • The TSC charter can be changed through proposal and agreement.
  • OPNFV's Release process is established by the TSC
10 min 

1 min

CIRV Mandate Review

  • Does CIRV have a regular meeting within OPNFV?
    • Al MortonAction: send email request to opnfv-tech-discuss list

    Former user (Deleted)

    • Good session on CIRV SW verification at VDTF
    • More info needed on other aspects of CIRV
    10 min
     

    Kuberef (CNTT RI-2) project creation Summary from Weekly Technical Discuss Meeting - Georg Kunz, Trevor Cooper , draft project proposal

    ??

    Al Morton

    RI-2 workstream proposing a project in OPNFV. Next steps: proposal (link shown to the Left), open comment period. E-mail sent to OPNFV on   Consensus to create at meeting; Vote at TSC 

    23

    Does everyone feel they have sufficient information to proceed with the vote??

    Wiki Vote starts as soon as Project Proposal is complete (Today/this week).

    Avoid overlap with R*-1, especially to establish our work in this area

    10


    20 min

    OPNFV Release Process

    •  Status
    up
  • Idea to release an integrated XX that is tied to CNTT
    • and any follow up discussion
      • Vote & Poll: TSC Approval of the 2020 Release Plan - Vote/Poll Link
      • Marketing messages process updates from last weeks discussion
      • Using Release meeting time slot to discuss the Release PROCESS - key stakeholders should join
      • Please join the OPNFV Release Process 2.0 Session (Joint with CNTT)

    Al Morton

    David McBride

    Issues we need to close:

    Can we move ahead with many non-integrated projects?

    Partial list of issues discussed:

    1. Project Candidates: RI-2 Instantiation, VSPERF, Airship, Prox/SampleVNF, CIRV
    ?? are Integrated
    1. , would participate in Integration testing, need to talk about others.
    2. Can TSC create the Requirements SC or WG?  (Charter says YES)
    3. Is OPNFV Releasing a Conformance Test Suite? (traceability to CNTT) 
    4. Is this Process for the JERMA Release? (yes)
    5. Are the Definitions of
    Integrated and Non-Integrated Projects Clear
    1. Gates clear?
      1. Testing of the CNTT-selected RC Test Cases
    Integrated projects
      1.  projects must pass Gating (s 17)
      2. Gates need to be established, install without errors, simple functional tests, success of more advanced features and automated with X-testing
    ToDo/
    1. Pre-requisites, include Integration TEST project (Morgan in ONAP), test what OPNFV delivers. 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

    •  CNTT Future Mode of Operation - deadline is September, in time to make a recommendation to the Governance Board.
      • Discuss current status - CNTT team is trying to make further progress on this by early
    June
    Need
      • Any Additional Status and Feedback from GB meeting or from Virtual Event?

    Jim Baker Scot Steele

    Scot Steele to provide feedback from LFN GB meeting

    10 min

    CNTT Engagement  – Future Work Items

    Former user (Deleted)
    Jim Baker

    • OPNFV 2.0 on hold during CNTT FMO discussion
    • No update on staffing proposal
    • Field test - Orange is doing test (is good)
    • RI/RC conformance - no update
    • CNTT Requirements - engagement based on test cases
    • CIRV mandate review - can drop?
      • Yes, there does not appear to be any interest in CIRV so we can remove this from the agenda.


    2 min

    OVP Engagement status update

    •  Discuss current status - how is this impacting OPNFV?

    Jim Baker

    Al Morton

    Trevor Cooper

    • VDTF Session on Performance testing with OVP 2.0 went well
    • Representation needed at bi-weekly OPV meeting.
    2 min

    OPNFV Project Reviews

    •  Projects:
      • ovn4nvf at future meeting
      • CIRV by  

    Jim Baker


    10 min

    Status Updates

    Former user (Deleted)
    Jim Baker
    Trevor 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
    •  Report: Summary of the June GB Meeting Cédric Ollivier
    •  Recording for the purpose of audio transcript only. Mark Beierl

    • new template concept is on hold while release process is being discussed

    Outstanding Action Items

    Task report
    spacesmeetings
    pageSize10
    labelstsc-meeting

    Minutes

    • Transcribe here with highlights from the Discussion Items

    DescriptionAssigneeDate ReportedNotes
    •  Jim Baker - start offical vote for TSC chair nomination per the OPNFV charter
    Jim Baker

     


    Al Morton

     


    •  Kanag to discuss resource description with Al Morton for Dovetail X-testing
    Al Morton

     



    Minutes

    Meeting Logistics

    • Quorum Reached
    • Minutes approved

    Announcements

    Read-out from June Governing Board Meeting

    • Cédric Ollivier Provides a readout
      • OPNFV was presented as a procedure project
      • Cédric highlighted the work that is being done in OPNFV

    CIRV Mandate Review

    Kuberef (CNTT RI-2) project creation

    • Call for remaining TSC members to please vote.

    OPNFV Release Process

    • Sufficient votes to close the vote
    • David McBride Addresses concerns that the process is overly complicated
    • Presented a simplified flowchart.
    • Requirements analysis is too time consuming to work during the TSC calls, so new subcommittee/working group is being created
    • Release meeting happens in the next hour, open for people to join and participate
    • Former user (Deleted) asks when we will close the vote
    • Al Morton notes that the vote is closing today
    • David McBride notes that the deck he showed does not change the process, it was merely a clarification

    CNTT Engagement status updates

    • CNTT has access to facilities that are on loan, but this needs to be formalized and CNTT needs to land somewhere for this to continue
    • RI and RC work with CNTT is going to be removed as ongoing agenda item

    OVP Engagement status update

    • Performance testing was discussed and clarification of functional vs. performance
    • Trevor Cooper led this discussion last week at vF2F

    OPNFV Project Reviews

    • Call out to see if anyone can reach out to the projects

    Status Updates

    • Budget for 2020 has the money for updates
    • Replacing UCS in Portland lab

    New Action items

    •