Project Name:
- Proposed name for the project:
VNF Guidelines and SDK - Proposed name for the repository:
vnfsdk
Project description:
- VNF onboarding is a challenge across the industry because of the lack of a standard format for VNFs.
- This project will address the problem for the ecosystem by:
- publishing guidelines for VNF vendors
- developing tools for vendor CI/CD toolchains
- developing validation and testing tools
- 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 portal and tool for
- package validation,
- lifecycle test (framework)
- functional test (framework)
- Marketplace for VNFs
- The functionality supplied by this project is intended for use by NFV operators, VNF product developers and VNF product DevOps teams.
Scope:
- Unified set of VNF Guidelines incorporating those from OPEN-O and ECOMP
- Data model for VNFs
- TOSCA, Yang, and HEAT
- NFV operator tools and SDK for ingestion (download) of VNF products from the VNF marketplace
- VNF Supplier DevOps tools and SDK for automated packaging and publication of VNF product releases
- A Network Function Marketplace (NF-MP) for publication, upload and download of VNF products and offerings
- Tooling necessary to support VNF coherence, environment and dependency checking during packaging, upload and download
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
- It also interacts with ICE
- 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
Resources:
- Primary Contact Person
- Chris Donley, christopher.donley@huawei.com
- Names, gerrit IDs, and company affiliations of the committers
- Ranny Haiby, ranny.haiby@nokia.com, Nokia
- Lianhao Lu, lianhao.lu@intel.com, Intel
- Victor Gao, victor.gao@huawei.com, Huawei
- Brian Hedstrom, brian.hedstrom@oamtechnologies.com, ARM
- Zongbiao Li, lizongbiao@huawei.com, Huawei
- Stephen Wright, AT&T
- Andy Mayer, AT&T
- Amir Levy, amir@gigaspaces.com, Gigaspaces
- Names and affiliations of any other contributors
- Project Roles (include RACI chart, if applicable)
Other Information:
- link to seed code (if applicable)
- VNF SDK is included in the OPEN-O Mercury release
- Vendor Neutral
- This project is vendor neutral and open-sourced under the Apache license from the OPEN-O project
- Meets Board policy (including IPR)
- yes
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name:
- JIRA project name: vnfsdk
- JIRA project prefix: vnfsdk
Repo name:
- org.onap.vnfsdk/guidelines
- org.onap.vnfsdk/pkgtools
- org.onap.vnfsdk/validation
- org.onap.vnfsdk/lctest
- org.onap.vnfsdk/functest
- org.onap.vnfsdk/mktplace
Lifecycle State: incubation
Primary Contact: Chris Donley
Project Lead: Chris Donley
mailing list tag [vnfsdk]
Committers:
- christopher.donley@huawei.com
- ranny.haiby@nokia.com
- lianhao.lu@intel.com
- victor.gao@huawei.com
- brian.hedstrom@oamtechnologies.com
- lizongbiao@huawei.com
*Link to TSC approval:
Link to approval of additional submitters: