Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rfc20: clarify R_lite rank:host mapping #439

Merged
merged 2 commits into from
Jan 28, 2025
Merged

rfc20: clarify R_lite rank:host mapping #439

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
03f7beb
rfc20: clarify R_lite rank:host mapping
garlick Jan 27, 2025
c82e2a3
rfc1: drop ossec.com link
garlick Jan 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions spec_1.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,5 +239,3 @@ Implementations
***************

- The `ZeroMQ community <http://zeromq.org>`__ uses the C4.1 process for many projects.

- `OSSEC <http://www.ossec.net/>`__ `uses the C4.1 process <https://ossec-docs.readthedocs.io/en/latest/docs/development/oRFC/orfc-1.html>`__.
10 changes: 6 additions & 4 deletions spec_20.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,8 +127,9 @@ R Format
.. data:: R_lite

(*array of dictionary*, REQUIRED) A list that identifies one or more
execution targets and the specific cores and GPUs they control. Each
entry SHALL have the following keys:
execution targets and the specific cores and GPUs they control.
The list entries need not appear in any particular order. Each entry
SHALL have the following keys:

.. data:: rank

Expand Down Expand Up @@ -157,8 +158,9 @@ R Format

Each entry SHALL be either a single hostname or an RFC 29 hostlist.

The order of hostnames MUST correspond to the order of execution targets in
:data:`R_lite`. However, the number of entries in each array need not be
The order of hostnames MUST correspond to the sorted list of execution
targets ranks in :data:`R_lite` so that they can be mapped one to one.
However, the number of entries in each array need not be
the same. For example, :data:`nodelist` MAY contain one hostlist entry
for all the execution targets spread over multiple :data:`R_lite` entries.

Expand Down
Loading