VNF SDK Frankfurt Backlog & User Stories

Scratchpad for Frankfurt planning.  Add unprioritized backlog items and user stories here. We will discuss collectively during VNFSDK team meetings.

Release 6 Mission:

Highlights:

• Support LCM Testing for LFN MVP working group and Badging
• Enhancement of VNF SDK VNF Test Platform Portal 
• Better integration with SDC
• VES Agent enhancement  & docs update
• PNF Usecase support 
• ETSI Standard Alignment support 
• CVC/CNTT/OVP support 
• HPA
• Python 3 / Java 11 Migration

User Stories

• Use VNFSDK for LFN Validtion testing (package syntax testing)
• The operator uses VNFSDK for vendor engagement/acceptance testing (includes onboarding testing and/or operator-developed tests)
• 3rd party lab uses VNFSDK for extended VNF testing (may include functional, non-functional, and/or  performance testing - tests developed by 3rd party labs)

Backlog Items

1. VES V7.0 C++ Implementation
2. TOSCA Grammar Validation
3. Integrate VNFSDK into CI/CD Tool Chain
4. Pkgtools: upgrade the python version from python2 to python3.? need more information from community.  VNFSDK-419 - Getting issue details... STATUS
5. pkgtools: support new SOL004 spec, v2.6.1 (could target for Frankfurt)  VNFSDK-420 - Getting issue details... STATUS
6. OVP VNF onboard testing:  test for HPA grammar & schema validation (target for Frankfurt)  VNFSDK-421 - Getting issue details... STATUS

Other potential considerations? 

• PNF onboarding support
• generic netconf server module for VNFs?
• K8s VNFs?
• HEAT→TOSCA migration tool?
• Image management/distribution (image upload to deploy VNFs)
  • quarantine area
  • separate from what happens after onboarding
  • includes model changes
  • encryption?
• Data model changes (boot disk, HPA format clarification, (deployment flavor support))
• Security (discuss with SEC and ARC)
• Support ONAP extensions in VNF descriptor