docs: add Getting Started section with prerequisites, quick start, and reference installation#1227
Merged
Merged
Conversation
bfeb251 to
cff6bad
Compare
8db8e6f to
3664db9
Compare
3664db9 to
64bc25b
Compare
Contributor
|
PR conflict, can you resolve it? |
64bc25b to
7b32e7c
Compare
|
🌿 Preview your docs: https://nvidia-preview-pull-request-1227.docs.buildwithfern.com/infra-controller |
7b32e7c to
4d41ce9
Compare
Contributor
Author
merge conflicts resolved, @shayan1995 since this touches your helm-prereqs README and SETUP-PHASES.md, please review. |
8 tasks
Contributor
|
/ok to test 9ec63e8 |
ajf
approved these changes
Apr 30, 2026
Contributor
|
Three issues which I noticed:
|
5a7ef10 to
3ae2584
Compare
5 tasks
Contributor
Author
|
@benhuntley issues addressed across both #1190 and #1227 |
3ae2584 to
19507de
Compare
Contributor
Author
|
/ok to test 19507de |
Contributor
Author
|
@Coco-Ben please review |
Coco-Ben
reviewed
May 5, 2026
Coco-Ben
approved these changes
May 5, 2026
Rewrites the entire Overview section of the NICo documentation and adds a new landing page, following the IA recommendation from CDEVS-2173. Overview section (5 pages): - What is NICo? — intro, "Why NICo exists" (sourced from VDR/Code Yellow), architecture overview with NICo Components and Prerequisite Components matching the architecture diagram, "Where NICo fits" stack diagram - Key Capabilities — hardware readiness, DPU lifecycle, multi-tenancy, trust/attestation, firmware control, deployment flexibility, GB200 rack-scale - Operational Principles — 5 foundational design principles - Day 0/1/2 Lifecycle — three operational phases - Scope and Boundaries — two-column tables showing NICo vs platform responsibilities (renamed from "What NICo Does Not Cover") Landing page (index.md): - Persona-based entry points: Deploy & Operate, Integrate, Evaluate - Quick links to HCL, release notes, FAQs, GitHub repos Other changes: - Replace "NCX Infra Controller" with "NVIDIA Infra Controller" in prose - Replace "GB200/GB300-class AI infrastructure" with "AI factory-scale infrastructure" - Fix /admin UI protocol: HTTP → HTTPS - Fix database name: forgedb → forge_system_carbide - Remove Route Server from NICo Components (not a NICo-deployed service) - Remove hand-wavey/marketing language across all overview pages - Remove duplicative content between overview pages - Add explicit URL slugs to prevent Fern slug mangling (what-is-ni-co) - Replace stale Introduction page (README.md) with new landing page Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Andrew Liu <andreliu@nvidia.com> -e Signed-off-by: Peter Gambrill <pgambrill@nvidia.com>
…d reference installation Adds the Getting Started section covering the full deployment path from prerequisites through first host discovery, following the IA recommendation from CDEVS-2173. Prerequisites (4 pages): - Hardware — site controller specs, compute system requirements, DPU details, BIOS/UEFI settings, link to HCL for supported GPUs/systems - Network — IP sizing formulas, address pools, ASN/VNI allocations, underlay BGP, EVPN overlay (with route server explanation), route-targets, switch config, site controller topology, physical cabling - Software — validated versions for all dependencies with "if you already have / if deploying reference" decision paths, installation order - BMC/OOB Setup — DHCP relay, BMC credentials, expected machines manifest, Redfish requirements Quick Start Guide (7 steps): 1. Build NICo Containers (links to existing build guide) 2. Prepare K8s Cluster (requirements, tools) 3. Configure Site (full checklist from helm-prereqs README) 4. Run setup.sh (phase table, what gets deployed) 5. Verify Site Controller (pod checks, LoadBalancer, Keycloak, carbide-cli) 6. Connect OOB Network (DHCP relay verification) 7. Discover First Host (credentials, manifest, TPM approval) Reference Installation: - Manual phase-by-phase installation (from SETUP_PHASES.md) - PKI architecture (3-layer cert chain) - PostgreSQL architecture (Zalando operator, credential flow) - Full troubleshooting guide Provisioning (Day 0 Operations): - Ingesting Hosts (consolidated with expected machines management) - Host Validation, SKU Validation (moved from Operations) Other changes: - helm-prereqs/README.md slimmed to config reference + pointers to docs - helm-prereqs/SETUP_PHASES.md removed (content in reference installation) - Old pages removed: site-reference-arch, site-setup, networking_requirements, expected_machine_update, kubernetes/bootstrap - TLS/SPIFFE page moved from kubernetes/ to development/ - CLI naming standardized: admin-cli (gRPC) vs carbide-cli (REST) - NTP clarified: not a NICo service, provided via DHCP option 42 - carbide-ntp removed from VIP table (chart doesn't exist) - Database name corrected: forgedb → forge_system_carbide - Landing page persona table updated to reference new pages Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Signed-off-by: Andrew Liu <andreliu@nvidia.com> -e Signed-off-by: Peter Gambrill <pgambrill@nvidia.com>
-e Signed-off-by: Peter Gambrill <pgambrill@nvidia.com>
-e Signed-off-by: Peter Gambrill <pgambrill@nvidia.com>
80a32c6 to
02354fd
Compare
shayan1995
approved these changes
May 5, 2026
inf0rmatiker
pushed a commit
to inf0rmatiker/infra-controller
that referenced
this pull request
May 7, 2026
…d reference installation (NVIDIA#1227) ## Summary Adds the Getting Started section to the NICo documentation, covering the full deployment path from prerequisites through first host discovery. - **Prerequisites** (4 pages): Hardware, Network, Software, BMC/OOB — consolidated from site-reference-arch.md, site-setup.md, and networking_requirements.md - **Building NICo Containers**: repositioned in nav before Quick Start - **Quick Start Guide**: 7-step deployment walkthrough (build → K8s → configure → deploy → verify → OOB → first host) with site configuration pulled from helm-prereqs/README.md - **Reference Installation**: manual phase-by-phase installation from SETUP_PHASES.md, plus PKI architecture, PostgreSQL architecture, and troubleshooting - **Provisioning (Day 0 Operations)**: new section with Ingesting Hosts, Host Validation, SKU Validation - **helm-prereqs/README.md**: slimmed to lightweight pointer to docs site - Old pages removed where fully superseded (site-reference-arch, site-setup, networking_requirements, expected_machine_update, bootstrap) - TLS/SPIFFE page moved from kubernetes/ to development/ - CLI naming standardized: admin-cli (gRPC) vs carbide-cli (REST) with distinction table ## Context Part of NICo Docs Code Yellow (FORGE-8168). Follows the IA recommendation from CDEVS-2173 for the Getting Started section structure. Builds on the Overview section work in PR NVIDIA#1190. ## Test plan - [ ] Preview with `fern docs dev` — verify all nav links resolve - [ ] Walk through Quick Start Guide steps 1-7 for completeness - [ ] Verify prerequisite pages cover all content from removed old pages - [ ] Verify Reference Installation troubleshooting section is complete - [ ] Check landing page persona table links resolve to new page paths - [ ] Verify helm-prereqs/README.md links point to published docs URLs 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Signed-off-by: Peter Gambrill <pgambrill@nvidia.com> Signed-off-by: Andrew Liu <andreliu@nvidia.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com> Co-authored-by: Peter Gambrill <pgambrill@nvidia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the Getting Started section to the NICo documentation, covering the full deployment path from prerequisites through first host discovery.
Context
Part of NICo Docs Code Yellow (FORGE-8168). Follows the IA recommendation from CDEVS-2173 for the Getting Started section structure. Builds on the Overview section work in PR #1190.
Test plan
fern docs dev— verify all nav links resolve🤖 Generated with Claude Code