cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sudha Ponnaganti (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-1640) overcommited memory is not getting displayed at zone level and used % is based on actual memory
Date Tue, 07 May 2013 10:33:16 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sudha Ponnaganti updated CLOUDSTACK-1640:
-----------------------------------------

    Fix Version/s: 4.2.0
    
>  overcommited memory is not getting displayed at zone level and used % is based on actual
memory
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1640
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1640
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            Assignee: Bharat Kumar
>             Fix For: 4.2.0
>
>         Attachments: screenshot-1.jpg
>
>
> Dashboard display overcommited memory at cluster and pod level with % of utilization
based on overcommited memory.At zone level actual memory is getting displayed with % based
on actual memory
> DB
> --------
> mysql> select * from cluster_details where cluster_id=1;
> +----+------------+-----------------------+-------+
> | id | cluster_id | name                  | value |
> +----+------------+-----------------------+-------+
> |  1 |          1 | cpuOvercommitRatio    | 2.0   |
> |  2 |          1 | memoryOvercommitRatio | 2.0   |
> +----+------------+-----------------------+-------+
> mysql> select * from op_host_capacity where host_id=1\G;
> *************************** 1. row ***************************
>                id: 12
>           host_id: 1
>    data_center_id: 1
>            pod_id: 1
>        cluster_id: 1
>     used_capacity: 29393682432
> reserved_capacity: 0
>    total_capacity: 16190157312
>     capacity_type: 0
>    capacity_state: Enabled
>       update_time: 2013-03-12 07:10:50
>           created: 2013-03-11 07:23:17
> *************************** 2. row ***************************
>                id: 13
>           host_id: 1
>    data_center_id: 1
>            pod_id: 1
>        cluster_id: 1
>     used_capacity: 4400
> reserved_capacity: 0
>    total_capacity: 9576
>     capacity_type: 1
>    capacity_state: Enabled
>       update_time: 2013-03-12 07:10:50
>           created: 2013-03-11 07:23:17
> 2 rows in set (0.00 sec)
> ERROR:
> No query specified
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message