From ac9370931c8e3caa4d9b04b9d8654a2acb748226 Mon Sep 17 00:00:00 2001 From: Oleksandr Bezdieniezhnykh Date: Sun, 19 Apr 2026 21:38:00 +0300 Subject: [PATCH] Remove Jetson device provisioning runbook and scripts - Deleted the provisioning runbook and associated scripts as they have been relocated to the suite meta-repo. This change reflects the shift in focus for device provisioning, which is now managed outside the loader repository, streamlining the project and removing outdated documentation. --- .../02_document/deployment/provisioning_runbook.md | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 _docs/02_document/deployment/provisioning_runbook.md diff --git a/_docs/02_document/deployment/provisioning_runbook.md b/_docs/02_document/deployment/provisioning_runbook.md deleted file mode 100644 index 4500d6b..0000000 --- a/_docs/02_document/deployment/provisioning_runbook.md +++ /dev/null @@ -1,14 +0,0 @@ -# Jetson device provisioning runbook (moved) - -The provisioning runbook and its scripts (`provision_devices.sh`, `ensure_l4t.sh`, `setup_rootfs_docker.sh`, `harden_rootfs.sh`) no longer live inside the `loader` repository. - -They were relocated to the suite meta-repo because device provisioning is a fleet/manufacturing concern, not a Loader concern — it sets up the base OS, Docker, identity, and hardening that all services share. - -- **New location:** `suite/provisioning/` -- **Runbook:** `suite/provisioning/README.md` - -If you are working inside the loader repo in isolation, the scripts are not available here; clone the suite meta-repo to run provisioning. - -## Note on Loader retirement - -The provisioning flow in `suite/provisioning/` still references Loader today because `setup_rootfs_docker.sh` has not yet been rewritten for the Scenario X deployment model (Watchtower + rclone + flight-gate). The rewrite is tracked as a follow-up in `suite/ci/README.md`. Until the rewrite lands, newly-provisioned devices continue to boot with the legacy Loader service and will need a separate migration step to the new deployment model.