| Note |
|---|
The ONAP TSC has approved the VNF SDK project proposal page v.61. Any changes made after version v.61 are not approved by the TSC. |
Project Name:
- Proposed name for the project:
VNF SDK & tooling - Proposed name for the repository:
vnfsdk
...
yellow dotted lines = VNF SDK scope
green dotted lines = VNF Requirements project Charter project [out of scope for VNF SDK]
blue dotted lines = ONAP VNF Validation project Approved VVP Project Proposal: VNF Validation Program (ONAP ICE) (5/30/17) [validation project out of scope; tools will be informed by validation requirements]
...
- 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
- functional test framework (functional tests are initially out of scope)
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.
Relationship to other VNF projects
This project is closely related to, and will work closely with, two separate projects:
- Approved VVP Project Proposal: VNF Validation Program (ONAP ICE) (5/30/17), responsible for developing a validation program to provide assurance of VNF interoperability with ONAP. It will document governance and processes.
- VNF Requirements Charter, responsible for documenting VNF guidelines and requirements. It will produce requirements documents.
VNF SDK will produce code in the form of packaging and test tools, a test framework and a reference repository/marketplace.
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, VNF Validation Program, 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
...
- Primary Contact Person
- Chris Donley, christopher.donley@huawei.com
- Names, gerrit IDs, and company affiliations of the committers
- Chris Donley, christopher.donley@huawei.com, Huawei
- Lianhao Lu, lianhao.lu@intel.com, Intel
- Victor Gao, victor.gao@huawei.com, Huawei
- Zongbiao Li, lizongbiao@huawei.com, Huawei
- Murali P, murali.p@huawei.com, Huawei
- Andy Mayer, am803u@att.com, AT&T
- Amir Levy, amir@gigaspaces.com, Gigaspaces
- Alex Vul, alex.vul@intel.com, Intel
- Chengli Wang, wangchengli@chinamobile.com, China Mobile
- Erik Sundelof, es4410@att.com, AT&T
- Ting Lu, tl2062@att.com, AT&T
- Fari Behi, fb2634@att.com, AT&T
- Wenyao Guan, guanwenyao@chinamobile.com, China Mobile
- Michael Brenner, michael@gigaspaces.com
- Names and affiliations of any other contributors
- Stephen Gooch, stephen.gooch@windriver.com, Wind River
- Eddy Raineri, eddy.raineri@windriver.com, Wind River
- Eric Debeau, eric.debeau@orange.com, Orange
- Helen Chen, helen.chen@huawei.com, Huawei
- Gary Wu, gary.i.wu@huawei.com, Huawei
- Oleg Kaplan, amdocs
- Trevor Cooper, trevor.cooper@intel.com, Intel
- Brian Hedstrom, brian.hedstrom@oamtechnologies.com, ARM
- Thinh Nguyenphu, thinh.nguyenphu@nokia.com, Nokia
- Zhaoxing Meng mail meng.zhaoxing1@zte.com.cn Company ZTE
- Huabing Zhao mail zhao.huabing@zte.com.cn Company ZTE
- Zygmunt Lozinski, zygmunt_lozinski@uk.ibm.com, IBM
- Don Levy, dl2378@att.com, AT&T
- Amy Zwarico, az9121@att.com, AT&T
- Suresh Nekkalapudi, snekkalapudi@vmware.com, VMWare
- Gershon Schatzberg, gershon.schatzberg@intel.com, Intel
- Ranny Haiby, ranny.haiby@nokia.com, Nokia
- maopeng zhang, zhang.maopeng1@zte.com.cn, ZTE
- Dave(Wei) Chen wei.d.chen@intel.com, Intel
- Steven Wright, sw3588@att.com, AT&T
- Andrei Kojukhov, andreik@amdocs.com, Amdocs
- Yang Xu, yang.xu3@huawei.com, Huawei
- Bruce Thompson, brucet@cisco.com, Cisco
- John Strassner, john.sc.strassner@huawei.com, Huawei (gerrit id strazzie123)
- Joe Zhang, zhang.zhou1@zte.com.cn, ZTE
- Xin Lu luxin7@huawei.com
- Zhong Quan quanzhong@huawei.com
- Dileep Ranganathan dileep.ranganathan@intel.com, Intel
- feng yuanxing feng.yuanxing@zte.com.cn
- Mickael Jezequel, mickael.jezequel@orange.com, Orange
- Project Roles (include RACI chart, if applicable)
...
- link to seed code (if applicable)
- VNF SDK is included in the OPEN-O Mercury release
- This project will also include seed code from ECOMP ICE, which is not yet available online.
- 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
...
Repo name:
- org.onap.vnfsdk/guidelinesmodel
- This repository stores VNF data models
- org.onap.vnfsdk/modelpkgtools
- This repository contains vendor CI/CD vnf packaging tools.
- org.onap.vnfsdk/validation
- This repository is used for vnf validation tools
- org.onap.vnfsdk/lctest
- This repository is for VNF lifecycle tests
- org.onap.vnfsdk/functest
- This repository is for the functional test framework
- org.onap.vnfsdk/refrepo
- This repository is for a reference vnf repository. It is the same as the OPEN-O marketplace repo.
- org.onap.vnfsdk/compliance
- This repository is for the compliance test framework.
Lifecycle State: incubation
Primary Contact: Chris Donley
Project Lead: Chris Donley
mailing list tag [vnfsdk]
Committers:
...