From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 0/2] aws: add dynamic kconfig support
Date: Sat, 6 Sep 2025 21:23:21 -0700 [thread overview]
Message-ID: <20250907042325.2228868-1-mcgrof@kernel.org> (raw)
Changes on this v2:
- adds the docs suggested by Chuck
- splits GPU amis in a separate patch
- drops the static files, as they are just noise
and I can instead re-generate them on the fly when
we decide this is ready to merge.
I've also changed the default GPU AMI to use
"Deep Learning OSS Nvidia Driver AMI GPU PyTorch*Ubuntu 22.04*" as that
actually has pytorch.
Luis Chamberlain (2):
aws: add dynamic cloud configuration support using AWS CLI
aws: enable GPU AMI support for GPU instances
.gitignore | 3 +
defconfigs/aws-gpu-g6e-ai | 42 +
docs/cloud-configuration.md | 268 ++++
.../templates/aws/terraform.tfvars.j2 | 5 +
scripts/aws-cli | 436 +++++++
scripts/aws_api.py | 1161 +++++++++++++++++
scripts/dynamic-cloud-kconfig.Makefile | 101 +-
scripts/generate_cloud_configs.py | 198 ++-
terraform/aws/kconfigs/Kconfig.compute | 109 +-
9 files changed, 2233 insertions(+), 90 deletions(-)
create mode 100644 defconfigs/aws-gpu-g6e-ai
create mode 100644 docs/cloud-configuration.md
create mode 100755 scripts/aws-cli
create mode 100755 scripts/aws_api.py
--
2.50.1
next reply other threads:[~2025-09-07 4:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 4:23 Luis Chamberlain [this message]
2025-09-07 4:23 ` [PATCH 1/2] aws: add dynamic cloud configuration support using AWS CLI Luis Chamberlain
2025-09-07 17:24 ` Chuck Lever
2025-09-07 22:10 ` Luis Chamberlain
2025-09-07 22:12 ` Luis Chamberlain
2025-09-08 14:12 ` Chuck Lever
2025-09-08 14:21 ` Chuck Lever
2025-09-08 15:23 ` Chuck Lever
2025-09-08 20:22 ` Luis Chamberlain
2025-09-07 4:23 ` [PATCH 2/2] aws: enable GPU AMI support for GPU instances Luis Chamberlain
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=20250907042325.2228868-1-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=cel@kernel.org \
--cc=da.gomez@kruces.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