Results for “multi-host”

Test kolu's remote-host features (multi-host / padi-remote) in a real browser against a real remote box — the ONLY full end-to-end harness for this surface (real ssh provision, no mock). Covers the isolated nix-run invocation (or just dev, which bakes the same agent source), ssh- provisioning a real remote box without touching production or another user's box, the chrome-devtools drive sequence for host-switch / split / code-browser / per-host-canvas, PID-exact teardown, and the reproduce- first rule for any bug the feature surfaces. Triggers on "test remote hosts", "test multi-host", "test padi-remote", "verify the host switch", "browser-test a remote host change", or before claiming a remote-host fix works.

The English summary is being prepared. Showing the original description.

Diagnose GKE TPU virtual machines that remain in repair by checking instance status, host events, and automatic repair history. Understand the impact on grouped TPU nodes and identify recovery steps for the user to apply.

• Investigating TPU VMs that remain in REPAIRING
• Assessing how a failed node affects a TPU slice
• Checking automatic repair history and failure reasons

Monitor TPU workloads on GKE using system metrics and PromQL, a metrics query language. Check utilization, memory, node availability, and interruptions to investigate infrastructure issues and calculate average recovery times and intervals between interruptions.

• Checking TPU utilization and memory usage
• Investigating node and node pool availability
• Tracing maintenance and preemption interruptions

Review how you use Superset and identify unused features that fit your workflow. Get a short list of suggestions, learn about each option, and set up selected features such as scheduled agents, parallel workspaces, or shared tasks.

• Find unused Superset features worth exploring
• Set up scheduled agent tasks
• Start parallel work in separate workspaces

Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + `temps agent`, wired with the real multi-host overlay (VXLAN, compute_cidr allocation) via `tools/dev-cluster/` in whichever checkout/worktree you run it from. Invoke when the user says "start the temps cluster", "spin up a multi-node dev cluster", "test this with multiple workers", "bring up worker nodes locally", "docker in dind cluster", or wants to verify cross-node behavior (node targeting, cluster DNS, overlay networking, node join/mTLS) that a single-node `start-temps` server cannot exercise. Distinct from `start-temps` (single-node, native binary, port-slot based) and `start-temps-ee` (single-node EE binary) — this is the only path that actually has more than one node.

The English summary is being prepared. Showing the original description.

Monitors and troubleshoots GKE TPU workloads, nodes, and node pools using GKE system metrics and PromQL. Use when monitoring TensorCore duty cycle, TPU memory, node readiness, multi-host TPU node pool availability, host maintenance or preemption interruptions, and calculating MTTR or MTBI metrics for GKE TPUs. Don't use for general non-TPU GKE workload monitoring or non-metric TPU debugging.

The English summary is being prepared. Showing the original description.

SSH hosts: add, list, exec, exec-all, scp, health-check.

The English summary is being prepared. Showing the original description.