2f4555be27
In a lot of placeses we are using word "benchmark" which can mean workload, subtask, or test case which is very confusing. This patch partially address wrong usage of "benchamrk" word Change-Id: Id3b2b7ae841a5243684c12cc51c96f005dbe7544
34 lines
897 B
ReStructuredText
34 lines
897 B
ReStructuredText
==========================================
|
|
Support testing clouds that are using LDAP
|
|
==========================================
|
|
|
|
Use Case
|
|
--------
|
|
|
|
A lot of production clouds are using LDAP with read only access. It means
|
|
that load can be generated only by existing in system users and there is no
|
|
admin access.
|
|
|
|
|
|
Problem Description
|
|
-------------------
|
|
|
|
Rally is using admin access to create temporary users that will be used to
|
|
produce load.
|
|
|
|
|
|
Possible Solution
|
|
-----------------
|
|
|
|
* Add some way to pass already existing users
|
|
|
|
|
|
Current Solution
|
|
----------------
|
|
|
|
* Add ability to specify existing users in the *ExistingCloud* plugin config
|
|
* When such an *ExistingCloud* deployment is active, and the task file does not
|
|
specify the *"users"* context, use the existing users instead of creating the
|
|
temporary ones.
|
|
* Modify the *rally show* commands to list resources for each user separately.
|