storperf:architecture
Differences
This shows you the differences between two versions of the page.
|
storperf:architecture [2015/10/01 16:01] Mark Beierl created |
storperf:architecture [2015/10/02 18:07] (current) Iben Rodriguez |
||
|---|---|---|---|
| Line 32: | Line 32: | ||
| * Historically report on tests saved in Carbon | * Historically report on tests saved in Carbon | ||
| * Extract test run data | * Extract test run data | ||
| + | |||
| + | ===== Food for thought ===== | ||
| + | |||
| + | * how will you build the VMs? - in your dev environment | ||
| + | * what goes into the VM? | ||
| + | * create the heat templates | ||
| + | * upload to arm | ||
| + | * scripts to run tests and collect results | ||
| + | * they should move to ARM - http://artifacts.opnfv.org/ But how? | ||
| + | * Manual upload to ARM | ||
| + | * Automatic upload with a Jenkins job - ??? | ||
| + | * Jenkins job to slave to deploy the VMs and run the tests on local lab environment | ||
| + | * There are two levels of tests being run. 1st is a unit level test performing a functional test done during the build. 2nd level is the actual performance testing. | ||
| + | * Jenkins job to collect the test results data files: hundreds of lines of statistics, IOPS, Latency, Bandwidth, Throughput, etc stored in a whisper database which can be exported into other formats | ||
| + | * This is one option: https://wiki.opnfv.org/wiki/jenkins#logging_and_graphing | ||
| ===== Future Plans ===== | ===== Future Plans ===== | ||
storperf/architecture.1443715281.txt.gz · Last modified: 2015/10/01 16:01 by Mark Beierl
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
