[2.1.0] - 2019-11-19
Please note that Python 2.7 will reach the end of its life on January 1st, 2020. A future version of Rally will drop support for Python 2.7, it will happen soon. Also, the same will happen with support of Python 3.4 and Python 3.5
Library netaddr from direct project requirements. We never use it at Rally framework.
Support of latest alembic
[2.0.0] - 2019-09-13
python jsonschema dependency is not limited by <3.0.0 anymore and you can use draft-7 as for now.
- rally task sla_check command was deprecated in Rally 0.8.0 in favor of rally task sla-check.
- rally-manage db command (and the whole rally-manage entry-point) was deprecated in Rally 0.10.0 in favor of rally db command.
- --namespace argument was deprecated in Rally 0.10.0 in favor of --platform which has better meaning. Affected commands: rally plugin show, rally plugin list, rally verify list-plugins, rally verify create-verifier.
- --tasks argument of rally task report command and --task argument of rally task use command were deprecated in Rally 0.10.0 in favor of unified --uuid argument.
- --junit argument of rally task report command is deprecated in Rally 0.10.0 in favor of rally task export --type junit-xml
[1.6.0] - 2019-06-19
A list of tests to skip while running verification now supports regular expressions.
- incompatibility with SQLAlchemy 1.3
- several py3 issues of verification component
[1.5.1] - 2019-05-15
rally deployment create --fromenv creates wrong spec for rally-openstack<=1.4.0 which doesn't pass rally deployment check.
[1.5.0] - 2019-05-08
New two charts EmbeddedChart and EmbeddedExternalChart for embedding custom html code or external pages as complete charts of scenarios.
[1.4.1] - 2019-02-28
- Python 3 issue of Verification component
- Docker README file
[1.4.0] - 2019-02-04
- Add the --html-static option to commands
rally task trends, it could generate trends report with embedded js/css.
- Removed dependency to
[1.3.0] - 2018-12-01
- Add the --deployment option to commands
rally task report and
rally task export that allows to report/export all tasks from defined deployment.
- Briefly: the new base image is published at Docker Hub Detailed story: Long time ago Rally team introduced first docker images which were hosted by rallyforge account at Docker Hub. Due to various circumstances we lost access to that account and Docker support restored access to it in a strange way (we lost all repositories and could not recreate them). That is why Rally team started publishing docker images from scratch. The new organization was created -xRally . Since we already had plans to move OpenStack plugins to the separate repository, we started publishing images with in-tree OpenStack plugins to xrally/xrally-openstack repository. As soon as, a separate package for OpenStack plugins was introduced, we switched the source of xrally/xrally-openstack Docker Hub repository to rally-openstack git repository. As for Rally 1.0.0 we finally have pure framework without heavy dependencies and can start publishing separate images for Rally framework itself which can be used as a base image for all plugins. New images will be located at xrally/xrally Docker Hub repository.
rally --version prints version of Rally framework with versions of installed plugins instead of printing just version of Rally framework.
- Dockerfile moved from the root directory to ./etc/docker/
A floating bug with
[1.2.1] - 2018-09-27
Minor inner fixes
[1.2.0] - 2018-09-19
- New validator
map_keys for checking keys of specific argument.
- Support of ElasticSearch 6.x cluster elastic exporter.
- Improved validation errors for task component.
- [ElasticSearch exporter] Do not send 'no-name-action' index when the item fails after some atomic actions completed and there is a root atomic. For example, there is 'wait-for-some-resource-ready' action. It consists of a bunch of get requests to update the current status. After specified timeout this action can fail if the resource is not in the right state. In such case, there is no reason to use 'no-name-action' for saving the error, the parent index (i.e 'wait-for-some-resource-ready') will already store it.
[1.1.0] - 2018-08-07
rally env cleanup command for performing disaster cleanup.
- New CI jobs for checking compatibility with Python 3.4, 3.6, 3.7 .
- The output of json task result exporter (
rally task report --json) is extended with information about environment where task was executed (new
- Add the --filter-by option to the command
rally task detailed, which allows us to show only those workloads which we are interested in (see the examples below). Examples:
- show only failed workloads
rally task detailed --filter-by sla-failures
- show only those workloads which include the next scenario plugin(s)
rally task detailed --filter-by scenarios=scenario1[,scenarios2...]
- requirements and constraints (suggested versions) files are updated.
- Disturbing warning message about removing in-tree OpenStack plugins. This message became redundant after Rally 1.0.0 when such plugins were removed.
- OpenStack related configuration options for sample file.
- Deprecated in Rally 0.10
rally.task.exporter.Exporter class in favor of
- 'async' argument of API method task.abort in favor of 'wait' argument which doesn't conflict with a reserved keyword in python 3.7
[1.0.0] - 2018-06-20
It finally happened. We are happy to inform you that OpenStack plugins has a single home - https://github.com/openstack/rally-openstack . All in-tree plugins are removed now and framework part become more lightweight.
What does it mean for you?!
If you are interested only in OpenStack plugins, just change the package you are installing from
rally-openstack. If you have custom OpenStack plugins which inherits from upstream, change python imports from
rally_openstack. That is all.
If you are interested not only in OpenStack, you can start using your favourite tool for various platforms and systems. Here you can find our first attempts to seize the world - https://github.com/xrally/xrally-docker and https://github.com/xrally/xrally-kubernetes.
Since OpenStack plugins were moved to the separate repository, the new release notes should become light as well, so there is no need in separate pages for each release. All release notes will be aggregated in a single file CHANGELOG.rst.
Also, it is sad to mention, but due to OpenStack policies we need to stop duplicating release notes at
git tag message. At least for now.
- All OpenStack related plugins.
- Validation of existing platforms in Python 3 environment.
- Support of testr for verifiers.
[0.0.0] - [0.12.1]
Release notes for Rally
0.12.1 are available at https://github.com/openstack/rally/tree/master/doc/release_notes/archive