From b7b12842d7ed5eefe499801cc6258d7dc6582f99 Mon Sep 17 00:00:00 2001 From: Jim Garlick Date: Thu, 14 Nov 2024 17:38:36 -0800 Subject: [PATCH] rfc27: add optional partial-ok hello flag Problem: there is no way for the scheduler to indicate that it can handle the new 'free' key in hello responses. The scheduler can put {"partial-ok":true} in the hello request to indicate this. --- spec_27.rst | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/spec_27.rst b/spec_27.rst index 6490189..d672d69 100644 --- a/spec_27.rst +++ b/spec_27.rst @@ -135,11 +135,19 @@ Hello ===== Before any other RPCs are sent to the job manager, the scheduler SHALL -send an empty request to ``job-manager.sched-hello`` with the -FLUX_MSGFLAG_STREAMING flag set. The job manager SHALL send one -response message for each job with allocated resources. Each response -payload SHALL consist of a JSON object with the following REQUIRED -keys: +send a request to ``job-manager.sched-hello`` with the FLUX_MSGFLAG_STREAMING +flag set. The request payload SHALL either be empty or consist of a JSON +object with the following OPTIONAL keys: + +partial-ok + (boolean) The scheduler SHALL set this flag to ``true`` if it can handle + the ``free`` key in hello responses. That is, it can process + jobs with partially released resource sets. If this key is missing it + SHALL be interpreted as ``false``. + +The job manager SHALL send one response message for each job with +allocated resources. Each response payload SHALL consist of a JSON object +with the following REQUIRED keys: id (integer) job ID