wsh:cluster-orchestration

Managing terminal sessions across multiple servers requires cluster orchestration to route and coordinate distributed workflows from a central hub. This Skill implements a hub-and-backends architecture to handle distributed session creation, server discovery, and health monitoring.

Parallelizing builds and tests across a federated cluster is best achieved through tag-based fan-out workflows. This Skill coordinates distributed sessions across multiple backends, allowing you to route parallel tasks to specific servers based on tags.

Health monitoring for distributed backends tracks server states to ensure only healthy servers participate in session routing. This Skill manages server registration and discovery, automatically handling failures by transparently reallocating or recreating sessions on healthy backends.

Yes, you can coordinate idle terminal sessions across different servers using cross-server idle coordination. This Skill manages distributed session states, ensuring synchronized idle handling and efficient resource utilization across the federated cluster.

You need a hub-backend architecture for session management when scaling terminal workflows requires isolation and coordination across a fleet of servers. This Skill provides a central hub to route sessions, monitor backend health, and manage distributed workflows.

Yes, this orchestration approach handles backend server failures automatically through transparent reallocation and recreation of sessions. When health monitoring detects a failed backend, the hub routes affected sessions to other healthy backends in the cluster.