From cfd38363d5a2df301c9c1820a7f922671455c618 Mon Sep 17 00:00:00 2001 From: "Mark A. Grondona" Date: Sat, 1 Aug 2026 08:19:48 -0700 Subject: [PATCH] rfc20: mark instance-local properties with leading + Problem: Flux may add resource properties itself to describe the local instance, such as a property representing queue membership. There is no way to tell such a property apart from one that describes the resource set in general, so a job's generated R may inherit instance properties that have no meaning in a child instance. Define a leading + in a property name to mark an instance-local property and specify that the scheduler should omit these properties when generating an R subset for job. Future proof the specification by stating that other components that generate an R subset MAY likewise omit instance-local properties. Assisted-by: Claude:Opus-4.8 --- spec_20.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/spec_20.rst b/spec_20.rst index 06d8bfda..60f8f1ea 100644 --- a/spec_20.rst +++ b/spec_20.rst @@ -194,6 +194,15 @@ R Format result in both ``amd-mi50@gpu`` and ``amd-mi50`` being valid properties for resources in the instance. + A leading ``+`` character marks an *instance-local* property: one that + describes the containing instance rather than an attribute of the + hardware, for example a property derived from queue membership. The + literal property SHALL apply to the defined execution target ranks as + usual. Because instance-local properties describe the instance and not + the resources themselves, a scheduler SHALL omit them from the *R* it + generates to allocate resources to a job. Other components that + generate an *R* subset MAY likewise omit them. + .. data:: starttime (*number*, OPTIONAL) The start time at which the resource set is valid.