Skip to content

feat(dx): implement monolithic architecture and expert-grade observability suite#163

Closed
nklowns wants to merge 17 commits intoublue-os:mainfrom
nklowns:feat/bazzite-dx-expert-monolith
Closed

feat(dx): implement monolithic architecture and expert-grade observability suite#163
nklowns wants to merge 17 commits intoublue-os:mainfrom
nklowns:feat/bazzite-dx-expert-monolith

Conversation

@nklowns
Copy link
Copy Markdown

@nklowns nklowns commented Apr 6, 2026

PR: feat(dx): implement monolithic architecture and expert-grade observability suite

Summary

This Pull Request introduces a major architectural refinement to bazzite-dx, transitioning to a "Monolithic Expert" pattern. It focuses on consolidating system logic, expanding the observability stack, and modernizing the build pipeline using the latest BlueBuild features.

Fixes #162

Technical Impact & Skeptical Analysis

  • Architecture: Implemented a 5-layer declarative build process in recipes/recipe.yml. This refactor reduces maintenance overhead by centralizing 25+ variants into a single, matrix-aware configuration.
  • Expert Observability: Integrated a production-grade suite for kernel and system analysis (bcc, bpftrace, bpftop, pcp, rocm-smi). These tools are layered natively to ensure kernel header synchronization and zero-dependency execution.
  • Modern Virtualization: Replaced legacy imperative scripts with podman-bootc, incus, and automated Systemd workarounds for libvirt and swtpm, ensuring persistent infrastructure stability.
  • File Stratification: Migrated from system_files to the modernized files/system pattern. This aligns with uBlue standards and improves "Stratum Protection" (Kernel-bound tools in OCI layers | User-space tools in Homebrew).
  • Validation Modules: Introduced local build-time verification (dx-verify) and security hardening (dx-hardening) to ensure image integrity before deployment.

Why this change was made

bazzite-dx has evolved beyond a simple "Bazzite + tools" layer. To match the excellence of Bluefin and Aurora DX, it requires a robust, "Enterprise-grade" workstation environment. This refactor provides developers with deep system visibility (eBPF/Observability) while maintaining the gaming-optimized performance of the Bazzite base.

Examples & Usage

  • System Monitoring: Execute monitor-performance (via ujust) to launch bpftop.
  • Cloud-Native Dev: Seamlessly use podman-bootc for image-based workflows.
  • Standardized Setup: Users can now audit their environment via ujust dx-status and ujust system-inventory.

📖 Documentation & Rebranding

The project identity has been redefined in the README.md and AGENTS.md to reflect our Expert Monolith philosophy. This includes detailed matrix documentation for the 25+ variants and the new Ready-to-Code automation suite.


🛠️ Upstream contributions

To solve the technical debt associated with OCI tagging in complex matrices, we have contributed core improvements to the BlueBuild engine:


Assisted-by: Antigravity via Claude-3.5-Sonnet

nklowns added 17 commits March 25, 2026 18:04
This commit consolidates the full modernization of Bazzite-DX to enterprise standards,
achieving technical parity with Bluefin-DX and Aurora-DX while preserving Bazzite's
specialized gaming foundation.

- Move virt-manager and QEMU setup to build-time scripts
- Replace interactive groupadd with systemd declarative service
- Layer vfio tools via Containerfile instead of runtime wget
- Align DX tools with aurora-dx and bluefin-dx parity
- implement isolated COPR installations for security
- add Bluefin-inspired developer toolkit (cascadia fonts, git-svn, etc)
- add conditional ROCm logic for non-nvidia hardware
- port Aurora-DX secure package patterns (kcli, podman-bootc)

Key Improvements:
- Security: Implemented 'Build Firewall' repo validation gate (Wave 1).
- Architecture: Refactored Containerfile for multi-stage OCI inheritance from common/brew images (Wave 2).
- Toolset: Integrated eBPF tracing tools (bcc, bpftrace) and DX-specific Brewfiles (Wave 3).
- Compatibility: Added DNF5 vendor overrides and automated Tailscale operator setup (Wave 4).
- Modularity: Migrated from monolithic setup to official uBlue hook system in user-setup.hooks.d (Wave 5).
- Virtualization: Ported SELinux workarounds for Incus, SWTPM, and Libvirt using bind-mount techniques (Wave 6).
- UX: Integrated Starship shell prompt and created customized Fastfetch DX preset (Wave 7).

This transformation elevates Bazzite-DX to a premium engineering workstation,
ensuring idempotency, maintainability, and seamless upstream alignment.
…te `Justfile` to utilize it for VM creation and add SSH forwarding, and revise `AGENTS.md` with updated workflow instructions and configuration references.
…d kernel arguments, and streamlined user provisioning
…v, and image-info modules while reorganizing Brewfiles and justfiles.
…IDIA version label propagation in build workflow
@nklowns
Copy link
Copy Markdown
Author

nklowns commented Apr 6, 2026

Hello @HikariKnight and @KyleGospo,

We are submitting this PR to formally modernize the bazzite-dx architecture into an Expert Monolith pattern.

Our goal was to streamline the 25+ variant matrix while significantly expanding the observability stack with native eBPF/kernel-bound tools. This approach ensures that Bazzite-DX remains the definitive workstation for high-performance engineering on Atomic Desktops.

We have also tackled the OCI tagging friction we encountered during this refactor by contributing core improvements to the BlueBuild engine (cli#746 and cli#747).

Looking forward to your feedback on this architectural shift.


Assisted-by: Antigravity via Claude-3.5-Sonnet

@KyleGospo KyleGospo closed this Apr 6, 2026
@ublue-os ublue-os locked and limited conversation to collaborators Apr 6, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Modernizing Bazzite-DX with Monolithic Architecture and Expert Tooling

2 participants