2020-05-04 Meeting notes

Date

May 4, 2020

Attendees

LF Staff: @Heather Kirksey @Jim Baker
Committee Members: @Ryan Hallahan @Rabi Abdel @Trevor Lovett @Trevor Cooper @Kanag  @Marc Price  @bill.mulligan  @Olivier Smith @Yan Yang   (I was not able to capture full attendance as I was sharing material, please feel free to update as needed)
Proxies:
Guests:

Minutes

Announced Results of CVC and CNOVP Election Results

  • CVC Chair - @Lincoln Lavoie

  • CVC Co-Chair - @Yan Yang

  • CNOVP Subcommitte Lead - @Trevor Lovett

  • CNOVP Subcommitt Co-Lead - @Rabi Abdel

Continued Review of WS02 Findings 

  • Material updated based on F2F observations (material)

  • Discussion Regarding Key Decisions from April F2F (NOTE: items in italics are quotes from the material)

    • "CNTT’s RA-2 will be the location and hub for CNF Requirements"

      • RA-2 can still refer to requirements and specifications outside of RA-2 (ex: CNCF Tug work), but the thought is it would be the hub

      • Desire for CNF requirements to be hosted in a LFN project (if even indirectly)

      • Some concerns raised that CNTT focus has been solely on infrastructure vs. true CNF requirements (ex: Cloud Nativeness)

      • This means RA-2 can not point back to the Ref Model for CNF requirements.

      • Action Item: @Trevor Lovett & @Rabi Abdel Need to confirm the scope and types of requirements that RA-2 will include and if lack of traceability to RM is a concern to be solved

    • "NFVi Performance Testing will move out of the badging program, and move to a benchmarking initiative"

      • Conformance with performance requirements may be needed in the future

      • Creating the requirements at this time may not be achievable

      • Focus would be on establishing a benchmarking initiative to standardize how benchmarking of the NFVI would be performed (example: what would be measured, what tools used, approved labs, etc.)

      • OVP can play a valuable role in specifying how this benchmarking program would work even if we don't start with badging

      • Benchmarking may evolve to explicit conformance requirements in the future

      • Need a team focused on defining how this would work, tools to be used, and what is needed from the various project

      • Proposal is to create a workstream to focus on this, but need volunteers

    • "Performance testing of CNFs should be out of scope for OVP"

      • Felt this may not be out of long term scope of OVP, but is out of scope for MVP.

      • Statement will be revised to be specific to the MVP.

    • Only made it through 3 bullets.

Action items

@Trevor Lovett  & @Rabi Abdel confirm the scope and types of requirements that RA-2 will include and if lack of traceability to RM is a concern to be solved
All - Volunteer for Performance Benchmarking workstream