Scratchpad for El Alto planning. Add unprioritized backlog items and user stories here. We will discuss collectively during VNFSDK team meetings.
Release 5 Mission:
Highlights:
- Finish the Vulnerability issue fix.
- Enhance the security about VNFSDK docker( like remove JDWP port, enable HTTPS in OOM deployment and daily Job)
- Support LCM Testing for LFN MVP working group
- Refine the PNF Onboarding/Pre-Onboarding for 5G Use Case
- VNFSDK VTP enhancement for profile and artifacts that inherit the capability from CLI.
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
- VES V7.0 C++ Implementation
- TOSCA Grammar Validation
- Integrate VNFSDK into CI/CD Tool Chain
Other potential considerations? (from Casablanca)
- 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