> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/admin-guide/sizing-and-upgrades.md).

# Sizing and upgrades

![Sizing from System monitor](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FDuh5rzclbBuDf9rd95hE%2Fve20261112v5-infrastructure.png?alt=media)

## Goal

Pick CPU/RAM/disk for your class size and plan upgrades.

## Sizing tiers

| Tier     | vCPU | RAM       | Disk        | Notes                   |
| -------- | ---- | --------- | ----------- | ----------------------- |
| Light    | 8    | 16 GB     | 200 GB      | Few Docker / small QEMU |
| Teaching | 16   | 32 GB     | 250 GB+     | Mixed class             |
| Advanced | 32+  | 64-128 GB | 500 GB-1 TB | vJunos / many QEMU      |

Prefer bare-metal USB for deep nested QEMU.

## Recipe: before a big class

1. Confirm Launch Budget / free disk on Home
2. Pre-import images
3. Cap student quotas
4. Smoke-test one Certified platform end-to-end

## Upgrades

### In-place update package (preferred for API/UI fixes)

See [In-place updates](/admin-guide/in-place-updates.md). Example:

```bash
sudo vexnx-update apply /path/vex-nx-1.0.44-to-1.0.45-amd64.vxp
```

### Full OVA / USB (major releases or OS changes)

1. Export / note management IP and licence file
2. Deploy new OVA or re-flash USB ISO per vendor instructions
3. Re-import images if the data disk was not preserved
4. Re-activate licence
5. Confirm Compatibility Certified chips and Docker seeds

Always read the release notes for the version you install (example artifacts: `vex-nx-1.0.44.ova`).

## Related

* System requirements
* [Maintenance](/admin-guide/maintenance.md)
* Licence editions and activation


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vex-nx.com/admin-guide/sizing-and-upgrades.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.