All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v1 8/8] gen_hosts: Replace pynfs hosts template
Date: Wed, 10 Sep 2025 15:38:48 -0400	[thread overview]
Message-ID: <20250910193849.779453-9-cel@kernel.org> (raw)
In-Reply-To: <20250910193849.779453-1-cel@kernel.org>

From: Chuck Lever <chuck.lever@oracle.com>

Commit 40df5ef72d19 ("gen_hosts: use kdevops_workflow_name directly
for template selection") appears to have removed the pynfs hosts
template completely, replacing it with the "write your own"
template.

Fixes: 40df5ef72d19 ("gen_hosts: use kdevops_workflow_name directly for template selection")
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 .../gen_hosts/templates/workflows/pynfs.j2    | 36 ++++++++++++++++++-
 1 file changed, 35 insertions(+), 1 deletion(-)

diff --git a/playbooks/roles/gen_hosts/templates/workflows/pynfs.j2 b/playbooks/roles/gen_hosts/templates/workflows/pynfs.j2
index 6145b1a0d245..867df8137dd5 100644
--- a/playbooks/roles/gen_hosts/templates/workflows/pynfs.j2
+++ b/playbooks/roles/gen_hosts/templates/workflows/pynfs.j2
@@ -1,7 +1,41 @@
 {# Workflow template for pynfs #}
 [all]
 localhost ansible_connection=local
-write-your-own-template-for-pynfs-workflow
+{% for host in pynfs_enabled_hosts %}
+{{ kdevops_host_prefix }}-{{ host }}
+{% if kdevops_baseline_and_dev %}
+{{ kdevops_host_prefix }}-{{ host }}-dev
+{% endif %}
+{% endfor %}
 
 [all:vars]
 ansible_python_interpreter = "{{ kdevops_python_interpreter }}"
+
+[baseline]
+{% for host in pynfs_enabled_hosts %}
+{{ kdevops_host_prefix }}-{{ host }}
+{% endfor %}
+
+[baseline:vars]
+ansible_python_interpreter = "{{ kdevops_python_interpreter }}"
+
+[dev]
+{% if kdevops_baseline_and_dev %}
+{% for host in pynfs_enabled_hosts %}
+{{ kdevops_host_prefix }}-{{ host }}-dev
+{% endfor %}
+{% endif %}
+
+[dev:vars]
+ansible_python_interpreter = "{{ kdevops_python_interpreter }}"
+
+[pynfs]
+{% for host in pynfs_enabled_hosts %}
+{{ kdevops_host_prefix }}-{{ host }}
+{% if kdevops_baseline_and_dev %}
+{{ kdevops_host_prefix }}-{{ host }}-dev
+{% endif %}
+{% endfor %}
+
+[pynfs:vars]
+ansible_python_interpreter = "{{ kdevops_python_interpreter }}"
-- 
2.51.0


  parent reply	other threads:[~2025-09-10 19:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10 19:38 [PATCH v1 0/8] Fixes for recent commits Chuck Lever
2025-09-10 19:38 ` [PATCH v1 1/8] gen_nodes: Re-title the playbook Chuck Lever
2025-09-10 19:38 ` [PATCH v1 2/8] devconfig: Remove "dnf update" optimizations for terraform hosts Chuck Lever
2025-09-10 19:38 ` [PATCH v1 3/8] gen_hosts: Get the "separate kernel builder" workflow working again Chuck Lever
2025-09-10 19:38 ` [PATCH v1 4/8] gen_hosts: Restore missing groups to the fstests hosts template Chuck Lever
2025-09-10 19:38 ` [PATCH v1 5/8] gen_hosts: Restore missing groups to the gitr " Chuck Lever
2025-09-10 19:38 ` [PATCH v1 6/8] gen_hosts: Restore missing groups to the ltp " Chuck Lever
2025-09-10 19:38 ` [PATCH v1 7/8] gen_hosts: Restore missing groups to the nfstest " Chuck Lever
2025-09-10 19:38 ` Chuck Lever [this message]
2025-09-10 19:51 ` [PATCH v1 0/8] Fixes for recent commits Luis Chamberlain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250910193849.779453-9-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=kdevops@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.