Skip to content

Commit 1e254f6

Browse files
grondomergify-bot
authored andcommitted
rfc25: add optional exclusive key to node resource vertex
Problem: Jobspec V1 does not define an exclusive key for resources in the resource section. This makes it impossible to offer a consistent interface for users for the `flux mini` commands when only the `-N` option is used. Add `exclusive` key to Jobspec V1 only for `node` type resource vertices. The intent is to ensure that a user can request exclusive access to nodes whether an instance allocates nodes exclusively by default or not.
1 parent 981ca71 commit 1e254f6

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

spec_25.rst

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,11 @@ A resource vertex SHALL contain only the following keys:
9393

9494
- label
9595

96-
The definitions of ``unit``, ``with``, and ``label`` SHALL match
96+
a ``node`` type resource vertex MAY also contain the following optional keys:
97+
98+
- exclusive
99+
100+
The definitions of ``unit``, ``with``, ``exclusive`` and ``label`` SHALL match
97101
those found in RFC14. The others are redefined and simplified to mean the
98102
following:
99103

0 commit comments

Comments
 (0)