Request a demo

Take the product tour

Four short walkthroughs on sample product screens. Use Next and Previous, or the arrow keys. The product interface is English-only.

A node stops responding

  1. The cluster summary shows gpu-02 with READY Unknown and the code E-NODE-008.

  2. Problems shows E-NODE-008, its age, and runbook RB-NODE-008.

  3. The node page opens the coded error card. First field: what happened.

  4. No new job lands on the node; running jobs continue.

  5. The node is marked Unknown, and the drain lifts by itself when the node returns.

  6. The next step for the operator and the offline runbook to follow.

  7. The operator can cordon the node to keep it out of the queue during maintenance.

Step 1 of 7

An alert, its impact, and a two-step approval

  1. E-PROV-007 on gpu-03: a change that BareStax will not apply while jobs run.

  2. The impact view separates what is confirmed from what is only possible, with the age of the data.

  3. Jobs 4521 and 4533 run on gpu-03.

  4. The approver must read the impact before continuing.

  5. The approver types gpu-03 to confirm, so a wrong target is hard to approve. Try it.

Approval: drain-gpu-03

Read the impact on gpu-03; press Continue to approve.

Request
drain-gpu-03 · node.drain
Requested by
user:operator-1
Their reason
Configuration drift that requires downtime (E-PROV-007)
Blast radius
2 jobs · 1 tenant (research-a)
Policy
four-eyes-drain
Verified: 1 node, 2 jobs, 1 tenant4521, 4533 · 2 min ago

Confirm the approval: drain-gpu-03

The person who opened the request cannot approve it.

user:operator-2

Sample product interface
Step 1 of 5

A researcher starts a Jupyter session

  1. The portal form asks for a queue, the number of GPUs, and the duration.

  2. The session is submitted as a scheduled job.

  3. The job waits with a visible reason, then runs on gpu-01 and opens in the browser.

  4. Every portal action can be copied as a command for scripts.

Step 1 of 4

A container image needs two people

  1. operator-1 asks to promote a scanned image.

  2. The requester cannot approve their own request.

  3. A second person, approver-2, reviews and approves.

  4. A third person approves; the image is signed with the cluster key and becomes available to compute nodes.

Step 1 of 4

See it on your own cluster