Minutes

OVP 2019.12

• Expecting a submission for the first TOSCA VNF soon.

OVP 2020.r1 Release

• Still aiming for an OVP release in the September time-frame.

• ONAP VNF Testing Status

  • Frankfurt Go/No-Go should be called on Thursday, June 11.

  • Testing was already included, so it will be ready for the inclusion in the 2020.r1 release.

  • @Kanag  to confirm if the TOSCA tests have been updated and included in the Frankfurt release.

• CNTT RC-1 NFVI Testing Status

  • Trial testing is ramping up, using the RI-1 deployment (Intel Pods)

  • Mirantis is participating in the trial testing as a commercial vendor

  • VMware (OpenStack Integrated) is still in the planning phase, but hoping to participate

  • Orange is also testing on their OpenStack Implementation in their deployment / lab

  • Scot Steele from AT&T is heading up these activities

• Portal Updates

  • Existing portal will require updates to support the evolution of the OVP releases

  • Currently, there are no developers focused on the portal from the community

  • Working on developing a set of requirements for the portal, including work flow and how new releases are added, etc.

  • To support the program, we can make a proposal to the board to allocate some budget to contract the development effort for the portal.

  • Questions:

    • How will the project / work be managed, i.e. where would the contract developer report up to?

    • Outcome of the development would become open source contribution to xyz?  Dovetail, new project, etc?

    • Longer term support or additional of new features "down the road?"

OVP Maintenance

• OPNFV TSC has has officially archived the OPNFV projects Yardstick and Bottlenecks on June 2, 2020.  Both project are used by the Dovetail NFVI testing, per the below list.

  • OVP 2018.01: -> 8 HA test cases (Yardstick)

  • OVP 2018.09: -> 10 HA test cases (Yardstick), 1 stress test (Bottlenecks)

  • OVP 2019.12: -> 10 HA test cases (Yardstick), 1 stress test (Bottlenecks)

• The OVP test tooling still continues to work, allowing OVP to remain active. However, no support for the aforementioned test cases can be expected.

• How should the OVP releases deal with this situation? 

  • Should older releases of OVP be removed from "in-force," where a company could not submit devices to that release after a specific date?

• Is CNTT including these requirements in their RC-1 requirements?  

  • Are they using other projects?

  • https://wiki.opnfv.org/pages/viewpage.action?pageId=54919245

• Will move this discussion into the upcoming virtual event CVC sessions.

Cloud Native Subcommittee Update

• Tests from CNCF Conformance Group could be used as input to the badge

  • Could develop a "profile" or similar as a way to select a subset of test cases for the badge

  • They have agreed testing should be aligned with the program and CNTT

June LFN Virtual Event Plan

• Proposed Sessions:

  • Plenary - OVP Status and Evolution

  • Plenary - Cooperative exploration between open source and standards regarding testing

  • OPNFV - Performance Testing: CNTT RC and OVP2.0 Performance Testing Requirements

  • CNTT - Where performance is relevant to CNTT

    • Would be ideal if this could be scheduled before the "OPNFV - Performance Testing" topic

  • OPNFV - OVP 2.0 Cloud Native Operator Panel

Any other business

• June 22 CVC meeting will be cancelled in favor of the June virtual event.