opnfv_platform_characterization
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
opnfv_platform_characterization [2014/11/06 04:52] Trevor Cooper created |
opnfv_platform_characterization [2014/11/06 05:46] (current) Trevor Cooper |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ==== Project Name: ==== | ==== Project Name: ==== | ||
| - | * Proposed name for the project: ''project-name'' | + | * Proposed name for the project: ''OPNFV Platform Characterization'' |
| - | * Proposed name for the repository: ''repo-name'' | + | * Proposed name for the repository: ''tbd'' |
| - | * Project Categories: ''(Documentation, Requirements, Integration & Testing, Collaborative Development)'' | + | * Project Categories: ''Integration & Testing'' |
| - | * | + | |
| ==== Project description: ==== | ==== Project description: ==== | ||
| - | * Provide high level description of intended project and OPNFV use case and benefit, if needed. | + | The OPNFV Platform Characterization project targets functional and performance testing of OPNFV releases on community agreed platform configurations as a reference for evaluating and developing NFVI solutions. |
| - | * Include any architecture diagrams or specifications, reference to OPNFV requirements list. | + | |
| + | A set of prioritized use-cases will provide focus and drive individual projects with either of the following approaches ... | ||
| + | * OPNFV Platform - **VNF deployment Testing** (NFV use-cases with focus on functional testing) | ||
| + | * OPNFV Platform - **Performance Benchmarking** (micro or macro benchmarks with focus on platform performance and stability) | ||
| ==== Scope: ==== | ==== Scope: ==== | ||
| - | * Describe the problem being solved by project | + | Objective is to characterize the OPNFV Platform (capabilities, performance limits, etc.) … the intention is NOT to validate performance of Vendor's proprietary VNFs (there are many different approaches to deploying VNFs to achieve certain service level requirements) |
| - | * Specify any interface/API specification proposed, | + | |
| - | * Specify testing and integration: | + | Individual projects will be proposed, discussed and initiated by the Test & Performance sub-group ... |
| - | * Debugging and Tracing | + | * Use case being addressed |
| - | * Unit/Integration Test plans | + | * Metrics |
| - | * Client tools developed for status shows etc. | + | * Known requirements or existing benchmarks |
| - | * Identity a list of features and functionality will be developed. | + | * Test cases |
| - | * Identify what is in or out of scope. So during the development phase, it helps reduce discussion. | + | * Test methodology - including special tools and requirements for generating load |
| - | * Describe how the project is extensible in future | + | * Target platform (SUT) configuration/s - hardware and software |
| + | * Network topology | ||
| + | * Interfaces being exercised | ||
| + | * VNFs or other workloads being used | ||
| + | |||
| + | |||
| + | |||
| + | ==== Project Categories ==== | ||
| + | |||
| + | **__VNF deployment Testing__** | ||
| + | |||
| + | * Use-cases (ETSI NFV) | ||
| + | * Test cases | ||
| + | |||
| + | * Deployment configurations | ||
| + | * VNF configuration | ||
| + | * Network topology / configuration | ||
| + | |||
| + | * Focus is on functional testing - verify OPNFV Platform functionality of VIM and NFVI | ||
| + | |||
| + | * Approach | ||
| + | * Break down the use case into a basic core function in its minimalistic form and provides the necessary topology, traffic patterns etc | ||
| + | * Collect info in traffic profiles | ||
| + | |||
| + | * Use cases initially proposed | ||
| + | * virtual Provider Edge | ||
| + | * virtual Evolved Packet Core | ||
| + | * IP Multimedia Subsystem | ||
| + | * Content Delivery Network, CDN Node | ||
| + | * Home Gateway, NAT, ALG, RGW etc. | ||
| + | |||
| + | |||
| + | **__Performance Benchmarking__** | ||
| + | |||
| + | * Test cases (Test Specification) | ||
| + | * Characterize components … NIC, vSwitch, hypervisor, etc. | ||
| + | * Map to VNF deployment use-cases | ||
| + | |||
| + | * Platform configuration | ||
| + | |||
| + | * Focus is on performance testing | ||
| + | * verify OPNFV Platform performance of NFVI components and sub-systems | ||
| + | * identify performance limiting hardware and software entities in the system and provide solutions to improve the performance of the system | ||
| + | * Scaling and performance the NIC, vNIC, vSwitch, hyper-visor, CPU, Memory, storage devices etc., and their associated metrics like throughput, latency, cpu utilization, etc | ||
| + | |||
| + | * Approach | ||
| + | * test cases that are used to measure the OPNFV platform characteristics as well as certain core functions of the OPNFV platform | ||
| + | * specify various platform components and associated metrics and detailed test plan | ||
| - | ==== Testability: ''(optional, Project Categories: Integration & Testing)'' ==== | ||
| - | * Specify testing and integration like interoperability, scalability, high availablity | ||
| - | * What QA and test resources will be available? | ||
| - | ==== Documentation: ''(optional, Project Categories: Documention)'' ==== | + | ==== Documentation: ==== |
| * API Docs | * API Docs | ||
opnfv_platform_characterization.1415249567.txt.gz · Last modified: 2014/11/06 04:52 by Trevor Cooper
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
