Go to file

Thomas Stallinger 086917deec feat: resolve Runtime Blueprint and add Fedora backend for kickstart generation

30_runtime_blueprint.sh calls POST /templates/{id}/resolve with the
device_id from the server handshake and the template_id from the
Bereitstellungsvorlage selection, storing the resulting Runtime
Blueprint under /run/tuxflotte/runtime/.

40_backend.sh dispatches to backends/${backend_id}/backend.sh based on
the resolved backend_id and drives the backend_init/validate/
generate_config/launch/postinstall lifecycle from 06-backend-api.md.

backends/fedora/backend.sh implements that lifecycle for Fedora:
backend_generate_config() renders kickstart.tpl via envsubst using the
Runtime Blueprint's installation_directives and the device hostname,
embedding the resolved Merkmal blueprints as JSON for the (not yet
implemented) Provisioning Agent to apply later. Replaces the old
git-clone-based %post bootstrap. backend_launch()/backend_postinstall()
are Phase 1 stubs pending the live-ISO boot integration (see
platform-docs ADR-0003).

2026-07-18 10:49:50 +02:00

backends/fedora

feat: resolve Runtime Blueprint and add Fedora backend for kickstart generation

2026-07-18 10:49:50 +02:00

config

Refactor installer into modular orchestration framework

2026-07-07 10:27:32 +02:00

grub

feat: add local boot entries and bump ISO to 0.2

2026-07-13 10:46:33 +02:00

scripts

feat: resolve Runtime Blueprint and add Fedora backend for kickstart generation