From: Luis Chamberlain <mcgrof@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH 0/6] monitoring: restructure into modular architecture and extend workflow coverage
Date: Tue, 16 Sep 2025 15:40:17 -0700 [thread overview]
Message-ID: <aMnnUTz8teP-iF-e@bombadil.infradead.org> (raw)
In-Reply-To: <20250916-monitoring-refactor-v1-0-307d3fb48bfd@samsung.com>
On Tue, Sep 16, 2025 at 02:17:16PM +0200, Daniel Gomez wrote:
> This patch series restructures kdevops monitoring from a monolithic
> architecture into a modular, extensible framework, similar to the recent
> work done in other playbooks such as bootlinux or guestfs. Also, expand
> workflow coverage to include blktests and sysbench support.
>
> The modular design allows to have dedicated monitor Ansible code which
> makes it easier to maintain in the long run. Use the top level role
> files as orchestrators for the individual monitors.
>
> Note: I have a new monitor built on top of this refactor using the
> same pattern. However, I realized that we can make it even easier if
> we switch to systemd services. We get journal support as well as proper
> service lifecycle management, etc. I think, this would simplify the
> implementations significantly and provide more robust monitoring
> infrastructure for production environments.
>
> I'm not planning to send a conversion yet but I figured I'd mentioned it
> for discussion and future possible work path.
>
> Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
Applied and pushed, thanks!
Luis
prev parent reply other threads:[~2025-09-16 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 12:17 [PATCH 0/6] monitoring: restructure into modular architecture and extend workflow coverage Daniel Gomez
2025-09-16 12:17 ` [PATCH 1/6] monitoring: restructure tasks into modular architecture Daniel Gomez
2025-09-16 12:17 ` [PATCH 2/6] blktests: add monitoring framework integration Daniel Gomez
2025-09-16 12:17 ` [PATCH 3/6] monitoring: restructure monitor_collect_only.yml to use modular architecture Daniel Gomez
2025-09-16 12:17 ` [PATCH 4/6] blktests: add monitor-results support for interim monitoring Daniel Gomez
2025-09-16 12:17 ` [PATCH 5/6] sysbench: add monitoring framework integration Daniel Gomez
2025-09-16 12:17 ` [PATCH 6/6] sysbench: add monitor-results support for interim monitoring Daniel Gomez
2025-09-16 22:40 ` 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=aMnnUTz8teP-iF-e@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=da.gomez@kernel.org \
--cc=da.gomez@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox