From: Luis Chamberlain <mcgrof@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
Vincent Fu <vincent.fu@samsung.com>,
kdevops@lists.linux.dev
Subject: Re: [PATCH v2] workflows: add fio-tests performance tests
Date: Tue, 26 Aug 2025 13:49:40 -0700 [thread overview]
Message-ID: <aK4d5LWHx7QSxbwt@bombadil.infradead.org> (raw)
In-Reply-To: <9556825e-1df1-4c5b-a36d-48d2404852f8@kernel.org>
On Tue, Aug 26, 2025 at 09:18:37PM +0200, Daniel Gomez wrote:
> On 21/08/2025 23.28, Luis Chamberlain wrote:
> > diff --git a/workflows/fio-tests/Makefile b/workflows/fio-tests/Makefile
> > new file mode 100644
> > index 000000000000..cc641606e98c
> > --- /dev/null
> > +++ b/workflows/fio-tests/Makefile
> > @@ -0,0 +1,68 @@
> > +ifeq (y,$(CONFIG_WORKFLOWS_DEDICATED_WORKFLOW))
> > +export KDEVOPS_HOSTS_TEMPLATE := fio-tests.j2
> > +endif
> > +
> > +fio-tests:
> > + $(Q)ansible-playbook $(ANSIBLE_VERBOSE) \
> > + --connection=ssh \
> > + --inventory hosts \
> > + --extra-vars=@$(KDEVOPS_EXTRA_VARS) \
> > + playbooks/fio-tests.yml \
> > + $(LIMIT_HOSTS)
>
> I missed this...
>
> The --connection and --inventory arguments shouldn't be necessary. They are
> managed by the inventory (hosts) file itself and the ansible.cfg.
>
> Can you add a cleanup patch on top so it's consistent with the rest of the
> wrappers?
Pushed.
> FYI, in future cleanups, I'd also like to get rid of the ANSIBLE_VERBOSE and
> control it through ansible.cfg (key: vebosity) [1] and expose it as kconfig
> option.
>
> Link: https://docs.ansible.com/ansible/latest/reference_appendices/config.html#default-verbosity [1]
>
> This should apply to all the ansible-playbook wrappers added.
OK, well until then I'll keep it for now.
Luis
prev parent reply other threads:[~2025-08-26 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 21:28 [PATCH v2] workflows: add fio-tests performance tests Luis Chamberlain
2025-08-26 16:55 ` Luis Chamberlain
2025-08-26 19:18 ` Daniel Gomez
2025-08-26 20:49 ` Luis Chamberlain [this message]
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=aK4d5LWHx7QSxbwt@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kernel.org \
--cc=da.gomez@kruces.com \
--cc=kdevops@lists.linux.dev \
--cc=vincent.fu@samsung.com \
/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