public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: "Chuck Lever" <cel@kernel.org>
To: "Luis Chamberlain" <mcgrof@kernel.org>,
	"Daniel Gomez" <da.gomez@kernel.org>
Cc: kdevops@lists.linux.dev
Subject: Re: [PATCH] terraform: refactor tasks into provider-specific modules
Date: Fri, 19 Dec 2025 13:02:06 -0500	[thread overview]
Message-ID: <c61997bd-8918-46ad-bd52-df4046f5c34a@app.fastmail.com> (raw)
In-Reply-To: <20251217154630.2977625-1-cel@kernel.org>



On Wed, Dec 17, 2025, at 10:46 AM, Chuck Lever wrote:
> The terraform role's main.yml had grown to nearly 800 lines with
> Lambda Labs and DataCrunch provider-specific logic interleaved
> throughout the file. This made maintenance difficult and required
> understanding the entire file to make changes for a single provider.
> 
> This refactoring creates a plugin-like architecture where each cloud
> provider's unique requirements are isolated in dedicated task files.
> The new structure separates concerns by operation (bringup, destroy)
> and by provider (lambdalabs, datacrunch, generic), making it
> straightforward to add support for new providers or modify existing
> ones without risk of breaking other providers.
> 
> Common functionality shared across all providers, such as SSH
> configuration and status reporting, is now cleanly separated in a
> common directory. This follows patterns already established in other
> roles like bootlinux and guestfs.
> 
> Generated-by: Claude AI
> Signed-off-by: Chuck Lever <cel@kernel.org>

Merged into origin/main.


Chuck Lever

      reply	other threads:[~2025-12-19 18:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 15:46 [PATCH] terraform: refactor tasks into provider-specific modules Chuck Lever
2025-12-19 18:02 ` Chuck Lever [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=c61997bd-8918-46ad-bd52-df4046f5c34a@app.fastmail.com \
    --to=cel@kernel.org \
    --cc=da.gomez@kernel.org \
    --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