Change how big each session's VM is
Do this when sessions on one MicroVM node need more room, or when each VM asks for more than the machine has. On a MicroVM node, each session runs in its own VM. A size set on the node wins over one set for a project or for your organization, and those win over Jaah's default.
Who can do this: requires the org admin role and the permission to edit nodes. Without them, the Shape tab is read-only. It is read-only too on a node the operator locked, on a Jaah cloud node, or one shared with other organizations.
Plan: needs MicroVM nodes on your plan. The Shape tab shows only while your plan includes it.
- In the sidebar, select Directory, then the Machines tab.
- Select the node's name, then its Shape tab.
- Read Size. It lists vCPUs, RAM and Disk, each with its value and where it comes from: from node, from project, from org or from system, the default.
- Select Edit size. A box opens for each size: vCPUs, RAM (MiB) and Disk (GiB). A box holds the node's own value, or is blank when the node inherits it. Under a blank box, Now shows the size in force.
- Type a whole number in each box you want to change. Clear a box to inherit that size again.
- Select Save, or Cancel to leave the sizes as they were. Save stays unavailable until something changed and every box holds a whole number.
- Check Size again: each value you set now reads from node.
If the size is larger than the machine, a warning under Size says Larger than this host with the machine's vCPUs and RAM. A node starts a VM only while it has the free RAM and disk for it, so lower the size or use a larger machine.
On a Whole-node VM node, the tab shows VM size instead, the size of the node's one VM. Changing it restarts that VM.
Related
- Choose a node's shape: turn MicroVM on or off on a node.
- How nodes work: how nodes, slots and sessions fit together.
- Change a cloud node's machine type or disk: give the machine itself more room.