rally-openstack/samples/deployments
msimonin 851bf0e6ad OSprofiler support
The OSprofiler is a distributed trace toolkit library.
It helps to trace internal calls of Openstack services including RPC, DB
and WSGI.

This patch integrates OSprofiler in Rally. Rally can trigger the
profiling on a per-iteration basis. To do so a secret key
(profiler_hmac_key) is stored alongside the credentials and used to
initialize the profiler in the constructor of the scenarios. A
configuration parameter (enable_profiler) can disabled the profiling.

Note that in this patch we don't embed the full osprofiler report but
only a trace id. This trace id can be used to retrieve the full trace
from the osprofiler tool later.

Change-Id: I7602856d094e073fde80d287b4d92b5750aacc3c
Co-Authored-By: rcherrueau <Ronan-Alexandre.Cherrueau@inria.fr>
Implements: spec osprofiler
2017-05-27 15:09:42 +02:00
..
existing-keystone-v3-osprofiler.json OSprofiler support 2017-05-27 15:09:42 +02:00
existing-keystone-v3.json Update deployment samples 2017-03-22 08:49:56 +00:00
existing-with-given-endpoint.json Update deployment samples 2017-03-22 08:49:56 +00:00
existing-with-predefined-users.json Update deployment samples 2017-03-22 08:49:56 +00:00
existing.json Update deployment samples 2017-03-22 08:49:56 +00:00
README.rst Finish support of benchmarking with existing users 2015-04-24 18:46:34 +03:00

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