* fix lable of database section. it should be [database] instead of [db]
* create `/home/rally/data` dir by rally user instead of root, so rally
could operate the database there.
* modify the volume path
* update the docs
Change-Id: Ia4df80e2ce570ede4582c875c0550d5ba8da60d9
ChenHb and Hai Shi were added long time ago to rally core team, but the
info page was not updated yet.
Change-Id: I59f7d7e08127a99c3d8447aa15f04549d15a07df
- Remove translations
Nobody is using translations for Rally and I don't think that
anybody is going to use it. Target auditory for Rally are
developers/operators which usually know well english.
For me this looks like waste of resources, performance
degradation (cause we are calling _()), complexity
(+1 thing that you need to know)
- Pass to log already formatted strings
It's very bad because in case of wrong formatting, it
doesn't fail instead just writes errors to the logs,
as well information about trace is lost, so it's super
hard to fix it
Log wrapper doesn't allow to use LOG anymore for
formatting strings
All places are fixed
- Improve logging of exceptions
LOG.exception() already logs exception, which means it's bad idea to
pass str(e) to it. Instead we should provide clear description of what
happend. Improved few places to write warnings or exceptions in case
of different level of logs. In few places just use LOG.exception
- Part of log messages were improved and simplified
Depends-On: If23d874e8b73de12ba2b8c4e028a55543af6381b
Change-Id: Ibc1e1f4f554649d14b8fe4801557b83922ecefe3
Every day Rally step by step closer to the point where Rally is going to be
generic framework and it would be possible to split Rally & Rally OpenStack Plugins
One of the blockers for doing this is certification & samples directories and
their contents. Current apporach creates a lot of confusion:
- Rally Users are running samples against production
- Rally samples are actually not that usefull, because creating from them
tasks takes a lot of time
- Rally Users don't know what certification task is and how to use it
- Samples are hard to ship/find in packaged way (when rally is installed)
- Samples are going to be impossible to ship after the split
- We have to keep hunderds of yaml/json files in actual state
in our repo (extra work for developers)
Proposed approach is to:
- Create mechansim CLI command that generates samples using plugin names
- Rename certification -> tasks
- Put in tasks directory pre created and tested tasks for different use cases:
key performance metrics, functional testing, load testing of key functionality,
ha Testing
- Remove samples as they are not needed anymore
Change-Id: I4c45224c3af637d17dab0edea038c69a2bae8b1a
Adhering to coding conventions. Refer to ``Code conventions`` at
https://docs.openstack.org/contributor-guide/ for details.
"." is synonymous with source in bash, but not in POSIX sh, so we
should use "." if the script is run by "/bin/sh".
"/bin/sh" is often used in cron.
Change-Id: I0ee691d84a19f3f06f111d50e23c0c9c80ebd402
1) Update doc links according to OpenStack document migration
2) Use https instead of http for docs links
Change-Id: Id606f43f486e98fc33b699b36e468de954ec677d
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
Last time I removed step 9 tutorial for deploying openstack from
rally document (https://review.openstack.org/#/c/475932/).
However, I forgot to update the tutorial step number after that.
This just updates the tutorial step number to make it continuous.
Change-Id: Ib16408350b147eeb70b5de9b18f8014ac12714a6
The scenario_plugin.py was updated, however, the documentation still
has the old instruction for creating a plugin. Let's update that in-
struction. Let's also add 'required_services' and 'required_platform'
in the sample to make it more complete.
Change-Id: I6d36ea51a3ee32b94ab296c77195ee22652f40ec
The devstack deployer plugin was removed, however, the documentation
has not been updated. Let's update the documentation and remove that
tutorial.
Change-Id: Ideef4b2b70e182d9fa396fea6f00df0fa8cc4343
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
Fix the Sphinx html_last_updated_fmt for Python3.
The html_last_updated_fmt option is interpeted as a
byte string in python3, causing Sphinx build to break.
This patch makes it utf-8 string.
Change-Id: Ife5b7762c8ebce005f2a3a3b59f8c01eca48c55d
In overview.rst file, removed "we" from the file.
In distributed_load_generation.rst file, changed "have" to "has".
Change-Id: I9532ffa0314a9ad5f35bbe33a5ce42c6bb52c7b5
Default image in devstack was changed recently from uec to qcow2.
All rally jobs except rally-mos now need to be updated accordingly.
devstack changes:
* Id65ebae73b28da7185cb349b714b659af51ef77f
* I5c154ec25555e768954538fc22b4f5d5975b2deb
Change-Id: Ia4d4afb661d8bcc7c38b0a16b508294f789eef14
The main goal of this patch is to move Tempest context related code
from the rally/plugins/openstack/verification/tempest/config.py file
to the separate rally/plugins/openstack/verification/tempest/context.py
file.
Also,
1. Functions such as 'add_extra_options' and 'extend_configfile' were
moved from the rally/plugins/openstack/verification/tempest/config.py
file to rally/verification/utils.py because these functions can be
used by other verifier plugins in the future.
2. Now Tempest log, test image and lock files are stored in the
corresponding deployment directory.
3. Now the 'floating_network_name' option from the 'network' section is
configured as well.
4. A small cleanup was done.
Change-Id: I12c7918400c736b71c5a8044bb1aa53122fb96f1
* plugin_reference is extended to build data for particular Plugin Base cls
* plugin_reference is extended to build data for all Plugin Bases (instead
of just building data for hardcoded classes).
* cli_reference is extended to build data for particular command
* new include_vars extension is introduced for including const data in docs
Change-Id: I76d9f85e41c6ab8e622f6d3581478962144525ba
Add final 80 symbols margin check, as well as additional check for
trailing spaces. Fix all docs not matching this rule.
Change-Id: I8b4814fad0acaba6ce1de7aa6f90d1f7ecc4153d
All information related to Rally community and project
info has been refactored. Modified files fit 80 symbols
margin where possible.
[TODO] add 80 symbols margin check similar to what
Performance Documentation has
Change-Id: Id4f33733c2b9aa141df4eeb0f24a21d82290a962
