public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH] terraform/aws: Add an AMI menu entry for Deep Learning AMIs
Date: Fri, 10 Oct 2025 08:32:37 -0400	[thread overview]
Message-ID: <30a479ab-0d77-406b-bca4-87d7c893dec1@kernel.org> (raw)
In-Reply-To: <aOhYhHgUIdiC5qvk@bombadil.infradead.org>

On 10/9/25 8:51 PM, Luis Chamberlain wrote:
> On Wed, Oct 08, 2025 at 03:38:40PM -0400, Chuck Lever wrote:
>> From: Chuck Lever <chuck.lever@oracle.com>
>>
>> The entry uses Amazon's owner ID (137112412989) and includes search
>> patterns for "Deep Learning AMI" and "Deep Learning Base" AMIs,
>> which are AWS's pre-configured GPU-enabled images for machine
>> learning workloads.
>>
>> Generated-by: Claude AI
>> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
>> ---
>>  terraform/aws/scripts/gen_kconfig_ami | 9 +++++++++
>>  1 file changed, 9 insertions(+)
>>
>> Luis, this is untested. Can you apply this patch, rebuild the compute
>> menu, and see if it provides the desired results?
> 
> Sure, but I'm at a loss, is there a dynamic kconfig thing?

I haven't adapted your patches that add make targets for regenerating
the menus yet. Again, I wanted an MVP for us to kick around for a bit
first. Driving this stuff from make is definitely a to-do.

But this should work for now:

$ cd terraform/aws
$ scripts/gen_kconfig_ami > kconfigs/Kconfig.ami


> I also can't
> get any instance up on my account as I have the VPC issue so I can't
> test unless that's fixed.

I will be able to do simple testing when I get back to my lab in a
couple days.


-- 
Chuck Lever

      reply	other threads:[~2025-10-10 12:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08 19:38 [RFC PATCH] terraform/aws: Add an AMI menu entry for Deep Learning AMIs Chuck Lever
2025-10-10  0:51 ` Luis Chamberlain
2025-10-10 12:32   ` 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=30a479ab-0d77-406b-bca4-87d7c893dec1@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --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