Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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:

User Stories


Backlog Items

  1. Enhance dovetail integration so we can use it in LFN Compliance/Verification testing
  2. 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.)
  3. Incorporate vnfreqs testable requirements
  4. Support SDC on boarding tests (maybe allow SDC to replace refrepo portal, but use vnfmarket-be for their own onboarding test engine
  5. consistent support for HEAT/TOSCA VNFs (as defined in VNFReqs) - may not be 100% common
  6. HPA, SOL-004 certificate, and other carry-over items
  7. VES: multivim enhancements
  8. 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)






  • No labels