ffb38f8127
1. connect_string store in deployment and get in credential 2. if has got connect_string and hmac_key,rally get osprofiler data and process them in osprofilerchart 3. new js code will receive the data from osprofiler chart and generate graphs Change-Id: Id477a10489102425fae79ecf6719b1e0739e92c0 |
||
---|---|---|
.. | ||
existing-keystone-v3-osprofiler.json | ||
existing-keystone-v3.json | ||
existing-with-given-endpoint.json | ||
existing-with-predefined-users.json | ||
existing.json | ||
README.rst |
Rally Deployments
Rally needs to have information about OpenStack Cloud before you actually can run any tests against it.
You need create a deployment input file and run use command bellow:
rally deployment create --file <one_of_files_from_this_dir> --name my_cloud
Below you can find samples of supported configurations.
existing.json
Register existing OpenStack cluster.
existing-keystone-v3.json
Register existing OpenStack cluster that uses Keystone v3.
existing-with-predefined-users.json
If you are using read-only backend in Keystone like LDAP, AD then you need this sample. If you don't specify "users" rally will use already existing users that you provide.
existing-with-given-endpoint.json
Register existing OpenStack cluster, with parameter "endpoint" specified to explicitly set keystone management_url. Use this parameter if keystone fails to setup management_url correctly. For example, this parameter must be specified for FUEL cluster and has value "http://<identity-public-url-ip>:35357/v2.0/"