public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>,
	Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH v3 01/10] playbooks: fix playbook name for all hosts plays
Date: Fri, 16 May 2025 14:51:16 +0200	[thread overview]
Message-ID: <7cd31cfc-751e-41c2-a9e5-8962d842edd9@kernel.org> (raw)
In-Reply-To: <6dedbabd-79b5-4350-8a11-287cc33de568@oracle.com>



On 06/05/2025 22.39, Chuck Lever wrote:
> On 5/5/25 5:24 PM, Daniel Gomez wrote:
>> From: Daniel Gomez <da.gomez@samsung.com>
>>
>> Fix name rule by naming all the playbooks that run in all hosts.
>>
>> https://ansible.readthedocs.io/projects/lint/rules/name/
> 
> Nit: name[casing] states these names must begin with an upper case
> letter. Ditto for 02/10.
> 
> Would be slightly nicer, perhaps, if these names were documentary
> sentences, as they are in the roles themselves.

I'm getting a bit of “buddy” assistance on some playbooks I'm less/not 
familiar with. Here's the first pass covering about half of them.


--- a/playbooks/blktests.yml
+++ b/playbooks/blktests.yml
-- name: blktests
+- name: Linux kernel block layer tests (blktests)
--- a/playbooks/bootlinux-local.yml
+++ b/playbooks/bootlinux-local.yml
-- name: bootlinux-local
+- name: Bootlinux (localhost only)
--- a/playbooks/bringup_guestfs.yml
+++ b/playbooks/bringup_guestfs.yml
-- name: bringup_guestfs
+- name: Bringup Guests (libguestfs)
--- a/playbooks/build_qemu.yml
+++ b/playbooks/build_qemu.yml
-- name: build_qemu
+- name: Build QEMU
--- a/playbooks/common.yml
+++ b/playbooks/common.yml
-- name: common
+- name: Common (shared role)
--- a/playbooks/create_data_partition.yml
+++ b/playbooks/create_data_partition.yml
-- name: create_data_partition
+- name: Create Directory Data Path (e.g. /data partition)
--- a/playbooks/devconfig.yml
+++ b/playbooks/devconfig.yml
-- name: devconfig
+- name: Configure developer environment on target systems
--- a/playbooks/fstests.yml
+++ b/playbooks/fstests.yml
-- name: fstests
+- name: "Filesystem testing suite setup - (x)fstests (control node only)"
-- hosts: baseline:dev
+- name: Filesystem testing suite setup - (x)fstests
+  hosts: baseline:dev
--- a/playbooks/pynfs.yml
+++ b/playbooks/pynfs.yml
-- name: pynfs
+- name: Configure and run pynfs testing workflow
--- a/playbooks/reboot-limit.yml
+++ b/playbooks/reboot-limit.yml
-- name: reboot-limit
+- name: reboot-limit stability test workflow
--- a/playbooks/rxe.yml
+++ b/playbooks/rxe.yml
-- name: rxe
+- name: Set up software-emulated RoCE RDMA over Ethernet (rxe) via udev
--- a/playbooks/selftests.yml
+++ b/playbooks/selftests.yml
-- name: selftests
+- name: Set up and run Linux kernel selftests (kselftests)
--- a/playbooks/siw.yml
+++ b/playbooks/siw.yml
-- name: siw
+- name: Set up software-emulated iWARP RDMA over TCP/IP (siw) via udev
--- a/playbooks/smbd.yml
+++ b/playbooks/smbd.yml
-- name: smbd
+- name: Set up Samba server with shared volume and system integration
--- a/playbooks/sysbench.yml
+++ b/playbooks/sysbench.yml
-- name: sysbench
+- name: Sysbench workflow
--- a/playbooks/terraform.yml
+++ b/playbooks/terraform.yml
-- name: terraform
+- name: Manage infrastructure lifecycle and SSH access with Terraform
--- a/playbooks/update_etc_hosts.yml
+++ b/playbooks/update_etc_hosts.yml
-- name: update_etc_hosts
+- name: Update target /etc/hosts with all targets and disable cloud-init
--- a/playbooks/update_ssh_config_guestfs.yml
+++ b/playbooks/update_ssh_config_guestfs.yml
-- name: update_ssh_config_guestfs
+- name: Update OpenSSH client configuration file (libguestfs)



  parent reply	other threads:[~2025-05-16 12:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 21:24 [PATCH v3 00/10] Define Ansible inventory in the Ansible Configuration file Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 01/10] playbooks: fix playbook name for all hosts plays Daniel Gomez
2025-05-06 20:39   ` Chuck Lever
2025-05-07 12:04     ` Daniel Gomez
2025-05-07 14:02       ` Chuck Lever
2025-05-16 12:51     ` Daniel Gomez [this message]
2025-05-17 19:43       ` Chuck Lever
2025-05-17 20:34         ` Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 02/10] playbooks: fix playbook name for localhost plays Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 03/10] Makefile: use long form of limit argument for clarity Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 04/10] Makefile: print target when debug Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 05/10] .github/workflows/fstests.yml: enable make verbosity Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 06/10] ansible_cfg: add inventory support Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 07/10] gen_hosts: templates: include localhost in the all group Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 08/10] Makefile: use inventory from ansible.cfg Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 09/10] ansible_cfg: add support to change ansible.cfg file location Daniel Gomez
2025-05-05 21:24 ` [PATCH v3 10/10] docs: ansible_cfg: add documentation Daniel Gomez
2025-05-06 20:35 ` [PATCH v3 00/10] Define Ansible inventory in the Ansible Configuration file 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=7cd31cfc-751e-41c2-a9e5-8962d842edd9@kernel.org \
    --to=da.gomez@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=da.gomez@samsung.com \
    --cc=kdevops@lists.linux.dev \
    --cc=mcgrof@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox