openstack/rally
Code Issues Proposed changes

Update stackforge to openstack

Browse Source 
Found the issue while configuring devstack,
the libs were having stackforge location.

Change-Id: Ibd93eccb7d89cb6b06a1e8cc1d7d6f65ce52f352
This commit is contained in:
Swapnil Kulkarni 2015-04-20 13:59:43 +05:30
parent cb153fc13f
commit 3fb277d122
20 changed files with 32 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contrib/devstack/lib/rally
View File

@ -22,7 +22,7 @@ set +o xtrace
# --------
# Set up default repos
RALLY_REPO=${RALLY_REPO:-${GIT_BASE}/stackforge/rally.git}
RALLY_REPO=${RALLY_REPO:-${GIT_BASE}/openstack/rally.git}
RALLY_BRANCH=${RALLY_BRANCH:-master}
# Set up default directories

4
doc/release_notes/v0.0.3.rst
View File

@ -53,7 +53,7 @@ New Features & API changes
rally.conf option is deprecated
Like in this sample
https://github.com/stackforge/rally/blob/14d0b5ba0c75ececfdb6a6c121d9cf2810571f77/samples/deployments/existing.json#L11-L12
https://github.com/openstack/rally/blob/14d0b5ba0c75ececfdb6a6c121d9cf2810571f77/samples/deployments/existing.json#L11-L12
Specs
@ -64,7 +64,7 @@ Specs
This spec describes new task input format that will allow us to generate
multi scenario load which is crucial for HA and more real life testing:
https://github.com/stackforge/rally/blob/master/doc/specs/in-progress/new_rally_input_task_format.rst
https://github.com/openstack/rally/blob/master/doc/specs/in-progress/new_rally_input_task_format.rst
Plugins

6
doc/source/concepts.rst
View File

@ -78,7 +78,7 @@ Note that inside each scenario configuration, the benchmark scenario is actually
Developer's view
^^^^^^^^^^^^^^^^
From the developer's perspective, a benchmark scenario is a method marked by a **@scenario** decorator and placed in a class that inherits from the base `Scenario <https://github.com/stackforge/rally/blob/master/rally/benchmark/scenarios/base.py#L40>`_ class and located in some subpackage of `rally.benchmark.scenarios <https://github.com/stackforge/rally/tree/master/rally/benchmark/scenarios>`_. There may be arbitrary many benchmark scenarios in a scenario class; each of them should be referenced to (in the task configuration file) as *ScenarioClassName.method_name*.
From the developer's perspective, a benchmark scenario is a method marked by a **@scenario** decorator and placed in a class that inherits from the base `Scenario <https://github.com/openstack/rally/blob/master/rally/benchmark/scenarios/base.py#L40>`_ class and located in some subpackage of `rally.benchmark.scenarios <https://github.com/openstack/rally/tree/master/rally/benchmark/scenarios>`_. There may be arbitrary many benchmark scenarios in a scenario class; each of them should be referenced to (in the task configuration file) as *ScenarioClassName.method_name*.
In a toy example below, we define a scenario class *MyScenario* with one benchmark scenario *MyScenario.scenario*. This benchmark scenario tests the performance of a sequence of 2 actions, implemented via private methods in the same class. Both methods are marked with the **@atomic_action_timer** decorator. This allows Rally to handle those actions in a special way and, after benchmarks complete, show runtime statistics not only for the whole scenarios, but for separate actions as well.
@ -165,7 +165,7 @@ Also, all scenario runners can be provided (again, through the **"runner"** sect
Developer's view
^^^^^^^^^^^^^^^^
It is possible to extend Rally with new Scenario Runner types, if needed. Basically, each scenario runner should be implemented as a subclass of the base `ScenarioRunner <https://github.com/stackforge/rally/blob/master/rally/benchmark/runners/base.py#L137>`_ class and located in the `rally.benchmark.runners package <https://github.com/stackforge/rally/tree/master/rally/benchmark/runners>`_. The interface each scenario runner class should support is fairly easy:
It is possible to extend Rally with new Scenario Runner types, if needed. Basically, each scenario runner should be implemented as a subclass of the base `ScenarioRunner <https://github.com/openstack/rally/blob/master/rally/benchmark/runners/base.py#L137>`_ class and located in the `rally.benchmark.runners package <https://github.com/openstack/rally/tree/master/rally/benchmark/runners>`_. The interface each scenario runner class should support is fairly easy:
.. parsed-literal::
@ -260,7 +260,7 @@ In the example below, the **"users" context** specifies that the *"NovaServers.b
Developer's view
^^^^^^^^^^^^^^^^
From the developer's view, contexts management is implemented via **Context classes**. Each context type that can be specified in the task configuration file corresponds to a certain subclass of the base [https://github.com/stackforge/rally/blob/master/rally/benchmark/context/base.py **Context**] class, located in the [https://github.com/stackforge/rally/tree/master/rally/benchmark/context **rally.benchmark.context**] module. Every context class should implement a fairly simple **interface**:
From the developer's view, contexts management is implemented via **Context classes**. Each context type that can be specified in the task configuration file corresponds to a certain subclass of the base [https://github.com/openstack/rally/blob/master/rally/benchmark/context/base.py **Context**] class, located in the [https://github.com/openstack/rally/tree/master/rally/benchmark/context **rally.benchmark.context**] module. Every context class should implement a fairly simple **interface**:
.. parsed-literal::

2
doc/source/contribute.rst
View File

@ -56,7 +56,7 @@ Several Linux distributions (notably Fedora 16 and Ubuntu 12.04) are also starti
.. code-block:: none
git clone git@github.com:stackforge/rally.git
git clone git@github.com:openstack/rally.git
6. Checkout a new branch to hack on:

6
doc/source/install.rst
View File

@ -23,7 +23,7 @@ Automated installation
.. code-block:: none
git clone https://git.openstack.org/stackforge/rally
git clone https://git.openstack.org/openstack/rally
./rally/install_rally.sh
**Notes:** The installation script should be run as root or as a normal user using **sudo**. Rally requires either the Python 2.6 or the Python 2.7 version.
@ -33,7 +33,7 @@ Automated installation
.. code-block:: none
git clone https://git.openstack.org/stackforge/rally
git clone https://git.openstack.org/openstack/rally
./rally/install_rally.sh -v
@ -52,7 +52,7 @@ It is also possible to install Rally with DevStack. First, clone the correspondi
.. code-block:: none
git clone https://git.openstack.org/openstack-dev/devstack
git clone https://github.com/stackforge/rally
git clone https://github.com/openstack/rally
Then, configure DevStack to run Rally:

2
doc/source/plugins.rst
View File

@ -387,4 +387,4 @@ You can refer to your scenario runner in the benchmark task configuration files
Different plugin samples are available `here <https://github.com/stackforge/rally/tree/master/samples/plugins>`_.
Different plugin samples are available `here <https://github.com/openstack/rally/tree/master/samples/plugins>`_.

2
doc/source/project_info.rst
View File

@ -20,7 +20,7 @@ Project Info
Useful links
------------
- `Source code <https://github.com/stackforge/rally>`_
- `Source code <https://github.com/openstack/rally>`_
- `Rally road map <https://docs.google.com/a/mirantis.com/spreadsheets/d/16DXpfbqvlzMFaqaXAcJsBzzpowb_XpymaK2aFY2gA2g/edit#gid=0>`_
- `Project space <http://launchpad.net/rally>`_
- `Bugs <https://bugs.launchpad.net/rally>`_

2
doc/source/tutorial/step_0_installation.rst
View File

@ -22,7 +22,7 @@ Installing Rally is very simple. Just execute the following commands:
.. code-block:: none
git clone https://git.openstack.org/stackforge/rally
git clone https://git.openstack.org/openstack/rally
./rally/install_rally.sh
**Notes:** The installation script should be run as root or as a normal user using **sudo**. Rally requires either the Python 2.6 or the Python 2.7 version.

6
doc/source/tutorial/step_1_setting_up_env_and_running_benchmark_from_samples.rst
View File

@ -26,7 +26,7 @@ We assume that you have a :ref:`Rally installation <tutorial_step_0_installation
Registering an OpenStack deployment in Rally
--------------------------------------------
First, you have to provide Rally with an Openstack deployment it is going to benchmark. This should be done either through `OpenRC files <http://docs.openstack.org/user-guide/content/cli_openrc.html>`_ or through deployment `configuration files <https://github.com/stackforge/rally/tree/master/samples/deployments>`_. In case you already have an *OpenRC*, it is extremely simple to register a deployment with the *deployment create* command:
First, you have to provide Rally with an Openstack deployment it is going to benchmark. This should be done either through `OpenRC files <http://docs.openstack.org/user-guide/content/cli_openrc.html>`_ or through deployment `configuration files <https://github.com/openstack/rally/tree/master/samples/deployments>`_. In case you already have an *OpenRC*, it is extremely simple to register a deployment with the *deployment create* command:
.. code-block:: none
@ -40,7 +40,7 @@ First, you have to provide Rally with an Openstack deployment it is going to ben
Using deployment : <Deployment UUID>
...
Alternatively, you can put the information about your cloud credentials into a JSON configuration file (let's call it `existing.json <https://github.com/stackforge/rally/blob/master/samples/deployments/existing.json>`_). The *deployment create* command has a slightly different syntax in this case:
Alternatively, you can put the information about your cloud credentials into a JSON configuration file (let's call it `existing.json <https://github.com/openstack/rally/blob/master/samples/deployments/existing.json>`_). The *deployment create* command has a slightly different syntax in this case:
.. code-block:: none
@ -81,7 +81,7 @@ Finally, the *deployment check* command enables you to verify that your current
Benchmarking
------------
Now that we have a working and registered deployment, we can start benchmarking it. The sequence of benchmarks to be launched by Rally should be specified in a *benchmark task configuration file* (either in *JSON* or in *YAML* format). Let's try one of the sample benchmark tasks available in `samples/tasks/scenarios <https://github.com/stackforge/rally/tree/master/samples/tasks/scenarios>`_, say, the one that boots and deletes multiple servers (*samples/tasks/scenarios/nova/boot-and-delete.json*):
Now that we have a working and registered deployment, we can start benchmarking it. The sequence of benchmarks to be launched by Rally should be specified in a *benchmark task configuration file* (either in *JSON* or in *YAML* format). Let's try one of the sample benchmark tasks available in `samples/tasks/scenarios <https://github.com/openstack/rally/tree/master/samples/tasks/scenarios>`_, say, the one that boots and deletes multiple servers (*samples/tasks/scenarios/nova/boot-and-delete.json*):
.. code-block:: none

2
doc/source/tutorial/step_6_discovering_more_benchmark_scenarios.rst
View File

@ -23,7 +23,7 @@ Scenarios in the Rally repository
Rally currently comes with a great collection of benchmark scenarios that use the API of different OpenStack projects like **Keystone**, **Nova**, **Cinder**, **Glance** and so on. The good news is that you can combine multiple benchmark scenarios in one task to benchmark your cloud in a comprehensive way.
First, let's see what scenarios are available in Rally. One of the ways to discover these scenario is just to inspect their `source code <https://github.com/stackforge/rally/tree/master/rally/benchmark/scenarios>`_.
First, let's see what scenarios are available in Rally. One of the ways to discover these scenario is just to inspect their `source code <https://github.com/openstack/rally/tree/master/rally/benchmark/scenarios>`_.
Rally built-in search engine
----------------------------

2
doc/source/tutorial/step_7_deploying_openstack.rst
View File

@ -18,7 +18,7 @@
Step 7. Deploying OpenStack from Rally
======================================
Along with supporting already existing OpenStack deployments, Rally itself can **deploy OpenStack automatically** by using one of its *deployment engines*. Take a look at other `deployment configuration file samples <https://github.com/stackforge/rally/tree/master/samples/deployments>`_. For example, *devstack-in-existing-servers.json* is a deployment configuration file that tells Rally to deploy OpenStack with **Devstack** on the existing servers with given credentials:
Along with supporting already existing OpenStack deployments, Rally itself can **deploy OpenStack automatically** by using one of its *deployment engines*. Take a look at other `deployment configuration file samples <https://github.com/openstack/rally/tree/master/samples/deployments>`_. For example, *devstack-in-existing-servers.json* is a deployment configuration file that tells Rally to deploy OpenStack with **Devstack** on the existing servers with given credentials:
.. code-block:: none

2
doc/user_stories/nova/boot_server.rst
View File

@ -67,7 +67,7 @@ https://review.openstack.org/#/c/96300/
**Deployment**
Rally was deployed for cluster using `ExistingCloud <https://github.com/stackforge/rally/blob/master/samples/deployments/existing.json>`_ type of deployment.
Rally was deployed for cluster using `ExistingCloud <https://github.com/openstack/rally/blob/master/samples/deployments/existing.json>`_ type of deployment.
**Server flavor** ::

2
optional-requirements.txt
View File

@ -1,2 +1,2 @@
git+git://github.com/stackforge/python-mistralclient.git
python-muranoclient>=0.5.5
python-muranoclient>=0.5.5

2
rally-jobs/README.rst
View File

@ -37,4 +37,4 @@ Useful links
* About plugins: https://rally.readthedocs.org/en/latest/plugins.html
* Plugin samples: https://github.com/stackforge/rally/tree/master/samples/plugins
* Plugin samples: https://github.com/openstack/rally/tree/master/samples/plugins

2
rally/ui/templates/base.mako
View File

@ -40,7 +40,7 @@
<div class="header">
<div class="content-wrap">
<a href="https://github.com/stackforge/rally">Rally</a>&nbsp;
<a href="https://github.com/openstack/rally">Rally</a>&nbsp;
<span><%block name="header_text"/></span>
</div>
</div>

10
samples/tasks/README.rst
View File

@ -69,22 +69,22 @@ ScanarioClass should be a subclass of the base Scenario class
and scenario_method specifies what benchmark task should be run. Section
"args" is also related to scenario. To learn more about scenarios
configuration, see samples in `samples/tasks/scenarios
<https://github.com/stackforge/rally/tree/master/samples/tasks/scenarios>`_.
<https://github.com/openstack/rally/tree/master/samples/tasks/scenarios>`_.
Section "runners" specifies the way, how task should be run. To learn
more about runners configurations, see samples in `samples/tasks/runners
<https://github.com/stackforge/rally/tree/master/samples/tasks/runners>`_.
<https://github.com/openstack/rally/tree/master/samples/tasks/runners>`_.
Section "context" defines different types of environments in which task can
be launched. Look at `samples/tasks/contexts
<https://github.com/stackforge/rally/tree/master/samples/tasks/contexts>`_
<https://github.com/openstack/rally/tree/master/samples/tasks/contexts>`_
for samples.
Section "sla" defines details for determining compliance with contracted values
such as maximum error rate or minimum response time.
Look at `samples/tasks/sla
<https://github.com/stackforge/rally/tree/master/samples/tasks/sla>`_ for
<https://github.com/openstack/rally/tree/master/samples/tasks/sla>`_ for
samples.
See a `detailed description of benchmark scenarios, contexts & runners
<https://github.com/stackforge/rally/tree/master/source/concepts.rst>`_.
<https://github.com/openstack/rally/tree/master/source/concepts.rst>`_.

2
samples/tasks/runners/README.rst
View File

@ -5,5 +5,5 @@ This directory contains task runners conficuration samples.
Samples here are presented with methods of Dummy scenario. To see samples
of usage other scenarios, go to `samples/tasks/scenarios
<https://github.com/stackforge/rally/tree/master/samples/tasks/scenarios>`_.
<https://github.com/openstack/rally/tree/master/samples/tasks/scenarios>`_.

2
samples/tasks/scenarios/README.rst
View File

@ -7,5 +7,5 @@ from "args" section to actual values for your deployment.
Samples here are presented with constant runner. To see samples of using
other runners, go to `samples/tasks/runners
<https://github.com/stackforge/rally/tree/master/samples/tasks/runners>`_.
<https://github.com/openstack/rally/tree/master/samples/tasks/runners>`_.

4
tests/ci/rally-gate/index.mako
View File

@ -43,7 +43,7 @@
<h2>About Rally</h2>
<p>Rally is benchmark system for OpenStack:</p>
<ul>
<li><a href="https://github.com/stackforge/rally">Git repository</a>
<li><a href="https://github.com/openstack/rally">Git repository</a>
<li><a href="https://rally.readthedocs.org/en/latest/">Documentation</a>
<li><a href="https://wiki.openstack.org/wiki/Rally/HowTo">How to use Rally (locally)</a>
<li><a href="https://wiki.openstack.org/wiki/Rally/RallyGates">How to add Rally job to your project</a>
@ -53,7 +53,7 @@
<ol>
<li>Fetch rally task from <a href="rally-plot/task.txt">here</a></li>
<li>Fetch rally plugins from <a href="rally-plot/plugins.tar.gz">here</a></li>
<li>Install OpenStack and Rally using <a href="https://github.com/stackforge/rally/tree/master/contrib/devstack">this instruction</a></li>
<li>Install OpenStack and Rally using <a href="https://github.com/openstack/rally/tree/master/contrib/devstack">this instruction</a></li>
<li>Unzip plugins and put to <code>.rally/plugins/</code> directory</li>
<li>Run rally task: <code>$ rally task start task.txt</code></li>
</ol>

2
tests/ci/rally-gate/index_verify.mako
View File

@ -127,7 +127,7 @@
<h2>About Rally</h2>
<p>Rally is benchmarking and verification system for OpenStack:</p>
<ul>
<li><a href="https://github.com/stackforge/rally">Git repository</a>
<li><a href="https://github.com/openstack/rally">Git repository</a>
<li><a href="https://rally.readthedocs.org/en/latest/">Documentation</a>
<li><a href="https://wiki.openstack.org/wiki/Rally/HowTo">How to use Rally (locally)</a>
<li><a href="https://wiki.openstack.org/wiki/Rally/RallyGates">How to add Rally job to your project</a>