rally-openstack/doc
Boris Pavlovic af1c8b7652 Improve Rally Logging (part 2)
- 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
2017-10-05 22:57:39 +00:00
..
ext Use "anyOf" instead of "oneOf" in users@openstack plugin 2017-09-19 20:40:45 -07:00
feature_request Rephrase docs call things properly 2017-08-03 18:39:10 +00:00
release_notes Rephrase docs call things properly 2017-08-03 18:39:10 +00:00
source Improve Rally Logging (part 2) 2017-10-05 22:57:39 +00:00
specs Switch everything to `rally db` 2017-08-29 13:25:41 -07:00
user_stories Rephrase docs call things properly 2017-08-03 18:39:10 +00:00
README.rst Change deployment model schema 2016-03-28 17:20:46 +03:00

README.rst

Content of doc directory

This directory contains everything that is related to documentation and bureaucracy. You can find here 4 subdirectories:

feature_request

If some use case is not covered by Rally, it is the right place to request it. To request new feature you should just explain use case on high level. Technical details and writing code are not required at all.

source

Source of documentation. Latest version of documentation.

specs

Specs are detailed description of proposed changes in project. Usually they answer on what, why, how to change in project and who is going to work on change.

user_stories

Place where you can share any of Rally user experience. E.g. fixing some bugs, measuring performance of different architectures or comparing different hardware and so on..

release_notes

The latest.rst contains new features and API changes of Rally's latest release. And you could find all old releases in archive.