KLYRN VM / Blog

A refused machine says exactly why

When KLYRN VM cannot place a machine it names the reason: how much memory, disk or processor was short, or which state the node is in.

· 1 min read · The KLYRN team

DesignOperations

An operator picked a node, pressed Create, and read: "The chosen compute node cannot place this virtual machine." Under Details was the same sentence again. The panel had worked out the reason and then kept it to itself.

From 1.1.7 the sentence carries it.

What it says now

For a node you chose: "971 GiB memory short (needs 977 GiB, allocated 26 GiB of 31 GiB at 1.0x)." The same for disk and processors, with what was needed and what was free. A node that is held, in maintenance, in observe mode or not connected says that instead.

When no node was chosen and none could take the machine, every node is listed by name with its own reasons, so "nowhere" becomes a list you can act on.

What a customer reads

A customer is told which of their own numbers did not fit: not enough free memory for this size, not enough disk, or nothing in the chosen location. They are not told the names of your hosts or how much of each you have sold. That is your business, and the older message carried it in its details for anyone who looked.

How it is kept true

The create journey in the test suite now refuses a machine on purpose and checks that the reason is on the page without opening anything. A message that goes back to saying nothing fails the build.

The same rule runs through the rest of the panel: a host says what is wrong with it in a sentence, and an error says what happened and what to do next.