From 6ca2b84ddcf4c45c4b0b0cbec9e718db0e4c3178 Mon Sep 17 00:00:00 2001 From: "Mark A. Grondona" Date: Fri, 19 Jan 2024 11:14:30 -0800 Subject: [PATCH] admin-guide: clarify queue property name requirements Problem: There is a statement in the admin guide that it is good practice to use property names that match the corresponding queue name, but no reason for this practice is given. Explain that queue properties do not need to match the queue name, but note that it is good practice because it allows flux-resource list to suppress these duplicate names in is output. --- guides/admin-guide.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/guides/admin-guide.rst b/guides/admin-guide.rst index 2a2535a7..676e9bdc 100644 --- a/guides/admin-guide.rst +++ b/guides/admin-guide.rst @@ -732,8 +732,12 @@ Adding Queues It may be useful to configure a Flux system instance with multiple queues. Each queue should be associated with a non-overlapping resource subset, -identified by property name. It is good practice for queues to create a -new property that has the same name as the queue. +identified by property name. It is good practice for queues to create a +new property that has the same name as the queue. (There is no requirement +that queue properties match the queue name, but this will cause extra entries +in the PROPERTIES column for these queues. When queue names match property +names, :command:`flux resource list` suppresses these matching properties +in its output.) When queues are defined, all jobs must specify a queue at submission time. If that is inconvenient, then ``policy.jobspec.defaults.system.queue`` may