From 3a8b975b1459af5bf57e67d1d9ef960d5a756baf Mon Sep 17 00:00:00 2001 From: "Dong H. Ahn" Date: Fri, 29 Oct 2021 22:32:02 -0700 Subject: [PATCH] rfc25: add moldable specification into Jobspec V1 Copy the minimum viable moldable specification from our canonical job spec (RFC14) to job spec version 1 (RFC25). Need to support a moldable jobspec including resources.count.min both within flux-core and fluxion in order to enable node-exclusive scheduling (e.g., typical system instance scheduling policy). --- spec_25.rst | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/spec_25.rst b/spec_25.rst index a7d68c73..46a51aed 100644 --- a/spec_25.rst +++ b/spec_25.rst @@ -104,9 +104,23 @@ following: below. **count** - The ``count`` key SHALL indicate the desired number of - resources matching the current vertex. The ``count`` SHALL be a single integer - value representing a fixed count + The ``count`` key SHALL indicate the desired number or range of + resources matching the current vertex. The ``count`` SHALL have one + of two possible values: either a single integer value representing + a fixed count, or a dictionary which SHALL contain the following key: + + **min** + The minimum required count or amount of this resource + + A ``count`` + which specifies the ``min`` key SHALL be considered a request for + *at least* that number of a resource, and the scheduler SHALL generate + the *R* that contains the maximum number of the resource that is + available. By contrast, + if a fixed count is given to the ``count`` key, the scheduler SHALL + match any resource that contains *at least* ``count`` of the resource, + but its *R* SHALL contain exactly ``count`` of the resource + (potentially leaving excess resources unutilized). V1-Specific Resource Graph Restrictions