zuul
/
zuul
Code Issues Proposed changes

Explicitly callout ZooKeeper as ext dependency 

ZooKeeper is mentioned under the Nodepool external dependency
section, but really needs to be in its own section to make
it more easily identifiable as an external system.

Change-Id: I8dea96eee7062769f0ce72c463c48fc8dfa329ad
This commit is contained in:
David Shrewsbury 2019-01-23 09:32:01 -05:00
parent 25f4f7a45c
commit c43ff013f2
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/source/admin/installation.rst
View File

@ -84,11 +84,14 @@ ensure you have Nodepool installed and any images you require built.
Zuul only makes one requirement of these nodes: that it be able to log
in given a username and ssh private key.
ZooKeeper
~~~~~~~~~
.. TODO: SpamapS any zookeeper config recommendations?
Nodepool uses Zookeeper to communicate internally among its
Nodepool uses ZooKeeper to communicate internally among its
components, and also to communicate with Zuul. You can run a simple
single-node Zookeeper instance, or a multi-node cluster. Ensure that
single-node ZooKeeper instance, or a multi-node cluster. Ensure that
the host running the Zuul scheduler has access to the cluster.
Ansible