openstack/rally
Code Issues Proposed changes
720eff5472
rally/samples/deployments
History
Angus Lees 3f79951a11 OpenStackProvider: Optionally wait for cloud-init 
cloud-init writes a result.json when finished[1].  When
wait_for_cloud_init=true is provided, this change uses result.json to
detect when cloud-init has finished, and raises an exception if it
finished with errors.

[1] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/status.txt

Change-Id: I7e0bcce733b008b488c8e1cf9bb74b5b6192cfbc
2015-08-19 12:12:39 +10:00
..
for_deploying_openstack_with_rally OpenStackProvider: Optionally wait for cloud-init 2015-08-19 12:12:39 +10:00
existing-keystone-v3.json Fix sample json file 2015-08-12 14:48:30 -04:00
existing-with-given-endpoint.json Fix sample json file 2015-08-12 14:48:30 -04:00
existing-with-predefined-users.json Finish support of benchmarking with existing users 2015-04-24 18:46:34 +03:00
existing.json Fix sample json file 2015-08-12 14:48:30 -04: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/"