This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
platform_tooling [2014/11/06 00:47] Wenjing Chu [Scope:] |
platform_tooling [2014/11/06 05:49] (current) Wenjing Chu [Scope:] |
||
|---|---|---|---|
| Line 30: | Line 30: | ||
| Test bed infrastructure and tooling project extends to all the SW and HW components needed to establish and operate such a test bed. It should: | Test bed infrastructure and tooling project extends to all the SW and HW components needed to establish and operate such a test bed. It should: | ||
| - | - support both micro/macro level testing, virtual infrastructure level or VNFC or VNF level testing | + | - support both micro/macro level testing, virtual infrastructure level, or VNFC or VNF level testing |
| - can host multi-origin/multi-vendor VNFs, i.e. compositions of vnfc's | - can host multi-origin/multi-vendor VNFs, i.e. compositions of vnfc's | ||
| - | - support regression, functional, and performance/benchmark testing | + | - support sanity, regression, functional, and performance/benchmark testing |
| - covers both hw and sw components | - covers both hw and sw components | ||
| Line 40: | Line 40: | ||
| - Access tools: Web access | - Access tools: Web access | ||
| - Access tools: Console access | - Access tools: Console access | ||
| + | - Physical access | ||
| - Access tools: Reservation / multi-user/tenant | - Access tools: Reservation / multi-user/tenant | ||
| - On-boarding of vnf/vnfc tools | - On-boarding of vnf/vnfc tools | ||
| Line 47: | Line 48: | ||
| - Test load generators, benchmark tools: sw, hw, open source, commercial | - Test load generators, benchmark tools: sw, hw, open source, commercial | ||
| - Test VNFs, common target or auxiliary VNFs - these VNFCs or VNFs are needed for testing, benchmarking, and for helping developers building their own test scenarios | - Test VNFs, common target or auxiliary VNFs - these VNFCs or VNFs are needed for testing, benchmarking, and for helping developers building their own test scenarios | ||
| + | - A standard set of bottom-up test cases | ||
| - inter-testbed connectivity emulation, if needed | - inter-testbed connectivity emulation, if needed | ||
| - stand-alone nfvc connectivity emulation, if needed | - stand-alone nfvc connectivity emulation, if needed | ||
| Line 88: | Line 90: | ||
| * Identify what is in or out of scope. So during the development phase, it helps reduce discussion. | * Identify what is in or out of scope. So during the development phase, it helps reduce discussion. | ||
| - | TBD | + | |
| + | In scope: | ||
| + | - Bottom-up test cases that validate the functions of a release | ||
| + | - Bottom-up benchmark / performance tests | ||
| + | - VNF sw to support the above goals | ||
| + | - Automation tools to support the above | ||
| + | - Software and hardware tools that support developer sandbox | ||
| + | - VNF, devops, etc. sw to support the sandbox | ||
| + | - Shared common tools | ||
| + | |||
| + | Out of scope: | ||
| + | - Complex NFV use cases | ||
| * Describe how the project is extensible in future | * Describe how the project is extensible in future | ||
| - | TBD | + | |
| + | The project may be expanded in several dimensions: Just some examples. | ||
| + | - Additional / different hardware flavors or designs or models | ||
| + | - Additional software variations as the overall opnfv support expands, e.g. Linux distribution, OpenStack distributions, Hypervisor / Containers, etc. | ||
| + | - Each release of opnfv will bring in new functions | ||
| + | - New methods of interacting with the test beds | ||
| + | - New instances of test beds | ||
| + | - New tools and test cases / use cases that the test bed can support | ||
| + | |||
| ==== Testability: ''(optional, Project Categories: Integration & Testing)'' ==== | ==== Testability: ''(optional, Project Categories: Integration & Testing)'' ==== | ||