Logistics

What needs to be put on the R2 backlog for HPA (e.g., epics and stories). Need to ultimately build the template.

Alex has defined the tuples that would go into the list in the template. This needs to be reviewed by all interested parties.

Need community support in creating these templates.

Lack of clarity in what SDC will ingest for HPA from VNF SDK. Should have a follow up discussion and review the flow diagrams. There is no plan to do HPA inside of HEAT templates. SDC would work on TOSCA templates only. VNF's expressed as HEAT templates would be translated into TOSCA as part of VNF SDK toolkit. This has a downstream affect, for example on SO. vCPE use case should be updated to support TOSCA templates. This needs discussed ASAP. What about the Resource Orchestrator (David)? SDC currently supports both template types.

From VNF SDK, we need to know what needs done (e.g., pure TOSCA model?) Need a one time conversion for HEAT VNFs.

Should ONAP formally deprecate HEAT templates in R2 or R3? Or continue to support HEAT? It makes more sense to create a migration plan and a hard cutover date for ONAP supporting TOSCA templates only. This should be brought up to the TSC.

Items to be discussed and/or resolved:

Should VNF SDK project take over the License Builder User Interface currently in SDC

Once SDC on-boards the VNF, the VNFD should not be modified with SP extensions. This can be added as meta-data. (Alex & Andrei)

Has the VVP project agreed to take on the new VEVP functionality? This needs discussed within the project team for R2.

How does APP-C integrate with SDC?

(Paul) How can vendors add data such as Ansible playbooks/Chef Cookbooks (and APP-C Template). Should APP-C integrate with VVP (VEVP) to accomplish this? Testing needs to be done for this. You need an ONAP Self Serve test environment. The APP-C UI is used to configure the playbook. This should be part of SDC as part of the design studio. Are these playbooks part of the VNF Package placed in the Marketplace? Alex mentioned a white paper written on this topic using NETCONF/YANG as a case study for VNF configuration/testing. Need to specify what artifacts we are supporting. Security needs to be concern around trusted sources (VNF itself and for Ansible Server). AT&T did a security risk assessment, and raised some items. Should these be brought to the Security Subcommittee? Who covers Ansible within the boundaries of ONAP? Start with Jason Hunt and new Software Architecture sub-team.

Alex raised the concern that TOSCA (templates, simple YAML 1.2) items need resolved ASAP. How can we reuse the Amsterdam code for validation? We need to make sure we have the right things in the Info Model. This needs nailed down by Jan 8.

We need to schedule a meeting between SDC, VVP and VNFSDK. First week of January?

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)
• JIRA Epics

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.