Versions Compared

Version Old Version 4 New Version 5
Changes made by

Al Morton

Al Morton

Saved on

Key

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

Table of Contents

...

TimeItemPresenterNotes
5 min

Meeting Logistics

Al Morton

5 min

Announcements

Al Morton


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

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.
10 min
  •  

    CIRV Mandate Review

    • TSC feels the Common Infrastructure Realization & Validation (CIRV) Home to review its mandate and believes that there is a disconnect between what the project started out doing and what it is currently doing.
    • TSC asks for formal project review within two weeks - by 
    • Do we have a regular meeting within OPNFV?
Al MortonAction: send email request to opnfv-tech-discuss list
10 min
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  Does everyone feel they have sufficient information to proceed with the vote??

10 min

OPNFV Release Process

  •  Status up and any follow up discussion

David McBride

Issues we need to close:

  1. Can we move ahead with many non-integrated projects?
    1. Idea to release an integrated XX that is tied to CNTT
  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?



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 progress on this by early June. CNTT FMO Meeting Minutes
    • Need Status and Feedback from GB meeting

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

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

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

...