You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b66e15b
Browse filesBrowse the repository at this point in the historyBrowse files
Update the resource-management guide to describe the new
`<series>.<size>` instance-type preset scheme:
- five series (t1, c1, s1, u1, m1) covering CPU:memory ratios from
1:0.5 to 1:8
- eight sizes (nano through 4xlarge) per series
- explicit callout that legacy `medium` (1 CPU / 1Gi) and new
`*.medium` (2 CPU) names overlap but resources do not
- 1:1 legacy-to-instance-type mapping table for the seven deprecated
flat names that remain accepted as aliases
- mention of the API-server deprecation warning and the platform
upgrade migration that rewrites stored values
Also correct CPU values in the prior table that disagreed with the
actual cozy-lib library (nano was listed as 100m / 128Mi but
cozy-lib has always rendered 250m / 128Mi for nano, and so on for
every row); pin the table on the values cozy-lib actually returns.
Track corresponding code change at cozystack/cozystack#2607.
Assisted-By: Claude <[email protected]>
Signed-off-by: Aleksei Sviridkin <[email protected]>
Presets follow a cloud-style `<series>.<size>` naming convention. Five series cover the full CPU-to-memory ratio range, and each series ships eight sizes (`nano` through `4xlarge`):
Memory follows from the series ratio. For example, `t1.small` is 1 CPU / 512Mi, `c1.small` is 1 CPU / 1Gi, `s1.small` is 1 CPU / 2Gi, `u1.small` is 1 CPU / 4Gi, and `m1.small` is 1 CPU / 8Gi. Ephemeral storage is 2Gi for every preset.
49
63
50
64
In CPU, the `m` unit is 1/1000th of a full CPU time.
51
65
66
+
#### Watch out: legacy and instance-type `medium` differ
67
+
68
+
The legacy flat preset `medium` had **1 CPU / 1Gi**. The new `*.medium` sizes have **2 CPU**. The names overlap but the resources do not. The legacy table below stays correct — `medium → c1.small (1 CPU / 1Gi)` — but if you read the instance-type sizing matrix first and pick `c1.medium` "to keep things the same as before", you will double your CPU. When in doubt, consult the legacy-to-instance-type mapping below.
69
+
70
+
#### Legacy flat preset names (deprecated)
71
+
72
+
The seven short names that existed before the instance-type rename remain accepted as backward-compatibility aliases. They render exactly the CPU and memory they did before — so an existing HelmRelease or app CR continues to behave identically. The 1:1 mapping is:
73
+
74
+
| Legacy | CPU | Memory | Instance-type equivalent |
Legacy names are scheduled for removal in a future Cozystack release; new manifests should use the instance-type form. The Cozystack API server logs a deprecation warning whenever an app CR carries a legacy value, naming the suggested replacement.
85
+
86
+
A platform upgrade runs a one-shot migration (Migration 39) that walks every `HelmRelease.spec.values` and every app CR under `apps.cozystack.io/v1alpha1` and rewrites legacy values to their instance-type equivalents in place. The conversion is idempotent, best-effort, and never changes CPU or memory.
87
+
52
88
Cozystack presets are defined in an internal library
[`cozy-lib`](https://github.com/cozystack/cozystack/tree/main/packages/library/cozy-lib). The canonical reference, including the full size matrix and migration table, lives in [`docs/operations/resource-presets.md`](https://github.com/cozystack/cozystack/blob/main/docs/operations/resource-presets.md).
0 commit comments