Skip to content

Add the v0.4 release post on Dynamo and AI Cluster Runtime - #37

Merged
negz merged 2 commits into
modelplaneai:mainfrom
negz:grove-is-in-the-heart
Sep 10, 2026
Merged

negz merged 2 commits into
modelplaneai:mainfrom
negz:grove-is-in-the-heart

Conversation

@negz

@negz negz commented Sep 2, 2026 •

Copy link
Copy Markdown
Contributor

What and why

Modelplane v0.4's two headline features are an NVIDIA Dynamo serving stack and serving stacks that take much of their component versions and configuration from NVIDIA AI Cluster Runtime. A smaller change starts a cloud's providers only once a control plane has a cluster on that cloud. This release post keeps the Dynamo walk-through and adds sections on the AICR-sourced stacks and the on-demand providers.

The first commit has nothing to do with the post, and fixes a next build failure the post triggers: normalizeAuthors set optional author fields even where frontmatter omits them, so an omitted field became an explicit undefined that getStaticProps can't serialize. Happy to split it into its own PR if you'd rather review it separately.

Checklist

  • Ran npm run build locally. npm run lint drops into next's interactive ESLint setup prompt, so there's no lint config in the repo to run.
  • Ran npm run validate-posts.
  • Signed off my commits with git commit -s.

A post's frontmatter can omit any author field except name, but
normalizeAuthors set every one of them regardless, so an omitted field
became an explicit undefined. getAllAuthors then reintroduced the same
keys when merging an author's posts, because ??= assigns when the left
side is nullish. The author pages pass an author straight through as a
getStaticProps prop, and Next.js refuses to serialize undefined, so the
build failed once an author who omits a field had a second post.

Drop undefined values when normalizing, and merge an author's posts by
spread rather than field by field, so a field absent from every post is
missing rather than undefined.

Signed-off-by: Nic Cope <nicc@rk0n.org>
@negz
negz force-pushed the grove-is-in-the-heart branch from f49e67f to 27db930 Compare September 2, 2026 19:09
@negz negz changed the title Add a post on per-cluster serving stacks Add a post on Dynamo support and per-cluster serving stacks Sep 2, 2026
@negz
negz force-pushed the grove-is-in-the-heart branch from 27db930 to 9f6bcf6 Compare September 2, 2026 19:14
@negz
negz force-pushed the grove-is-in-the-heart branch from 9f6bcf6 to bb6e8bb Compare September 2, 2026 19:30
@negz
negz force-pushed the grove-is-in-the-heart branch from bb6e8bb to 7769322 Compare September 2, 2026 19:52
@negz
negz force-pushed the grove-is-in-the-heart branch from 7769322 to e58fa01 Compare September 2, 2026 19:58
@negz
negz force-pushed the grove-is-in-the-heart branch from e58fa01 to 78640ef Compare September 2, 2026 20:39
@negz
negz force-pushed the grove-is-in-the-heart branch from 78640ef to 1199290 Compare September 2, 2026 23:20
@negz
negz force-pushed the grove-is-in-the-heart branch from 1199290 to 3659739 Compare September 9, 2026 22:09
@negz negz changed the title Add a post on Dynamo support and per-cluster serving stacks Add the v0.4 release post on Dynamo and AI Cluster Runtime Sep 9, 2026
@negz
negz force-pushed the grove-is-in-the-heart branch from 3659739 to 82ede77 Compare September 9, 2026 22:39
@negz
negz marked this pull request as ready for review September 9, 2026 22:44
@negz
negz force-pushed the grove-is-in-the-heart branch from 82ede77 to 6e942a1 Compare September 9, 2026 22:46
@negz
negz force-pushed the grove-is-in-the-heart branch from 6e942a1 to 99adc60 Compare September 9, 2026 23:03
@negz
negz force-pushed the grove-is-in-the-heart branch from 99adc60 to 311e06a Compare September 9, 2026 23:13
@negz
negz merged commit 2988f0a into modelplaneai:main Sep 10, 2026
2 checks passed
@negz
negz deleted the grove-is-in-the-heart branch September 10, 2026 17:48
Modelplane v0.4's two headline features are an NVIDIA Dynamo serving
stack, and serving stacks that take much of their component versions and
configuration from NVIDIA AI Cluster Runtime. A smaller change starts a
cloud's providers only once a control plane has a cluster on that cloud.

The post walks the Dynamo stack from the per-cluster opt-in through gang
scheduling, ModelExpress weight transfer, and one manifest that runs on
either stack, then turns to the AICR-validated versions underneath.

Signed-off-by: Nic Cope <nicc@rk0n.org>

This branch was successfully deployed

1 active deployment
Preview — 311e06a8 Deployed Sep 9, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant