Install, verify, upgrade, remove
Installation and lifecycle
The installer follows seven phases, makes no change before validation passes, and verifies every file it places against a SHA-256 manifest.
Installer phases
| Phase | What happens |
|---|---|
| 1. Discovery | Inspects the OS, architecture, web server, SELinux state, tools and existing configuration. No changes. |
| 2. Validation | Checks support and dependencies; stops before any change if something blocks the install. |
| 3. Preparation | Records existing configuration and prepares backups and a rollback plan. |
| 4. Installation | Installs the engine, service account, directories and configuration. |
| 5. Integration | Configures log access, SELinux labels where needed, and the systemd services. |
| 6. Verification | Confirms the engine actually runs, not just that commands succeeded. |
| 7. Completion | Records installed components, versions and changes. |
Manifest verification
- Every input file is checked against a SHA-256 manifest before anything is installed.
- Files already present with the expected content, owner and mode are kept; only changed files are replaced.
- Replaced files are backed up first, so an upgrade can be rolled back.
- Every installed file is verified again afterward, and the installer confirms the service account can execute the engine.
- The helper-only sudo rule is installed last, only after the helper, policy, account and sudo syntax all pass their checks.
- Running the installer again with no changes replaces nothing.
What the installer does not do
- It never configures, enables or starts the host firewall (firewalld).
- It never changes global sudo defaults or other users' privileges.
- It installs XDP components disabled.
- Runtime dependencies come from Red Hat repositories, installed through the package manager.
Updates
Each yearly renewal delivers a fresh build of the latest release, installed through the same verified process. Critical security fixes are delivered as soon as they are available.
Removal
Because the installer records what it owns, removal is designed to reverse only its own changes: services stopped and disabled, DAV's nftables table and XDP program removed, the sudo rule and service account deleted, and installer-owned files removed. Customer configuration is left as it was.
Packaging: the current release uses the manifest-verified installer described here. The final packaging format for
distribution is being decided with the certification.