Re: [PATCH v2 0/4] vLLM and the vLLM production stack

Chuck Lever <[email protected]> Sat, 4 Oct 2025 13:14:00 -0400
Newsgroups dev.linux.lists.kdevops
Organization kernel.org
Message-ID <[email protected]>
On 10/4/25 1:03 PM, Luis Chamberlain wrote:
>> I haven't done the follow-up work yet to integrate GPU-enabled AMIs into
>> the AWS Compute menu. That seems like it should be the top priority. I
>> need to go back and look at what you did to generate those in your
>> prototype, to close those gaps.
> Oh yes that's needed. I also need a patch to disable VPCs and enable
> public IPs.

AWS instances are created with public IPs (at least mine are, since my
buildbot master is still in my basement. :-)

Can you elaborate on what's missing here, and I will review patches or
try to help however I can.


> While at it, so that AWS won't eat my corporate expenditures
> I added a slack cloud-bill support too. The whole "static" stuff can be
> ignored, it doesn't work, I was just trying to add static instances
> to see if I could get some larger GPU instnaces to work but it didn't
> work and I gave up.

I assume by "static" you mean long-lived. I've been considering that for
things like kernel build nodes and buildbot masters. Sounds like there
are some interesting use cases to consider.


> But the rest of the changes are legit, please feel
> free to cherry pick what you see useful from here:
> 
> https://github.com/linux-kdevops/kdevops/tree/ci-testing/
> mcgrof/20251004-cloud-bill

Great! I will have a look at those.


-- 
Chuck Lever