How It All Fits Together
The big picture, before you dive into any one project
Skybaer Labs isn’t a set of disconnected side projects. It’s built to mirror how a small hybrid environment actually runs: a fleet of Linux servers under configuration management, a container platform hosting that automation, and a Windows enterprise stack tied into the same identity system as everything else. Here’s how the pieces connect.
Linux Fleet
control.lab drives Ansible playbooks against four RHEL 10 nodes for hands-on development and testing. See the Ansible / RHCE Lab.
Automation & Container Platform
AWX, running inside a nested OpenShift cluster, pulls the same playbooks from GitHub and runs them as scheduled or on-demand jobs against the whole fleet, Linux and Windows alike. See OpenShift & AWX.
Windows Enterprise Stack
DC01 (formerly WinLab2025) is the domain controller for the lab, and also runs SQL Server, IIS, and a Microsoft Endpoint Configuration Manager site. See Windows Integration.
One identity, both platforms
control.lab and the RHEL nodes join that same domain via realmd and sssd, so Linux and Windows share one directory instead of running as two separate islands.
What’s next: Foreman / Satellite
foreman.lab is live and mid-configuration for systems lifecycle management and patching, not yet wired into the automation above. See Foreman / Satellite.
