Skip to content

Commit 4d91bb0

Browse files
committed
rfc14: add constraints attribute to jobspec
Problem: RFC 31 defines a format for specification of generic job constraints, but RFC 14 does not define the location for a constraints in jobspec. Define attributes.system.constraints as the location in jobspec for RFC 31 defined constraints. Update the RFC 14 schema, but only describe `constraints` as an "object", the actual constraint object is meant to be validated by a scheduler, since different schedulers may support differing constraint "operators".
1 parent e5f6d63 commit 4d91bb0

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

data/spec_14/schema.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,8 @@
102102
"environment": { "type": "object" },
103103
"dependencies" : {
104104
"$ref": "file:data/spec_26/schema.json"
105-
}
105+
},
106+
"constraints" : { "type": "object" }
106107
}
107108
},
108109
"user": {

spec_14.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -345,6 +345,10 @@ Some common system attributes are:
345345
The value of the ``dependencies`` attribute SHALL be a
346346
list of dictionaries following the format specified in RFC 26.
347347

348+
**constraints**
349+
The value of the ``constraints`` attribute SHALL be a dictionary
350+
expressing job constraints following the specification in RFC 31.
351+
348352
**job**
349353
The ``job`` attribute is an optional dictionary containing job
350354
metadata. This metadata may be used for searching and filtering of

0 commit comments

Comments
 (0)