Scratch pad for Casablanca planning. Add unprioritized backlog items and user stories here. We will discuss collectively during VNFSDK team meetings.
Release 3 Mission:
Simplify the process of developing and onboarding VNFs. Expand ONAP's VNF ecosystem through compliance testing.
Highlights:
- Enhance dovetail integration so we can use it in LFN Compliance/Verification testing
- Improvements to function test for better integration into the framework
- Incorporate vnfreqs testable requirements
- consistent support for HEAT/TOSCA VNFs (as defined in VNFReqs) - may not be 100% common
- modular marketplace framework to make it easier to plug in tests (maybe configurable per application such as compliance testing, operator-vendor engagement, 3rd party enhancements, etc.)
- 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?)
- VES: multivim enhancements
- HPA, SOL-004 certificate, and other carry-over items
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?
- 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