noironetworks · tbachman · May 21, 2018 · May 22, 2018 · May 22, 2018 · May 29, 2018
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
@@ -0,0 +1,93 @@
+=========
+Changelog
+=========
+
+.. Changelogs are for humans, not machines. The end users of Rally project are
+   human beings who care about what's is changing, why and how it affects them.
+   Please leave these notes as much as possible human oriented.
+
+.. Each release can use the next sections:
+
+    - **Added** for new features.
+    - **Changed** for changes in existing functionality.
+    - **Deprecated** for soon-to-be removed features/plugins.
+    - **Removed** for now removed features/plugins.
+    - **Fixed** for any bug fixes.
+
+.. Release notes for existing releases are MUTABLE! If there is something that
+   was missed or can be improved, feel free to change it!
+
+[Unreleased]
+------------
+
+Changed
+~~~~~~~
+
+* The output of json task result exporter (``rally task report --json``) is
+  extended with information about environment where task was executed (new
+  ``env_name`` and ``env_uuid`` properties)
+* 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:
+    1. show only failed workloads
+       ``rally task detailed --filter-by sla-failures``
+    2. show only those workloads which include the next scenario plugin(s)
+       ``rally task detailed --filter-by scenarios=scenario1[,scenarios2...]``
+
+Removed
+~~~~~~~
+
+* 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
+  ``rally.task.exporter.TaskExporter``.
+
+[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`` to ``rally-openstack``. If you have custom
+OpenStack plugins which inherits from upstream, change python imports from
+``rally.plugins.openstack`` to ``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.
+
+Changed
+~~~~~~~
+
+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
+<https://github.com/openstack/rally/blob/master/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.
+
+Removed
+~~~~~~~
+
+* All OpenStack related plugins.
+
+Fixed
+~~~~~
+
+* Validation of existing platforms in Python 3 environment.
+* Support of testr for verifiers.
+
+[0.0.0] - [0.12.1]
+------------------
+
+Release notes for Rally ``0.0.0``-``0.12.1`` are available at
+https://github.com/openstack/rally/tree/master/doc/release_notes/archive
diff --git a/README.rst b/README.rst
@@ -2,6 +2,9 @@
 Rally
 =====
 
+Rally is tool & framework that allows one to write simple plugins and combine
+them in complex tests scenarios that allows to perform all kinds of testing!
+
 Team and repository tags
 ========================
 
@@ -28,14 +31,9 @@ Team and repository tags
 What is Rally
 =============
 
-Rally is a Benchmark-as-a-Service project for OpenStack.
-
-Rally is intended to provide the community with a benchmarking tool that is capable of performing **specific**, **complicated** and **reproducible** test cases on **real deployment** scenarios.
-
-If you are here, you are probably familiar with OpenStack and you also know that it's a really huge ecosystem of cooperative services. When something fails, performs slowly or doesn't scale, it's really hard to answer different questions on "what", "why" and "where" has happened. Another reason why you could be here is that you would like to build an OpenStack CI/CD system that will allow you to improve SLA, performance and stability of OpenStack continuously.
-
-The OpenStack QA team mostly works on CI/CD that ensures that new patches don't break some specific single node installation of OpenStack. On the other hand it's clear that such CI/CD is only an indication and does not cover all cases (e.g. if a cloud works well on a single node installation it doesn't mean that it will continue to do so on a 1k servers installation under high load as well). Rally aims to fix this and help us to answer the question "How does OpenStack work at scale?". To make it possible, we are going to automate and unify all steps that are required for benchmarking OpenStack at scale: multi-node OS deployment, verification, benchmarking & profiling.
-
+Rally is intended to provide a testing framework that is
+capable to perform **specific**, **complicated** and **reproducible**
+test cases on **real deployment** scenarios.
 
 **Rally** workflow can be visualized by the following diagram:
 
@@ -53,18 +51,30 @@ Who Is Using Rally
 Documentation
 =============
 
-`Rally documentation on ReadTheDocs <https://rally.readthedocs.org/en/latest/>`_ is a perfect place to start learning about Rally. It provides you with an **easy** and **illustrative** guidance through this benchmarking tool. For example, check out the `Rally step-by-step tutorial <https://rally.readthedocs.io/en/latest/quick_start/tutorial.html>`_ that explains, in a series of lessons, how to explore the power of Rally in benchmarking your OpenStack clouds.
+`Rally documentation on ReadTheDocs <https://rally.readthedocs.org/en/latest/>`_
+is a perfect place to start learning about Rally. It provides you with an
+**easy** and **illustrative** guidance through this benchmarking tool.
 
+For example, check out the `Rally step-by-step tutorial
+<https://rally.readthedocs.io/en/latest/quick_start/tutorial.html>`_ that
+explains, in a series of lessons, how to explore the power of Rally in
+benchmarking your OpenStack clouds.
 
 Architecture
 ------------
 
 In terms of software architecture, Rally is built of 4 main components:
 
-1. **Server Providers** - provide servers (virtual servers), with ssh access, in one L3 network.
-2. **Deploy Engines** - deploy OpenStack cloud on servers that are presented by **Server Providers**
-3. **Verification** - component that runs tempest (or another specific set of tests) against a deployed cloud, collects results & presents them in human readable form.
-4. **Benchmark engine** - allows to write parameterized benchmark scenarios & run them against the cloud.
+1. **Environment** - one of key component in Rally. It manages and stores
+   information about tested platforms. Env manager is using platform plugins
+   to: create, delete, cleanup, check health, obtain information about
+   platforms.
+2. **Task** component is responsible for executing tests defined in
+   task specs, persisting and reporting results.
+3. **Verification** component allows to wrap subunit-based testing tools and
+   provide complete tool on top of them with allow to do pre configuration,
+   post cleanup as well process and persist results to Rally DB for future use
+   like reporting and results comparing.
 
 Use Cases
 ---------
@@ -77,26 +87,29 @@ There are 3 major high level Rally Use Cases:
 
 Typical cases where Rally aims to help are:
 
-- Automate measuring & profiling focused on how new code changes affect the OS performance;
+- Automate measuring & profiling focused on how new code changes affect the
+  OpenStack performance;
 - Using Rally profiler to detect scaling & performance issues;
 - Investigate how different deployments affect the OS performance:
-	- Find the set of suitable OpenStack deployment architectures;
-	- Create deployment specifications for different loads (amount of controllers, swift nodes, etc.);
+
+    - Find the set of suitable OpenStack deployment architectures;
+    - Create deployment specifications for different loads (amount of
+      controllers, swift nodes, etc.);
 - Automate the search for hardware best suited for particular OpenStack cloud;
 - Automate the production cloud specification generation:
-	- Determine terminal loads for basic cloud operations: VM start & stop, Block Device create/destroy & various OpenStack API methods;
-	- Check performance of basic cloud operations in case of different loads.
 
+    - Determine terminal loads for basic cloud operations: VM start & stop,
+      Block Device create/destroy & various OpenStack API methods;
+    - Check performance of basic cloud operations in case of different loads.
 
 Links
-----------------------
+-----
 
 * Free software: Apache license
 * Documentation: https://rally.readthedocs.org/en/latest/
 * Source: https://git.openstack.org/cgit/openstack/rally
 * Bugs: https://bugs.launchpad.net/rally
 * Step-by-step tutorial: https://rally.readthedocs.io/en/latest/quick_start/tutorial.html
-* RoadMap: https://docs.google.com/a/mirantis.com/spreadsheets/d/16DXpfbqvlzMFaqaXAcJsBzzpowb_XpymaK2aFY2gA2g
 * Launchpad page: https://launchpad.net/rally
 * Gitter chat: https://gitter.im/rally-dev/Lobby
 * Trello board: https://trello.com/b/DoD8aeZy/rally
diff --git a/devstack/lib/rally b/devstack/lib/rally
@@ -84,6 +84,7 @@ fi
 # install_rally() - Collect source and prepare
 function install_rally() {
     setup_develop $RALLY_DIR
+    sudo pip install rally_openstack>=1.1.0
 }
 
 # configure_rally() - Set config files, create data dirs, etc

diff --git a/doc/release_notes/archive/v1.0.0.rst b/doc/release_notes/archive/v1.0.0.rst
@@ -0,0 +1,19 @@
+============
+Rally v1.0.0
+============
+
++------------------+-----------------------+
+| Release date     |     **06/20/2018**    |
++------------------+-----------------------+
+
+.. warning:: There is no in-tree OpenStack plugins anymore. They moved to
+    `the separate project <https://github.com/openstack/rally-openstack>`_.
+
+Starting from the current release all notes are written in a single file
+`CHANGELOG.rst <https://github.com/openstack/rally/tree/master/CHANGELOG.rst>`_
+Follow it for more details.
+
+Thanks
+~~~~~~
+
+ 2 Everybody!
diff --git a/doc/release_notes/latest.rst b/doc/release_notes/latest.rst
@@ -1 +1 @@
-archive/v0.12.1.rst
+archive/v1.0.0.rst
diff --git a/doc/source/plugins/implementation/hook_and_trigger_plugins.rst b/doc/source/plugins/implementation/hook_and_trigger_plugins.rst
@@ -169,7 +169,7 @@ and textual information.
             max: 0
 
 
-hook_example_script.sh generates dummy output in JSON format. Grafical
+hook_example_script.sh generates dummy output in JSON format. Graphical
 information format is the same as for workloads and the same types of
 charts are supported for the hooks.
 

diff --git a/doc/source/task/index.rst b/doc/source/task/index.rst
@@ -366,7 +366,7 @@ CLI References
 ==============
 
 For more information regarding Rally Task Component CLI please proceed
-to `CLI reference <../cli/cli_reference.html#category-task>`_
+to `CLI reference <../cli_reference.html#category-task>`_
 
 .. references:
 

diff --git a/doc/source/verification/overview.rst b/doc/source/verification/overview.rst
@@ -48,7 +48,8 @@ for:
   failed tests from it and so on. Btw, all verification runs arguments are
   stored in the database.
 * **Processing results**. Rally DataBase stores all `verifications
-  <link-to-glossary>`_ and you can obtain unified (across different verifiers)
+  <../overview/glossary.html#verification>`_
+  and you can obtain unified (across different verifiers)
   results at any time. You can find a verification run summary there, run
   arguments which were used, error messages and etc. Comparison mechanism for
   several verifications is available too. Verification reports can be generated

diff --git a/doc/specs/implemented/deployment_type.rst b/doc/specs/implemented/deployment_type.rst
@@ -15,8 +15,8 @@ unbound it from OpenStack.
 Problem description
 ===================
 
-Rally is able to examine only system that use Keystone as a authentication
-services, which limits sphere where Rally is suitable.
+Rally is able to examine only system that use Keystone as an
+authentication service, which limits sphere where Rally is suitable.
 
 At the moment to run Rally Task or Rally Verify you must specify OpenStack
 deployment which contains credentials of it. These credentials are used in

diff --git a/doc/specs/in-progress/cleanup_refactoring.rst b/doc/specs/in-progress/cleanup_refactoring.rst
@@ -133,7 +133,7 @@ Alternatives
   the tenants, regardless of resource naming, so we only need to keep track of
   Rally tenants (naming could be a solution here) and resources in admin
   tenant. In this case, we need to think about a case where Rally needs to
-  cleanup some resources from a existing tenant while leaving the rest
+  cleanup some resources from an existing tenant while leaving the rest
   available.
 
 * Use/enhance Tempest cleanup command (tempest/cmd/cleanup.py). Compare

diff --git a/etc/rally.bash_completion b/etc/rally.bash_completion
@@ -44,7 +44,7 @@ _rally()
     OPTS["plugin_show"]="--name --platform"
     OPTS["task_abort"]="--uuid --soft"
     OPTS["task_delete"]="--force --uuid"
-    OPTS["task_detailed"]="--uuid --iterations-data"
+    OPTS["task_detailed"]="--uuid --iterations-data --filter-by"
     OPTS["task_export"]="--uuid --type --to"
     OPTS["task_import"]="--file --deployment --tag"
     OPTS["task_list"]="--deployment --all-deployments --status --tag --uuids-only"
@@ -105,4 +105,4 @@ _rally()
     return 0
 }
 
-complete -o filenames -F _rally rally
+complete -o filenames -F _rally rally