Scratch pad for Dublin planning. Add unprioritized backlog items and user stories here. We will discuss collectively during VNFSDK team meetings.
Release 4 Mission:
Highlights:
- Enhance VNF Testing and integrate VVP in LFN CVC
- Support PNF Onboarding/Pre-Onboarding?
- Refine VNF Test Platform(VTP)
- Incorporate vnfreqs testable requirements
- move test case from pkgtools to validation and implemented by java.
- Support SDC on boarding tests (maybe allow SDC to replace refrepo portal, but use vnfmarket-be for their own onboarding test engine
- Package data model enhancements (internal and onboarding models?)
- SOL-004 Option2 Support
User Stories
- Use VNFSDK for LFN Compliance testing (package syntax testing)
- 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
- Accept multiple models →translation to ONAP model
- Enhancements to meet use cases?
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