Robert Collins e081b96221 Don't load system host keys.
There are three places that nodepool connects to hosts:
 - to bootstrap where by definition any existing host key must be wrong
 - to bring up a snapshot where again any existing host key must be wrong
 - to check a node is still running

Nodepool itself doesn't save the host key, so the third case will
typically warn as well, or if an administrator logged into a node from
the nodepool user account cause a failure.

As such it seems that system host key validation is not useful and
just serves to cause failures when a stale key is present.

Change-Id: I074314d61b5c520bdd67da24bfd2a8e626da0dc5
2014-01-20 13:23:04 +13:00
2014-01-20 13:23:04 +13:00
2013-08-15 09:47:23 -07:00
2013-08-13 17:10:06 +00:00
2013-10-14 12:33:27 -03:00
2013-09-03 09:27:04 -07:00
2013-08-15 09:47:23 -07:00
2013-12-10 08:42:24 -08:00
2013-09-13 11:09:15 -05:00

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 install git mysql-server libmysqlclient-dev g++ python-dev libzmq-dev
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;
Description
Manage a pool of nodes for a distributed test infrastructure
Readme 35 MiB
Languages
Python 98.3%
Shell 1.1%
Dockerfile 0.3%
Jinja 0.3%