zuul
/
nodepool
Code Issues Proposed changes
Manage a pool of nodes for a distributed test infrastructure
1,737 Commits 1 Branch 26 Tags 34 MiB
Python 98.2%
Shell 1.1%
Dockerfile 0.4%
Jinja 0.3%
Go to file
David Shrewsbury afa66c7f58 Only DeletedNodeWorker should delete nodes 
The proper/expected way to delete a node is to set its state to
DELETING and then allow the DeletedNodeWorker to actually delete
the instance and zookeeper node. Not doing it this way introduces
the race seen in commit 59d636740a.
This change fixes all the places (other than the nodepool command
to delete --now) where we were not doing it properly.

Change-Id: I1962ad672d3d5e646ed29beb07b720fc53d604ed
 		2018-02-20 08:27:09 -05:00
devstack Add opensuse-tumbleweed to nodepool dsvm testing 2018-02-15 20:16:36 -05:00
doc Store build logs automatically 2018-02-09 07:50:20 -08:00
nodepool Only DeletedNodeWorker should delete nodes 2018-02-20 08:27:09 -05:00
playbooks Avoid tools/nodepool-integration-setup.sh from zuul 2018-02-16 08:56:18 +01:00
tools Merge "Fix nodepool-zuul-functional" 2018-02-20 09:51:14 +00:00
.gitignore Add files for zuul-nodepool integration test 2017-01-24 09:46:08 -08:00
.gitreview Replace master with feature/zuulv3 2018-01-18 10:13:57 -08:00
.testr.conf Add a test for subnodes 2014-03-31 09:22:00 -07:00
.zuul.yaml Merge "Fix nodepool-zuul-functional" 2018-02-20 09:51:14 +00:00
LICENSE license: remove dos line break 2018-01-19 00:30:22 +00:00
README.rst Rename nodepoold to nodepool-launcher 2017-03-29 09:28:33 -04:00
bindep.txt Ensure only python3 is installed with bindep.txt 2018-02-14 12:19:16 -05:00
requirements.txt requirements: remove paramiko <2.0 cap 2017-12-19 13:54:22 -05:00
setup.cfg update supported python version in setup.cfg 2018-02-02 04:30:06 +00:00
setup.py Bump pbr requirements to >=1.3 2015-09-14 16:19:13 -04:00
test-requirements.txt Block sphinx 1.6 2017-05-16 16:35:51 -05:00
tox.ini Update tox docs environment to match build-sphinx-docs 2018-02-07 17:55:58 -06: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

Make sure you have pip installed:

wget https://bootstrap.pypa.io/get-pip.py
sudo python get-pip.py

Install dependencies:

sudo pip install bindep
sudo apt-get install $(bindep -b nodepool)

mkdir src
cd ~/src
git clone git://git.openstack.org/openstack-infra/system-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/system-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/system-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.

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

export NODEPOOL_SSH_KEY=`cat ~/.ssh/id_rsa.pub | awk '{print $2}'`

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
nodepool-launcher -d -c tools/fake.yaml

All logging ends up in stdout.

Use the following tool to check on progress:

nodepool image-list