From: Luis Chamberlain <mcgrof@kernel.org>
To: Daniel Gomez <da.gomez@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
kdevops@lists.linux.dev, Daniel Gomez <da.gomez@samsung.com>
Subject: Re: [PATCH] ansible: add lucid callback plugin for clean output
Date: Mon, 24 Nov 2025 16:07:47 -0800 [thread overview]
Message-ID: <aSTzU8kWAP6gQUN9@bombadil.infradead.org> (raw)
In-Reply-To: <20251121-lucid-v1-1-4981e36f71f4@samsung.com>
On Fri, Nov 21, 2025 at 08:44:59PM +0100, Daniel Gomez wrote:
> From: Daniel Gomez <da.gomez@samsung.com>
>
> Add the lucid callback plugin to provide clean, minimal Ansible output
> for kdevops workflows. Current Ansible output is verbose by default
> making it difficult to see what matters during long-running test
> operations. Lucid solves this by showing only changes and errors at
> default verbosity while providing progressive detail at higher levels.
>
> The plugin includes dynamic mode with live updates for interactive
> terminals showing running tasks with spinners and elapsed time similar
> to build system output. For CI/CD and piped contexts it automatically
> falls back to static output. All runs generate comprehensive logs with
> playbook names and timestamps allowing multiple executions to coexist
> without conflicts.
>
> Task-level output control is available via the output_verbosity variable
> allowing playbooks to specify per-task visibility. Execution time
> tracking highlights slow tasks exceeding configurable thresholds. Logs
> always capture full verbosity independent of display settings ensuring
> complete audit trails.
>
> Integrate lucid with kdevops Kconfig system providing options for
> time threshold, timestamp format, output mode (auto/static/dynamic),
> and log behavior. Add defconfig fragment for quick enablement. Update
> ansible.cfg template to generate callback configuration when selected.
> Make lucid the default callback for new configurations.
>
> Add documentation following Ansible's standard format covering
> requirements, parameters, usage examples, and behavior notes.
>
> Generated-by: Claude AI
> Signed-off-by: Daniel Gomez <da.gomez@samsung.com>
I saw the demo and am sold please yes!
Luis
prev parent reply other threads:[~2025-11-25 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 19:44 [PATCH] ansible: add lucid callback plugin for clean output Daniel Gomez
2025-11-25 0:07 ` 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=aSTzU8kWAP6gQUN9@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=chuck.lever@oracle.com \
--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