Backlog #2646

VMs, CPU and MEMORY of STOPPED VMs are not deduced from users monitoring

Added by EOLE Team over 7 years ago. Updated over 7 years ago.

Status:PendingStart date:01/16/2014
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:-

Description

Hello,

Trying to look at “Who is taking all that resources?” of our little cluster, I saw the report per user of VMs/CPU and MEMORY:

oneadmin@nebula:~$ oneuser list
  ID NAME            GROUP      AUTH           VMS            MEMORY         CPU
   0 oneadmin        oneadmin   core             -                 -           -
   1 serveradmin     oneadmin   server_c   0 /   0      0M /      0M   0.0 / 0.0
   2 user1           users      ldap       7 /   0    5.5G /      0M   0.7 / 0.0
[...]
<pre>

The problem is that @user1@ has only 3 *@RUNNING@* VMs, with 512MB memory each, other are in *@STOPPED@* state.

I think this report could make the difference between VMs with allocated resources and VMs without.

Maybe something like:
<pre>
oneadmin@nebula:~$ oneuser list
  ID NAME            GROUP      AUTH               VMS                   MEMORY         CPU
   0 oneadmin        oneadmin   core                 -                        -                 -
   1 serveradmin     oneadmin   server_c   0     /   0      0M        /      0M   0.0       / 0.0
   2 user1           users      ldap       3 (7) /   0    1.5G (5.5G) /      0M   0.2 (0.7) / 0.0
[...]
<pre>

Regards.

History

#1 Updated by Carlos Martín over 7 years ago

  • Category set to Core & System

It makes sense, maybe a VM in stopped or undeployed states should not be accounted for the VM quotas (nº of vms, cpu, mem).

#2 Updated by Ruben S. Montero over 7 years ago

  • Tracker changed from Request to Backlog

Also available in: Atom PDF