Open Zarquan opened 5 months ago
Experiment with this in CIRASA-planner
I was going to suggest this: size: 1024
for storage is a bit vague (follow the same rules as k8s? I admit sometimes all the different units/ways k8s allows you to specify things makes it hard to check how it's going to be interpreted, so maybe be more restrictive)?
Systems like Kubernetes allow the user to specify some numeric values as a string value with units. e.g. 2GiB, 200m cores etc
We should follow this for many of our basic resource min and max values.
An extension of this could add a regex in the schema definition for each field.