...
- Create and maintain VNF Requirements targeted to ONAP user audiences and the tasks they perform.For example:
- a a VNF Provider (developer) using VNF Requirements in designing, testing, and certifying a VNF for use on ONAP
- a Service Provider using VNF Requirements as prototype text for RFPs to acquire VNFs to run in an ONAP context
- This project This project will build an ecosystem for ONAP compatible VNFs by publishing guidelines and requirements:
- For For VNF vendors across the VNF lifecycle
- For the VNF Packages at acquisition time
- For the For the VNF validation and testing tools at onboarding timetime
- For the VNF functionality common to all VNFs at Service Design time
- For the VNF functionality common to all VNFs during Service Operation.
- Including VNF functionality considering vendor VNF CI/CD tool chains
- Including VNF functionality considering in service ONAP and network cloud CI/CD tool chains
- Including requirements and processes considering VNF validation and testing tools and processes
- For service providers to use as prototype text for RFPs such that
- the guidelines and requirement are individually numbered for tracking purposes e.g.
- to assess the degree of compliance by a VNF
- to assess the degree of compliance in VNF onboarding testing & validation programs
- This project will develop the VNF test cases and procedures for use in the VNF validation program
Scope:
- 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 incorporating 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
- 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 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 …)
...
- How does this project fit into the rest of the ONAP Architecture?
- Please Please Include architecture diagram if possible
- What other What other ONAP projects does this project depend on?
- SDN-C (for API requirements on VNFs)
- APPC (for VNF configuration configuration requirements)
- SDC (for VNF onboarding)
- DCAE (for VNF reporting requirements)
- Authentication and authorization Framework (for VNF Security Requirements)
- What What other projects depend on this project?
- VNF SDK
- VNF VNF tooling should support the development and packaging of VNFs that are are conformant to the VNF Requirements
- Requirements
- VNF VNF Validation program (ICE)
- VNF VNF Validation should be traceable traceable against the VNF Requirements
- Requirements
- Documentation
- References References to deliverables produced by this project may be included in various ONAP release documents maintained through the documentation project
- Reference Reference VNFs (now Integration Integration Project)
- Reference Reference VNFs should be VNF Requirement compliant. The Integration Project 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)
...