Table of Contents
outline true

Overview

...

VNF SDK's mission is to simplify the process of developing and onboarding VNFs and expanding ONAP's VNF ecosystem. For Service Providers, VNFSDK will reduce the time and level of testing required to identify, select, and onboard a VNF.  For vendors, VNFSDK will reduce integration efforts by defining a standard for VNF packaging with widespread operator acceptance.  VNFSDK can be used in a validation/conformance testing program in the future.

The Casablanca release will enhance existing functionality, introduce security, integrate with ONAP use-case flow and progress towards being carrier grade with high quality.

1. Enhance dovetail integration so we can use it in LFN Compliance/Verification testing
   1. Improvements to function test for better integration into the framework
2. Incorporate vnfreqs testable requirements
   1. consistent support for HEAT/TOSCA VNFs (as defined in VNFReqs) - may not be 100% common
      1. NB. HEAT tests will be developed by VVP, but may be implemented in VNFSDK for VNF Compliance Testing
3. 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.)
4. Support SDC on boarding tests (maybe allow SDC to replace refrepo portal, but use vnfmarket-be for their own onboarding test engine
5. Package data model enhancements (internal and onboarding models?)
6. VES: multivim enhancements, PNF registration, notification, and RAN metrics (5G use case)
7. Enhance HPA, SOL-004 certificate, and other carry-over items

Use Cases

1. Use VNF provider uses VNFSDK for VNF Compliance Testing
2. Support operator use of VNFSDK for vendor engagement/acceptance testing
3. 3rd Party Lab uses VNFSDK for extended VNF testing (may include functional, non-functional, and/or performance tests developed by 3rd party labs)
4. HPA
5. Enhance Security

Minimum Viable Product

Describe the MVP for this release.

...

Sub-Components

List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.

...

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

...