Manage a pool of nodes for a distributed test infrastructure
Go to file
James E. Blair 86e5ff9ed6 Include backing node request id in metastatic log
When we are satisfying a metastatic request by creating a new backing
node, we can end up logging the message:

  Assigned node 001 to backing node None slot 0

Which is not helpful when trying to find out which backing node 001
was assigned to.  We don't know the node id yet since it hasn't been
created, but in this case we can log the request id.  That can then
be associated with the actual node id in later log entries.

Change-Id: I409917319ab592c997f47e7f69636860fad8c2c9
2022-06-30 16:05:21 -07:00
contrib/statsd_exporter Add statsd_exporter mapping 2019-09-29 09:30:45 +00:00
doc Add nodepool.image_build_requests metric 2022-06-21 14:52:53 -07:00
etc Merge "Add systemd drop-in file for CentOS 7" 2018-05-09 18:09:54 +00:00
nodepool Include backing node request id in metastatic log 2022-06-30 16:05:21 -07:00
playbooks Switch to using openstackclient 2022-03-27 14:33:42 +02:00
releasenotes/notes Add nodepool.image_build_requests metric 2022-06-21 14:52:53 -07:00
tools Update ZooKeeper class connection methods 2022-06-29 07:46:34 -07:00
.coveragerc Switch to stestr 2018-04-26 11:52:17 -05:00
.dockerignore Build images with Dockerfile instead of pbrx 2019-01-24 16:11:12 +00:00
.gitignore Require TLS 2021-02-19 18:42:33 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:25:31 +00:00
.stestr.conf Switch to stestr 2018-04-26 11:52:17 -05:00
.zuul.yaml Pin minikube to 1.25.2 2022-06-23 10:18:44 -07:00
Dockerfile Merge "Add binutils to nodepool builder docker image" 2022-04-22 05:05:04 +00:00
LICENSE license: remove dos line break 2018-01-19 00:30:22 +00:00
README.rst Update devstack settings and docs for opendev 2019-04-23 13:03:21 +00:00
TESTING.rst Add more detail to TESTING.rst 2020-06-09 08:48:43 -07:00
bindep.txt Update Docker and bindep for Bullseye base images 2021-10-26 11:11:19 +11:00
requirements.txt Temporarily pin OpenStackSDK before 0.99 2022-06-01 20:27:04 +00:00
setup.cfg Set python metadata in setup.cfg to >=3.8 2022-05-06 13:48:58 -07:00
setup.py Bump pbr requirements to >=1.3 2015-09-14 16:19:13 -04:00
test-requirements.txt AWS tests: cleanup image deletion checking 2022-04-28 14:16:16 +10:00
tox.ini Require TLS 2021-02-19 18:42:33 +00:00

README.rst

Nodepool

Nodepool is a system for managing test node resources. It supports launching single-use test nodes from cloud providers as well as managing access to pre-defined pre-existing nodes. Nodepool is part of a suite of tools that form a comprehensive test system, including Zuul.

The latest documentation for Nodepool is published at: https://zuul-ci.org/docs/nodepool/

The latest documentation for Zuul is published at: https://zuul-ci.org/docs/zuul/

Getting Help

There are two Zuul-related mailing lists:

zuul-announce

A low-traffic announcement-only list to which every Zuul operator or power-user should subscribe.

zuul-discuss

General discussion about Zuul, including questions about how to use it, and future development.

You will also find Zuul developers in the #zuul channel on Freenode IRC.

Contributing

To browse the latest code, see: https://opendev.org/zuul/nodepool To clone the latest code, use git clone https://opendev.org/zuul/nodepool

Bugs are handled at: https://storyboard.openstack.org/#!/project/zuul/nodepool

Code reviews are handled by gerrit at https://review.opendev.org

After creating a Gerrit account, use git review to submit patches. Example:

# Do your commits
$ git review
# Enter your username if prompted

Join #zuul on Freenode to discuss development or usage.

License

Nodepool is free software, licensed under the Apache License, version 2.0.

Python Version Support

Nodepool requires Python 3. It does not support Python 2.