diff --git a/mkdocs/blog/posts/glm53-gb200-nvl72-coding-agents.md b/mkdocs/blog/posts/glm53-gb200-nvl72-coding-agents.md index 3c46f30d3..67d75719b 100644 --- a/mkdocs/blog/posts/glm53-gb200-nvl72-coding-agents.md +++ b/mkdocs/blog/posts/glm53-gb200-nvl72-coding-agents.md @@ -130,7 +130,7 @@ Almost all of the gain came from layout decisions: whether to disaggregate, how Both presets are public: [aggregated](https://sky.dstack.ai/presets/dstackai/glm53-gb200-nvl72-agentic-c48) and [PD disaggregated](https://sky.dstack.ai/presets/dstackai/glm53-gb200-nvl72-agentic-pd-c128). They can be deployed via `dstack` to any GPU cloud, Kubernetes, or bare-metal cluster with GB200 NVL72 nodes and a CPU node for the router. -To deploy on Crusoe, use `dstack`'s native integration: it can provision [VMs](../../docs/examples/clusters/crusoe.md#vms) through the `crusoe` backend or use a [Kubernetes](../../docs/examples/clusters/crusoe.md#kubernetes) cluster through the `kubernetes` backend. Any other nodes can be added as an [SSH fleet](../../docs/concepts/fleets.md). +To deploy on Crusoe, use `dstack`'s native integration: it can provision [VMs](../../docs/examples/clusters/crusoe.md#vms) through the `crusoe` backend or use a [Kubernetes](../../docs/examples/clusters/crusoe.md#kubernetes) cluster through the `kubernetes` backend. Any other nodes can be added as an [SSH fleet](../../docs/concepts/fleets.md). For a step-by-step setup of the GB200 NVL72 rack, from creating the VMs and enabling IMEX to validating NVLink, see Crusoe's [post](https://www.crusoe.ai/resources/blog/serving-glm-5-3-coding-agents-faster-on-nvidia-gb200-nvl72) on this work. Once the fleet is created, pull a preset, export it as a service configuration, and apply it: