Manage a pool of nodes for a distributed test infrastructure

Go to file

Clark Boylan 841750fdea Depend on hacking for its dependencies. flake8 does not pin its pep8 and pyflakes dependencies which makes it possible for new sets of rules to suddenly apply whenever either of those projects pushes a new release. Fix this by depending on hacking instead of flake8, pep8, and pyflakes directly. This will keep nodepool in sync with the rest of openstack even if it doesn't use the hacking rules (H*). Change-Id: Ice9198e9439ebcac15e76832835e78f72344425c		2014-03-26 12:39:41 -07:00
doc	Add docs	2014-01-14 01:00:43 +08:00
nodepool	Depend on hacking for its dependencies.	2014-03-26 12:39:41 -07:00
tools	Keep current and previous snapshot images	2014-02-21 13:08:26 -08:00
.gitignore	Ignore vim editor backup and swap files.	2014-01-20 13:23:04 +13:00
.gitreview	Added .gitreview	2013-08-13 17:10:06 +00:00
README.rst	Merge "Readme enhancements"	2014-01-27 22:54:15 +00:00
requirements.txt	Set paramiko version > 1.9.0	2014-03-23 19:36:41 -04:00
setup.cfg	Add a nodepool command	2013-09-03 09:27:04 -07:00
setup.py	Initial commit	2013-08-15 09:47:23 -07:00
test-requirements.txt	Depend on hacking for its dependencies.	2014-03-26 12:39:41 -07:00
tox.ini	Ignore hacking warnings	2013-09-13 11:09:15 -05:00

README.rst

Nodepool

Nodepool is a service used by the OpenStack CI team to deploy and manage a pool of devstack images on a cloud server for use in OpenStack project testing.

Developer setup

Install dependencies:

sudo apt-get -qy install git mysql-server libmysqlclient-dev g++ python-dev libzmq-dev python-pip
mkdir src
cd ~/src
git clone git://git.openstack.org/openstack-infra/config
git clone git://git.openstack.org/openstack-infra/nodepool
cd nodepool
sudo pip install -U -r requirements.txt
sudo pip install -e .

If you're testing a specific patch that is already in gerrit, you will also want to install git-review and apply that patch while in the nodepool directory, ie:

git review -x XXXXX

Create or adapt a nodepool yaml file. You can adapt an infra/config one, or fake.yaml as desired. Note that fake.yaml's settings won't Just Work - consult ./modules/openstack_project/templates/nodepool/nodepool.yaml.erb in the infra/config tree to see a production config.

If the cloud being used has no default_floating_pool defined in nova.conf, you will need to define a pool name using the nodepool yaml file to use floating ips.

Set up database:

mysql -u root

mysql> create database nodepool;
mysql> GRANT ALL ON nodepool.* TO 'nodepool'@'localhost';
mysql> flush privileges;

Export variable for your ssh key so you can log into the created instances:

export NODEPOOL_SSH_KEY=`cat ~/.ssh/id_rsa.pub`

Start nodepool with a demo config file (copy or edit fake.yaml to contain your data):

export STATSD_HOST=127.0.0.1
export STATSD_PORT=8125
nodepoold -d -c tools/fake.yaml

All logging ends up in stdout.

Use the following tool to check on progress:

nodepool image-list

After each run (the fake nova provider is only in-memory):

mysql> delete from snapshot_image; delete from node;