...
- 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.
- 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 C (for VNF life cycle managment and configuration)
- SDC Service Design & Creation (for VNF onboarding)
- DCAE (for VNF reporting requirements)
- Authentication Authentication and authorization Framework (for VNF Security Requirements)
- Modeling Modeling (for Tosca Data Modeling for VNF)
- 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 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)
...