
Tracking down builder decisions to do (or not do) things is made difficult by not having insight into certain data. Particularly, the upload recency table is used to determine whether or not images should be deleted from a provider. Having that data in debug logs helps tremendously. We also log when we delete the upload znode record and remove the 'stats' portion of ImageUpload str representation because it turns out to not be as useful as I had hoped in the beginning. Change-Id: Ic6e1ea0811879ed8eaf0216ef2a3b68e9380e727
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:
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:
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:
Start nodepool with a demo config file (copy or edit fake.yaml to contain your data):
All logging ends up in stdout.
Use the following tool to check on progress: