mirror of
https://github.com/azaion/loader.git
synced 2026-04-22 06:56:31 +00:00
Oleksandr Bezdieniezhnykh
ac6cb35112
- Deleted the Jetson device provisioning runbook and associated scripts (`provision_devices.sh`, `ensure_l4t.sh`, `harden_rootfs.sh`, `setup_rootfs_docker.sh`, and `.env.example`) as part of a cleanup effort. This streamlines the project by removing outdated documentation and scripts that are no longer in use.
15 lines
1.1 KiB
Markdown
15 lines
1.1 KiB
Markdown
# 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.
|