Fix nodepool algorithm formatting in zuulv3 spec

Change-Id: Ief6c8af0b6ba35903041be853273306e4f903d94
This commit is contained in:
James E. Blair 2017-02-28 13:35:06 -08:00
parent 26d8591e5f
commit 57e1621d7f
1 changed files with 8 additions and 8 deletions

View File

@ -134,14 +134,14 @@ the same provider.
A simple algorithm which does not require that any launcher know about
any other launchers is:
# Obtain next request
# If image not available, decline
# If request > quota, decline
# If request < quota and request > available nodes (due to current
usage), begin satisfying the request and do not process further
requests until satisfied
# If request < quota and request < available nodes, satisfy the
request and continue processing further requests
#. Obtain next request
#. If image not available, decline
#. If request > quota, decline
#. If request < quota and request > available nodes (due to current
usage), begin satisfying the request and do not process further
requests until satisfied
#. If request < quota and request < available nodes, satisfy the
request and continue processing further requests
Since Nodepool consists of multiple launchers, each of which is only
aware of its own configuration, there is no single component of the