refactor: represent requires in resources

Problem: a compatibility requirement needs to clearly be matched to resources, at least the subset that goes into a match in the graph. Solution: refactor the jobspec so top level resources can have slots that have nested "requires" at the level they are needed. I also found a way to remove the "slot" idea and just replace it with the idea of asking for replicas of a particular place in the resource request. Note that the implementation is not updated yet, just the spec, and I am opening a PR so I can stare at it. Signed-off-by: vsoch <[email protected]>
compspec · May 7, 2024 · 41bb5a3 · 41bb5a3
1 parent 035a590
commit 41bb5a3
Show file tree

Hide file tree

Showing 6 changed files with 796 additions and 256 deletions.
diff --git a/docs/docs/drafts/README.md b/docs/docs/drafts/README.md
@@ -4,3 +4,4 @@
 
  - [Spec Draft 1](spec-draft-1.md): an early variant
  - [Spec Draft 2](spec-draft-2.md): I liked this one the best, but the flexibility made implementation in Go impossible (serializing recursive structs into Go that could be two different types).
+ - [Spec Draft 3](spec-draft-3.md): better, but flawed in that requirements were separate from schedulable units of work, and more specifically, slots within them.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,3 +4,4 @@

		- [Spec Draft 1](spec-draft-1.md): an early variant
		- [Spec Draft 2](spec-draft-2.md): I liked this one the best, but the flexibility made implementation in Go impossible (serializing recursive structs into Go that could be two different types).
		- [Spec Draft 3](spec-draft-3.md): better, but flawed in that requirements were separate from schedulable units of work, and more specifically, slots within them.