...
- Proposed name for the project:
VNF Guidelines and SDK & tooling - Proposed name for the repository:
vnfsdk
...
- VNF onboarding is a challenge across the industry because of the lack of a standard format for VNFs.
- This project will build an ecosystem for ONAP compatible VNFs by: publishing guidelines and requirements for VNF vendors
- developing
a packaging modeldeveloping - tools for vendor CI/CD toolchains
- developing validation and testing tools
- defining & establishing a compliance program allowing VNF providers to obtain an ONAP Compatible label.
- This project will deliver a unified set of VNF guidelines
- It will deliver automation tools for VNF product specification, packaging, publication and ingestion
- This project will also deliver a tool for:
- package validation,
- lifecycle test (framework)
- functional test (framework)
- Reference Repository for VNFs to enable CI/CD without dependency on service provider ingestion [Note: business model out of scope]
- This project will also develop an ONAP Compatible compliance program
- Program governance
- Vendor self-testing guidelines
- Third-party lab guidelines
- The functionality supplied by this project is intended for use by NFV operators, VNF product developers and VNF product DevOps teams.
Scope:
...
- Data model for VNFs
- TOSCA, Yang, and HEAT
- NFV operator tools and SDK for ingestion (download) of VNF products
- VNF Supplier DevOps tools and SDK for automated packaging and publication of VNF product releases
- A Network Function Repository (NF-RP) for publication, upload and download of VNF products and offerings
- APIs for external interactions with VNF providers
- Tooling necessary to support VNF coherence, environment and dependency checking during packaging, upload and download
Note: This project will be the result of merging all relevant tools from the Open-O VNF SDK, ICE and SDC, and of course further development of the merged entity.
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- VNF SDK is one of the functional blocks in the ONAP Architecture supporting VNF packaging
- What other ONAP projects does this project depend on?
- This project depends on SDC, SO, Modeling, DCAE, ICE, and VNF Requirements
- How does this align with external standards/specifications?
- This project aligns with TOSCA and ETSI NFV VNF models
- HEAT will follow OpenStack specification
- Are there dependencies with other open source projects?
- OPEN-O (Mercury release)
- Robot
- ARIA (parser)
- OpenStack
...