public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH v5 07/12] gen_hosts: add service group to inventory templates
Date: Fri, 25 Jul 2025 10:13:35 +0200	[thread overview]
Message-ID: <fab5e148-de18-4644-875b-e1e45181b2fd@kernel.org> (raw)
In-Reply-To: <aIKOpSQPwuxvUvKL@bombadil.infradead.org>



On 24/07/2025 21.51, Luis Chamberlain wrote:
> On Thu, Jul 24, 2025 at 09:36:13PM +0200, Daniel Gomez wrote:
>> From: Daniel Gomez <da.gomez@samsung.com>
>>
>> Introduce a new 'service' group in all inventory templates that includes
>> service hosts (iscsi, nfsd, smbd, kdc). This provides a convenient way
>> to target all service hosts collectively for operations like guestfs
>> bringup and SSH configuration.
>>
>> The service group includes:
>> - iscsi hosts (when kdevops_enable_iscsi is enabled)
>> - nfsd hosts (when kdevops_nfsd_enable is enabled)
>> - smbd hosts (when kdevops_smbd_enable is enabled)
>> - kdc hosts (when kdevops_krb5_enable is enabled)
>>
>> This addresses issues where operations limited to 'baseline:dev' would
>> miss required service hosts, causing workflow failures.
>>
>> Generated-by: Claude AI
> 
> No newline needed

Making sure I'm not adding this line this time...

>>
>> Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
> 
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>

Thanks!

> 
>   Luis



  reply	other threads:[~2025-07-25  8:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 19:36 [PATCH v5 00/12] Define Ansible inventory in the Ansible Configuration file Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 01/12] playbooks: fix playbook name for all hosts plays Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 02/12] playbooks: fix playbook name for localhost plays Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 03/12] Makefile: use long form of limit argument for clarity Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 04/12] Makefile: print target when debug Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 05/12] .github/workflows/fstests.yml: enable make verbosity Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 06/12] ansible_cfg: add inventory support Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 07/12] gen_hosts: add service group to inventory templates Daniel Gomez
2025-07-24 19:51   ` Luis Chamberlain
2025-07-25  8:13     ` Daniel Gomez [this message]
2025-07-24 20:02   ` Chuck Lever
2025-07-25  8:36     ` Daniel Gomez
2025-07-25 14:00       ` Chuck Lever
2025-07-24 19:36 ` [PATCH v5 08/12] gen_hosts: templates: include localhost in the all group Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 09/12] Makefile: use inventory from ansible.cfg Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 10/12] ansible_cfg: add support to change ansible.cfg file location Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 11/12] docs: ansible_cfg: add documentation Daniel Gomez
2025-07-24 19:36 ` [PATCH v5 12/12] build.Makefile: fix verbosity of clean target Daniel Gomez
2025-07-25 14:03 ` [PATCH v5 00/12] Define Ansible inventory in the Ansible Configuration file Chuck Lever
2025-07-28  5:57 ` Daniel Gomez

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=fab5e148-de18-4644-875b-e1e45181b2fd@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