Ensure "VM" node memory counts include stopped VMs #105

Closed
opened 2020-10-12 17:47:05 -04:00 by JoshuaBoniface · 5 comments
JoshuaBoniface commented 2020-10-12 17:47:05 -04:00 (Migrated from git.bonifacelabs.ca)

As-is this only includes started/running VMs. Extend it to stopped, disabled, etc. VMs.

As-is this only includes started/running VMs. Extend it to stopped, disabled, etc. VMs.
JoshuaBoniface commented 2020-10-12 17:47:05 -04:00 (Migrated from git.bonifacelabs.ca)

changed milestone to %5

changed milestone to %5
JoshuaBoniface commented 2020-10-12 17:48:31 -04:00 (Migrated from git.bonifacelabs.ca)

mentioned in issue #104

mentioned in issue #104
JoshuaBoniface commented 2020-10-18 14:15:18 -04:00 (Migrated from git.bonifacelabs.ca)

Implemented this in a slightly nicer way by adding an additional "provisioned" memory field to the node info, in addition to the existing "allocated" memory field. The former tracks both running and non-running VMs, while the latter continues to count only running VMs.

Implemented this in a slightly nicer way by adding an additional "provisioned" memory field to the node info, in addition to the existing "allocated" memory field. The former tracks both running and non-running VMs, while the latter continues to count only running VMs.
JoshuaBoniface commented 2020-10-18 14:15:19 -04:00 (Migrated from git.bonifacelabs.ca)

closed

closed
JoshuaBoniface commented 2020-10-18 14:20:17 -04:00 (Migrated from git.bonifacelabs.ca)

mentioned in issue #106

mentioned in issue #106
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: parallelvirtualcluster/pvc#105
No description provided.