openstack/rally
Code Issues Proposed changes
f2d65679c4
rally/samples/deployments
History
morganrOL 238ca0c3d2 tempest: add `admin_domain_name' to generated conf 
Add admin_domain_name=default of autogenerated tempest.conf
This line prevents the keystone v3 related tests to be declared as failure.

Closes-Bug:1460680

Change-Id: I9e0eeb2e9392df17fc0e0c71bf9268482e921ac9
Signed-off-by: morganrOL <morgan.richomme@orange.com>
2015-06-05 09:30:46 +02:00
..
for_deploying_openstack_with_rally Fixes devstack repo 2015-05-11 11:38:36 +08:00
existing-keystone-v3.json tempest: add `admin_domain_name' to generated conf 2015-06-05 09:30:46 +02:00
existing-with-given-endpoint.json configure ssl in deployment config 2015-04-03 10:01:47 +08:00
existing-with-predefined-users.json Finish support of benchmarking with existing users 2015-04-24 18:46:34 +03:00
existing.json configure ssl in deployment config 2015-04-03 10:01:47 +08:00
README.rst Finish support of benchmarking with existing users 2015-04-24 18:46:34 +03:00

README.rst

Rally Deployments

Rally needs to be configured to use an OpenStack Cloud deployment before it can benchmark the deployment.

To configure Rally to use an OpenStack Cloud deployment, you need create a deployment configuration by supplying the endpoint and credentials, as follows:

rally deployment create --file <one_of_files_from_this_dir> --name my_cloud

If you don't have OpenStack deployments, Rally can deploy it for you. For samples of various deployments take a look at samples from for_deploying_openstack_with_rally directory.

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/"