From 57e1621d7ff228b19b05f71c5d289e88e29cc2e0 Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Tue, 28 Feb 2017 13:35:06 -0800 Subject: [PATCH] Fix nodepool algorithm formatting in zuulv3 spec Change-Id: Ief6c8af0b6ba35903041be853273306e4f903d94 --- specs/zuulv3.rst | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/specs/zuulv3.rst b/specs/zuulv3.rst index f688d09..782816d 100644 --- a/specs/zuulv3.rst +++ b/specs/zuulv3.rst @@ -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