Feature(s) request: Display resource usage, allow automatic migration

DerDanilo

Well-Known Member
Jan 21, 2017
400
67
48
It would be nice if one could see the used/assigned resources per server and cluster. This information is already available in PVE but spread over each VM. One has to do calculation writing things down, when this information could be shown in PVE itself with available information.

- Showing the used/assigned resources for all VMs on a node(and cluster) would be very useful, including a percentage of used resources based on a configured (aimed) logical limit.
- It would be especially usefull if one could configure a overcommitment value for CPU, RAM and Storage per Node.
- This feature could also detect if the average system load is to high (based on available cores etc.) and allow showing a warning based on preconfigured warning and limits.
- While at it, this feature could also be a starting point to allow automatic migration of VMs to nodes with free resources.

This idea is not aimed at replacing proper system monitoring. It's idea is based on being able to see the cluster resources usage and be able to better plan for adding new hardware. Additionally it could also allow using PVE to automatically migrate VMs if required, as listed above.

Maybe this could also allow implementing the maintanance mode for PVE nodes, to migrate all VMs to other nodes before shutdown. This is a very useful feature, which currently has to be done manually via API oder WebUI.

I know that it is not that easy to peroperly get the information for storage usage vs assignment (overcomittment), so this could be added at a later point.
Automatic migration in a timely manner is anyways just possible with the use of shared storage, hence this is not very important.


@tom @martin Do you think that this is something that we can see soon(ish)?
@Community What do you think about this idea?

Thanks in advance! :)
 

Dominic

Proxmox Staff Member
Staff member
Mar 18, 2019
1,156
129
68
Sounds useful to me. It would be great if you could open a feature request at bugzilla.proxmox.com for this! There it certainly does become forgotten.
Ideally this would be separated into multiple requests. Bugs and feature request can be defined to depend on (or be blocked by) others.
 

grefabu

Member
May 23, 2018
111
6
23
47
Hi Danilo,

one additional point: preserver start an VM when the limit will reached on the specified machine. So if an other process gain a sum of RAM, it should preverd to start when there isn't enough free/reach a critical limit. This could be helpful in case of using Ceph and other RAM intensive things,...

Bye

Gregor
 

DerDanilo

Well-Known Member
Jan 21, 2017
400
67
48
Hi Danilo,

one additional point: preserver start an VM when the limit will reached on the specified machine. So if an other process gain a sum of RAM, it should preverd to start when there isn't enough free/reach a critical limit. This could be helpful in case of using Ceph and other RAM intensive things,...

Bye

Gregor
Please add this to the bug if you think it's required.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!