system-config/doc/source/nodepool.rst
Clark Boylan 0f4b0fae64 Redo slave manifests for clarity and correctness.
The differences between openstack_project::slave,
openstack_project::slave_template, and openstack_project::bare_slave
were not always clear. Keep openstack_project::slave as the default long
running slave manifest, but replace slave_template with a
single_use_slave.pp to make it clear where single use slave config
begins. Add the ability to toggle automatic upgrades and jenkins sudo
rights to this new manifest. Finally, add a more verbose comment to
bare_slave explaining what it is useful for (having a jenkins like slave
host that doesn't need a firewall or ntp or automatic upgrades).

Change-Id: I3989c9e6ad9469f441ca5d3627f7b3b704d8a8da
2014-01-30 10:37:36 -08:00

35 lines
997 B
ReStructuredText

:title: Nodepool
.. _nodepool:
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.
At a Glance
===========
:Hosts:
* nodepool.openstack.org
:Puppet:
* :file:`modules/nodepool/`
* :file:`modules/openstack_project/manifests/single_use_slave.pp`
:Configuration:
* :file:`modules/openstack_project/templates/nodepool/nodepool.yaml.erb`
* :file:`modules/openstack_project/files/nodepool/scripts/`
:Projects:
* https://git.openstack.org/openstack-infra/nodepool
:Bugs:
* http://bugs.launchpad.net/openstack-ci
Overview
========
Once per day, for every image type (and provider) configured by nodepool, a new
image with cached data for use by devstack. Nodepool spins up new instances
and tears down old as tests are queued up and completed, always maintaining a
consistant number of available instances for tests up to the set limits of the
CI infrastructure.