Skip to content

Commit 302ec17

Browse files
committed
rfc20: drop the attributes section
Problem: the Rv1 attributes section is used by the early Fluxion queue implementation to store the assigned queue name in the system.scheduler key, but queues are now handled differently per RFC 33. Drop the attributes section.
1 parent 190cc35 commit 302ec17

File tree

1 file changed

+0
-24
lines changed

1 file changed

+0
-24
lines changed

spec_20.rst

Lines changed: 0 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -234,30 +234,6 @@ R Format
234234
occurs when a new Flux instance is started cannot do the same for the opaque
235235
:data:`scheduling` key.
236236

237-
.. data:: attributes
238-
239-
The purpose of the :data:`attributes` key is to provide optional
240-
information on this *R* document. The :data:`attributes` key SHALL
241-
be a dictionary of one key: :data:`system`.
242-
243-
Other keys are reserved for future extensions.
244-
245-
.. data:: system
246-
247-
Attributes in the :data:`system` dictionary provide additional system
248-
information that have affected the creation of this *R* document.
249-
All of the system attributes are optional.
250-
251-
A common system attribute is:
252-
253-
.. describe:: scheduler
254-
255-
The value of the :data:`scheduler` key is a free-from dictionary that
256-
may provide the information specific to the scheduler used
257-
to produce this document. For example, a scheduler that
258-
manages multiple job queues may add ``queue=batch``
259-
to indicate that this resource set was allocated from within
260-
its ``batch`` queue.
261237

262238
Example R
263239
=========

0 commit comments

Comments
 (0)