use_cases
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
use_cases [2014/10/08 21:03] Palani Chinnakannan |
use_cases [2014/10/13 20:05] Palani Chinnakannan |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | OPNFV Phase 1 use cases: | + | ====== OPNFV Deployment Test cases ===== |
| + | ---- | ||
| + | ** An Integration & Testing project category** | ||
| + | ====== Project description ====== | ||
| + | The first release of the OPNFV project is aimed at open source component integration to form the NFVI platform for VNF hosting and for basic NFVI platform performance measurements. A set of simple use cases are required to provide focus and drive for the project to meet these goals. These use cases should meet the following requirements: | ||
| + | * OPNFV Platform Integration | ||
| + | * OPNFV Platform Basic Performance Measurements | ||
| + | ==== OPNFV Platform Integration ==== | ||
| + | The requirement here is to have use case(s) that originates the tests required to verify the OPNFV Platform. The testing is basically to verify the __**integration**__ of the components like Openstack, ODL, KVM etc., to form a cohesive platform using which one could stand up a VNF. | ||
| - | OPNFV Phase 1 Use case | + | ==== OPNFV Platform Basic Performance Measurement==== |
| - | Project Categories: Integration & Testing | + | The requirement here is to make some basic performance measurement done that exposes the performance bottle necks and identify future improvements and enhancements required for a deploy-able NFV platform. |
| - | Project description: | + | The ETSI use cases document[1] lists a wide range of use cases. After a review of this document, followed by some level of discussion with the network operators, the following high level use cases are selected for meeting the above requirements: |
| + | * Standup a Virtual Provider Edge (section 6.3) | ||
| + | * Standup a EPC Network Function, MME or PGW (section 9.3) | ||
| + | * Standup a Content Delivery Network, CDN Node (Section 12.3) | ||
| + | * Standup a Home Gateway, NAT, ALG, RGW etc. (section 11.3) | ||
| + | For more details about these use cases, please refer to the above reference: | ||
| + | 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. | ||
| - | The first phase of the OPNFVProvide high level description of intended project and OPNFV use case and benefit, if needed. | + | ====== Scope: ====== |
| - | Include any architecture diagrams or specifications, reference to OPNFV requirements list. | + | |
| - | Scope: | + | This project enables the integration testing of the OPNFV platform 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 OPNFV platform to be designed on solid open source infrastructure as well as meet the demanding needs of network services and operations. |
| + | ===== Interface and API ===== | ||
| + | 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]] | ||
| - | Describe the problem being solved by project | + | ===== Testing and integration ===== |
| - | Specify any interface/API specification proposed, | + | |
| - | Specify testing and integration: | + | ==== OPNFV Platform Integration Macro Test Plan ==== |
| - | Debugging and Tracing | + | 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: |
| - | Unit/Integration Test plans | + | - Install and bring-up verification of the test system |
| - | Client tools developed for status shows etc. | + | - On-boarding of the Service VNF Descriptor |
| - | Identity a list of features and functionality will be developed. | + | - Defining the Day 0 Configuration for the VNF |
| - | Identify what is in or out of scope. So during the development phase, it helps reduce discussion. | + | - Deployment of the Service |
| - | Describe how the project is extensible in future | + | - Defining the Day 1 Configuration of the VNF |
| + | - Verification of the Service characteristics | ||
| - | Testability: ''(optional, Project Categories: Integration & Testing)'' | + | ==== OPNFV Platform Basic Performance Measurement Macro Test Plan==== |
| + | 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 performance | ||
| + | ==== | ||
| + | Debugging and Tracing ==== | ||
| - | Specify testing and integration like interoperability, scalability, high availablity | + | Unit/Integration Test plans |
| - | What QA and test resources will be available? | + | 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 | ||
| + | |||
| + | ==== Testability ==== | ||
| + | Specify testing and integration like interoperability, scalability, high availablity | ||
| + | What QA and test resources will be available? | ||
| + | |||
| + | ==== Documentation ==== | ||
| - | Documentation: ''(optional, Project Categories: Documention)'' | ||
| API Docs | API Docs | ||
| Functional block description | Functional block description | ||
| - | Dependencies: | + | ==== Dependencies ==== |
| - | + | - No Similar project identified. | |
| - | Identify similar projects is underway or being proposed in OPNFV or upstream project | + | - The project completion requires the integration of open source components specified below: |
| - | Identify any open source upstream projects and release timeline. | + | - Depends on the Continuous Integration Plan |
| - | Identify any specific development be staged with respect to the upstream project and releases. | + | - Depends on the Hardware and Software Integration Plan |
| - | Are there any external fora or standard development organization dependencies. If possible, list and informative and normative reference specifications. | + | ==== Commiters and Contributors ==== |
| - | 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 | + | |
| - | + | ||
| - | Planned deliverables | + | |
| - | + | ||
| - | 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? | + | ==== Planned deliverable ==== |
| - | Will this align with the current release cadence | + | This project will deliver the following: |
| + | * Use cases document | ||
| + | * Macro Test cases driven by the use cases | ||
| + | * Micro test cases driven by the Macro Test cases | ||
| + | * Performance measurement metrics | ||
| + | ==== Proposed Release Schedule ==== | ||
| + | This project proposal is for the first release of the OPNFV platform. | ||
| + | ==== References ==== | ||
| + | 1. ETSI GS NFV 001 V1.1.1: Network Function Virtualization; Use cases | ||
use_cases.txt · Last modified: 2014/10/13 20:07 by Palani Chinnakannan
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
