Skip to content

Add NVIDIA DGX Spark docs - #305

Open
YanisaHS wants to merge 9 commits into
canonical:mainfrom
YanisaHS:LNDENG-4933/dgx-spark-docs
Open

Add NVIDIA DGX Spark docs#305
YanisaHS wants to merge 9 commits into
canonical:mainfrom
YanisaHS:LNDENG-4933/dgx-spark-docs

Conversation

@YanisaHS

@YanisaHS YanisaHS commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

This PR is based on the content #293 (thanks to @rajannpatel for the original research and draft!! 🎈), but with revisions and restructuring.

The docs in this PR cover DGX Spark specifically, but are more tightly focused on the Landscape side of the workflow: registering the system, enabling remote script execution, and running NVIDIA's Landscape reference scripts.

Main changes from the original PR: I've removed the DGX provisioning part and NVIDIA scripts reference and linked to their documentation instead. This is because those are more relevant to NVIDIA and would be better maintained on their side.

Other notable (but minor) changes to the information:

  • Added Landscape Client installation with sudo pro enable landscape. The original PR assumed the client was already installed, and this matches NVIDIA's own enrollment steps.
  • Separated NVIDIA's production tools from their Landscape reference scripts. The how-to covers the reference scripts, since those are the ones written for remote script execution.
  • Added the interpreter requirement when adding a script, and how NVIDIA's scripts find attached files through LANDSCAPE_ATTACHMENTS.
  • Removed the out-of-band management sections (Redfish, IPMI, BMC), since Landscape doesn't use those interfaces.

@YanisaHS
YanisaHS marked this pull request as ready for review August 19, 2026 23:09

NVIDIA remains authoritative for DGX Spark and DGX OS, including platform compatibility, drivers, firmware, recovery, provisioning, hardware-level management, diagnostics, and the detailed behavior of NVIDIA tools.

NVIDIA's [Enterprise Lifecycle Integration](https://docs.nvidia.com/dgx/dgx-spark/enterprise-fleet-lifecycle.html) documentation distinguishes between production tools and Landscape reference scripts. The production tools are intended for fleet automation. The Landscape scripts are reference implementations designed for use with Landscape remote script execution and may require adaptation for an organization's processes. They are not a replacement for NVIDIA's production tools.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wish to add this sentence at the end of this paragraph: Both production tools and Landscape reference scripts can be run on one or more DGX workstation machines using Landscape's UI, or API.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rajannpatel Added. I changed it a tiny bit because this comment is on an older commit, so the language in that section changed a bit to. But it still addresses the same point you're making

@YanisaHS
YanisaHS requested a review from rajannpatel August 20, 2026 19:46
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.

2 participants