Why the topology page matters
The topology page expresses the whole platform in one operational language. It maps the application and identity plane to FreeIPA, Foreman, storage, gateways, dedicated jump relays, WoL relays, classrooms, and individual workstations. Operators can see not only what exists, but which path is responsible for authentication, provisioning, inventory, power, console access, and recovery.
Truthful evidence model
Topology dimensions
| Dimension | What the map communicates |
|---|---|
| Authority | Which system owns browser authentication, provisioning, Linux identity, authorization, inventory, and operational evidence. |
| Transport | HTTPS, SCIM bearer, LDAP/LDAPS, Kerberos, DNS, Puppet/Foreman, SSH, VNC, NFS, and WoL paths. |
| Physical context | Buildings, rooms, relays, seats, and surrounding infrastructure. |
| Health | Healthy, degraded, offline, blocked, unknown, stale, and conflicting states with reasons. |
| Remote support | Which jump and Guacamole path reaches each workstation and whether a console can be launched. |
| Safety | Configured relationships are not misrepresented as live traffic; sensitive or unrelated overlay addresses are excluded. |
From map to action
The map is not decorative. It is a navigation and diagnosis surface: choose a room, workstation, relay, identity system, or protocol edge; inspect the linked evidence; understand the blocker; then take the bounded action from the correct control plane.