Add node/cluster RAM validation to VM functionality #139

New Issue

joshuaboniface · 2021-08-05T00:21:57-04:00

JoshuaBoniface commented

2021-08-05 00:21:57 -04:00

(Migrated from git.bonifacelabs.ca)

While it has not come up in production yet, it would be very beneficial to ensure that a VM does not exceed the node or cluster total max memory during provisioning or modification (e.g. vm memory set or vm modify).

We already have a status check for memory on the cluster (that triggers a cluster-wide warning), and a validation during provisioning that checks for available disk space, so a similar methodology would be ideal but for memory instead. It can run when the API gets a new VM configuration and can fail out (with optional override flag) if the configuration is invalid.

While it has not come up in production yet, it would be very beneficial to ensure that a VM does not exceed the node or cluster total max memory during provisioning or modification (e.g. `vm memory set` or `vm modify`). We already have a status check for memory on the cluster (that triggers a cluster-wide warning), and a validation during provisioning that checks for available disk space, so a similar methodology would be ideal but for memory instead. It can run when the API gets a new VM configuration and can fail out (with optional override flag) if the configuration is invalid.

JoshuaBoniface commented

2021-09-13 01:55:29 -04:00

(Migrated from git.bonifacelabs.ca)

closed via commit 6e0d0e264e

closed via commit 6e0d0e264e10fd1e853d25b512567485f5dabd34

JoshuaBoniface commented

2021-10-03 22:47:55 -04:00

(Migrated from git.bonifacelabs.ca)

mentioned in commit 6e0d0e264e

mentioned in commit 6e0d0e264e10fd1e853d25b512567485f5dabd34

joshuaboniface referenced this issue from a commit

2023-09-01 15:58:46 -04:00