...
- This project will deliver a unified set of VNF Guidelines and Requirements.
- The VNF Guidelines and Requirements must be versioned to enable evolution based on operational experience
- The VNF Guidelines and Requirements will support the ONAP Architecture Principles.
- Identify a list of features and functionality will be developed.
- The VNF Guidelines and Requirements will support the Release 1 Use Cases.
- Use cases focused on VNF Requirements may be developed in this project, and they will need to be aligned with the ETE Platform use cases.
- It will be incorporating and integrating the source material on VNF Guidelines and Requirements from OPEN-O and ECOMP in Release 1
- VNF Guidelines and Requirements are to be refined beyond prototype text (e.g. through EPIC statements, use cases) to deliver test cases and test procedures for us in VNF onboarding & validation. VNF Requirement level use cases to be aligned with ETE platform use cases
- Identify what is in or out of scope. During the development phase, it helps reduce discussion.
- VNF Guidelines may be forward looking, or include best practices in VNF design and VNF lifecycle processes.
- VNF Requirements from ONAP APIs should be linked to the ONAP Release
- VNF Requirements may include:
- expected operational characteristics ( e.g. security, resilience, upgradeability)
- conditional requirements (e.g. When configured for deployment on High Availability Network Cloud Infrastructure, the VNF Shall …)
...
- What other ONAP projects does this project depend on?
- SDN-C (for API requirements on VNFs)
- APPC (for VNF configuration requirements)
- VF-C (for VNF life cycle managment and configuration)
- Service Design & Creation (for VNF onboarding)
- DCAE (for VNF reporting requirements)
- Authentication and authorization Framework (for VNF Security Requirements)
- Modeling (for Tosca Data Modeling for VNF)
- Multi-VIM/ MultiCloud (for network cloud infrastructure requirements)
- What other projects depend on this project?
- VNF SDK
- VNF tooling should support the development and packaging of VNFs that are conformant to the VNF Requirements
- VNF Validation program (ICE)
- VNF Validation should be traceable against the VNF Requirements
- Documentation
- References to deliverables produced by this project may be included in various ONAP release documents maintained through the documentation project
- Reference VNFs (now Integration Project)
- Reference VNFs should be VNF Requirement compliant. The Integration Project maintaining those Reference VNFS would be dependent on the VNF Requirements for validating compliance.
- How does this align with external standards/specifications?
- External specifications of APIs/Interfaces or Information/data models to be referenced where applicable
- Are there dependencies with other open source projects?
- OPEN-O (Mercury release)
- OpenECOMP
- OpenStack (Network Cloud Infrastructure Requirements)
...
- Primary Contact Person Steven Wright (AT&T) sw3588@att.com
- Names, gerrit IDs, and company affiliations of the committers
- Steven Wright sw3588@att.com (AT&T)
- Wenyao Guan guanwenyao@chinamobile.com (China Mobile)
- Andrei Kojukhov andreik@amdocs.com (Amdocs)
- Shitao Li lishitao@huawei.com (Huawei)
- Yuanxing Feng feng.yuanxing@zte.com.cn (ZTE)
- Herb Patten hp1256@att.com (AT&T)
- Ying Li liyingyjy@chinamobile.com (China Mobile)
- Names and affiliations of any other contributors
- Ryan Hallahan Hallahan rh173x@att.com (AT&T)
- Scott Blandford cb1694@att.com (AT&T)Herb Patten hp1256@att.com Blandford cb1694@att.com (AT&T)
- Fari Behi Behi fb2634@att.com (AT&T)
- Alan Weinstock Weinstock aw2574@att.com (AT&T)
- Andrei Kojukhov andreik@amdocs.com (Amdocs)
- Suresh Babu Nekkalapudi snekkalapudi@vmware.com (VMWARE)
- Chengli Wang wangchengli@chinamobile.com (China Mobile)
- Yan Yang yangyanyj@chinamobile.com (China Mobile)Jing Li liyingyjy@chinamobile.com (China Mobile)
- Gary Wu, gary.i.wu@huawei.com (Huawei)
- Hui Deng denghui12@huawei.com (Huawei)
- Nagesha Subramanya nagesha.subramanya@nokia.com (NOKIA)Jamil Chawki
- Tamas Varhegyi tamas.varhegyi@nokia.com (NOKIA)
- Jamil Chawki jamil.chawki@orange.com (Orange)
- Munir Ahmad Ahmad munir.ahmad@bell.ca (Bell Canada)
- Marc-Alexandre Choquette m.a.choquette@bell.ca (Bell Canada)
- Yuanxing Feng feng.yuanxing@zteMaopeng Zhang zhang.maopeng1@zte.com.cn (ZTE)
- Maopeng Zhang zhang.maopeng1@zte.com.cn
- Alex Vul alex.vul@intelAlex Vul alex.vul@intel.com (Intel)
- Gershon Schatzberg gershon.schatzberg@intel.com (intel)
- Linda Horn linda.horn@nokia.com (NOKIA)
- Marge Hillis marge.hillis@nokia.com (IntelNOKIA)
- Project Roles (include RACI chart, if applicable)
...
- Seed Code / documentation
- VNF Guidelines for Network Cloud and OpenECOMP,
- VNF Management Requirements for OpenECOMP,
- VNF Management Requirements for Open-O
- VNF Cloud Readiness Requirements for OpenECOMP,
- VNF Heat template Requirements for OpenECOMP
- VNF TOSCA Template Requirements for Open-O
- Vendor Neutral YES
- Meets Board policy (including IPR) YES
...
Project Name:
- JIRA project name: VNF Requirements
- JIRA project prefix: vnfrqts
Repo name: : ( all under https://gerrit.onap.org)
- vnfrqts/guidelines
- vnfrqts/requirements
- vnfrqts/epics
- vnfrqts/usecases
- vnfrqts/testcases
...
Wenyao Guan guanwenyao@chinamobile.com (China Mobile)Yuanxing Feng
feng.yuanxing@zteAndrei Kojukhov andreik@amdocs.com.cn (ZTEAmdocs)
*Link to TSC approval:
Link to approval of additional submitters: