Amc/Blueforce-Linux
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Blueforce-Linux/scripts/install
History
emirhanmamak-blueforce ef102b9657 feat(field-os): provisioning layer, real ISO build, offline contracts 
Adds the Blueforce Field OS provisioning stack on top of the existing fleet
architecture, without rewriting the working systems (installer, diagnostics,
Ansible, WireGuard/SSH/xRDP/RustDesk, Docker policies, monitoring, Docusaurus).

ISO build (the previous builder was a skeleton that produced no medium):
- boot layout is read from the base ISO at build time via
  `xorriso -report_el_torito as_mkisofs` and rebuilt with `-as mkisofs`;
  `-boot_image any replay` cannot work on Ubuntu live ISOs because the GRUB2
  MBR lives in the source image's first 16 sectors and the EFI system partition
  is an appended partition, neither of which is a file in the ISO9660 tree
- preflight now asserts El Torito boot metadata positively: xorriso exits 0 on
  a non-ISO input, which previously let an arbitrary file pass --check
- artifact produced and verified: dist/Blueforce-Field-OS-1.0.0-amd64.iso,
  6 481 917 952 bytes, SHA256 cb0cc56f...d431296, BIOS+UEFI entries preserved,
  /autoinstall.yaml at the media root, casper/minimal.squashfs byte-identical
  to the base
- recorded baseline deviation: the verified medium on the build host is the
  Desktop flavour, so the manifest carries a baseline_deviation block instead
  of hiding it; Server remains one flag away

Offline and identity:
- offline APT contract with concrete package requirements, pin format and an
  audit table; builds fail closed while pins are UNPINNED
- autoinstall keeps interactive-sections: [storage]: the operator confirms the
  target disk, and no automatic wipe is ever performed
- firstboot terminal wizard for the 8-digit dealer id, three-state lifecycle
  (PROVISIONED_OFFLINE -> ENROLLED -> READY) with fail-closed gates, so a
  missing internet link or WireGuard handshake cannot fail provisioning but can
  never produce a false READY

Fleet and migration:
- five read-only Ansible playbooks for Field OS version, provisioning,
  enrollment, remote channels and offline readiness, all wave-scoped with a
  separate production override
- Windows pre-migration inventory and data export extended to the full brief
  scope, read-only, never collecting credentials

Tests: tests/run-all.sh -> 8/8 pass, exit 0. Boot acceptance (UEFI, Legacy
BIOS, Secure Boot), air-gapped install, real enrollment endpoint and Windows
rollback remain LAB work and are listed in IMPLEMENTATION-REPORT.md.
2026-09-16 11:14:42 +03:00
..
installer feat(field-os): provisioning layer, real ISO build, offline contracts 2026-09-16 11:14:42 +03:00
optional/anydesk feat(field-os): provisioning layer, real ISO build, offline contracts 2026-09-16 11:14:42 +03:00
.gitkeep docs: Blueforce 700-device fleet architecture (TR) - GNOME baseline 2026-09-15 17:03:02 +03:00
blueforce-install.sh feat(field-os): provisioning layer, real ISO build, offline contracts 2026-09-16 11:14:42 +03:00
README.md feat(field-os): provisioning layer, real ISO build, offline contracts 2026-09-16 11:14:42 +03:00

README.md

Blueforce installer (scripts/install/)

Single entry point: sudo ./blueforce-install.sh --dealer-id <8 digits>.

  • Orchestrator: blueforce-install.sh (dealer-id gate ^[0-9]{8}$, hostname bf-<no> + device BF-<no>, ordered module runs, --resume, results to /var/log/blueforce-install.log + /var/lib/blueforce/install-state).
  • Modules: installer/modules/01-*.sh … 18-*.sh. Every module is idempotent and supports --check (read-only audit). Exit 0 = OK, 3 = SKIP.
  • Required remote-channel preconditions: set per-device WG_ADDRESS, WG_ENDPOINT, and WG_PEER_PUBKEY; WireGuard readiness requires a peer handshake no older than BF_WG_HANDSHAKE_MAX_AGE seconds (default 180) unless REQUIRE_WIREGUARD=false. Set RUSTDESK_SERVER to a real self-hosted endpoint and provide the pinned local RUSTDESK_DEB; placeholders are rejected.
  • Docker published ports default to deny. Add only reviewed tcp PORT or udp PORT entries to /etc/blueforce/docker-published-port-allowlist.conf; the enabled blueforce-docker-firewall.service reapplies that policy after Docker starts.
  • Exit codes: 0 READY · 1 module failure · 2 argument/format error.

Module map: 01-precheck · 02-system · 03-user · 04-hostname · 05-network · 06-wireguard · 07-ssh · 08-rdp · 09-rustdesk · 10-docker · 11-meg · 12-monitoring · 13-firewall · 14-update-policy · 15-logrotate · 16-gui · 17-healthcheck · 18-final-check.

NOTE on AnyDesk: there is deliberately no AnyDesk module. Remote access is covered by SSH-over-WireGuard, xRDP and RustDesk. AnyDesk stays a manual, per-device exception outside this installer.