Plans and sizing (docs)

Actions

15 actions, callable from the panel, the command palette and the API as POST /api/v1/a/<id>. Internal actions used between modules are not listed.

Action	What it does	Risk	Preview
`sizing.profile.detect`	Detect hardware and the recommended profile	low	No dry run
`sizing.profile.get`	Install profile, tuning values and pending re-tune (read)	low	No dry run
`sizing.profile.apply`	Choose a profile or re-tune	critical
`sizing.retune.check`	Check whether the hardware changed	low	No dry run
`sizing.capacity.get`	Capacity planner (read)	low	No dry run
`sizing.capacity.export`	Export the capacity planner (read)	low	No dry run
`sizing.placement.suggest`	Node with the most headroom for a plan (read)	low	No dry run
`sizing.preset.generate`	Generate Starter, Business, Agency, Reseller and Dedicated plans	medium
`sizing.plan.update`	Edit a plan with an apply mode	high
`sizing.plan.delete`	Delete a plan, migrating its accounts first	high
`sizing.plan.export`	Export plans as JSON (read)	low	No dry run
`sizing.plan.import`	Import plans from JSON	medium
`sizing.oversell.get`	Overselling policies (read)	low	No dry run
`sizing.oversell.set`	Set an overselling policy	high
`sizing.keys.check`	New limit keys	low	No dry run

Permissions and limits

Permissions

sizing.view See hardware, profile and capacity
sizing.profile.manage Choose a profile and re-tune servers
sizing.plans.view See plan tools and overselling policy
sizing.plans.manage Apply, delete, import and generate plans
sizing.oversell.manage Set overselling policy

Plan limits

sizing.disk_mb Disk quota (home, mail and databases)
sizing.ram_mb Memory of an account's processes
sizing.cpu_percent CPU of an account (100 = one core)

Engineering notes

Generated from modules/sizing/docs.md at build d90e9e2. These are the notes the engineers keep next to the code: precise, technical, and honest about what is not done yet.