Start, stop, and destroy
Power controls live on the instance header. Each change queues a job and returns accepted — the panel does not wait on the node. While a power or switch-title job is open, the header refreshes until it settles.
Desired, then observed
Services lists your instances that are not destroyed. Start, stop, and destroy sit in the instance header. The control plane records desired power, enqueues a job, and returns accepted. Observed power catches up when the node reports. While that job is open, the header hides a second click and refreshes until the job settles.
A dead node session is not a stopped guest. Desired power stays until you change it. Destroy removes the instance from Services after the destroy job finishes — keep the instance id if you still need support about that volume.
From the panel
Open the instance from Services. Use the header controls — the overview does not grow a second power strip. Switch title and pack editors stay on their own cards.
- Open the instance from Services.
- Start, stop, or destroy from the header.
- Wait for observed power to match what you set.
- Copy the instance id if support needs to match jobs or nodes.
What start, stop, and destroy change
Start sets desired power to running and queues a job. Stop sets desired power to stopped and keeps the join host. Destroy removes the instance after the destroy job finishes. None of these run the guest inside the panel. Observed power is what the node last reported.