public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
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 8/8] docs: Organize cloud providers with Neoclouds section
Date: Sat,  6 Dec 2025 08:56:22 -0800	[thread overview]
Message-ID: <20251206165624.2640158-9-mcgrof@kernel.org> (raw)
In-Reply-To: <20251206165624.2640158-1-mcgrof@kernel.org>

Reorganize the terraform documentation to distinguish between
traditional cloud providers and neoclouds. A neocloud is a specialized
cloud provider focused on GPU-as-a-Service for AI and ML workloads,
with infrastructure optimized for raw speed, dense GPU clusters, and
simplified pricing.

Traditional providers include Azure, AWS, GCE, and OCI. Neoclouds
include DataCrunch and Lambda Labs with their GPU-focused offerings.
The documentation now includes links to Lambda Labs dynamic Kconfig
generation and CLI reference documentation.

Generated-by: Claude AI
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
 README.md                 |  2 +-
 docs/kdevops-terraform.md | 33 ++++++++++++++++++++++++++++++++-
 2 files changed, 33 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 52b07aed..bb64c640 100644
--- a/README.md
+++ b/README.md
@@ -526,7 +526,7 @@ Below are sections which get into technical details of how kdevops works.
   * [Linux distribution support](docs/linux-distro-support.md)
   * [Overriding all Ansible role options with one file](docs/ansible-override.md)
   * [kdevops Vagrant support](docs/kdevops-vagrant.md)
-  * [kdevops terraform support - cloud setup with kdevops](docs/kdevops-terraform.md)
+  * [kdevops terraform and cloud provider support](docs/kdevops-terraform.md) - AWS, Azure, GCE, OCI, Lambda Labs, DataCrunch
   * [kdevops local Ansible roles](docs/ansible-roles.md)
   * [Tutorial on building your own custom Vagrant boxes](docs/custom-vagrant-boxes.md)
 
diff --git a/docs/kdevops-terraform.md b/docs/kdevops-terraform.md
index 0dd42048..51f92004 100644
--- a/docs/kdevops-terraform.md
+++ b/docs/kdevops-terraform.md
@@ -7,10 +7,13 @@ a Terraform plan.
 Terraform is used to deploy your development hosts on cloud virtual machines.
 Below are the list of clouds providers currently supported:
 
+**Traditional Cloud Providers:**
   * azure - Microsoft Azure
   * aws - Amazon Web Service
   * gce - Google Cloud Compute
   * oci - Oracle Cloud Infrastructure
+
+**Neoclouds (GPU-optimized):**
   * datacrunch - DataCrunch GPU Cloud
   * lambdalabs - Lambda Labs GPU Cloud
 
@@ -271,7 +274,18 @@ If your Ansible controller (where you run "make bringup") and your
 test instances operate inside the same subnet, you can disable the
 TERRAFORM_OCI_ASSIGN_PUBLIC_IP option for better network security.
 
-### DataCrunch - GPU Cloud Provider
+## Neoclouds
+
+A neocloud is a new type of specialized cloud provider that focuses on offering
+high-performance computing, particularly GPU-as-a-Service, to handle demanding
+AI and machine learning workloads. Unlike traditional, general-purpose cloud
+providers like AWS or Azure, neoclouds are purpose-built for AI with
+infrastructure optimized for raw speed, specialized hardware like dense GPU
+clusters, and tailored services like fast deployment and simplified pricing.
+
+kdevops supports the following neocloud providers:
+
+### DataCrunch
 
 kdevops supports DataCrunch, a cloud provider specialized in GPU computing
 with competitive pricing for NVIDIA A100, H100, B200, and B300 instances.
@@ -450,3 +464,20 @@ provider_installation {
 ```
 
 For more information, visit: https://datacrunch.io/
+
+### Lambda Labs
+
+kdevops supports Lambda Labs, a cloud provider focused on GPU instances for
+machine learning workloads with competitive pricing.
+
+For detailed documentation on Lambda Labs integration, including tier-based
+GPU selection, smart instance selection, and dynamic Kconfig generation, see:
+
+  * [Lambda Labs Dynamic Cloud Kconfig](dynamic-cloud-kconfig.md) - Dynamic configuration generation for Lambda Labs
+  * [Lambda Labs CLI Reference](lambda-cli.1) - Man page for the lambda-cli tool
+
+Lambda Labs offers various GPU instance types including A10, A100, and H100
+configurations. kdevops provides smart selection features that automatically
+choose the cheapest available instance type and region.
+
+For more information, visit: https://lambdalabs.com/
-- 
2.51.0


      parent reply	other threads:[~2025-12-06 16:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-06 16:56 [PATCH 0/8] neoclouds: add new datacrunch / verda support Luis Chamberlain
2025-12-06 16:56 ` [PATCH 1/8] terraform: Use directory checksum in SSH key filenames Luis Chamberlain
2025-12-06 22:28   ` Chuck Lever
2025-12-12 19:14     ` Chuck Lever
2025-12-15 15:41       ` Chuck Lever
2025-12-06 16:56 ` [PATCH 2/8] devconfig: Add tmux.conf copying to target systems Luis Chamberlain
2025-12-06 16:56 ` [PATCH 3/8] terraform: Enable fact gathering for localhost Luis Chamberlain
2025-12-07 16:23   ` Chuck Lever
2025-12-06 16:56 ` [PATCH 4/8] terraform: Add DataCrunch GPU cloud provider integration Luis Chamberlain
2025-12-16 16:12   ` Chuck Lever
2025-12-06 16:56 ` [PATCH 5/8] kconfig: Add support for merging defconfig fragments Luis Chamberlain
2025-12-07 16:25   ` Chuck Lever
2025-12-07 20:37   ` Daniel Gomez
2025-12-06 16:56 ` [PATCH 6/8] terraform: Add tier-based GPU selection for Lambda Labs Luis Chamberlain
2025-12-16 18:05   ` Chuck Lever
2025-12-06 16:56 ` [PATCH 7/8] terraform: Document " Luis Chamberlain
2025-12-16 19:30   ` Chuck Lever
2025-12-06 16:56 ` 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=20251206165624.2640158-9-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