066942a0ac
When we first started putting nodepool metadata into the server record in OpenStack, we json encoded the data so that we could store a dict into a field that only takes strings. We were also going to teach the ansible OpenStack Inventory about this so that it could read the data out of the groups list. However, ansible was not crazy about accepting "attempt to json decode values in the metadata" since json-encoded values are not actually part of the interface OpenStack expects - which means one of our goals, which is ansible inventory groups based on nodepool information is no longer really a thing. We could push harder on that, but we actually don't need the functionality we're getting from the json encoding. The OpenStack Inventory has supported comma separated lists of groups since before day one. And the other nodepool info we're storing stores and fetches just as easily with 4 different top level keys as it does in a json dict - and is easier to read and deal with when just looking at server records. Finally, nova has a 255 byte limit on size of the value that can be stored, so we cannot grow the information in the nodepool dict indefinitely anyway. Migrate the data to store into nodepool_ variables and a comma separated list for groups. Consume both forms, so that people upgrading will not lose track of existing stock of nodes. Finally, we don't use snapshot_id anymore - so remove it. Change-Id: I2c06dc7c2faa19e27d1fb1d9d6df78da45ffa6dd
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.pyInstall 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 XXXXXCreate 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.
Set up database for interactive testing:
mysql -u root
mysql> create database nodepool;
mysql> GRANT ALL ON nodepool.* TO 'nodepool'@'localhost';
mysql> flush privileges;Set up database for unit tests:
mysql -u root
mysql> grant all privileges on *.* to 'openstack_citest'@'localhost' identified by 'openstack_citest' with grant option;
mysql> flush privileges;
mysql> create database openstack_citest;Note that the script tools/test-setup.sh can be used for the step above.
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
nodepoold -d -c tools/fake.yamlAll logging ends up in stdout.
Use the following tool to check on progress:
nodepool image-listAfter each run (the fake nova provider is only in-memory):
mysql> delete from snapshot_image; delete from node;