parallelvirtualcluster/pvc
1
0
Fork 0
Code Issues 11 Pull Requests Projects Releases 113 Wiki Activity

Add cluster "balance" action #10

New Issue
Closed
opened 2018-07-17 14:58:32 -04:00 by JoshuaBoniface · 6 comments
JoshuaBoniface commented 2018-07-17 14:58:32 -04:00 (Migrated from git.bonifacelabs.ca)
Copy Link

As suggested by @MichalKozanecki, add a PVC client function to "balance" a cluster based on a specific category.

Some obvious categories could be:

a) RAM allocation
b) vCPU allocation

The balance would then perform permanent moves to distribute VMs as best as it can across all nodes.

There are a couple caveats to this though that I'd have to work in logic for:

a) Keeping same-group VMs on different nodes (e.g. don't "balance" ldap1 and ldap2 onto the same HV even if that makes "sense" RAM/vCPU-wise).
b) Keeping potential-CPU-usage somewhat balanced (for spiky VMs like embyX).

As suggested by @MichalKozanecki, add a PVC client function to "balance" a cluster based on a specific category. Some obvious categories could be: a) RAM allocation b) vCPU allocation The balance would then perform permanent moves to distribute VMs as best as it can across all nodes. There are a couple caveats to this though that I'd have to work in logic for: a) Keeping same-group VMs on different nodes (e.g. don't "balance" `ldap1` and `ldap2` onto the same HV even if that makes "sense" RAM/vCPU-wise). b) Keeping potential-CPU-usage somewhat balanced (for spiky VMs like `embyX`).
JoshuaBoniface commented 2018-07-20 02:22:03 -04:00 (Migrated from git.bonifacelabs.ca)
Copy Link

Can use the four options from #11: mem, load, vcpus, vms

Just assume every node starts with nothing and go from there.

Can use the four options from #11: mem, load, vcpus, vms Just assume every node starts with nothing and go from there.
JoshuaBoniface commented 2018-10-16 12:33:54 -04:00 (Migrated from git.bonifacelabs.ca)
Copy Link

Will definitely be adding this feature with logic for (a) but not (b) (since we can never really know how spiky a VM is).

Will definitely be adding this feature with logic for (a) but not (b) (since we can never really know how spiky a VM is).
JoshuaBoniface commented 2018-10-23 00:48:26 -04:00 (Migrated from git.bonifacelabs.ca)
Copy Link

changed title from {-[ENHANCEMENT] -}Add cluster "balance" action to Add cluster "balance" action

changed title from **{-[ENHANCEMENT] -}Add cluster "balance" action** to **Add cluster "balance" action**
JoshuaBoniface commented 2018-10-23 00:48:44 -04:00 (Migrated from git.bonifacelabs.ca)
Copy Link

added ~113 ~114 labels

added ~113 ~114 labels
JoshuaBoniface commented 2019-10-24 16:37:04 -04:00 (Migrated from git.bonifacelabs.ca)
Copy Link

I'm closing this one out. With the way PVC is developing, I don't think this feature is reasonable. This is something an administrator would have to evaluate based on complete data and then perform as required.

I'm closing this one out. With the way PVC is developing, I don't think this feature is reasonable. This is something an administrator would have to evaluate based on complete data and then perform as required.
JoshuaBoniface commented 2019-10-24 16:37:04 -04:00 (Migrated from git.bonifacelabs.ca)
Copy Link

closed

closed
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
API
blocked
Issue blocked by another issue
bug
CLI
Client
Issues abut the client frontends
Daemon
Issues abut the node daemon
debt
Technical debt that should be investigated or cleaned up
documentation
feature
improvement
No Label
Client
feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: parallelvirtualcluster/pvc#10
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?