50fa2eb653
For the moment all users for tasks are taken randomly and there is no way to balance them between tasks. It may be very useful when we have difference between first usage of tenant/user and all consecutive. In this case we get different load results. Therefore, add enum config option 'user_choice_method' to 'users' context that defines approach for picking up users. Two values are available: - random - round_robin Default one is compatible with old approach - "random". Also, update one of scenarios to use "round_robin" approach to make sure it works. Change-Id: I26fb090eb89c22f5d50529cb73b6ed54fc3d7e15 |
||
---|---|---|
.. | ||
attach-security-service-to-share-network.json | ||
attach-security-service-to-share-network.yaml | ||
create-security-service-and-delete.json | ||
create-security-service-and-delete.yaml | ||
create-share-network-and-delete.json | ||
create-share-network-and-delete.yaml | ||
create-share-network-and-list.json | ||
create-share-network-and-list.yaml | ||
create-share-without-share-networks-and-delete.json | ||
create-share-without-share-networks-and-delete.yaml | ||
list-share-servers.json | ||
list-share-servers.yaml | ||
list-shares.json | ||
list-shares.yaml |