James E. Blair 49da9c0c92 Have buildZooKeeperHosts accept a config object
Add a new ZooKeeperServerConnection class which represents the
information needed to connect to a server, and then have the
config parser create that object instead of its own internal
representation of the connection.  Modify the ZooKeeper class
to accept this new object to specify what connection(s) it
should use.

The new class implements the equality operator so that it may
still be used in the same way as other ConfigValue objects (that
is, checking to see if the configuration has been updated).

Change-Id: I4cfa3866e3b0ae2a730c1e624570cd7025901808
2016-08-18 13:52:10 -07:00
2014-03-31 09:22:00 -07:00
2015-12-10 12:54:23 -05:00
2015-10-29 10:44:41 +05:30
2016-07-14 15:10:38 -07:00
2016-01-12 15:33:01 -08:00
2015-09-14 16:19:13 -04:00
2016-08-15 10:27:07 -07:00
2016-07-07 16:32:06 -04: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 update
sudo apt-get -qy install git mysql-server libmysqlclient-dev g++\
                 python-dev python-pip libffi-dev libssl-dev qemu-utils\
                 libxml2-dev libxslt1-dev python-lxml
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.

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;

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.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%