Move "tempest concurrency" feature request to implemented
Change-Id: Ifb4d886cccf3a06dad575db9b38a2ebaa3f10795
This commit is contained in:
parent
485310c16a
commit
db49cc51e7
@ -0,0 +1,24 @@
|
|||||||
|
========================================
|
||||||
|
Running Tempest using custom concurrency
|
||||||
|
========================================
|
||||||
|
|
||||||
|
|
||||||
|
Use case
|
||||||
|
--------
|
||||||
|
|
||||||
|
User might want to use specific concurrency for running tests based on his
|
||||||
|
deployment and available resources.
|
||||||
|
|
||||||
|
|
||||||
|
Problem description
|
||||||
|
-------------------
|
||||||
|
|
||||||
|
"rally verify start" command does not allow to specify concurrency
|
||||||
|
for tempest tests. And they always run using concurrency equal
|
||||||
|
to amount of CPU cores.
|
||||||
|
|
||||||
|
|
||||||
|
Possible solution
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
* Add ``--concurrency`` option to "rally verify start" command.
|
Loading…
x
Reference in New Issue
Block a user