Document first successful Fedora provisioning milestone

lessons-learned.md

@@ -0,0 +1,61 @@
+# Lessons Learned
+
+## Fedora Kickstart
+
+### Network
+
+The installer was able to retrieve Kickstart files via HTTPS through Pangolin.
+
+### DNS
+
+Initial tests indicated DNS resolution issues. Verification showed that network connectivity was available and the Kickstart file could be downloaded.
+
+### Disk Naming
+
+The virtual machine used:
+
+* VirtIO SCSI controller
+* SCSI disk (scsi0)
+
+The installer exposed the disk as:
+
+/dev/sda
+
+not:
+
+/dev/vda
+
+Therefore:
+
+ignoredisk --only-use=vda
+
+caused installation failure.
+
+### User Accounts
+
+An unattended installation requires either:
+
+* a valid root account configuration
+* or a local user definition
+
+### Post Installation
+
+The following actions were successfully executed in %post:
+
+* MOTD creation
+* Git installation
+* Ansible installation
+* Repository cloning
+
+### Architectural Validation
+
+The following concept has been successfully validated:
+
+Generic installation media
+→ Activation service
+→ Profile
+→ Installer definition
+→ Automatic installation
+→ Git repositories
+→ Configuration management
+

milestones.md

@@ -0,0 +1,36 @@
+# Milestones
+
+## 2026-06-16
+
+### First successful unattended Fedora installation
+
+A Fedora virtual machine was successfully installed using a Kickstart definition served from the provisioning platform.
+
+Installation flow:
+
+Fedora Netinstall ISO
+→ HTTPS
+→ anode.stallinux.de
+→ Kickstart definition
+→ Automatic installation
+→ Reboot
+→ Successful login
+
+Verified components:
+
+* Proxmox VM
+* Pangolin reverse proxy
+* FastAPI provisioning service
+* HTTPS / Let's Encrypt
+* Fedora Kickstart
+* Automatic partitioning
+* User creation
+* Package installation
+* Post-install scripts
+* Git repository access
+* Ansible installation
+
+Result:
+
+The core architecture of the Stallinux Provisioning Platform has been validated end-to-end.
+