Page History

R2 planning

• How should we structure sub-projects and corresponding leads
• Review Beijing VNF SDK User Stories, features and fixes (and assign owners)
• Start creating user stories for the epics (and add/change epics, as needed)

Notes from last meeting:

Chris presenting the current R2 feature set.

Sonar will be used to measure the code quality and code coverage for Java source code.

Wenyao: Feature/Function Testing as a sub-project in R2. We brought the framework in from Open-O. Is this the test framework for a VNF? There is a robot framework. It can inject some data. Functional testing of VNFs should not be in scope (Brian). Andrei believes ONAP should do some level of non-functional testing, but in a separate project such as VVP.

Andrei: Should we start creating a user story based on what we described as basics security features of ETSI SOL004 in our backlog?

Discussion happened around VNF inside versus outside testing (e.g., internal/inside testing of virus checking). Some VNFs will be encrypted.

Alex would like to add this item: VNF Templates built to describe VNFs. Could use what SDC was using. Enhance it with the 1.1/1.2 YAML grammar.

We should explicitly invite ALL VNF Suppliers to review the project scope and features for R2.

Team agrees with the 5 items listed on the R2 planning page. See action items below.

VES Collector R2 Resource Needs:

VM needs 2 or more CPUs, 2-4 GB RAM, 50 GB HDD.

Check latest schedule.