|
|
(43 intermediate revisions by 7 users not shown) |
Line 1: |
Line 1: |
− | = Rally setup =
| |
| | | |
− | == Rally with DevStack all in one installation ==
| + | <big>'''Rally wiki documentation is obsolete.'''</big> |
− | An alternative to manual Rally installation is to use it as a part of DevStack. The ''contrib/devstack/'' directory of the Rally repository contains the files necessary to integrate Rally with DevStack. These files are used below while configuring DevStack.
| |
| | | |
− | To install:
| + | ''Everything moved to https://rally.readthedocs.org'' |
| | | |
− | DEVSTACK_DIR=.../path/to/devstack
| + | Here is [https://rally.readthedocs.org/en/latest/install.html Rally Installation Guide] |
− | cp lib/rally ${DEVSTACK_DIR}/lib
| |
− | cp extras.d/70-rally.sh ${DEVSTACK_DIR}/extras.d
| |
− | | |
− | To configure DevStack to run Rally:
| |
− | | |
− | cd ${DEVSTACK_DIR}
| |
− | echo "enable_service rally" >> localrc
| |
− | | |
− | Finally, run DevStack as usually:
| |
− | | |
− | ./stack.sh
| |
− | | |
− | | |
− | | |
− | == Manual installation ==
| |
− | | |
− | === Prerequisites ===
| |
− | Start with installing some requirements that Rally needs to be set up correctly. The specific requirements depend on the environment you are going to install Rally in:
| |
− | | |
− | '''Ubuntu'''
| |
− | sudo apt-get update
| |
− | sudo apt-get install libpq-dev git-core python-dev libevent-dev libssl-dev python-pip
| |
− | sudo pip install pbr
| |
− | | |
− | '''CentOS'''
| |
− | sudo yum install gcc git-core postgresql-libs python-devel libevent-devel openssl-devel
| |
− | #install pip on centos:
| |
− | curl -o /tmp/ez_setup.py https://sources.rhodecode.com/setuptools/raw/bootstrap/ez_setup.py
| |
− | sudo /usr/bin/python /tmp/ez_setup.py
| |
− | sudo /usr/bin/easy_install pip
| |
− | sudo rm setuptools-*.tar.gz
| |
− | sudo pip install -i https://pypi.rhodecode.com/ --upgrade pip
| |
− | sudo pip install pbr
| |
− | | |
− | '''VirtualEnv'''
| |
− | | |
− | Another option is to install Rally in virtualenv; you should then install this package, create a virtualenv and activate it:
| |
− | | |
− | sudo pip install -U virtualenv
| |
− | virtualenv .venv
| |
− | . .venv/bin/activate # NOTE: Make sure that your current shell is either bash or zsh (otherwise it will fail)
| |
− | sudo pip install pbr
| |
− | | |
− | === Installing Rally ===
| |
− | The next step is to clone & install rally:
| |
− | | |
− | git clone https://github.com/stackforge/rally.git && cd rally
| |
− | python setup.py install
| |
− | | |
− | Now you are ready to configure Rally (in oder for it to be able to use the database):
| |
− | | |
− | sudo mkdir /etc/rally
| |
− | sudo cp etc/rally/rally.conf.sample /etc/rally/rally.conf
| |
− | sudo vim /etc/rally/rally.conf
| |
− | # Change the ''"connection"'' parameter in line 145, e.g. to ''connection="~/.rally/"'' (or any other place)
| |
− | | |
− | After the installation step has been completed, you need to create the Rally database:
| |
− | | |
− | rally-manage db recreate
| |
− | | |
− | And finally you are able [https://wiki.openstack.org/wiki/Rally/HowTo to use it]
| |
− | | |
− | | |
− | | |
− | == Running Rally's Unit Tests==
| |
− | Rally should be tested with tox, but is not compatible with the current version of tox, so install tox 1.6.1 then run it.
| |
− | | |
− | pip install 'tox<=1.6.1'
| |
− | tox
| |