Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rfc25: add moldable specification into Jobspec V1 #302

Closed
wants to merge 1 commit into from
Closed

rfc25: add moldable specification into Jobspec V1 #302

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 17 additions & 3 deletions spec_25.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down