From 03c64cd7760986fd9294f1a7f822eed6cd48e0b0 Mon Sep 17 00:00:00 2001
From: Jim Garlick <garlick.jim@gmail.com>
Date: Mon, 11 Mar 2024 10:28:27 -0700
Subject: [PATCH] rfc27: add R to sched.free request

Problem: flux-framework/flux-core#5783 adds R to the sched.free
request to avoid an extra lookup.

Add R to the sched.free request payload definition in RFC 27.
---
 spec_27.rst | 31 +++++++++++++++++++++++--------
 1 file changed, 23 insertions(+), 8 deletions(-)

diff --git a/spec_27.rst b/spec_27.rst
index 74dd7b8c..4e191ef2 100644
--- a/spec_27.rst
+++ b/spec_27.rst
@@ -571,22 +571,37 @@ Free
 
 The job manager SHALL send a ``sched.free`` request when a job that is
 holding resources enters CLEANUP state.  The request payload consists of
-a JSON object with the following REQUIRED key:
+a JSON object with the following REQUIRED keys:
 
 id
   (integer) job ID
 
+R
+  (object) RFC 20 resource set from which the ``scheduling`` key MAY be
+  omitted.
+
 Example:
 
 .. code:: json
 
-   {
-     "id": 1552593348
-   }
-
-Upon receipt of the ``sched.free`` request, the scheduler MAY look up *R*
-in the KVS by job ID according to the job schema (RFC 16).
-It SHOULD mark the job's resources as available for reuse.
+  {
+    "id": 1552593348,
+    "R": {
+      "version": 1,
+      "execution": {
+        "R_lite": [
+          { "rank": "0", "children": { "core": "0-3" } }
+        ],
+        "nodelist": [ "test0" ],
+        "starttime": 1710076092,
+        "expiration": 1710076122
+      }
+    }
+  }
+
+
+Upon receipt of the ``sched.free`` request, the scheduler SHOULD mark the
+job's resources as available for reuse.
 
 Once the ``sched.free`` request has been processed by the scheduler, it SHALL
 send a response with payload consisting of a JSON object with the following