Versions Compared

Old Version 1

changes.mady.by.user Al Morton

Saved on

compared with

New Version Current

changes.mady.by.user David McBride

Saved on

Key

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

Table of Contents

Date

26 May  

Attendees

...

Absent

Absent

Non TSC Attendees

Non TSC Attendees

  • Add as needed

...

Agenda items

TimeItemPresenterNotes

...

5 min

Meeting Logistics

05
26

Al Morton


3 min

Announcements

  •  
Linux Foundation Insights presentation from Weekly Technical Discuss meeting - presentation and minutes Future topic
cases 
  • cases.  Bottlenecks' Stress test spawns VMs till it breaks in OVP
  •  Future topic: XTesting as a project - graduation or formalisation of it.  We don't want it to be similar to the Test DB where we lost maintainers.
  •  ETSI Plugtest https://www.etsi.org/events/1683-nfv-mec-plugtests is  .  Do we want to try to run any XTesting/Functest there against any of the VIMs that will be present?
Al Morton
Shubhra Kar

5 min

Virtual Event Planning (June 22-25)

  •  Volunteer for Project reviews at the Round-Robin (~20 min each)
  • Project proposal submission page - Deadline   <<<<<<<Tomorrow !!!!!!
  • Any Sessions on Tactical Issue discussions within OPNFV ?? 
  • keep total time in mind - 

    • Jack Morgan

    Action add/check the Joint topics

    OPNFV TSC Meeting - need slot

    Release Meeting

      • looking for projects to participate in this proposal
    •  Registration for the Virtual Event - Registration Link

    Unknown User (jentoio)




    20
    5
    min

    OPNFV Release Process

    •  What does OPNFV WANT from the next Release?
    •  Next Steps: finish this discussion at tech discuss on  
      • Continue Using Release meeting time slot to discuss the new Release PROCESS - key stakeholders should join.
      • Capture IMPROVEMENTS to proposed process
      • Release meetings
    will resume 02
      • continue  

    David McBride

    Need review at least for Marketing messages (possible vote) weeks in advance

    Agenda update on Monday - after Weekly Tech Discuss meeting

    10 min

    OPNFV Project Reviews

    •  Projects:
    TBD

      • ovn4nvf at future meeting
      • sampleVNF
    re-incarnates as RAPID?

    Note: Request for project reviews to be scheduled, if not, archive on  :   yardstick, container4nfv, clover, bottlenecks, rocket, edgecloud

    #Agree to Archive projects that have not reviewed or scheduled: yardstick, container4nfv, clover, bottlenecks, rocket, edgecloud

    Jim Baker

      • : Status  Development Continues, Need to Update Committer List and elect new PTL

    Jim Baker Al Morton

    ACTION to schedule ovp4nfv

    5

    ACTION to schedule ovp4nvf and sampleVNF

    yardstick and bottlenecks used in OVP, a small # of tests, but important need to send the message archived 

    0
    min

    What more do we want from Program Management?

    •  Contract PM support for limited time - potential elements:
  • Help create procedures/bridges to other communities (e.g. CNTT)
  • wiki cleanup - needs community participation
  • calendar/zoom audit and sync

    • Jim Baker


    10 min

    CNTT Engagement  – Current Item

    •  CNTT Future Mode of Operation
    Mode
    • meetings have begun, with clear decision criteria and data-driven decision-making.
      • Deadline is September, in time to make a recommendation to the GB.
      • Discuss current status - CNTT
    FOM

    Al Morton
    Jim Baker Scot Steele Unknown User (scott.steinbrueck)

    		Pre-meeting notes: Need OPNFV Views on this, not so much like OS community to have RACI, "OPNFV" entry needs more detail, we need to work together better, maybe make OPNFV's version of this chart.
    10 minOVP Engagement (standing topic)

    2 min

    CNTT Engagement  – Future Work Items

    •  Reference Infrastructure and Reference Conformance work with CNTT
      • Beyond CNTT's Terms of Reference (Scope), license issue is not a big risk for the amount of code in CNTT docs.
    •  Review OPNFV's overall process to respond to CNTT Requirements
      • CNTT Requirements have been revised - Release was
      • Need revised assessment:
      • Test Identification
      • Ref Instantiation and automation of deployment and testing
      • Badging
    •  

      TSC Review of Staffing Proposal to CNTT plus Field Trial Testing Plan and Staffing

      • CNTT discussions? other updates??
      • Input from OPNFV New Release Process meeting (virtual event,  ) 
        • Release plans can use template of project work items, duration and skills needed.
        • Negotiate between projects and requirement stakeholders - TSC facilitates
    •  

      CIRV Mandate Review

      • Mark Beierl has looked at the Common Infrastructure Realization & Validation (CIRV) Home page and its mandate and believes that there is a disconnect between what the project started out doing and what it is currently doing.
      • TSC agreed there is as an opportunity to improve  
      • On  Weekly Tech Discussion Agenda
    •  OPNFV 2.0 Actions: Work Progress Page and Agreements Capture Page
      • CNTT in OPNFV Update (Qiao Fu  )
        • CIRV Project relationship - Interactions on the basis of WIKI updates

    Al Morton
    Jim Baker


    2 min

    Status Updates

    Jack Morgan

    Unknown User (jentoio)
    Trevor Bramwell

    Downtime needed: might not be able to login between 1700 and 2100 UTCTimeItemWhoNotesMinutes




    Outstanding Action Items

    Task report
    spacesmeetings
    pageSize10
    labelstsc-meeting

    Minutes

    Logistics

    • Minutes

    ...

    • approved
    • Quorum reached

    Announcements

    • One more week to nominate TSC Chair
    • No nominations received so far
    • No representation for Plugtest as it is now too late
    • Xtesting cannot be separated from Functest

    Virtual Event Planning

    • No actions

    Release Process

    • Concern was expressed over the role of PTLs in the requirements part of release planning process
    • PTLs would have veto authority over requirements
    • This is a 'release of releases', is independent of project's release process or cadence
    • Need to have a formal agreement of the proposal so we can move forward with itTranscribe here with highlights from the Discussion Items

    Action items

    •