This is an old revision of the document!
An Integration & Testing project category
The first release of the OPNFV project is aimed at overall open source component integration with some scope for VNF performance measurements. A set of simple use cases are required to provide focus and drive for the project. These use cases should meet the following requirements: * OPNFV Infrastructure Integration * OPFNV Infrastructure Grass Roots Performance
Exercise the integration of the OPNFV infrastructure components like Openstack, ODL, KVM etc., to stand up simple VNFs.
Exercise the OPNFV infrastructure component performance bottle necks and identify future improvements and enhancements required for a deploy-able NFV Infrastructure.
The following are the high level use cases that fits the needs: * Standup a Virtual Provider Edge * Standup a Mobile Packet Gateway * Standup a Content Delivery Network Gateway
These use cases can be achieved using open source VNFs, custom simulators those mimic the traffic patterns exhibited by the above network devices and finally using some Vendors VNF.
This project enables the integration testing of the OPNFV initial infrastructure that is built using the open source components. In addition, the project enables performance measurement that exposes the limitations and bottlenecks present in the infrastructure software and hardware. These efforts enables the OPFNV infrastructure to be designed on solid open soruce infrastructure as well as meet the demanding needs of network services and operations.
The project does not propose any new API specification. The project uses the standard open source component APIs from openstack, ODL, KVM etc. The project will test out these component APIs and their applicability for a stand alone NFV use cases identified above. The exact APIs set under test are [[here]]
The goal of the infrastructure integration testing is to verify the integration of the infrastructure components like openstack, ODL etc. This following macro test scenarios are specified to verify this integration requirement: - [[Install and bring-up verification of the test system]] - [[On-boarding of the Service VNF Descriptor ]] - [[Defining the Day 0 Configuration for the VNF ]] - [[Deployment of the Service ]] - [[Defining the Day 1 Configuration of the VNF ]] - [[Verification of the Service characteristics ]]
The goal of this Use case is to verify the delivered performance by the infrastructure. The macros test cases for this use case is built on top of the above use case. These are as follows: - [[ VNF Orchestration and deployment time ]] - [[ VNF boot up time]] - [[ VNF Network performance ]] - [[ VNF Compute performance ]] - [[ VNF Hyper-visor performance ]] - [[ VNF Storage perforamnce ]]
Debugging and Tracing Unit/Integration Test plans Client tools developed for status shows etc. Identity a list of features and functionality will be developed. Identify what is in or out of scope. So during the development phase, it helps reduce discussion. Describe how the project is extensible in future
(optional, Project Categories: Integration & Testing)
Specify testing and integration like interoperability, scalability, high availablity What QA and test resources will be available?
(optional, Project Categories: Documention)
API Docs Functional block description
Identify similar projects is underway or being proposed in OPNFV or upstream project Identify any open source upstream projects and release timeline. Identify any specific development be staged with respect to the upstream project and releases. Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications. If project is an integration and test, identify hardware dependency.
Committers and Contributors:
Name of and affiliation of the maintainer Names and affiliations of the committers Any other contributors
Described the project release package as OPNFV or open source upstream projects. If project deliverables have multiple dependencies across other project categories, described linkage of the deliverables.
Proposed Release Schedule:
When is the first release planned? Will this align with the current release cadence